Fix: 'Failed to load server DLL' / cs.so Not Loading

The server refuses to start and prints a variant of:

Failed to load server DLL

or, on Linux, a failure to load cs.so / dlopen of the game library. The game DLL is the code that is Counter-Strike — cs.so (Linux) or mp.dll (Windows), or its ReGameDLL replacement. When the engine cannot load it, there is no mod to run, so the server dies at boot. The cause is always one of: wrong path, wrong architecture, or a broken Metamod hand-off. Here is how to isolate it.

1. Read which file it failed on

The full console line names the path the engine tried. Get it:

./hlds_run -game cstrike -console +map de_dust2 2>&1 | head -40

Note the exact filename in the error — whether it points at cstrike/dlls/cs.so, a Metamod path, or a ReGameDLL file. That path is the whole diagnosis.

2. Check liblist.gam

cstrike/liblist.gam tells the engine which game DLL to load via its gamedll / gamedll_linux lines:

gamedll "dlls\mp.dll"
gamedll_linux "dlls/cs.so"

If these point at a file that does not exist — a typo, a renamed folder, a ReGameDLL install that changed the filename — the load fails. Confirm the referenced file is actually present:

ls -l cstrike/dlls/cs.so

A missing or misnamed cs.so here is the single most common cause. Restore the stock file or fix the path to match reality.

3. Understand the Metamod hand-off

When you run Metamod, the engine loads Metamod as the game DLL, and Metamod in turn loads the real game DLL named in addons/metamod/plugins.ini... except the real game DLL is pointed to by liblist.gam being redirected to Metamod. The critical detail: with Metamod installed, liblist.gam's gamedll_linux should point at Metamod's .so, and Metamod loads the actual cs.so. If someone edited one side and not the other — Metamod path in liblist.gam but Metamod misconfigured, or the real cs.so path lost — you get this error. If the failing file is metamod, jump to the metamod.so fix; if it is cs.so, the game DLL itself is the problem.

4. Rule out an architecture mismatch

The game DLL is 32-bit. A 64-bit-only host, or a mixed install where someone dropped a 64-bit build in, fails to load with an incompatible-ELF error. Check the file:

file cstrike/dlls/cs.so

It must report ELF 32-bit. If it says 64-bit, you have the wrong build — install the 32-bit game DLL and its 32-bit libraries (libc6:i386, libstdc++6:i386). This is the same class of problem as the libstdc++ error.

5. Match ReGameDLL to the engine

If you replaced the stock game DLL with ReGameDLL_CS, it must be a build compatible with your engine (ReHLDS strongly recommended). A ReGameDLL binary built against a different ReHLDS API, or dropped onto plain HLDS it does not support, can fail to load or crash immediately. Reinstall a ReGameDLL release matching your ReHLDS version, and make sure liblist.gam points at the ReGameDLL file, not the old stock one.

One subtle ReGameDLL trap: it typically installs its cs.so in place of the stock one under cstrike/dlls/, so a botched install can leave you with a zero-byte or partially-copied file that the engine reports as a load failure rather than a missing file. Check the size and permissions of the file liblist.gam names, and if in doubt drop the stock cs.so back to prove the engine and paths are fine before re-layering ReGameDLL on top.

Common errors

• Points at cs.so that is missing — wrong path in liblist.gam or a deleted file. Restore it and fix the path.
• Points at metamod — this is a Metamod load failure, not the game DLL. See the metamod fix.
• wrong ELF class / incompatible — a 64-bit game DLL on a 32-bit contract. Install the 32-bit build.
• Failed right after installing ReGameDLL — the ReGameDLL build does not match your engine. Reinstall a matching release.
• Works without Metamod, fails with it — the Metamod hand-off in liblist.gam/plugins.ini is misconfigured.

Verification

Start the server in the foreground and watch it pass the DLL load without error, reaching the map:

./hlds_run -game cstrike -console +map de_dust2

A clean boot to the map means the game DLL loaded. If you run Metamod, confirm the chain with meta list after startup — Metamod running plus a spawned map proves both the Metamod hand-off and the underlying cs.so loaded correctly. Connect a client to a live round to be sure the mod is really running and not a stub.