The truth about player-side connect strings and the steam:// link
Startup argument builder · Astro Colony
Space colony building and automation (native dual-platform dedicated server) · Action / Adventure / Casual
Both the AMP and egg command lines, never inventing -Port=
Player tools (5)
Instant interactive calculations and recipe plannersFive symptom branches, including "an over-long name disables the password"
An honest registration of Workshop's UNVERIFIED status
Three buildids at three timestamps, with no announcement to corroborate
Semantics of the six boolean switches plus the rollback window
Server admin and config generation (8)
Config files, startup scripts and command wizards for running a serverPlayers, autosaving and the rollback window (estimates clearly labelled)
The single registered query port plus the inferred game port
Both ports labelled separately by evidence grade
Three appids dispatched per platform plus component 1007
Both the AMP and egg command lines, never inventing -Port=
13 keys, platform-forked paths, paste pre-check
Native Windows, native Linux and Wine side by side
Making "no RCON, no commands" explicit
Astro Colony Dedicated Server Install (SteamCMD)
SteamCMD appid 2934900
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 2934900 validate +quit
Astro Colony Config file paths
AstroColony/Saved/Config/LinuxServer/ServerSettings.iniAstroColony/Saved/Config/WindowsServer/ServerSettings.ini
Server notes
The dedicated server forks into two appids by platform: Windows uses 2662210 (and additionally pulls component appid 1007 into AstroColony/Binaries/Win64) while Linux uses 2934900; AMP deliberately installs the Linux appid into a directory named after the Windows appid (App.BaseDirectory=./astro-colony/2662210/), so both platforms share one path layout and looking up directories by appid leads to a wrong conclusion. A native Linux binary exists, so this title does not need Wine (the third-party Wine egg is an optional grade-C route). For ports, upstream registers only the 27015/UDP query port; the game port is registered nowhere and offers no way to change it, so multiple instances per host are not supported upstream. The config path forks by platform (two ServerSettings.ini files under WindowsServer and LinuxServer, both using the section /Script/ACFeature.EHServerSubsystem), and editing the wrong directory has no effect. The server name travels only on the command line as -SteamServerName: AMP declares ServerName as an ini key but never maps it, so a ServerName= line never appears in the ini; a name longer than 45 characters disables the server password (AMP verbatim), while the official egg and the third-party egg simply cap it at 30. The Seed cap is the int32 value 2147483647 (the egg says digits_between:1,10), yet a production template ships the 17-digit 97234982389468723, which both panels would reject; this site does not truncate for you, because truncating means a different world. Zero is a legal, distinct setting for both AutosaveInterval (disable autosaving) and AutosavesCount (retain none). Booleans are written True/False here (AMP and the real file agree), while the official egg's environment defaults are 1/0 and are written straight into the same ini; both encodings are registered side by side and not adjudicated. Of the 6 boolean switches, Sandbox and UnlimitedResourceStack are single-source keys (registered by AMP only), while SavegameName appears only in the real file. The admin surface is standard input with no remote-management port, and all three of AMP's player-event regexes are ^$ with MonitorChildProcessName empty, so the panel's online-player count is not trustworthy for this title. Shutdown has three readings: AMP ExitMethod=OS_CLOSE (under which ExitString=stop can never be sent), the official egg's ^C, and the third-party Wine egg's ^^C. There are two ready signals and they agree: AMP's regex and the egg's literal both anchor on "server create success".
FAQ
- Which Astro Colony server-admin tools are available?
- We list 8 tools for Astro Colony: Capacity planner, Port map, Firewall rule generator, SteamCMD install script, Startup argument builder, ServerSettings.ini generator, Runtime and environment, Admin surface and console. All of them run straight in your browser.
- Which ports does Astro Colony need open?
- Astro Colony defaults to 27015/UDP, 7777/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 Astro Colony server?
- Install it with SteamCMD — the dedicated server app id for Astro Colony is 2934900, so +app_update 2934900 validate downloads or updates it. Config files usually live at AstroColony/Saved/Config/LinuxServer/ServerSettings.ini, AstroColony/Saved/Config/WindowsServer/ServerSettings.ini.
- 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.