Configuration

Ready Up reads these files:

Settings for Auto Tournament (token, webhook URL, heartbeat URL) are console commands, not keys in a file. See Commands. Ready Up saves them for you.

readyup.cfg

The file sits next to the core, libserver.so. The installer creates it from readyup.cfg.example only if it is missing, so your changes survive updates.

The format is one key=value per line. Lines that start with # or // are comments. Quote a value that has spaces. Booleans take 0/1 (also n/y, f/t). Unknown keys are ignored.

debug=0
banner=1
chat_prefix=<DarkRed>[Ready Up]<Default>

welcome=1
ready_hud=1
hud_brand="Auto Tournament"

[fleet]
url=https://tournament.example.com
enroll_key=rfk_...

Where each key is read

• Core keys must be above the first [section] line. The core stops reading at the first section.
• Match keys can be at the top of the file (where they have always been), in a [match] section, or in game/csgo/cfg/ReadyUp/match.cfg. When a key is set in more than one place, the later one in that list wins.
• Other plugins read their [<plugin>] section, for example [fleet], [practice] or [midas]. The file game/csgo/cfg/ReadyUp/<plugin>.cfg wins over the section. In that file, keys can be at the top or in the [<plugin>] section.

Reloading

• ru reload in the console, or .ru reload in chat as an admin, reloads the core keys. Plugins read their own settings again too.
• The match plugin checks its files once a second and reloads by itself when one changes. The Midas plugin reads its settings every 5 seconds.
• The fleet plugin reads its settings when it loads. Use ru plugin reload fleet after a change.
• The status_http_* keys are read once at start. Restart the server to change them.

Core keys

Status endpoint

The core serves a small read-only HTTP endpoint for monitoring tools. See Status endpoint.

If you bind to anything other than a loopback address, a token of at least 16 characters is required. Without one, the endpoint does not start.

Chat colors

chat_prefix, admin_prefix and the captain prefixes take color tokens: <Default>, <White>, <DarkRed>, <Green>, <LightYellow>, <LightBlue>, <Olive>, <Lime>, <Red>, <LightPurple>, <Purple>, <Grey>, <Yellow>, <Gold>, <Silver>, <Blue>, <DarkBlue>, <BlueGrey>, <Magenta>, <LightRed>, <Orange>.

chat_prefix="<Green>[PUG #1]<Default>"

Match keys

Read by the match plugin (match.so). See Where each key is read.

Chat

Welcome screen and HUD

Keep the three timing keys (hud_tick_ms, hud_resend_ms, hud_duration_s) at their defaults. CS2 replays the panel's open animation on every send, and only a resend every frame gives a steady panel. Slower values make it blink.

The logo must be a public PNG, already scaled to the size you want. SVG does not work, and the client ignores width and height. An image in a panel that is resent every frame flashes. The CS2 client only renders a small part of HTML. Admins can test what works in game with .ru hud test 1 to .ru hud test 7. 8 to 11 measure the panel: rows, width and image sizes. .ru hud anim measures how fast the client redraws it.

Each player has one panel in the middle of the screen. When two things want it at once, the more urgent one wins: the map change card and the Workshop download bar, then the welcome card and test panels, then the ready panel.

With ready_hud=0 the panel is off and the chat reminders come back. Ready-up still works.

Warmup and scrims

In warmup, nothing drops when a player dies, and there is no bomb. Ready Up sets this itself, also when ru_cfg_exec_enable is 0. Going live puts CS2's defaults back.

After a day or more on one map, player animations in CS2 run in slow motion while the tick rate stays fine. A map load fixes it. That is why idle_map_refresh_hours exists, and why loading a match always changes map, even onto the map the server is already on.

Pauses, ready and forfeit

These are the values for scrims, and the fallback for matches whose config leaves a rule out. A match config can set each one with a key of the same name. See Match rules.

Tactical timeouts (.tac) use CS2's own timeouts. Their number and length are mp_team_timeout_max and mp_team_timeout_time, set in live.cfg or the match cvars.

Esports mode

The ruleset key itself is a core key. See Esports mode.

Testing only

Never turn these on for a real match. Ready Up logs a warning each time one turns on.

With either flag on and no human on CT or T, the knife round lasts 30 seconds, because bots do not knife each other.

Plugin settings

The practice and Midas settings are on Plugins. The whitelist has no settings file. Use ru whitelist in the console.

Fleet keys

Read by the fleet plugin (fleet.so) from the [fleet] section, or from game/csgo/cfg/ReadyUp/fleet.cfg. The fleet package installs a fleet.cfg with every line commented out, so the plugin stays idle until you set url. The same names with a fleet_ prefix (fleet_url, fleet_enroll_code, ...) also work. See Fleet mode.

Mode configs

cfg/ReadyUp/*.cfg are normal CS2 config files with server settings for each mode. The packages have them in readyup/cfg-templates/ReadyUp/. The installer copies missing ones to game/csgo/cfg/ReadyUp/. Edit the copies there.

The same folder holds the plugin settings files practice.cfg, midas.cfg and fleet.cfg. Those are Ready Up settings, not CS2 configs.

live.cfg, knife.cfg and prac.cfg start from the MatchZy defaults.

Two rules for warmup.cfg:

• Do not add mp_warmup_start. Ready Up does not use CS2's own warmup, because its WARMUP text covers the ready panel. Ready Up makes its own warmup instead: players respawn, rounds do not end, you can buy anywhere, nothing drops on death, and there is no bomb.
• It sets sv_hibernate_when_empty 0. Keep that. A hibernating server runs no frames, and Ready Up does its work in frames.

When the files run

By default Ready Up runs:

• knife.cfg for the knife round,
• live.cfg when a scrim goes live, and after the knife side pick,
• prac.cfg when practice turns on, and idle.cfg when it turns off,
• esports_live.cfg instead of live.cfg under ruleset=valve, always.

For warmup, it sets the warmup settings itself. A match without a knife round goes live with its own settings, without live.cfg.

The cvars of a loaded match are applied after live.cfg, so they always win over it.

To run the mode files on every mode change, as MatchZy does, turn on cfg exec in the console:

ru_cfg_exec_enable 1

The built-in warmup settings can be changed with the ru_warmup_* console commands. See Commands.

Data files

Ready Up has no database. Each plugin keeps its state in small JSON files in its data folder, game/csgo/readyup/plugins/<plugin>/. Every file has a "version", is replaced in one step (a temp file, then a rename), and is never in a release zip, so updates keep it.

A file that is broken, or from a newer version, is moved to <name>.corrupt-<time>. Ready Up logs it and starts that part fresh.

Delete match/state.json to forget saved settings and a half-finished match.

Environment variables

Set these before the server starts.