Professional Documents
Culture Documents
First tell the server to allow bots, press tilde (~) to open the console and type:
/bot_enable 1
/reload
the <type> should use one of the following bot file names:
boa
cheetah
chicken
cobra
c ockroach (<== space between the C and the O added to pass BB filters)
cougar
goose
mantis
penguin
puma
python
raven
scarab
scorpion
tiger
widow
so the following would add a level 4 bot called "=lvl4=Puma" to the blue team:
Each bot type has it's own weapon load out - Puma for example uses a LR300ML + Spas + Baretta
combo. By making sure at least 1 bot has the same weapons as you, you'll never run out of ammo.
Tactically, the bots are not very bright, and you can't give them orders like q3 bots, however they do
use the same evasion techniques (varying levels of crouching, bunny hopping and strafing) as live
players, with varying levels of aggression.
If you want to add more than one bot at a time, you might want to make a .cfg file which you save to
your q3ut4 directory
[pre]
/====== sample_bot.cfg======
/====== sample_bot.cfg======
[/pre]
/exec <filename>
Note while the example above tries to add bots to the blue team - the server will spread them evenly on
both teams - so add an even number or face the chagrin of continually getting pwned at spawn, by bots.
As mentioned before, the bots mimic certain aspects of real life, in teams they will mimic certain
aspects of team life, like occasionally tking you for no reason, ignoring calls for backup or medic, and
appearing to be AFK at spawn.
Removing bots
/kick <nick>
If you have more than 1 bot, or you can't be arsed typing whatever l33t nick you gave that 1 bot you
added, you can use this to take all bots off the server:
/kick allbots
though be warned the server checks for nick matches in the player list first, so player 'allbots' would
probably not be too happy with you, having been bumrushed off the server for no apparent reason.
Not every map in UT4 has bot support, the following do, sort of -
Abbey
Algiers
Austria
Dressing room
Firing Range
Mandolin *
Riyadh
Prague*
Toxic*
Uptown
Some maps work better than others - the maps marked with an asterisk are maps where the bots have
trouble getting out of the spawn points.
start server
alt gr + 4
3.Escribimos:
/bot_enable 1
4.Reiniciamos la partida
/reload
5.Agregamos los bots
boa
cheetah
chicken
cobra
cockroach
cougar
goose
mantis
penguin
puma
python
raven
scarab
scorpion
tiger
widow
7.Nivel
8.Ejemplo:
en algunos mapas los bots se quedan mirando hacia al cielo, en otros actuan muy torpemente o
simplemente no se pueden agregar. Por eso he creado una lista de mapas en los cuales los bots cumplen
un buen funcionamiento:
abbey
abbey ctf
algiers
austria
casa
dressing room
riyadh
sanctuary
turnpike terror
/bot_enable 1 and start the server through the appropriate menu choices
• The <type> should use one of the following bot file names:
• boa
• cheetah
• chicken
• cobra
• c ockroach (<== space between the C and the O added to pass BB filters)
• cougar
• goose
• mantis
• penguin
• puma
• python
• raven
• scarab
• scorpion
• tiger
• widow
• The <level> should be an integer between 1 (n00bish) – 5 (malevolent)
• The <team> should be either Blue, or Red
• The <ping> is just a placeholder, put 76 in
• The <server nick> should be what you want to name the bot
• To recap, the following would add a level 4 bot called “ThePuma” to the blue team:
/addbot Puma 4 Blue 76 ThePuma
Each bot type has it’s own weapon load out – Puma for example uses a LR300ML + Spas +
Baretta combo. By making sure at least 1 bot has the same weapons as you, you’ll never run out
of ammo.
Tactically, the bots are not very bright, and you can’t give them orders like q3 bots, however
they do use the same evasion techniques (varying levels of crouching, bunny hopping and
strafing) as live players, with varying levels of aggression.
Bot configuration files
• If you want to add more than one bot at a time, you might want to make a .cfg file which you
save to your q3ut4 directory
/====== sample_bot.cfg======
• Note while the example above tries to add bots to the blue team – the server will spread
them evenly on both teams – so add an even number or face the chagrin of continually
getting pwned at spawn, by bots.
• As mentioned before, the bots mimic certain aspects of real life, in teams they will
mimic certain aspects of team life, like occasionally tking you for no reason, ignoring
calls for backup or medic, and appearing to be AFK at spawn.
Removing bots:
/kick <nick>
• If you have more than 1 bot, or you can’t be arsed typing whatever l33t nick you gave that 1 bot
you added, you can use this to take all bots off the server:
/kick allbots
• though be warned the server checks for nick matches in the player list first, so player
‘allbots’ would probably not be too happy with you, having been bumrushed off the
server for no apparent reason.
Maps for running bots
• Not every map in UT4 has bot support, the following do, sort of:
• Abbey
• Algiers
• Austria
• Dressing room
• Firing Range
• Mandolin *
• Riyadh
• Prague*
• Toxic*
• Uptown
• Some maps work better than others – the maps marked with an asterisk are maps where the bots
have trouble getting out of the spawn points.
• The maps found most useful in upping my game are :
• Firing range - good for close quarters practice
• Riyadh – add several bots for sniper target practice
• Algiers – for finding sweet spots on the map to fire from cover
• Dressing room – for mixed terrain levels + varying range battles – though bots will fall
into the river in the middle and remain in there.