Checking CounterStrikeSharp After the September Update

CounterStrikeSharp v1.0.374 from September 7, 2026 adds the CustomHudLayout API, fixes a bug in DropActivePlayerWeapon, and updates schema definitions to 1.41.7.7. The release alone doesn't confirm the compatibility of every plugin on your server.

Back up your existing framework and plugin files, and after a controlled update, check the loading chain: meta list, then css_plugins list, then the MatchZy functions you use. Also test map changes and your own HUD or weapon plugins. Record the tested framework version together with the plugin versions.

Don't install an older MatchZy package that bundles CounterStrikeSharp over an already updated framework without checking first. Check the included versions first, or use the plugin-only package if the requirements are already met. The MatchZy releases explicitly distinguish between these packages.

What Builds on What?

The order matters: MetaMod:Source loads native extensions, CounterStrikeSharp provides the C# plugin framework, and MatchZy runs as a CounterStrikeSharp plugin. After a CS2 update, the framework versions need to match the current server build.

This structure also explains why errors almost always cascade from the bottom up: if MetaMod doesn't load, CounterStrikeSharp never starts in the first place, and MatchZy then never shows up in any plugin list. If you reinstall MatchZy first in this situation, you're fixing the wrong layer. So always work your way up from the lowest level.

Requirements

Before you start, check three things:

  • Server access: You need access to the plugin manager in the panel or to the file manager. For the manual method, you need SFTP access to the game server files.
  • A current backup: Plugin installations write into game/csgo/addons/. A backup before the first write access saves you a complete reinstall if something goes wrong.
  • A stopped server: Never write to addons/ while the server is running. Half-written files lead to loading errors that are hard to distinguish from real version conflicts.

Installation in the Panel

  1. Create a backup and stop the server.
  2. Open the Plugin Manager and install MetaMod:Source first.
  3. Then install CounterStrikeSharp.
  4. Start the server once. MetaMod and CounterStrikeSharp must appear in the log without any loading errors.
  5. Stop the server again, install MatchZy, and start it.
  6. Check with css_plugins list in the server console whether MatchZy is loaded.

For manual installation, MetaMod and CounterStrikeSharp go under game/csgo/addons/; MatchZy goes under game/csgo/addons/counterstrikesharp/plugins/MatchZy/. Use the plugin manager whenever possible so paths and compatible versions are selected automatically.

The intermediate start after step 3 isn't an optional extra step. It cleanly separates two sources of error: if the server already gets stuck here, it's the framework's fault, not MatchZy's. If you install everything in one go and the server no longer starts, you're left guessing afterward which of the three components is to blame.

Basic Commands for a Match

Players use the chat commands:

.ready       mark ready
.unready     unmark ready
.pause       pause the match
.unpause     resume the match

Depending on your MatchZy configuration, the same commands can also start with !. Admins load a match configuration via the load command provided by MatchZy; check the exact file name in your MatchZy configuration beforehand.

Useful server commands:

status
mp_warmup_end
mp_restartgame 1
changelevel de_mirage
bot_kick

If you want to start matches regularly without console work, the CS2 Match Center with MatchZy is the more convenient way: teams, map, format, and GOTV can be set there via a form instead of typing every setting as a command.

Narrowing Down Errors

The three most common symptoms have clearly distinguishable causes:

  • css_plugins list doesn't recognize the command. Then CounterStrikeSharp isn't loaded. Check the startup log to see whether MetaMod even initialized — without MetaMod, there's no CounterStrikeSharp.
  • css_plugins list runs, but MatchZy is missing from the output. The framework and plugin layer are fine, but MatchZy is in the wrong directory or doesn't match the installed CounterStrikeSharp version.
  • The server no longer starts after installation. Usually a version conflict after a CS2 update. Remove MatchZy as a test, start the server, and work your way back up.

Always read the startup log from top to bottom. The first Failed, Error, or Exception block names the affected layer; everything after that is usually a follow-on error that disappears on its own once the root cause is fixed.

After a CS2 Update

If plugins suddenly go missing, don't reinstall the whole game server. First check whether MetaMod and CounterStrikeSharp still load, update both frameworks, and then MatchZy. The first Failed, Error, or Exception block in the startup log usually shows the affected layer.

Valve releases CS2 updates without regard for third-party frameworks. So there can be hours to days between an update and the matching MetaMod or CounterStrikeSharp version. For league matches with a fixed date, it's worth controlling automatic updates deliberately, so a server doesn't switch to a build right before the match for which no compatible plugins exist yet.

FAQ

Do I also need to install SourceMod? Not for MatchZy. MatchZy builds on CounterStrikeSharp. SourceMod is a separate, parallel plugin ecosystem and isn't needed for this stack.

In what order do I need to update? Always from the bottom up: first MetaMod:Source, then CounterStrikeSharp, and finally MatchZy. The other way around, the upper plugin loads against a framework that doesn't yet match the server build.

Why don't the chat commands respond? Either MatchZy isn't loaded — css_plugins list shows this — or your configuration uses a different command prefix. Both .ready and !ready are common.

Can I install plugins while the server is running? No. Stop the server first. Write access to addons/ while the process is running creates incomplete files and loading errors that look like version conflicts.

Where can I find the official documentation? The installation steps and configuration options for MatchZy are in the MatchZy documentation. For version questions around the Metamod/SourceMod family, the overview of required versions at AlliedModders is the reference.

The server runs, but performance drops during the match. That's not really a plugin problem in the strict sense. Check tick rate and server load separately from the plugin stack — there's a dedicated guide on tick rate and performance on CS2 servers.