Plugins and updates

Update CS2

Valve updates CS2 often. An outdated server cannot load matches, and Auto Tournament shows CS2 update required.

csm update-game

This updates master-install with SteamCMD, stops all servers, copies the new files to each server and starts them again. Players on the servers are kicked, so do not run it during a match.

To update only one server:

csm update-server 2

Update the plugins

csm update-plugins

This installs Ready Up, the native CS2 plugin, on every server (on an instance host, as a new shared layer), copies your overrides and restarts the servers. It follows the Ready Up release channel and license answer set with csm plugins (see csm plugins -h). A host linked to Auto Tournament gets Ready Up updates from the platform's Update Ready Up button instead.

csm 1.23 and newer no longer install MatchZy Enhanced, Metamod or CounterStrikeSharp. Auto Tournament 3.x does not support MatchZy Enhanced.

The update monitor

The update monitor checks each server's log and updates servers that need it. Install it as a cron job that runs every 5 minutes:

csm install-monitor-cron

Other intervals use cron syntax for the minute field:

csm install-monitor-cron "*/10"

To remove it:

csm remove-monitor-cron

To run one check by hand:

csm monitor

How the monitor works

When Steam reports a new CS2 version, CS2 writes MasterRequestRestart to the server log. The monitor looks for this line in each server's log. When it finds one:

• A stopped server is updated and started.
• A running server is updated only when it is idle. That means no players are connected, no match is loaded, and both have been true for the idle grace period (10 minutes by default). Ready Up tells it whether a match is loaded and who is connected. If the server doesn't answer, the monitor treats it as busy and waits.
• If updates are on hold, the monitor only logs that an update is available and restarts nothing. See Hold updates during an event.

To update an idle server, the monitor announces the restart in chat, stops the server, updates it, starts it and checks that it comes back. It does this one server at a time and never touches a server with players on it.

After an update, the monitor waits an hour before it updates the same server again, so a server that keeps reporting an update does not restart in a loop.

The monitor writes its log to auto_update_monitor.log in the csm log folder. Run csm logdir to find it.

Hold updates during an event

The monitor can't see whether a tournament is running. It only sees whether a server is idle, and servers are often idle between matches. Before an event, turn automatic updates off:

csm updates hold on

While the hold is on, the monitor never restarts a server. When the event is over:

csm updates hold off

The hold is saved and survives reboots. csm update-game and csm update-server still work while it is on, so you can update by hand between rounds.

To see the current settings:

csm updates status

Change the idle grace period

A server must stay idle this many minutes before the monitor updates it:

csm updates grace 20

Set up automatic updates

Install the update monitor:

csm install-monitor-cron

That's it. When CS2 updates, each server is updated the next time it has been idle for the grace period. Remember to run csm updates hold on before an event.