amx.cfg - The main config
The amx.cfg file in your addons/amx/config
folder is where most of the settings are made for AMX. This file is
executed every map change. So if you make a change to this file, it's
not necessary to restart the server unless the change is needed
immediately.
All the settings in this file have comments
describing what that setting does, and the different values that can be
used. Below you will find additional help for the amx.cfg file.
amx_mode
Valid Settings:
Example:
Description:
0, 1 or 2
amx_mode "1"
0 Disables admin access all together. AMX runs, but no one will have admin access even if they are set up to.
1 is normal operation for AMX.
2 will kick anyone not in the
users.ini file. This is in effect the same as a private server.
amx_default_access
Valid Settings:
Example:
Description:
a through u & z (can be more than one letter)
amx_default_access "z"
This
is what access any player would have when joining your server. Be
careful with this. If you wanted to allow voting, you would assign this
value the letter j.
amx_password_field
Valid Settings:
Example:
Description:
Anything.
amx_password_field "_pw"
This
password field needs to match on the server and the client. It can be
what ever you want, but it must match. If you use the default shown
above, then the clients should have
setinfo _pw "password" set in their userconfig.cfg file in their
mod folder. For more info on how to set a client up as an admin using password go
here.
amx_correct_usersfile
Valid Settings:
Example:
Description:
0 or 1
amx_correct_usersfile "1"
0 is for normal operation. 1 will attempt to correct easily identifiable errors in the users.ini file.
amx_realadmin_flags
Valid Settings:
Example:
Description:
"abcdefghijklmnopqrstuvwy"
amx_realadmin_flags "cdefghijlmnopqrstuvw"
Admin
flags that represent a real admin. To be considered as a real admin, he
must have a least one of the flags. It's not advised to change them,
except if you want to modify which admins can see the show activity
messages or to change some access in game (depends on the plugin
features).
amx_show_activity
Valid Settings:
Example:
Description:
0, 1, 2, 3, 4 or 5
amx_show_activity "2"
This will cause AMX to make public some AMX functions as they happen in game (amx_show_activity "1"), and also the admin who is running the command if desired ("2"). This may be helpful in keeping admins accountable, but it also reveals who an admin is. amx_show_activity "3" shows actions with names to admins, and without names to normal users. amx_show_activty "4" and "5" show actions without names for the first, and with for the second, but only to admins.
amx_show_clcmds
Valid Settings:
Example:
Description:
0, 1 or 2
amx_show_clcmds "1"
Show client commands
"0" : disabled (don't show any client command)
"1" : show all client commands except for protected commands
"2" : show all client commands
This
cvar enables the possibility to see each client command who are
executed by an admin, which has the acess to the amx_clcmd command,
but this feature is available from admin activity messages, so only
if amx_show_activity is not set to 0. If amx_show_clcmds is set to
0, client commands will be hidden in the admin activity messages.
amx_chat_anonymous
Valid Settings:
Example:
Description:
0, 1 or 2
amx_chat_anonymous "2"
Anonymous chat commands
"0" : disabled
"1" : enabled, but only if amx_show_activity is not set to 2
"2" : always enabled
This
will make totaly valid the anonymous chat commands, however, these chat
commands with both "y" to the end of everyone won't be anomymous,
like others.
amx_scrollmsg
Valid Settings:
Example:
Description:
Any message.
amx_scrollmsg "Welcome! You're on %hostname%" 600
This
message appears in the lower center of the screen and scrolls by at a
specified interval. The number at the end is the interval in seconds,
so 600 seconds would make the message appear every 10 minutes. Make
sure to use quotes around your message. If you use %hostname%
it will be replaced with your server's hostname. However if you don't
like the default scrollmsg color you may add just after the time any color
you want in the RGB format (like in the below amx_imessage commands) or
use a "?" to define a random color.
amx_imessage
Valid Settings:
Example:
Description:
Any message.
amx_imessage "Welcome to %hostname%!" "000100255"
This message appears in the center of the screen. The number at the end is the color you want the message to appear in. Use
this web applet to get the numeric value of the RGB color you want to use, either use the "
?" argument to display a random color. Make sure to use quotes around your message.
%hostname% will be replaced with your server's hostname. You can specify several
amx_imessage lines: the messages will cycle.
Also,
you may translate your sentences into the end of the
amx/lang/imessage.txt file, but make sure your default sentences
defined in your
amx.cfg file are in English language and the same
as they have been copy to the
imessage.txt file (to use the
English default
language is adviced to work properly).
amx_freq_imessage
Valid Settings:
Example:
Description:
Length of time in seconds.
amx_freq_imessage "180"
Setting this to 180 would cause the amx_imessage to display every 3 minutes.
amx_flood_time
Valid Settings:
Example:
Description:
Length of time in seconds.
amx_flood_time "0.75"
Setting this to 0.75
means players can't use the say command more than once every 3/4's of a
second. This helps to prevent people from flooding the server with
unwanted chat.
amx_reservation
Valid Settings:
Example:
Description:
0~4
amx_reservation "0"
The value this is set to will control how the reserved slot is handled.
"0" : disables the plugin
"1" : kicks the player with the shortest playing time
"2" : kicks the player with the longest playing time
"3" : kicks the player with the highest ping
"4" : AMX 0.9.9 mode: amx_reservedslots are reserved, nobody is kicked when an admin connects to a full server
amx_reservedslots
Valid Settings:
Example:
Description:
0~maxplayers
amx_reservedslots "0"
Number of slots you want to reserve for your admins (if amx_reservation is set to 4).
amx_hideslots
Valid Settings:
Example:
Description:
0 or 1
amx_hideslots "0"
Hide the reserved slots or not (if amx_reservation is set to 4).
amx_time_display
Valid Settings:
Example:
Description:
See amx.cfg file.
See amx.cfg file.
This
controls the text reminder at the bottom of the screen that tells you
how many minutes are remaining on the current map. The amx.cfg has the
best description for this. Most people will probably leave this its
default setting.
amx_time_voice
Valid Settings:
Example:
Description:
0 or 1
amx_time_voice "0"
When
a player types /thetime or /timeleft as a chat message, the current
time or time left for the map is displayed. This setting will cause a
voice to say what time it is as well when set to 1.
amx_vote_delay
Valid Settings:
Example:
Description:
Length of time in seconds.
amx_vote_delay "10"
This is the time in seconds before another vote is allowed.
amx_vote_time
Valid Settings:
Example:
Description:
Length of time in seconds.
amx_vote_time "10"
Time in seconds a vote will stay up for voting.
amx_vote_answers
Valid Settings:
Example:
Description:
0 or 1
amx_vote_answers "1"
Setting this to 1 causes what people voted to be known to everyone.
amx_votekick_ratio
Valid Settings:
Example:
Description:
0.00 to 1.00
amx_votekick_ratio "0.40"
Vote
ratios work like this: 0.10 = 10%, 0.50 = 50%, 1.00 = 100%. You get the
idea. This is the percentage required for a kick vote to go through.
Consider carefully what you set this to, or the minority of players on
your server will have decision making abilities if you allow voting.
amx_voteban_ratio
Valid Settings:
Example:
Description:
0.00 to 1.00
amx_voteban_ratio "0.40"
Vote
ratios work like this: 0.10 = 10%, 0.50 = 50%, 1.00 = 100%. You get the
idea. This is the percentage required for a ban vote to go through.
Consider carefully what you set this to, or the minority of players on
your server will have decision making abilities if you allow voting.
amx_votemap_ratio
Valid Settings:
Example:
Description:
0.00 to 1.00
amx_votemap_ratio "0.40"
Vote
ratios work like this: 0.10 = 10%, 0.50 = 50%, 1.00 = 100%. You get the
idea. This is the percentage required for a map vote to go through.
Consider carefully what you set this to, or the minority of players on
your server will have decision making abilities if you allow voting.
amx_vote_ratio
Valid Settings:
Example:
Description:
0.00 to 1.00
amx_vote_ratio "0.50"
Vote
ratios work like this: 0.10 = 10%, 0.50 = 50%, 1.00 = 100%. You get the
idea. This is the percentage required for a vote to go through.
Consider carefully what you set this to, or the minority of players on
your server will have decision making abilities if you allow voting.
amx_mapmenu_mapsloc
Valid Settings:
Example:
Description:
0, 1 or 2
amx_mapmenu_mapsloc "0"
Allows you to choose the location of the maps listed on the maps menu. 0 uses the maps.ini. 1 uses the mapcycle.txt. 2 uses the contents of the maps folder.
amx_votemapmenu_mapsloc
Valid Settings:
Example:
Description:
0, 1 or 2
amx_votemapmenu_mapsloc "0"
Allows you to choose the location of the maps listed on the votemap menu. 0 uses the maps.ini. 1 uses the mapcycle.txt. 2 uses the contents of the maps folder.
amx_mapchooser_mapsloc
Valid Settings:
Example:
Description:
0, 1 or 2
amx_mapchooser_mapsloc "0"
Allows you to choose the location of the maps that can be voted on. 0 uses the amx_mapchooser_mapsfile. 1 uses the mapcycle.txt. 2 uses the contents of the maps folder.
amx_mapchooser_mapsfile
Valid Settings:
Example:
Description:
Any file name.
amx_mapchooser_mapsfile "maps.ini"
Allows
you to choose the location of the maps that can be voted on when
amx_mapchooser_mapsloc is set to 0. The file must be in amx/config/
folder.
amx_mapchooser_type
Valid Settings:
Example:
Description:
0, 1 or 2
amx_mapchooser_type "0"
This setting controls how the maps are voted on for the next map. 0 chooses random maps from what amx_mapchooser_mapsloc is set to. 1 chooses maps by nomination. 2 chooses a random map from amx_mapchooser_mapsloc (there is no vote).
amx_nominfromfile
Valid Settings:
Example:
Description:
0 or 1
amx_nominfromfile "0"
This setting controls what maps can be nominated for voting. 0 chooses from the maps folder. 1 uses the setting from amx_mapchooser_mapsloc.
But maps who have been listed into history file have not displayed in the list, and can't be nominated by any player.
amx_maxnominperplayer
Valid Settings:
Example:
Description:
Any number.
amx_maxnominperplayer "1"
This setting controls how many maps each player can nominate.
amx_extendmap_max
Valid Settings:
Example:
Description:
Any number.
amx_extendmap_max "3"
This is the maximum amount of times a map can be extended (if you use mp_timelimit).
amx_extendmap_step
Valid Settings:
Example:
Description:
Length of time in minutes.
amx_extendmap_step "15"
Time in minutes that a mapcycle will be extended if vote to do so succeeds.
amx_extendround_max
Valid Settings:
Example:
Description:
Any number.
amx_extendround_max "3"
This setting controls how many times a map can be extended (if you use mp_maxrounds).
amx_extendround_step
Valid Settings:
Example:
Description:
Any number.
amx_extendround_step "3"
This
setting controls how many rounds a map is extended. If
amx_extendround_max is set to 3, then a map can be extended three
times. Each extension lasts 3 rounds, or whatever amx_extendround_step
is set to.
amx_extendwin_max
Valid Settings:
Example:
Description:
Any number.
amx_extendwin_max "3"
This
method for map extension can be used if the server uses mp_winlimit.
This setting controls how many times the map can be extended in wins.
For example if mp_winlimit is set to 10, an extension vote is called
when the number of wins of a team reaches 8. If people vote to extend
and amx_extendwin_step is set to 3, mp_winlimit is set to 13.
amx_extendwin_step
Valid Settings:
Example:
Description:
Any number.
amx_extendwin_step "3"
This
setting controls how many wins a map is extended. If amx_extendwin_max
is set to 3, then a map can be extended three times. Each extension
lasts 3 wins, or whatever amx_extendwin_step is set to.
amx_manage_plugins
Valid Settings:
Example:
Description:
0 or 1
amx_manage_plugins "0"
Automatically add/remove plugins from AMX's plugins.ini according to the content of the plugins folder.
amx_manage_modules
Valid Settings:
Example:
Description:
0 or 1
amx_manage_modules "0"
Automatically add/remove modules from AMX's modules.ini according to the content of the modules folder.
amx_log_to_hl_logs
Valid Settings:
Example:
Description:
0 or 1
amx_log_to_hl_logs "0"
Automatically
copy the logs generated by the AMX log functions to the Half-Life logs.
Useful to regroup all the logs in the same folder/file.
amx_debug
Valid Settings:
Example:
Description:
0, 1 or 2
amx_debug "0"
Provides extra output on the console and/or AMX log files for debugging problems. 0 = No logging, 1 = Prints to server console, 2 = Prints to server console and the AMX logs.
amx_langdebug
Valid Settings:
Example:
Description:
""
amx_langdebug "fr de pl"
To debug a language put its 2 letter code between quotes. Separate the codes by a space.
For example: amx_langdebug "fr de pl"
If you want to debug a language for a plugin, enable only this plugin in your plugins.ini.
Errors are logged to amx/logs/error_langYearMonthDay.log
"" means disabled
Counter-Strike Specific cvars
amx_bomb_frags
Valid Settings:
Example:
Description:
Any number.
amx_bomb_frags "3"
This allows you to modify the number of frags awarded to a successful bomb plant or defusal.
amx_statsx_duration
Valid Settings:
Example:
Description:
Length of time in seconds.
amx_statsx_duration "12.0"
The amount of seconds that the player stats stay up on the screen after you die.
amx_statsx_freeze
Valid Settings:
Example:
Description:
Length of time in seconds.
amx_statsx_freeze "-2.0"
This
is the amount of time that the stats from the previous round stay up on
the screen. Giving this a -2 value means the stats will disappear 2
seconds before the freezetime ends (ie. whatever the mp_freezetime cvar is set to).
csstats_rank
Valid Settings:
Example:
Description:
0, 1 or 2
csstats_rank "1"
This controls how player ranks are tracked. 0 = playername, 1 = SteamID, 2 = IP address.
csstats_rankbots
Valid Settings:
Example:
Description:
0 or 1
csstats_rankbots "1"
This controls whether or not bots are included in the rankings.
csstats_pause
Valid Settings:
Example:
Description:
0 or 1
csstats_pause "0"
0 = Normal operation, stats being tracked, 1 = Player stats will not be tracked.
csstats_maxsize
Valid Settings:
Example:
Description:
0 to 7000
csstats_maxsize "3500"
Maximum number of players tracked in the stats. Setting this to 0 disables the stat tracking.
csstats_reset
Valid Settings:
Example:
Description:
0 or 1
csstats_reset "1"
Setting this to 1 will force the stats to be reset on the next map change.
Day of Defeat Specific cvars
amx_dodstats_topvalue
Valid Settings:
Example:
Description:
Any number.
amx_dodstats_topvalue "12"
This cvar allows you to change the maximum players value displaying to the top15.
amx_dodstats_duration
Valid Settings:
Example:
Description:
Length of time in seconds.
amx_dodstats_duration "5.0"
The amount of seconds that the player stats stay up on the screen after you die.
dodstats_rank
Valid Settings:
Example:
Description:
0, 1 or 2
dodstats_rank "1"
This controls how player ranks are tracked. 0 = playername, 1 = SteamID, 2 = IP address.
dodstats_rankbots
Valid Settings:
Example:
Description:
0 or 1
dodstats_rankbots "1"
This controls whether or not bots are included in the rankings.
dodstats_pause
Valid Settings:
Example:
Description:
0 or 1
dodstats_pause "0"
0 = Normal operation, stats being tracked, 1 = Player stats will not be tracked.
dodstats_maxsize
Valid Settings:
Example:
Description:
0 to 7000
dodstats_maxsize "3500"
Maximum number of players tracked in the stats. Setting this to 0 disables the stat tracking.
dodstats_reset
Valid Settings:
Example:
Description:
0 or 1
dodstats_reset "1"
Setting this to 1 will force the stats to be reset on the next map change.