CS2 Dedicated Server Setup: GSLT, server.cfg and the Tickrate Question

If you are coming from CS:GO, the first thing to unlearn is tickrate. CS2 uses a subtick system: the server records when an input happened between ticks rather than snapping it to a tick boundary. Selling or configuring "128 tick CS2" is meaningless — the setting does not do what it did in CS:GO.

Install

CS2's dedicated server is Steam app 730 — the same AppID as CS:GO, which is why the two are distinguished at the egg or branch level rather than by app:

steamcmd +force_install_dir /home/container +login anonymous \
         +app_update 730 validate +quit

Budget the disk properly. A CS2 install runs about 30 GB, which means a plan with exactly 30 GB is at the edge before you have stored a single demo or workshop map. We flag this in our own provisioning: if you intend to keep demos, start at 40 GB.

You need a GSLT, and you can lose it

A Game Server Login Token ties your server to a Steam account. Without one, your server will not appear publicly. Two things people learn the hard way:

• A token is bound to one server. Running several servers means several tokens.
• Tokens expire if the server sits unused, and they can be revoked for the whole account if any server on it gets flagged. Do not share one Steam account across clients you do not control.

Set it in server.cfg:

sv_setsteamaccount "YOUR_GSLT_TOKEN"

A server.cfg that does something

hostname "Your Server Name"
sv_setsteamaccount "YOUR_GSLT_TOKEN"
rcon_password "use-a-long-random-string"
sv_password ""            // set to lock the server

sv_lan 0
sv_cheats 0
sv_pure 1

// Rates: leave headroom, do not cap players at defaults
sv_minrate 128000
sv_maxrate 0              // 0 = unlimited
sv_mincmdrate 64
sv_maxcmdrate 128

Note what is not here: no tickrate line. There is nothing useful to set.

RCON is the part people get wrong

RCON is remote command execution on your server. A weak RCON password is not a minor issue — it is full control. Use a long random string, never reuse it across servers, and change it whenever someone leaves your admin team.

What actually determines how the server feels

With tickrate off the table, three things are left, in order of impact:

1. Network path to your players. Physical distance sets a floor no configuration can beat. A server in the wrong region will feel worse than a badly tuned one in the right region.
2. Single-core CPU performance. The server simulation does not spread neatly across many cores.
3. Plugin load. Every tick spent in a plugin is a tick not spent simulating.

We provision CS2 with 2 GB of RAM as the floor. RAM is rarely the constraint for CS2 — CPU and network are.