The direct-connect address; 27015 is the game, query and RCON port at once
Black Mesa workshop
The officially licensed Half-Life remake · Sci-fi FPS, deathmatch and co-op
Black Mesa hosting in short: the dedicated-server appid is 346680 (Black Mesa Dedicated Server, type Tool, oslist windows,linux, so native on both platforms with no Wine) and the base game is 362890. There are only three ports and the engine own defaults corroborate them: 27015 carries the game traffic, the A2S query and SourceRCON at once (AMP names it "Game and RCON Port" with protocol Both), 27005 is the client port and 27020 SourceTV (which -nohltv can disable); the engine cvar defaults hostport=27015, clientport=27005 and tv_port=27020 agree with LinuxGSM, AMP, gamedig and the real container. Config lives in bms/cfg/. This site registers 99 server-relevant keys drawn from the full engine dump of 1929 entries (489 cmd and 1440 cvar); the dump header claims 1779 entries at version stamp 030616, a gap of 150, and both figures are registered. Commands and cvars must be told apart: mp_disable_autokick, maxplayers, sv_pure and sv_setsteamaccount are all cmd entries in the engine, so writing them as cfg assignment lines does nothing - and the AMP template that nothing references still carries the mp_disable_autokick line while the template actually in use has dropped it. Defaults come from the server.cfg.orig shipped with the game (mp_timelimit 900, mp_fraglimit 30, mp_teamplay 1, mp_forcerespawn 1) and are shown next to the engine defaults (mp_fraglimit 0, mp_teamplay 0). Three upstream defaults exist for the player cap (AMP 8, LinuxGSM 16, the real container 32) and no official maximum was ever published. Cooperative play is not built in: it needs the three-layer stack Metamod:Source, then SourceMod, then SourceCoop, which AMP automates across 16 update stages behind an InstallMod switch. A Game Server Login Token is requested against the base appid 362890 and passed as +sv_setsteamaccount. The version anchor is recorded as inferred: appinfo lists 5 branches (public and public-beta currently share one buildid, and there is an april-2024-rollback branch), but the dedicated-server appid has zero news items and the base game feed is entirely third-party and aggregator content, so no branch can be mapped to a release announcement. Every official documentation source was unreachable this round (blackmesa.com returns 403 with a Cloudflare challenge, wiki.blackmesa.com returns 000 and the developer GitHub organisation has no public repositories), so the precedence between the command line and the cfg is marked unverifiable.
Player tools (5)
Instant interactive calculations and recipe plannersFive branches, including GSLT and -strictportbind failures
No official CPU or RAM spec; the 30 GB disk figure is sourced; three tickrate readings
Five branches including a rollback one; the news feed is third-party content, so confidence is inferred
The engine dump has 1929 entries; this site registers the 80 server-relevant ones and separates cmd from cvar
Server admin and config generation (8)
Config files, startup scripts and command wizards for running a serverThree player-count defaults side by side (8 / 16 / 32); RAM is required
Three ports corroborated by engine defaults, plus collision detection
Port 27015 must get both TCP and UDP because RCON shares it
appid 346680, anonymous login, 30 GB of disk, GSLT via the base appid 362890
Five launch strings side by side, two cfg-loading mechanisms, GSLT as a placeholder only
Shipped defaults, no assignment lines for cmd entries, and the ban files exec-ed at the end
SourceRCON shares the game port, quit shuts it down, and cmd versus cvar is separated
Metamod:Source, then SourceMod, then SourceCoop (required for co-op)
Black Mesa Ports & Protocols
| Port | Protocol | Purpose |
|---|---|---|
| 27015 | TCP/UDP | The game port, which also carries the A2S query and SourceRCON (AMP names it "Game and RCON Port" verbatim) |
| 27005 | UDP | The client port; the engine default matches the WindowsGSM plugin, which computes game port minus 10 |
| 27020 | UDP | The SourceTV port; AMP exposes a -nohltv switch to disable it |
FAQ
- Which Black Mesa server-admin tools are available?
- We list 8 tools for Black Mesa: Capacity and player budget, Port matrix, Firewall rules, Install script, Startup arguments, server.cfg generator, Commands and RCON, The three-layer mod stack. All of them run straight in your browser.
- Which ports does Black Mesa need open?
- Black Mesa defaults to 27015/TCP/UDP, 27005/UDP, 27020/UDP. Use the actual instance configuration and allow only the listed protocols and ports. Check the host firewall, router forwarding and game visibility settings.
- How do I install a dedicated Black Mesa server?
- Install it with SteamCMD — the dedicated server app id for Black Mesa is 346680, so +app_update 346680 validate downloads or updates it. Config files usually live at bms/cfg/server.cfg, bms/cfg/bmdmserver.cfg, bms/cfg/banned_ip.cfg.
- Do these tools cost anything or need installing?
- No. Everything runs in the page: no install, no sign-up, no cost. Enter your values and the result appears instantly, and you can copy the generated configs and commands with one click.