Counter-Strike 2 server setup: GSLT, subtick and plugins explained

Anyone setting up a Counter-Strike 2 server for the first time runs into three terms left over from the CS:GO era: GSLT, tickrate and SourceMod. Two of the three work differently in CS2 than most guides claim. This article lays out what you really need for a server to practise with your team, run a 10-man or start a public community server — and what you can safely skip.

When do you need a GSLT token?

A Game Server Login Token (GSLT) links your server to a Steam account and is required if your server should appear in the public server browser of CS2. For anything private — scrims, a league match against another team, an evening with friends — a token is not needed: players connect directly with connect ip:port and that works without a GSLT.

If you do want to be listed, create the token on Steam's Game Server Account Management page with App ID 730. You get a string of 32 characters that you paste into the server configuration (with us, in the panel, in the GSLT field). Note: the Steam account that creates the token must be in good standing (no VAC ban, phone number linked) and one token belongs to one server. How to enter it in our panel is in the knowledge base: setting a GSLT token.

128 tick no longer exists: subtick

In CS:GO tickrate was the big distinction between "normal" servers (64 tick) and competitive servers (128 tick). CS2 abolished that concept. The engine works with subtick: the server records the exact moment of every input within a tick, so perceived accuracy sits closer to the old 128-tick feel without the tickrate being adjustable. The launch parameter -tickrate 128 is silently ignored. Any provider advertising 128-tick CS2 servers is selling a setting that does nothing.

What does matter for the experience is the latency between player and server and how stably the server hits its ticks. A server in the Netherlands with good routes to the Benelux, Germany and Poland delivers pings of 5 to 30 milliseconds, and a fast processor core ensures the server never falls behind even with ten players and plugins. Read more on why location matters in our article on server location and ping.

Plugins: Metamod and CounterStrikeSharp

SourceMod, the standard from CS:GO, does not work on CS2. The current plugin stack is Metamod:Source as the base layer with CounterStrikeSharp (CSS) on top, a framework in which plugins are written in C# on .NET. Almost everything you want on a community server now exists as a CSS plugin: match management for 5v5 and 10-mans, warm-up settings, retakes, executes, admin commands, ranks and anti-cheat helpers.

The installation order is always: first Metamod, then CounterStrikeSharp, then the plugins. After a CS2 update, first check whether Metamod and CSS have been updated before updating the server; a Valve update can break an older Metamod version and then the server no longer starts. At MC-Node you turn off automatic updates in the panel when you run plugins, so you choose the moment yourself.

The basic configuration

The server settings live in cfg/server.cfg (general) and per game mode in the gamemode files. What you set in any case:

• hostname: the name in the browser and on the scoreboard.
• sv_password: always a password for a private server.
• rcon_password: the admin password for remote commands; pick a long one, because RCON is exposed on the server port.
• game_type and game_mode: 0/1 for competitive, 0/0 for casual, 1/2 for deathmatch, 0/2 for wingman.
• sv_cheats 0 and sv_pure 1: leave at default on a server where people play seriously.
• 7 Days to Die co-op server settings: blood moons, loot, difficulty
• Enshrouded dedicated server: the settings that make the difference

Load maps with map de_mirage or through a mapgroup; Workshop maps with host_workshop_map followed by the Workshop ID.

Running a 10-man or scrim

For matches use a match plugin (MatchZy is the best-known on CSS) that handles knife round, sides, overtime and pauses and optionally records a demo. A practical setup: password on, no GSLT needed, mp_autokick 0 so nobody gets kicked during a pause, and warm-up time set so players can connect calmly. Share the IP and password in Discord, and set a new password after the match if you also use the server for other groups.

Performance: what a CS2 server needs

CS2 is heavier than CS:GO, especially on the processor. For a 5v5 server with plugins count on a fast core (4 GHz or more) and 4 to 6 GB of RAM; a public 24-slot server with many plugins wants 8 GB. Storage matters little as long as it is SSD or NVMe. Our CS2 servers run on AMD hardware with NVMe in the Netherlands and can be cancelled monthly; the panel installs Metamod and CounterStrikeSharp with one click and keeps the server on the version you choose.

Common mistakes

The three tickets we see most. A GSLT from an account with a VAC ban or without a phone number: the server starts, but never appears in the browser and the log line about it is easy to miss. Installing plugins before Metamod: CounterStrikeSharp then does not load and every plugin throws a cryptic error. And leaving automatic updates on with plugins: after a Valve update the server no longer starts with an outdated Metamod, exactly on the evening the team wants to play. Set updates to manual, read the first twenty lines of the console after every start, and keep a copy of your cfg folder.

Step by step

1. Create the server, set hostname, sv_password and rcon_password.
2. Only for a public server: create a GSLT with App ID 730 and enter it.
3. Install Metamod and CounterStrikeSharp, then the plugins you need.
4. Choose the game mode, test maps, automatic updates off if you run plugins.
5. Play a short match with two players and check ping and tick stability.

After that it is maintenance: with every CS2 update first check Metamod and CSS, then update the server, then the plugins. Keep that order and you will rarely have a server that does not start.