There is an ini file for GameBots that is in UT2004\System\ directory (GameBots2004.ini). In the ini file various parameters affecting the bot, the server and the game mechanics may be added. The ini file is separated by tags („[ExampleTag]“) to the parts that always configure the class specified in the tag. We will go through the most important ones below.
[GameBots2004.RemoteBot] Here we configure the variables affecting the bot (agent) itself (speed, respawning, debuging features, etc.). Some usefull variables are below:
bPerfectLocationAim=false – If the bot should have perfect aim also for location targets and stationary targets. If set to true bot accuracy setting will be used just when aiming to another bot or player (specified in the SHOOT command by „Target“ variable).
bAutoSpawn=true – If the bot will be automatically respawned after death.
bDrawTraceLines=False – Wheter the rays visualizing automatic ray tracing should be spawned.
[GameBots2004.BotConnection] Here we set if the game will be pausable for bots, if they will be allowed to cheat and also delay between two synchronous message batches. Usefull parameters:
bSynchronousMessagesOff=false - boolean. Enables disables synchronous messages for the bots.
visionTime=0.250 - float. Delay between two synchronous batches in seconds.
bAllowCheats=True - boolean. If the bots are allowed to cheat - that means if they can spawn items for themselves by ADDINV command and if they can be set to be invulnerable.
bAllowPause=true - boolean. If the bots are allowed to pause the game.
bExport...=true - boolean. Sets which batch messages will be exported as a response to the READY command (Mutators, NavPoints, Inventory, GameInfo, Movers, etc.).
[GameBots2004.ControlConnection] This configures features of control connection – connection that controls the game mechanics – changing the map, kicking the players, etc.
bExport...=true - boolean. Sets which batch messages will be exported as a response to the READY command (Mutators, NavPoints, Inventory, GameInfo, Movers, etc.).
[GameBots2004.BotDeathMatch] Generally GameBots2004.DesiredGameTypeToConfigure. Here we configure desired game type. We can set time limit here, maximum number of players, goal score, etc. bAllowControlServer enables or disables possibility of control connections. Here we also set the ports on which will run bot server and control server. Usefull parameter:
bAllowControlServer=True - boolean. If the control server will be allowed or not .
BotServerPort=3000 – sets the port for bot connections.
ControlServerPort=3001 – sets the port for control server connections.
ObservingServerPort=3002 – sets the port for observer connections
bRandomPorts=false - boolean. If we want to use random ports (used ports will be displayed in the server console window screen). This will override set ports.
TimeLimit=120 - integer. Time limit how long before the game ends in minutes.
GoalScore=25 - integer. How many points player needs to score to win (game will end).
MaxSkill=7 – Sets the max available skill level for GameBots and epic bots on the server. Setting here holds for all derived game classes. Ranges from 0 (excluded) to 7.
[GameBots2004.GBHUD] Configures which features of GBHUD should be on and off by default and some default settings.
NavPointBeaconDrawDistance=500 – Maximum distance of navigation point from the player for which we will be drawing its name.
DisplayPlayerPositions=1 – Display additional debug information for the bots. Set to 0, 1 or 2. 0 means no additional information, 1 means player location, 2 means player location, focus and field of view.
b...=true/false – various booleans setting GBHUD features.
[GameBots2004.BotServer and GameBots2004.ControlServer] Here we set maximum number of connections that we will accept for control connections and for remote bots. Usefull parameter:
MaxConnections=10 - integer. Maximum connections to the server.
In GameBots ini file you find much more parameters affecting the game. They are usually commented.