This guide covers the bmdmserver module in AlphaGSM.
bmdmserver is currently PASSED on the documented Ubuntu 24.04 Linux baseline. The current GitHub integration lane still exercises both process and Docker runtime selection, and the validated Linux lifecycle stays aligned across both backends while local runs remain process-backed by default unless you opt into the Docker backend.
Requirements
screen
- SteamCMD runtime libraries (
lib32gcc-s1, lib32stdc++6)
- Python packages from
requirements.txt
Quick Start
Create the server:
alphagsm mybmdmserv create bmdmserver
Run setup:
alphagsm mybmdmserv setup
Start it:
alphagsm mybmdmserv start
Check it:
alphagsm mybmdmserv status
Stop it:
alphagsm mybmdmserv stop
Setup Details
Setup configures:
- the game port (default 27015)
- the install directory
- the executable name
- SteamCMD downloads the server files
- default configuration and backup settings
Useful Commands
alphagsm mybmdmserv update
alphagsm mybmdmserv backup
Notes
- Module name:
bmdmserver
- Default port: 27015
- Process and Docker integration readiness use AlphaGSM
info --json protocol
a2s; Docker does not depend on a host screen log.
Server variables
After create bmdmserver, inspect or change these with set:
alphagsm myserver set --list
alphagsm myserver set KEY --describe
alphagsm myserver set KEY VALUE
| Key |
Aliases |
Type |
What it does |
map |
gamemap, startmap, level, worldname |
string |
The currently selected map or level. Example: dm_bounce. |
maxplayers |
users |
integer |
Maximum number of player slots. Example: 16. |
port |
gameport |
integer |
The primary game port. Example: 27015. |
rconpassword |
rconpass, querypassword, query_administrator_password |
string |
Remote console password for administrative access. Stored as a secret. |
servername |
hostname, name |
string |
The server's public name shown to players. Example: AlphaGSM Black Mesa: Deathmatch. |
serverpassword |
sv_password, password |
string |
Password required for players to join the server. Stored as a secret. |
Developer Notes
Run File
- Executable:
srcds_run
- Location:
<install_dir>/srcds_run
- Engine: Source
- SteamCMD App ID:
346680
Server Configuration
- Config file:
bms/cfg/server.cfg
- Key settings:
hostname — Server name
sv_maxrate — Max network rate
rcon_password — Remote console password
- Default port:
27015
- Default map:
dm_bounce
- Max players:
16
- Ports:
- Game port:
27015 (UDP)
- Client port:
27005 (UDP)
- SourceTV port:
27020 (UDP)
- Template: See server-templates/bmdmserver/
Maps and Mods
- Map directory:
bms/maps/
- Mod directory:
bms/addons/
- Workshop support: No
- Mod notes: AlphaGSM now supports
manifest, direct archive url, gamebanana, and moddb addon sources for this server through the shared Source addon flow. The built-in manifest currently includes metamod and sourcemod. mod cleanup removes only AlphaGSM-tracked addon files and keeps cache/state under .alphagsm/mods/bms/.
- Map install: Copy
.bsp files into bms/maps/ and add to bms/cfg/mapcycle.txt.
- Mod install: Copy addon folders into
bms/addons/.
Frequently asked questions
What support evidence is recorded for Black Mesa: Deathmatch?
Recorded lifecycle pass. Review the game guide for installation, account, licensing and runtime prerequisites before setup.
Which runtimes can run Black Mesa: Deathmatch?
Declared runtimes: Docker or a Linux host process.
Which ports does Black Mesa: Deathmatch use?
27015/UDP, 27015/TCP, clientport/UDP, sourcetvport/UDP. Named port values remain unknown; review the game guide and configuration for additional requirements.
Can I add mods to Black Mesa: Deathmatch?
No mod support is declared in this snapshot; review the game guide before adding mods.
How should I back up Black Mesa: Deathmatch?
A module-specific backup hook is declared. Review the game guide for its scope, restore procedure and shutdown requirements.