debug commands Options

[Cheeseh]

rcbot debug bot <botname>

first use this command to debug a particular bot

rcbot debug bot_goto

stand on a waypoint while debugging a bot, and the bot will go to the waypoint you are standing at, for debugging paths

rcbot debug bot_flush

clears all bot tasks and starts again. If bot is stuck on some task you can use this to kick start the bot.

rcbot debug util 1

prints what <bot name> is choosing to do

rcbot debug task 1

prints what's happening in the bots current task

rcbot debug nav 1

prints / shows navigation debug information

------------------------------ get prop commands ----------------------------

these commands are useful for finding variables stored in entities

rcbot debug findclass <class substring>

will find the correct classname with <class substring> e.g.

rcbot findclass player

might print...

CODE

CDODPlayer
CBasePlayer

Then you know what classes exist

rcbot debug printprops <class>

prints all known variables for the entity <class>

e.g.

rcbot debug printprops CDODGameRulesProxy

will print something like...

CODE

m_flRestartRoundTime
baseclass
m_bAlliesAreBombing
dod_gamerules_data
m_bAxisAreBombing
m_iRoundState
m_AlliesRespawnQueue
m_bInWarmup

rcbot debug getprop CDODGameRulesProxy <variable>

this will return a value for this variable in several formats (int,float,vector,bool)

It finds the nearest entity with this classname (unfortunatlely CBasePlayer/CDODPlayer will always find you!)

e.g.

rcbot debug getprop CDODGameRulesProxy m_bInWarmup

will print something like

CODE

bool = true, int = 1, float = ... etc...

[genmac]

Nice! very useful for tracking down stuff on the bot and map's entities.