Server running tips

General configuration recommendations

bms/cfg/server.cfg

mp_teamplay 1 // provides lag-free noblock
sv_always_run 1 // avoids glitchy sprinting weapon animations

sv_tags "custom, coop, sourcecoop"
sv_cheats 0
sv_alltalk 1
mp_timelimit 2700 // 0 to disable
mp_mapcycle_empty_timeout_seconds 600 // changes maps in empty server

sourcecoop_homemap "bm_c0a0a"

bms/cfg/mapcycle.txt

Add bm_* maps to the mapcycle. Use bms/maplist.txt as reference.

Workshop

Adding workshop content is relatively easy. Of course, you can't add everything. Each map has to be supported by SourceCoop or have support built-in.

• Officially supported maps
• Additional information about workshop in Black Mesa

Guide

On linux, first copy steamclient.so from steamcmd/linux32 to your server's bin folder. Backup in case.

1. Create subscribed_file_ids.txt under <server>/bms.
2. Add a workshop item id per line. It is part of the url when viewing the workshop.
3. Restart your server. You should see each item begin downloading or updating.

For troubleshooting, Steam saves its own logs. If using LinuxGSM, this would be under /home/bmdmserver/.local/share/Steam/logs/workshop_log.txt

Third party plugins

We recommend the following plugins to run alongside SourceCoop.

• Crashed Map Recovery
• Connect Announce
• BM Spectator list