CS2 plugin frameworks comparedMetamod, CounterStrikeSharp and what became of SourceMod

Published on August 9, 2026 · last updated on November 4, 2026

The layers at a glance

A CS2 server with plugins consists of two layers that build on each other - plus the actual plugins:

The order is mandatory: without Metamod, CounterStrikeSharp does not load; without CounterStrikeSharp, no plugin built on it runs. The installation of both layers is described in install Metamod & CounterStrikeSharp.

What became of SourceMod

SourceMod was the standard under CS:GO - for CS2, it is not the common choice. With the switch to Source 2, the engine changed so much that the plugin ecosystems have grown anew.

For Counter-Strike 2, CounterStrikeSharp has established itself as the platform against which most current plugins are built. So anyone coming from CS:GO is not looking for a SourceMod replacement for their old plugins, but for the CS2 equivalent of the feature they want.

The practical consequence: old CS:GO plugins cannot be carried over. For the common use cases - match control, retake, executes, 1v1 - there are established CS2 plugins for each.

Why versions are so sensitive

The most common cause of a CS2 server that no longer starts after an installation is a version mismatch in this chain:

• A CS2 update can render Metamod unusable until a new Metamod version comes out.
• A new CounterStrikeSharp version can break older plugins.
• A plugin for an older API does not load under the new version.
• gameinfo.gi overwritten - the Metamod entry regularly disappears with game updates.

This leads to a simple rule for operation: after every CS2 update, check first, then play. Before a tournament in particular, this is mandatory - see tournament and LAN setup.

Do I need this at all?

Not every server needs a framework. The honest distinction:

• Possible without plugins: competitive, deathmatch, Wingman, casual, Workshop maps, bots, practice config, demo recording.
• Only with plugins: MatchZy match control, retake, executes, 1v1 arena with leaderboard, surf timer.

That is more than many expect: a pure training and competitive server for a team gets surprisingly far with the basic equipment. You only need the foundation when you want real modes or match control.

Install, check and remove a plugin

The process is the same for all CounterStrikeSharp plugins, whether MatchZy, a retake or an executes plugin:

1. Download the release that matches the installed CounterStrikeSharp version.
2. Unpack the content via WebFTP or SFTP into addons/counterstrikesharp/plugins/ - one folder level too many is the most common installation mistake.
3. Run css_plugins reload or restart the server.
4. Check with css_plugins list via RCON whether the plugin really is on the list.

Removing a plugin is just as simple: delete the folder, restart the server. The only thing that matters is discipline - always install only one plugin at a time and check the list in between. Anyone who uploads three archives at once and then has a silent server searches for the cause considerably longer.

Most plugins create their configuration files themselves on the first start. Do not rely on them surviving an update unchanged: make a copy via SFTP beforehand. There are no automatic backups; backups are self-service throughout.

How to recognize a maintained plugin

There are several CS2 plugins for almost every task, but by no means all of them are still being developed. Because the chain of game, Metamod and CounterStrikeSharp shifts with every update, maintenance counts for more than features here. Four clues before downloading:

• A release after the last big CS2 update. If the latest version is months old, the project has practically been abandoned.
• A note on the tested CounterStrikeSharp version. Anyone who states it has understood why installations fail.
• Documented configuration. A plugin without described options is set up by trial and error - and after every update, you will not find your way back.
• Answered issue reports. The signal is not the number of open reports, but whether anyone answers at all.

And one decision up front that saves a lot of time later: start with as few plugins as possible. Every additional plugin is another candidate that has to catch up after the next game update. A server with two maintained plugins is usually back up days earlier after a patch than one with ten - and that is exactly what matters when the weekend's games are planned.

Frequently asked questions