SourceCoop Server Crashing, Hanging on Maps or Can't Connect

Most SourceCoop problems fall into three groups. If a map hangs or crashes while loading, set mod_forcetouchdata 0 in server.cfg, which stops map data pre-caching and fixes known problem maps like bm_c4a4a. If co-op features vanish or the server crashes after a Black Mesa update, the SourceCoop, SourceMod or Metamod build no longer matches the game, so update them together. If friends cannot connect, check UDP 27015, sv_lan 0, the password order and that their developer console is on.

Problem 1: A map hangs or crashes on load

The server is fine on most maps, then freezes or crashes during one specific level change. The usual cause is map data pre-caching, controlled by mod_forcetouchdata. With it on, the server pre-loads models and other map data, and on certain maps that hangs. The Nihilanth map, bm_c4a4a, is the best known example.

Fix:

mod_forcetouchdata 0

Add it to bms/cfg/server.cfg, restart, and load the map again. If it still crashes:

1. Check the server console for the last lines before the crash. A missing model or material name points to a broken or partial game install. Run SteamCMD with validate:

steamcmd +force_install_dir /home/bms/server +login anonymous +app_update 346680 validate +quit

2. Try the map with only SourceCoop loaded. If you added other SourceMod plugins, one of them may not expect co-op map transitions. Move extra plugins into addons/sourcemod/plugins/disabled/ and test.

Problem 2: Everything broke after a Black Mesa update

Black Mesa updates can change engine internals that SourceMod and SourceCoop rely on. Symptoms:

• The server starts, but SourceCoop features are gone: no persistent gear, no revives.
• The console shows SourceMod gamedata or signature errors.
• The server crashes when the first player joins.

Fix it in this order:

1. Check sm plugins list in the server console. Plugins marked as failed or errored confirm the problem.
2. Look at the SourceCoop releases page on GitHub for a newer release made for the current game version, and its notes on which SourceMod and Metamod builds it needs.
3. Update SourceMod, Metamod:Source and SourceCoop together, so all three match.
4. Restart and check sm plugins list again.

Until a matching release exists, you can hold the server on the previous working version by not updating Black Mesa on the server, but then players on the new build may not be able to join. Usually the best option is to wait a few days for SourceCoop to catch up.

Problem 3: SourceCoop never loads at all

On a fresh install, if the server runs like plain Black Mesa deathmatch:

• Metamod not loading. Type meta version in the server console. If it is not recognized, Metamod is not installed in bms/addons or its loader file is missing.
• SourceMod not loading. sm version should answer. If not, SourceMod is in the wrong folder.
• Wrong SourceCoop build. Releases have assets for different games. Use the Black Mesa (bms) build.
• Teamplay off. Start with +mp_teamplay 1 on the launch line, as SourceCoop expects.

Problem 4: Friends cannot connect

The console step trips up the most players. Black Mesa hides the developer console by default, so share the exact steps: enable console in options, press ~, password, then connect ip:27015.

Problem 5: Map transitions drop players

Map changes are where co-op breaks most often. If players disconnect at transitions:

• They might be missing a custom map. Most files download on connect, but custom Workshop maps do not.
• A slow client can time out while the next map loads. Ask everyone to install Black Mesa on an SSD if they can.
• An extra plugin hooking map changes can conflict with SourceCoop. Test with extras disabled.

Problem 6: Lag with a bigger group

SourceCoop is light, but the campaign has busy fights. If the server stutters with a larger group, check CPU before memory: Source servers run game logic on one main thread, so a fast core matters most. Lowering the player cap to a sensible 6 to 10 also helps. The game server lag guide walks through the general checks.

If you are still setting the server up, the SourceCoop hosting guide shows the install order that avoids most of these problems, and the Black Mesa map names list helps when a start map typo is the issue.

Avoiding most of this

On a GamezServers SourceCoop server, SourceMod, Metamod and SourceCoop are installed and matched for you, and if an update needs different builds you can change the SourceCoop release and the SourceMod and Metamod build numbers in the panel and reinstall. The mod_forcetouchdata toggle is a panel switch, Black Mesa's server update is a setting you turn on when you are ready, and the server has its own address with the port open. Back up before updating, so a bad combination is one click to undo.

FAQ

How do I fix SourceCoop hanging on bm_c4a4a?

Set mod_forcetouchdata 0 in server.cfg and restart. It disables map data pre-caching, which causes hangs on that map.

Why did SourceCoop stop working after a Black Mesa update?

The update changed things SourceMod and SourceCoop rely on. Install a SourceCoop release made for the new version, with matching SourceMod and Metamod builds.

How do I check if SourceCoop is loaded?

Type sm plugins list in the server console and look for the SourceCoop plugins without errors.

Why can't my friends connect to my SourceCoop server?

Usually the developer console is off on their side, UDP 27015 is closed, or they typed the password after connect.