Before you start
You need administration rights, the actual allocated address and port, a Steam account eligible for GSLT management, and a copy of existing files. These are documentary steps, not commands executed on customer services.
Confirm the project really uses CS2
Record the game and build from server logs. CS2 and CS:GO do not use the same extension interfaces or runtime environment. A folder called csgo still appears within CS2, so its name alone does not identify the old game. Check maps, packs and tools before copying an earlier installation. Retaining an old directory structure does not establish compatibility.
Create a GSLT and keep it private
A Game Server Login Token links the server to your Steam account. Use the official server account management page and application 730. Steam requires an eligible account, including ownership of the game, a qualifying phone number and no limited, locked or community-banned account state. A token does not replace a game licence. Enter it through your service’s protected setting rather than a public example, screenshot or code repository.
Define the match before adding extensions
For a scrim, agree on the map, teams, rounds and administrator rights. For practice, list the functions you actually need. Deathmatch, Workshop maps and retakes are different projects and can need additional plugins or content. Do not assume an installer or ready-made preset exists without checking your panel. A smaller first configuration is easier to reproduce and investigate.
Check the Metamod and CounterStrikeSharp chain
CounterStrikeSharp documentation uses Metamod:Source and distinguishes downloads containing the runtime from those without it. Review current prerequisites and versions, then back up affected files before changing them. A CS2 update can require new extension releases. Do not copy an old installation procedure or an entire configuration blindly. Record which versions form the working combination.
Introduce MatchZy when your project needs it
MatchZy is a third-party project for organised matches and practice. Check its release, dependencies and administrator configuration. Test the required commands with a small group, followed by round transitions, map changes and pause recovery. Do not grant all players additional rights to work around a plugin problem. Preserve the configuration and component versions used for a successful test.
Validate after each change
First check startup, then a client connection, Steam authentication and the selected mode. Add extensions one at a time to isolate incompatibilities. Observe CPU, memory and logs during representative play: adequate RAM alone does not guarantee smooth simulation. Retain a known working configuration. Send support the exact error and relevant versions while keeping GSLTs and other secrets out of the report.
For your situation
| Situation | Next check |
|---|---|
| The server starts without plugins | Validate joining, map selection and match rules before adding extensions. |
| An update breaks a plugin | Check compatible versions and recover a coherent saved configuration without exposing the token. |
| You have an old CS:GO pack | Identify CS2 replacements and test each component independently. |
Official sources
These documents describe the relevant protocols and software. Your service terms and configuration still need to be checked.