Install MetaMod and CounterStrikeSharp on a CS2 Server

Prepare a rollback point

Stop the server and copy game/csgo/addons, game/csgo/gameinfo.gi, game/csgo/cfg and launch parameters. Record the CS2 build and obtain archives only from official sites or repositories. Compatibility changes quickly after game updates, so read CounterStrikeSharp's current requirements at installation time.

For a first install, the documentation requires CounterStrikeSharp With Runtime. Install the required Visual C++ Redistributables on Windows; on Linux ensure ICU (libicu or the distribution equivalent) exists.

Install MetaMod:Source

1. Download the compatible MetaMod:Source 2.x build specified by CounterStrikeSharp.
2. Extract its addons directory into game/csgo/, producing game/csgo/addons/metamod.
3. In game/csgo/gameinfo.gi, add Game csgo/addons/metamod below Game_LowViolence csgo_lv, as the CounterStrikeSharp guide specifies.
4. Restart and run meta list in the server console.

If the command is unknown, inspect the directory tree and gameinfo.gi. A CS2 validation or update may replace that file, so check it after patches.

Install CounterStrikeSharp and one plugin

1. Download the official with-runtime package for the operating system.
2. Copy its addons directory into game/csgo/ without creating addons/addons.
3. Restart and run meta list; CounterStrikeSharp should appear as loaded.
4. Inspect CounterStrikeSharp logs before adding extensions.
5. Add one compatible plugin to its documented directory, restart, and test with a minimally privileged account.

Do not install an archive whose source or binary cannot be verified. A server plugin may read files, execute commands and process player identifiers.

Update and troubleshoot

Schedule: stop, backup, update CS2, test vanilla/MetaMod, update MetaMod and CounterStrikeSharp, then plugins one at a time. CounterStrikeSharp says its upgrade copy does not overwrite configuration, but retain a backup.

If the server crashes, restore gameinfo.gi and move addons out of the load path to confirm vanilla starts. Reintroduce MetaMod, CounterStrikeSharp and plugins in stages. An empty or unavailable meta list implicates the loader; a .NET error more often points to runtime or ICU.

For full file and restart access, compare CS2 hosts.

Quick questions

Why use the with-runtime package first? It includes the .NET runtime CounterStrikeSharp needs and removes one variable from initial diagnosis.

Why can Metamod disappear after a CS2 update? Validation may replace gameinfo.gi; compare it with the backup and reapply only the documented loader line.

How should plugins be restored? Start vanilla, then MetaMod, then CounterStrikeSharp, and finally one plugin at a time while checking logs at every restart.