Install script · The Front

The Front Dedicated Server Install (SteamCMD)

SteamCMD appid 2334200

sudo useradd -m -s /bin/bash steam
sudo apt update && sudo apt install -y steamcmd lib32gcc-s1
sudo -u steam -i \
  /usr/games/steamcmd +force_install_dir /opt/gameserver \
  +login anonymous +app_update 2334200 validate +quit

https://www.playthefront.com/

The Front Config file paths

• TheFrontManager/ServerConfig_AMP.ini
• -ConfigServerName="AMP"
• TheFrontManager/ServerConfig_AMP.ini (fetched)
• ProjectWar/Binaries/Win64 (appid 1007)
• server_settings.conf + server_settings.help
• altsavedirectoryname="${defaultmap}"

Server notes

First, ports: the four ports are 5001 (game, UDP), 5002 (lobby beacon, UDP, which AMP describes verbatim as Port used for lobby beacon traffic), 5003 (shutdown/remote admin, TCP) and 27015 (Steam query, UDP). AMP ports.json, the LinuxGSM tfserver config (port/beaconport/shutdownport/queryport) and the community conf (+Port/+BeaconPort/+ShutDownServicePort/+QueryPort) all agree; the fourth reading is the WindowsGSM plugin, which hard-codes 27047 and 27048 with QueryMethod A2S and PortIncrements 0. The 27016/27017/27018 that this site used to list belong to no source at all and have been removed and registered as pollution item C2. The port group span is 22014 (27015 minus 5001), so a smaller multi-instance step interleaves; no upstream source publishes an official step and the community help states verbatim that only ONE server runs on each port number. Second, the security fact about 5003 needs its own paragraph: AMP describes it neutrally as a port used for the shutdown service while the community help states verbatim that it is a Remote Admin port that SHOULD NOT be forwarded and has No Password protection - an unauthenticated remote-admin port. This site flags it in three places (the port matrix, the firewall generator and the triage page) and the firewall does not open it by default. Third, the dedicated-server appid is split per platform: 2612550 (The Front Dedicated Server, oslist windows) and 2334200 (The Front Linux Dedicated Server, oslist linux), installed by two separate SteamCMD stages in AMP updates.json, both carrying UpdateSourceArgs=2285150 (the client appid; developer and publisher are both Samar Studio); another stage installs the Steamworks SDK Redist (appid 1007) into ProjectWar/Binaries/Win64 and the community install string carries app_update 1007 unconditionally, though neither explains whether Linux needs it. Fourth, config: AMP metaconfig points at TheFrontManager/ServerConfig_AMP.ini, a file AMP downloads from its own CDN with a FetchURL stage and renames (it does not ship inside the server package); the command line decides which config is read through -ConfigServerName="AMP", so a wrong name silently loads nothing. The key registry holds 136 slots: the ini union of 128 keys (124 in the AMP template plus four only in the community conf - EnableAntiCheat, FollowNpcMaxLevel, QueryPort and ServerTags - while IsCanMail exists only in AMP) plus 8 command-line-only parameters, and every ini key lives under the single [BaseServerConfig] section. Fifth, the community file writes 13 of its 127 lines with a leading + and 114 without, while none of the 124 AMP keys has one; which form the binary accepts cannot be verified, so the generator defaults to no prefix and offers a switch (D5). Sixth, versioning: appinfo returns empty depots and zero branches for all three appids, so no buildid exists; both server appids have zero news items and the six client items are all weekly maintenance notices (author Fighter, latest 2026-09-29 02:59 UTC) with no version number in title or body; the only version string is the community README label v1.0.22 (grade C, 2024-01-09), which visibly trails the weekly cadence. AMP UpdateAvailableRegex shows a version appears only in the server log, so confidence stays inferred. Seventh, official documentation is unreachable: the AMP Meta.URL points at www.playthefront.com, which returns 000 this round (also for /llms.txt, /dedicated-server, /news and /sitemap.xml); thefront.wiki.gg returns 403 (every wiki.gg domain did this round); the developer has no public repository; the Steam store page returns only a generic shell. There is therefore no grade-A hosting documentation, and the only per-key documentation is the grade-C community help file (9362 bytes covering all 127 keys), with the grade labelled everywhere. Eighth, hardware: neither the developer nor the four upstream sources publishes any CPU, memory or disk figure, yet the player cap has three readings (40 in AMP, 40 in the community conf, 24 generated inline by WindowsGSM) and LinuxGSM splits maxplayers=40, maxqueuesize=50 and queuevalidtime=120 into three keys; no per-player memory formula is offered and the only sourced performance figure is the AMP GameMaxFrameRate default of 35 (described verbatim as Sets the server framerate). Ninth, the anticheat switch has three different names: UseEAC in the AMP panel (default true), EnableAntiCheat only in the community ini, and anticheat in LinuxGSM - turning one off does not turn off the others. Tenth, admin authorization rests on a single comment: LinuxGSM states verbatim that serveradmins takes 17-digit Steam IDs separated by commas, and no source gives a file format or permission-tier system, so no permission matrix is invented. Eleventh, several traps: ClearSeverTime is a wipe schedule (the community help says verbatim that it sets the time at which all server data will be wiped, and the Sever spelling is the game own, present in both upstream copies) - the AMP template leaves it empty while the community conf carries a concrete date; world-related keys apply only when a new world is created; and the LinuxGSM altsavedirectoryname="${defaultmap}" means the save directory name follows the map, so switching maps switches the save directory with no source stating whether an old save can be restored. Twelfth, two upstream spelling defects: the game own ClearSeverTime (Sever, not Server) and the LinuxGSM typo damangeallies (whose AMP counterpart is IsCanFriendDamage); typing is also inconsistent, since IsCanMail=1.000000 is a float while its siblings IsCanSelfDamage=0 are integers, so validation follows key semantics and enums rather than name prefixes. Thirteenth, four launch forms: AMP uses -{0}="{1}" (quoted values) and passes -ConfigServerName=; LinuxGSM adds -MultiHome= and -log; the community script calls ./FrontServer (a different executable name from AMP TheFrontServer) and is the only form exposing the ?udrs=eos|steam backend switch (neither AMP nor LinuxGSM has it and no source explains the difference); WindowsGSM appends three performance flags. Fourteenth, the runtime signals are verifiable: the readiness signature is LogLoad: (Engine Initialization) Total time: N.N seconds, player join and leave have regexes carrying account=STEAM: and guid=, shutdown is ExitString=stop with ExitMethod=OS_CLOSE, and SupportsLiveSettingsChanges=False means a restart is required after config edits. Fifteenth, the query channel: gamedig lists this game (port_query 27015, protocol valve, release_year 2023) but its entry has no port field at all, an unusual shape; the WindowsGSM QueryMethod is A2S, so serverProtocol stays steam_a2s with that oddity registered. Sixteenth, privacy: several upstream defaults must not be copied (the AMP ServerName brand string and the random eight-digit ServerID template, the LinuxGSM servername and servertags both set to LinuxGSM, and the concrete ClearSeverTime date in the community conf), so this site never adopts a brand string as a default, emits only placeholders for ServerPassword and ServerAdmins, and reports pasted secrets by length. Seventeenth, the search tool failed again this round (eighth consecutive round, same failure mode) and with the official site and wiki unreachable and no developer repository, no community forum or self-media was screened and no such claim is made; the need and failure evidence is derived from the defensive design of the upstream artifacts and from their contradictions, item by item.