The direct-connect address; AMP builds its connect link from the query port, which is easily mistaken for the main port
Firewall rules · The Front
Open-world survival crafting and sieges · Survival / Crafting / Multiplayer siege
5001/5002/27015 over UDP; 5003 over TCP and not opened by default (an unauthenticated remote-admin port)
Player tools (5)
Instant interactive calculations and recipe plannersFive branches: not listed, unjoinable, shut down remotely, config ignored, world lost after a map change
None of the four upstream sources publishes a hardware spec; the only sourced performance figure is GameMaxFrameRate=35
All three appids publish zero branches; the news is a weekly maintenance notice with no version number
A player-side reading of the 128 keys (57 in the GM ratio family), documented by the community help file (grade C)
Server admin and config generation (8)
Config files, startup scripts and command wizards for running a serverThree player-cap readings (40/40/24) plus the two queue keys side by side; no hardware spec; no per-player MB formula
Four ports across five readings (WindowsGSM uses a completely different 27047/27048)
5001/5002/27015 over UDP; 5003 over TCP and not opened by default (an unauthenticated remote-admin port)
A different appid per platform (2612550 / 2334200) plus the Steamworks SDK component 1007
Four forms side by side: AMP, LinuxGSM, the community script (with ?udrs=eos|steam) and WindowsGSM (with performance flags)
136 key slots (128 ini keys plus 8 command-line only), one section, with the + prefix form switchable
serveradmins takes 17-digit SteamIDs; the three anticheat switches all have different names
Four keys on one screen; a non-empty ClearSeverTime raises a red warning because it wipes all server data
The Front Ports & Protocols
| Port | Protocol | Purpose |
|---|---|---|
| 5001 | UDP | The main game port. AMP, LinuxGSM (port="5001") and the community config (+Port=5001) all agree, and the community help file warns verbatim that only ONE server runs on each port number. |
| 5002 | UDP | The lobby beacon port (AMP verbatim: lobby beacon traffic). It has a different job from the game port, so opening only the game port leaves players connected but unable to reach the lobby. |
| 5003 | TCP | TCP 5003 may expose remote administration without password protection; do not forward it publicly. |
| 27015 | UDP | The Steam query port. gamedig records port_query 27015 with protocol valve, and the community help gives the usable range verbatim as 27015-27050 with a caution for non-professionals. Note that AMP builds its connect link from exactly this port ($SteamQueryPort), which is why many people mistake 27015 for the server port. |
FAQ
- Which The Front server-admin tools are available?
- We list 8 tools for The Front: Capacity and player budget, Port matrix, Firewall rules, Install script, Startup arguments, ServerConfig generator, Admins and anticheat, Backup and wipe. All of them run straight in your browser.
- Which ports does The Front need open?
- The Front defaults to 5001/UDP, 5002/UDP, 5003/TCP, 27015/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 The Front server?
- Install it with SteamCMD — the dedicated server app id for The Front is 2334200, so +app_update 2334200 validate downloads or updates it. Config files usually live at TheFrontManager/ServerConfig_AMP.ini, -ConfigServerName="AMP", TheFrontManager/ServerConfig_AMP.ini (fetched).
- 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.