RBOT Admin Access
RBOT checks a password pair to grant full admin command access. The server console variable rbot_password holds the required password, and rbot_password_key holds the name of the client info key that players set on their end.
| Step | Where | Value |
|---|---|---|
| 1. Set password on server | Server console / config | rbot_password <yourpassword> |
| 2. Set key name on server | Server console / config | rbot_password_key rbot_pass (default) |
| 3. Authenticate as player | Client console | setinfo rbot_pass <yourpassword> |
rbot_pass. You can change this by setting rbot_password_key to any key name.Waypoint Editor Access
Waypoint editor access is completely separate from general RBOT admin access. It is controlled by the waypoint_access.cfg file and authenticated via the rbwp client info key (the legacy key rbot_waypoint_pw is also accepted for backward compatibility).
| Role | Permissions |
|---|---|
admin | Can use the waypoint editor |
owner | Can use the editor and permanently erase waypoint files from disk |
Identity matching in waypoint_access.cfg supports player names or auth id style identifiers (STEAM_*, VALVE_*, etc.).
rbot_password) does not grant waypoint editor access. Both systems must be configured independently.Waypoint Lock Model
Only one active waypoint editor session is allowed at a time. When a player opens an editor session, they acquire the lock. Any other player who tries to enter the editor will receive a lock-denied message.
Server Requirements
All waypoint editor commands — commands under rbot wp... and rbot wpedit... — require a dedicated server. These commands are rejected when the server is running in listen (non-dedicated) mode.