The direct-connect address; 27015 is the game, query and RCON port at once
#RCON shares the game port#a single port
Open tool →
Full engine cvar dump
Firewall rules · Black Mesa
The officially licensed Half-Life remake · Sci-fi FPS, deathmatch and co-op
Player tools indexed: 5
Admin consoles: 8
Port 27015 must get both TCP and UDP because RCON shares it
Player tools (5)
Instant interactive calculations and recipe plannersFive branches, including GSLT and -strictportbind failures
#GSLT and listing#-strictportbind
Open tool →
No official CPU or RAM spec; the 30 GB disk figure is sourced; three tickrate readings
#no official hardware spec#30 GB of disk
Open tool →
Five branches including a rollback one; the news feed is third-party content, so confidence is inferred
#five branches#including a rollback branch
Open tool →
The engine dump has 1929 entries; this site registers the 80 server-relevant ones and separates cmd from cvar
#1929 dumped entries#cmd versus cvar
Open tool →
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 defaults side by side#RAM required
Generate config →
Three ports corroborated by engine defaults, plus collision detection
#corroborated by engine defaults#no official step
Generate config →
Port 27015 must get both TCP and UDP because RCON shares it
#27015 needs TCP and UDP#RCON restrictable by source
Generate config →
appid 346680, anonymous login, 30 GB of disk, GSLT via the base appid 362890
#appid 346680#GSLT via 362890
Generate config →
Five launch strings side by side, two cfg-loading mechanisms, GSLT as a placeholder only
#five launch strings#two cfg mechanisms
Generate config →
Shipped defaults, no assignment lines for cmd entries, and the ban files exec-ed at the end
#shipped defaults#no assignment lines for cmds
Generate config →
SourceRCON shares the game port, quit shuts it down, and cmd versus cvar is separated
#SourceRCON#quit to shut down
Generate config →
Metamod:Source, then SourceMod, then SourceCoop (required for co-op)
#a three-layer mod stack#required for co-op
Generate config →
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.