Config and console commands

Availiable commands for podbot
Commands in podbot.cfg file

minbotskill (value) - Sets the minimum Skill if Bots are created without specifying the Skill. Correct values are 1-100. Default is 1.

maxbotskill (value) - Sets the maximum Skill if Bots are created without specifying the Skill. Must be bigger than minbotskill of course ! Correct values are minbotskill-100. Default is 100.

min_bots (value) - configure the minimum number of bots that will run on the server. Default is 0.

max_bots (value) - configure the maximum number of bots that will run on the server. Default is 0.

If You don't specify min/max_bots (You will comment them out in Your podbot.cfg) then the function auto/add kick bot (described a bit below) will not work. If You specify them - then they will support a minimum and maximum number of bots running on the server. Bots will be added to the server until the total number of players (bots and humans) reaches the max_bots value. Each time a new player joins the server, a bot will be kicked from the server unless there are only min_bots number of bots currently on the server. After players disconnect from the server, bots will be automatically added back to the server until the total number of players reaches max_bots again. You should make max_bots be AT LEAST one less than the maxplayers value (otherwise no one will be able to join your server). Some more explanation to this function You can find here: bla_bla_link

botchat (on|off) - Turns on/off Botchatting. Bots chat if they killed someone, if the Bomb was planted or if they are dead and bored. Default is on.

NOTE:

BotChat.txt file must be in addons/podbot directory even if Botchat is turned off !

jasonmode (on|off) - Turns on/off Jason Mode ! Meaning Bots don't buy weapons and only use the knife for combat ! Greets to Auxois ! Use this for much fun with e.a. cs_estate or cs_office . Default is off.

wptfolder (folder) - Sets the default Folder for loading/saving Waypoint Files. This folder HAS to be inside the POD-Bot Directory ! Don't put it into quotation marks and don't use spaces or a trailing backslash ! Default folder - wptdefault

detailnames (on|off) - Turns on/off the Skilldisplay behind names and the personality ( [POD], [P*D], [P0D] ) before the name. Default is on.

inhumanturns (on|off) - If you think that a Skill 100 Bot is too weak for you, you can turn this on to have that unfair turning from previous versions again. Note that this overrides the turn amounts in botskill.cfg . Default is off

botsfollowuser (number) - Sets the maximum number of Bots in the team to follow the same user (when Radio Command "Follow Me" is used). Default is 3.

maxweaponpickup (number) - Sets the maximum number of weapons Bots are allowed to pickup during a round. Default is 1.

shootthruwalls (on|off) - This Variable specifies if Bots are allowed to shoot through Walls if they saw an enemy or if they heard someone on the other Side of a Wall. Default is on.

usespeech (on|off) - Turns on/off usage of HL Engine Speech Synthesis at the game start. Default is on.

botspray (on|off) - Set this to off to disallow Bot Logo Spraying. Default is on.

mapstartbotdelay (value) - Delay (in seconds) of bots joining after new map start to prevent kick some human-players at map change. Default is 5.

timer_sound (value) - Default is 1.0 (in seconds).
timer_pickup (value) - Default is 0.3 (in seconds).
timer_grenade (value) - Default is 0.5 (in seconds).
These Settings above specify the rate (in seconds) of updating some of the Bot Checks like: some sound, some possibility of pickup any item or usage grenade by bots. If you've got a slow computer you could try changing these to higher values to get some performance back.
NOTE:
This seriously affects the Bots Perception. If you have a fast computer you might try lowering them to get better even better playing results.

welcome_msgs (on|off) - Lets You to disable some welcome messages, if You would like for example the people don't know there are some bots on the server. Default is on.

danger_factor (value) - The setting here specifies the danger factor with which the bots will weighten any waypoint where they have been killed in the past, in order to avoid it later. The higher the value, the more the bot will care about these waypoints and pick other routes instead. Progression is logarithmic. Warning: higher values require more CPU. Default is 2000.

addbot [skill [personality [team [model [name]]]]]

Adds a Bot with parameters - skill You can write from 1 to 100; if You will write 101 it will mean random skill from minbotskili to maxbotskill specified above.
Personality - 1 to 3 or 5 and these value mean:

- 1 - Normal [POD]
- 2 - Aggresive [P*D]
- 3 - Defensive [P0D]
- 5 - Random personality from these 3 above

