Installing Metamod:Source and SourceMod without breaking it

Metamod:Source and SourceMod are two pieces of software with one job between them, and the order they are installed in is the whole difference between a working server and an afternoon of confusion.

Metamod loads first and hooks the engine. SourceMod loads on top of Metamod and provides everything you actually want — admin commands, plugins, the scripting runtime. Install them in the wrong order, or mismatch their versions against the game, and both fail together with an error that names neither.

Metamod first, confirmed before anything else

The Metamod:Source installation guide walks the process. The step people skip is the verification at the end: start the server, run meta list in the console, and confirm it responds.

If meta list returns nothing, Metamod is not loaded and nothing you do to SourceMod will help. The most common causes are extracting into the wrong directory (it goes in the game folder, not the server root) and a build that does not match the engine branch.

Do not proceed until that command answers. Ten minutes here saves an evening later.

SourceMod second

Then SourceMod, into the same game folder. Same verification: sm version in the console. If Metamod reports itself and SourceMod does not, the problem is isolated to one piece of software rather than spread across two.

This is the entire reason for installing them separately rather than extracting both archives at once. A single extraction that fails gives you one symptom and two suspects.

Version pinning, and the Tuesday problem

Both are built against the engine. When the game updates (which for Source titles happens without warning), a mismatched build stops loading, and every plugin stops with it.

Servers that handle this well know which build they are running and where the download came from. Servers that handle it badly find out when players report that admin commands stopped working, and then discover they cannot remember which version was installed or why.

Write it down. A file in the server root listing the Metamod build, the SourceMod build and the date is the cheapest insurance available, and it is the same habit that makes a crash traceable rather than mysterious.

Snapshots versus stable

SourceMod publishes stable builds and snapshots. Snapshots are newer and sometimes the only thing that works with a just-updated game.

Run stable when the game is stable. Move to a snapshot when an update breaks you and the stable branch has not caught up, and move back when it does. Living permanently on snapshots means every one of your plugin problems has an extra variable in it.

Gamedata, and the errors that look like plugin bugs

SourceMod ships gamedata files describing where things live in the game binary. When the game updates, those offsets move, and gamedata has to catch up.

A plugin that worked yesterday and now throws an error about a signature or an offset is nearly always a gamedata problem, not a plugin problem. The plugin author has not broken anything — the ground moved underneath them.

This distinction matters because the instinct is to remove the plugin. Removing it hides the symptom and keeps the cause, and the next plugin using the same function will fail identically.

What to install before you need it

Once SourceMod loads, the plugin set is a separate decision, and the useful ones are boring: admin commands, a ban system, and whatever your gamemode needs. Everything else is worth resisting until somebody asks for it.

A large plugin list is the main reason Source servers become difficult to update: every additional author is another chance that one of them has stopped maintaining their work, and a server that cannot survive a game update is a server on a countdown. That fragility belongs in the same conversation as what keeps a community server alive past its first month rather than being treated as a purely technical concern.

Keep a copy of the working set

The version pinning above is advice about what to install. This is advice about what to keep.

When an update breaks the server, the fastest recovery is not finding which build works. It is putting back the one that was working an hour ago, and that requires having kept it. An addons/ directory archived before every change, with the date in the filename, costs a few megabytes and turns a bad evening into a two-minute rollback.

The same archive answers the harder question later. Six weeks after a plugin started misbehaving, the useful diagnostic is what changed between then and now, and a folder of dated copies answers that immediately while memory does not, which is the same reason keeping a record of changes pays off on every other part of a server.

The order, one more time

Metamod. meta list. SourceMod. sm version. Then admins and immunity, then plugins, one at a time, with a restart between each.

It is slower than extracting everything at once and it is the only version of this process that tells you what went wrong when something does, which is the same reason every other change worth making is made one at a time.