Post by Isaak on Jul 7, 2010 12:20:11 GMT -5
Once upon a time, long long ago Valve software released bots for Team Fortress 2.
For an entirely insignificant span of time there was much rejoicing. This was even more short lived than one would initially assume for the common man could not afford to purchase a bot of his very own.
NO LONGER.
Now you to can own your own fleet of bots and have them dance for your amusement, for a large server or just in your own little LAN server.
(This information is updated as of 7-7-2010)
(Changes will be made as updates occur.)
The Commands
====================
nav_generate
This command will generate the navigation code for the bots.
This command is still useless on game types that bots do not understand like Payload or Capture the Flag.
All official maps that bots work on currently have a nav mesh, do not generate a new one.
sv_cheats must be set to "1" for this command to function.
tf_bot_difficulty
Use this command to set bot difficulty while playing.
Set to "0" for Easy.
Set to "1" for Normal.
Set to "2" for Hard.
tf_bot_prefix_name_with_difficulty
Any bot added after this command is set to "1" have their difficulty setting placed inside their name.
tf_bot_keep_class_after_death
Setting this command to "1" will prevent all bots from changing their class.
tf_bot_quota #
The number used in this command will effect how many bots are present in the server depending upon the tf_bot_quota_mode setting.
tf_bot_quota_mode
Set this to "normal" for tf_bot_quota to control total number of bots in the server.
Set this to "match" for tf_bot_quota to control total number of bots per human player in the server.
Set this to "fill" for tf_bot_quota to control the minimum number of player slots for bots to keep full.
tf_bot_join_after_player
If this command is set to "1" then bots will not be allowed to spawn or exist in the server until at least one human player joins.
tf_bot_auto_vacate
If this command is set to "1" then bots will automatically leave to allow human players to join.
tf_bot_add
Use this command, in conjunction with multiple parameters, to add bots to your game. If you do not choose a parameter it will use a default value.
You can set their class: scout, soldier, pyro, demoman, heavyweapons, engineer, medic, sniper, spy (Defaults to random.)
You can set their difficulty: easy, normal, hard (Defaults to tf_bot_difficulty.)
You can set their team: red, blue (Defaults to balanced teams.)
You can set how many to add with your chosen parameters above. (Default to one bot.)
These parameters do not conflict with one another and do not need to be in any specific order.
Examples:
tf_bot_add 6 scout = Three red Scouts and three blue Scouts with tf_bot_difficulty difficulty.
tf_bot_add hard heavyweapons blue = One Heavy on blue team with hard difficulty setting.
tf_bot_add 8 normal = Four red bots and four blue bots of normal difficulty and random classes.
tf_bot_kick all
Removes all bots from the server.
I find it is easier to quickly remove all bots and then add new ones from scratch than it is to try and target the removal of a single bot and then change other parameters to prevent another bot from auto-joining. Useful for bot team-balance issues.
For more selective bot removal the standard status and kick commands do work with bots, but it is unwieldy and time consuming.
Many standard bot names also contain unusual characters, making it even more difficult to remove by name.
Lastly, when adding a bot you also are adding a bot slot, kicking a bot will usually result in another bot instantly taking its place.
The main reason why tf_bot_kick all is so useful is because it removes the bots and their player slots.
mp_humans_must_join_team
Set this command to red, blue, or any to force players onto a specific team. Useful for humans versus bot matches.
mp_highlander
When this command is set to "1" then there will only be allowed up to one of every class. This command works with bots to help keep them under more control to help prevent bot teams with four Heavies or five Engineers, but you will also be limited to one of each class yourself.
NOTE: Sometimes the bots accidentally ignore mp_highlander, this is caused when, for example, a bot has just died and another bot spawns as the same class. This is easily solved by just murdering the offenders.
That is all for now, please enjoy and remember that if given the chance a bot would kill you any everyone you love, so keep them under your thumb with this helpful guide.
Isaak
For an entirely insignificant span of time there was much rejoicing. This was even more short lived than one would initially assume for the common man could not afford to purchase a bot of his very own.
NO LONGER.
Now you to can own your own fleet of bots and have them dance for your amusement, for a large server or just in your own little LAN server.
(This information is updated as of 7-7-2010)
(Changes will be made as updates occur.)
The Commands
====================
nav_generate
This command will generate the navigation code for the bots.
This command is still useless on game types that bots do not understand like Payload or Capture the Flag.
All official maps that bots work on currently have a nav mesh, do not generate a new one.
sv_cheats must be set to "1" for this command to function.
tf_bot_difficulty
Use this command to set bot difficulty while playing.
Set to "0" for Easy.
Set to "1" for Normal.
Set to "2" for Hard.
tf_bot_prefix_name_with_difficulty
Any bot added after this command is set to "1" have their difficulty setting placed inside their name.
tf_bot_keep_class_after_death
Setting this command to "1" will prevent all bots from changing their class.
tf_bot_quota #
The number used in this command will effect how many bots are present in the server depending upon the tf_bot_quota_mode setting.
tf_bot_quota_mode
Set this to "normal" for tf_bot_quota to control total number of bots in the server.
Set this to "match" for tf_bot_quota to control total number of bots per human player in the server.
Set this to "fill" for tf_bot_quota to control the minimum number of player slots for bots to keep full.
tf_bot_join_after_player
If this command is set to "1" then bots will not be allowed to spawn or exist in the server until at least one human player joins.
tf_bot_auto_vacate
If this command is set to "1" then bots will automatically leave to allow human players to join.
tf_bot_add
Use this command, in conjunction with multiple parameters, to add bots to your game. If you do not choose a parameter it will use a default value.
You can set their class: scout, soldier, pyro, demoman, heavyweapons, engineer, medic, sniper, spy (Defaults to random.)
You can set their difficulty: easy, normal, hard (Defaults to tf_bot_difficulty.)
You can set their team: red, blue (Defaults to balanced teams.)
You can set how many to add with your chosen parameters above. (Default to one bot.)
These parameters do not conflict with one another and do not need to be in any specific order.
Examples:
tf_bot_add 6 scout = Three red Scouts and three blue Scouts with tf_bot_difficulty difficulty.
tf_bot_add hard heavyweapons blue = One Heavy on blue team with hard difficulty setting.
tf_bot_add 8 normal = Four red bots and four blue bots of normal difficulty and random classes.
tf_bot_kick all
Removes all bots from the server.
I find it is easier to quickly remove all bots and then add new ones from scratch than it is to try and target the removal of a single bot and then change other parameters to prevent another bot from auto-joining. Useful for bot team-balance issues.
For more selective bot removal the standard status and kick commands do work with bots, but it is unwieldy and time consuming.
Many standard bot names also contain unusual characters, making it even more difficult to remove by name.
Lastly, when adding a bot you also are adding a bot slot, kicking a bot will usually result in another bot instantly taking its place.
The main reason why tf_bot_kick all is so useful is because it removes the bots and their player slots.
mp_humans_must_join_team
Set this command to red, blue, or any to force players onto a specific team. Useful for humans versus bot matches.
mp_highlander
When this command is set to "1" then there will only be allowed up to one of every class. This command works with bots to help keep them under more control to help prevent bot teams with four Heavies or five Engineers, but you will also be limited to one of each class yourself.
NOTE: Sometimes the bots accidentally ignore mp_highlander, this is caused when, for example, a bot has just died and another bot spawns as the same class. This is easily solved by just murdering the offenders.
That is all for now, please enjoy and remember that if given the chance a bot would kill you any everyone you love, so keep them under your thumb with this helpful guide.
Isaak
