Commands

How commands work

• Player commands start with a dot in chat, for example .r.
• Ready Up commands are .ru <command> <subcommand>, for example .ru match start or .ru map change de_mirage. Every .ru command is for admins, except .ru, .ru version, .ru help, .ru list and .ru dm status|top|hud.
• In the server console and over RCON, the same commands start with ru and no dot: ru match start. The console is always allowed.
• A player can also type ru ... in their own game console, like Metamod's meta or CounterStrikeSharp's css_ commands. The same admin checks apply, and nothing shows in chat.

.ru help lists the commands, one line each. .ru help <command>, or just .ru <command>, lists its subcommands. An unknown command answers unknown command, type .ru help.

Help, state and error replies go only to the player who asked. Actions that concern everyone, such as a pause or a map change, are announced to all.

Which commands exist depends on the plugins you run. ru help in the server console lists all of them.

Player commands

These come from the match plugin.

With no match loaded, only the ready commands and .forceready work. The others say they need a live match. You must be on CT or T to ready up.

With a match loaded, only players on the match roster can use these commands.

See Pauses for the limits.

Practice

These come from the practice plugin and only work in practice mode. Anyone on the server can use them.

Admin commands

Admin commands need admin rights. See Who is an admin. Anyone else gets not authorized, and nothing happens.

Match

From the match plugin.

Modes

Maps

From the essentials plugin.

During a knife round or a live map, these are refused unless you add force.

Every player sees a Changing map to ... card for 5 seconds. While the server downloads a Workshop map, they then see a progress bar in the middle of the screen until the map starts. The console gets a progress line every 5 seconds.

Admins

From the essentials plugin.

Whitelist

From the whitelist plugin.

Midas, deathmatch and addons

From the optional plugins. See Plugins.

Plugins and server

From the core.

Who is an admin

A player is an admin if one of these is true:

• The Steam64 ID is in admins.json of the essentials plugin. This counts in every mode, also in fleet mode.
• The Steam64 ID is in the admins list of the loaded match config.
• The Steam64 ID is in the admin list that Auto Tournament serves at ru_admins_url.
• Fleet mode: the Steam64 ID is in the platform's admin list.

The server console and RCON are always allowed.

Without the essentials plugin, admins.json is not read, and only the other sources count.

admins.json

game/csgo/readyup/plugins/essentials/admins.json:

{
  "version": 1,
  "admins": [
    { "steamid64": "76561198000000000", "name": "alice" }
  ]
}

ru admins add and remove write it for you. You can also edit it by hand. Ready Up reads it again within 30 seconds after it changes. Write it in one step: to a temp file, then rename it. A file that is not valid JSON, or has no "version", is moved to admins.json.corrupt-<time>, and Ready Up starts with no admins from the file.

The first admin must be added from the server console (or in the file), because no one in chat has rights yet:

ru admins add 76561198000000000

Older builds kept the file in plugins/match/admins.json. The essentials plugin copies it over the first time it loads.

Each server has its own file. To share admins between servers, copy the file, point them at the same ru_admins_url, or use fleet mode. In fleet mode, the local file is a safety net: the server owner stays an admin even when the platform sends no list.

Console and RCON commands

Run these in the server console or over RCON. Every .ru ... command above also works here as ru ....

Core

These work without any plugin.

ru <name> ... also reaches a console command of a plugin, so ru fleet status runs fleet status.

Console only

Auto Tournament

Auto Tournament sets these for you over RCON. Run a command without a value to see the current value. They survive a restart. See Settings that survive a restart.

In fleet mode, none of these are needed. The platform talks to the server over one WebSocket.

Demos and series end

Ready Up records a GOTV demo when a map goes live.

Warmup

These change Ready Up's own warmup. They apply the next time warmup rules are set.

Money in warmup is topped up after each purchase. That is warmup_money in readyup.cfg, not a console setting. See Configuration.

These values survive a restart, except ru_dev_bots_scrim. See below.

Settings that survive a restart

The match plugin saves these console settings in game/csgo/readyup/plugins/match/state.json when you change them in the console, over RCON or from a cfg file. It applies them again when it loads after a server restart. They are also kept across ru plugin reload match.

• ru_match_token, ru_webhook_url, ru_heartbeat_url, ru_admins_url, ru_admins_refresh_seconds. <setting> clear forgets them.
• ru_cfg_exec_enable and every ru_warmup_* setting.
• Every ru_demo_* setting, including the upload headers.
• The three ru_series_end_kick_delay_* settings.

Only values that differ from the built-in default are saved. <setting> default goes back to the default and forgets the saved value. A later command wins over the saved value, so a setting in server.cfg still applies on every start.

Saved values are plain text, like the match token and upload header values. Keep state.json private.

Fleet

These come from the fleet plugin. See Fleet mode.

Skins

These come from the skins plugin. See Skins.