Team 1 is for Terrorists, 2 for Counter Terrorists and 5 to use auto-assign.
Model (class) is 1-4 or 5 (5 means random from 1 to 4).
Name is of course the name for this Bot.
If You want to use space in the name of Your bot You have to use quotes (for example: addbot 100 2 1 4 "James Bond").
You may not specify some argument without these before (for example - You may not specify bot's name without its skill nor personality nor team nor model - like this:
addbot Roger
this is an invalid call of the function addbot and then some bot with all random parameters (including also the name) will be added to the game.
You don't need of course specify all parameters - but if You need to specify some of them exactly - all other You have to specify as random. In our example to add some bot with the name Roger You have to write the line:
addbot 101 5 5 5 Roger
and this call of addbot function is correctly.
If You want to add some bot to the game with skill 100 to T team, the line should be like this:
addbot 100 5 1
In this case the parameters AFTER the latest one You need to specify - aren't important (You don't need write anything more). The model will be selected automatically and the name will be choosen from botnames.txt file.

Some other examples:

addbot -->skill gets based on mix\max, all else random
addbot 50 -->skill is 50 all else random
addbot joeblogs --> skill is based on min/max, name is joeblogs, all else random
addbot 100 1 2 1 "Mr Kabby" -->all have been set

fillserver [skill [personality [team [model]]]]

Meaning of the parameters is like for addbot command. This command let You fill the server by bots until reaching by podbots+human_players(or other bots):
a) the max_bots value if it is specyfied (different than 0)
b) max_players if max_bots is not specyfied (or is equal to 0)
If You want fill Your server by bots with random skill (between minbotskill and maxbotskill), but as "aggresssive" (and You don't care about their models or team), write this line:
fillserver 101 2
If You want for example fill the server by bots with skill 100, random personality , random team and random model - write this line:
fillserver 100
If You wish to fill the server by bots, but all bots to one team only - then write this:
a)example for T team and skill 90, all else random:
fillserver 90 5 1
b)example for CT team and skill and personalities randomly, model 3:
fillserver 101 5 2 3
The rules are the same for parameters like for addbot command (except 'name' parameter - for fillserver this parameter doesn't exist).

NOTE:

If You want fill server by bots to only one team don't forget set-up game variables "mp_autoteambalance" and "mp_limitteams" to 0.
Podbot control console commands

You can change all parameters described above from console - if You wish to do this. Any command You want to write in console for this bot You have to start with prefix "pb" without quotes. For example:
pb minbotskill 60
pb jasonmode on

Except these commands described above there are also some other available commands You can write in console.

pb experience - this command force bot dll to save the experience file (pxp) exactly at the moment of calling it (after typing in console). Normally these pxp files (with experience of bots - like sombody died near some waypoint number) are saved at the end of the map (before starting the new one).

pb help - this command lists all available bot console commands. In the future we want to write more precisly help for every command separately.

pb killbots - this command kill all pod bots in the game. Useful for testing if bots got stuck somewhere becasue of bad waypointing and You want simply finish the round.

pb remove (#bot_id | bot_name) - this command lets kick the selected bot from the game. bot_id parameter is this what You can see when You write status in console (the same like for standard kick command). bot_name - it's second method to specify which one bot has to be kicked (it's like kick by the name).

NOTE:

If Your bot has a space in its name (for example - James Bond) You need to use quotes to successfully usage of the remove command. Example:
pb remove "[P*D]James Bond (100)"
Look at this example with attention - if detailnames is on - You have to write also this personality prefix and skill sufix - all must be in quotes - because all of this it's the bot's name in this example.

pb removebots - this command kick bots from Your server until reaching min_bots. If min_bots is 0 then all bots will be kicked out by this command.

pb weaponmode (value) - correct value are 1 to 7. This command lets You select the weapon will be used by bots only (they will not buy another type).

- 1 - Knife only (JasonMode!)
- 2 - Pistols
- 3 - Shotguns
- 4 - Machine Guns
- 5 - Rifles
- 6 - Sniper Weapons
- 7 - All Weapons (Standard)

pb version - this command returns the version number (as a string) of the POD's build

Waypoint console commands

These commands below are valid only on listenserver.

waypoint teleport (value) - Teleports You to the waypoint number You write here.

waypoint stats - Shows the number of different waypoints you did already set.

pb debuggoal (value) - this command force bots to go to the waypoint number specyfied here as a goal (target). Default is -1 (-1 means no extra goal waypoint specyfied and bots aren't forced to go to some waypoint). More info You can find in Waypointing section of this doc.