Originally Posted by meanmod MEANcommands.txt
Bot management commands: (Admins only)
-----------------------------------------------------------------
m_botmode < option >
Options:
botvshuman
botvsbot
humanvshuman
botswhenoneplayer
botswhenxplayers <maxplayers>
botsfillserver
botvshuman : Bot vs human play is activated and enforced.
botvsbot: Allows bots to play against bots. Humans can join any team.
NOTE: botvshuman and botvsbot use the command settings from m_autobalancebots
to fill the server with bots and keep the bot to human ratio balanced.
m_autobalancebots on <minbots> <maxbots> <ratio>
Where the server is filled with <minbots> to start with.
For each human player that joins the server, bots will be added
according to the value specified for <ratio>.
Example,
if <ratio> is 0, no new bots will be added when a human joins
if <ratio> is 1, then 1 new bot will be added for each human player that joins
if <ratio> is 2, then 2 new bots will be added for every human player
humanvshuman: Human only play is enabled. All bots are
automatically removed from server and will never rejoin unless
manually added by the ServerOp or Admin.
botswhenxplayers <xplayers>
Bots will be added to the game based on the <maxbots> setting
specified with the m_autobalancebots command. When more than "x"
human players join the server, as specified by <xplayers>, all
the bots will be kicked out leaving only human players. When no
human players are in game, the server will be filled with
<minbots>
Example:
minbots = 5
maxbots = 8
maxplayers = 4
Example series:
0 humans on server, <minbots> = 5 bots on server
1 human joins, <maxplayers> not exceeded, <maxbots> = 8 bots on server
2 humans join, <maxplayers> not exceeded, <maxbots> = 8 bots on server
3 humans join, <maxplayers> not exceeded, <maxbots> = 8 bots on server
4 humans join, <maxplayers> not exceeded, <maxbots> = 8 bots on server
5 humans join, <maxplayers> exceeded, 0 bots on server
6 humans join, <maxplayers> exceeded, 0 bots on server
botsfillserver: The server is filled with bots up to <maxbots>.
As human players join, the bots will reduce by the same number
of humans that are present until no more bots are present. When
the server has no human players, the server is filled with
<minbots>.
Example:
minbots = 5
maxbots = 8
Example series:
0 humans on server, <minbots> = 5 bots on server
1 human joins, <maxbots> - 1 = 7 bots on server
2 humans join, <maxbots> - 2 = 6 bots on server
3 humans join, <maxbots> - 3 = 5 bots on server
4 humans join, <maxbots> - 4 = 4 bots on server
5 humans join, <maxbots> - 5 = 3 bots on server
6 humans join, <maxbots> - 6 = 2 bots on server
7 humans join, <maxbots> - 7 = 1 bots on server
8 humans join, <maxbots> - 8 = 0 bots on server
9 humans join, <maxbots> - 9 = 0 bots on server
NOTE: Uses m_autobalancebots <maxbots> value to fill server with
bots, <minbots> is used only when there are no humans in the game.
Bot team enforcement is turned off by default and bots will join
both teams. In addtion mp_autobalance will be turned on by default.
Use command "m_switchbotteam" to limit bots to one team only - if
you specify a particular team mp_autobalance will be turned off.
default minimum access level: admin2
m_enforcebotteam < on | off >
Any human player found on the designated bot team will get blown
up automatically at start of each round. Active only when bots
are in the game.
Default Setting: off
default minimum access level: admin2
m_enforcehumanteam [on [ct|te|any] | off]
When set to "on", humans will be forced to reside on a specific team.
If the team is not specified, "any" team will be assumed. If any team
is in effect AND enforcement is "on", the server will decide what team
humans must reside on by choosing the team with the most humans on it.
When all humans leave the game, the human team is set back to "any".
To fix the human team to a specific team, specify "ct" or "te" as the
team. This will force the server to always choose a specific team. When
a team is specified, the team will not be reset to "any" after all
humans leave the game.
The enforcement is active ONLY when there are bots in the game,
otherwise it will have no effect.
Use this command to force humans onto a specific team, while allowing
bots to exist on both teams.
m_allowonbotteam <userid> [ yes | no ]
allows player to join bot team when m_enforcebotteam is on.
default minimum access level: clan member
The below commands work only if bots support server side commands.
m_autobalancebots < on | off > [ < minbots > < maxbots > < ratio > ]
bots will auto balance to keep teams even with a ratio of bots
to humans. You can specify a minimum and maximum number of bots
allowed and the ratio. The default is minbots= 4, maxbots= 8,
ratio= 1.75 bots for every human player. When there are no humans
in the game, minbots will always be present.
default minimum access level: admin2
m_autobalancedisplay < on | off >
CVAR Turns on or off the display of autobalancing information
to the server console.
m_switchbotteam < te | ct | any >
switches the bot team to the team specified. leave blank to
toggle the bot team from the current team to the opposing team.
specify "any" to allow bots on any team.
default minimum access level: clan member
m_addbot < number_of_bots > [ ct | te ]
adds < number_of_bots > to the specified team. with no aurguments,
will add 1 bot to the designated bot team, or if there is no
designated bot team, then to a randomly assigned team.
default minimum access level: admin2
NOTE: m_addbot will allow reverse order of arguments,
for example these entries are all valid:
m_addbot te
m_addbot ct
m_addbot 2 te
m_addbot ct 6
m_addbots < number_of_bots > [ ct | te ]
Works exactly the same as m_addbot. This command was added
because it was natural for many people to type this version
of the command in place of m_addbot.
m_autokillbots [on|off]
When set to "on" the bots will be auto killed to force a round end.
The auto kill is triggered as soon as all human players have died,
but there remain one or more live bots on each team.
m_killbots < all | te | ct >
kills all bots on specified team.
default minimum access level: admin2
m_kickbot < number_of_bots > [ ct | te ]
kicks < number_of_bots > from the specified team. No arguments
will kick 1 bot from the server. If a bot team is specified, only
bots from that team will be kicked.
default minimum access level: admin2
m_kickbots [ te | ct ]
kicks all bots on specified team. No arguments will kick all
bots from server no matter what team they are one.
default minimum access level: admin2
m_botskill <lowest | low | medium | high | highest | insane | random> | <0 - 100>
sets the bot skill when bots are added to the server. You can specify
a range from 0 to 100 where 0 is lowest skill and 100 is best skill.
Alternatively, specify "lowest" through "highest" for preset ranges.
Note: The skill value is automatically translated and scaled to
match the equivalent skill for whatever bot is loaded.
default minimum access level: clan member
lowest = bots that almost never shoot at you
low = bots that will occasionally shoot at you
medium = bots are pretty good, but slow on the trigger
high = bots are very good
highest = very skilled bots that are a bitch to beat
insane = for experts only! The bots will almost never miss.
Note: The "insane" setting is actually a bot cheat. It disables the
inaccuracy from weapon recoil and movements (such as running while
firing). This allows for normally unattainable accuracy. All other
skill settings do not use cheats.
m_botskilldelay <seconds>
CVAR to adjust skill reaction times. Larger values make the
bots easier to kill because their reaction times will be slower.
No effect when skill is set to "highest" or "insane".
Range: 0.0 to 5.0
Default: 0.25
m_autoskillswitch [on|off] | [ probability ]
Turns on/off auto bot skill switching on map change. A probability
between 0 and 100% can be specified. A probability of 100% will
ensure the skill is changed to a randomly selected level on each
map change. As new bots are spawned they will be assigned the new
skill level.
Range: 0 to 100
Default: 20
default minimum access level: server op
m_autosteamswitch [on|off] | [ probability ]
Turns on/off auto bot team switching on map change. A probability
between 0 and 100% can be specified. A probability of 100% will
ensure the bot team is switched on each map change. Default is
ON 20%
default minimum access level: server op
m_kickdupbots [ on|off ]
Command to kick from server bots with duplicate names. Duplicate
names are preceeded with "(n)" when n is a one or two digit
number, anything else will not be considered as a duplicate name.
Default: off
WARNING: Setting this to "on" with POD bots will result in
problems with your game whenever a duplicate bot is kicked.
To reduce duplicate POD bot names, it is recommended that you
add at least 150 names to your botnames.txt file.
|