The direct-connect and steam://connect address; AMP builds its connect link from the query port 27015 while the main game port is 7777
MORDHAU workshop
Medieval Melee Combat · Medieval Melee / Multiplayer
MORDHAU server quick reference: the main game port is 7777 (not 27015), the Steam query port is 27015, the beacon port is 15000 (described verbatim by AMP as used for connecting players), and the role of 7778 contradicts itself upstream (RCON over TCP for AMP, PEER over UDP for the real container). The dedicated-server appid is 629800 (MORDHAU Dedicated Server, type Tool, oslist windows,linux, so both platforms are native and no compatibility layer is involved). Config lives in Mordhau/Saved/Config/LinuxServer/Game.ini (WindowsServer on Windows) with 56 key slots in total (54 writable), 13 of which carry different defaults in different sources. There are four map lists that do not cover each other (AMP 98, LinuxGSM 60, community 42, container 21). There is no grade-A hosting documentation for this game: the official site has no hosting page, the official wiki returns 401/000 and the developer Triternion has 0 public repositories. No hardware spec is published by anyone, yet the player cap has five readings, none of them official.
Player tools (5)
Instant interactive calculations and recipe plannersFive branches: not listed, listed but unjoinable, RCON failing, config ignored, startup failing
Neither the developer nor the four upstream sources publish any hardware spec; the player cap has five readings and disk usage can only be measured
appinfo publishes no branch data for this appid, so no buildid exists; all that is available is the latest official patch announcement and the version regex in the server log
The 98 asset-path to short-name mappings AMP registers across 10 mode prefixes, plus three naming forms
Server admin and config generation (8)
Config files, startup scripts and command wizards for running a serverFive player-cap readings side by side (8/16/16/20/48), none of them official; no per-player memory formula is offered
Four ports across five readings; 7778 is RCON over TCP for AMP but PEER over UDP for the real container
iptables and ufw flavours; because the role of 7778 is unresolved, both TCP and UDP are opened by default with the reason stated
appid 629800 with anonymous login; appinfo says oslist=windows,linux so both platforms are native and no Wine is involved
Four launch forms side by side; the map argument has three forms (short name, full asset path, partial path)
56 key slots (54 writable plus 2 panel-only) across 3 sections, with 13 default-value conflicts shown side by side
Validates upstream lists: splits the glued entry on line 45 of the LinuxGSM file and flags the 20 maps absent from the AMP enum
Separates the three credentials RconPassword, AdminPassword and ServerKey; only placeholders are ever emitted
MORDHAU Ports & Protocols
| Port | Protocol | Purpose |
|---|---|---|
| 7777 | TCP/UDP | The main game port (AMP marks it Both and describes it verbatim as main game traffic; LinuxGSM and gamedig register UDP) |
| 27015 | TCP/UDP | The Steam query port (A2S, protocol valve per gamedig; this is the port AMP puts into its connect link) |
| 15000 | TCP/UDP | The beacon port (AMP verbatim: used for connecting players; opening only the query port leaves it listed but unjoinable) |
| 7778 | TCP/UDP | Role unresolved: AMP treats it as RCON over TCP, the real container as PEER over UDP, LinuxGSM does not open it, and both ini copies still default RconPort to 0 |
FAQ
- Which MORDHAU server-admin tools are available?
- We list 8 tools for MORDHAU: Capacity and player budget, Port matrix, Firewall rules, Install script, Startup arguments, Game.ini generator, Map rotation, RCON and admin credentials. All of them run straight in your browser.
- Which ports does MORDHAU need open?
- MORDHAU defaults to 7777/TCP/UDP, 27015/TCP/UDP, 15000/TCP/UDP, 7778/TCP/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 MORDHAU server?
- Install it with SteamCMD — the dedicated server app id for MORDHAU is 629800, so +app_update 629800 validate downloads or updates it. Config files usually live at Mordhau/Saved/Config/LinuxServer/Game.ini, Mordhau/Saved/Config/WindowsServer/Game.ini, -GameIni=${servercfgfullpath}.
- 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.