The truth about player-side connect strings and the steam:// link
Astro Colony workshop
Space colony building and automation (native dual-platform dedicated server) · Action / Adventure / Casual
Astro Colony server quick reference: this title has three appids — client 1614550, Windows dedicated server 2662210 (appinfo name verbatim "Astro Colony Dedicated Server", oslist=windows) and Linux dedicated server 2934900 (name "Astro Colony Dedicated Server Linux", oslist=windows,linux). Developer and publisher are both Terad Games; store release 2 Jun, 2026. Ports are the peculiarity here: AMP's ports.json registers exactly one port, 27015/UDP (verbatim "Port used for Steam query traffic"), and AMP also makes it the primary application port (PrimaryApplicationPortRef=SteamQueryPort) while its command line carries only -QueryPort; the official egg likewise has only SERVER_QUERY_PORT, marked user_editable=false. The value usually treated as the game port, 7777/UDP, is registered by no upstream artifact — it is merely the conventional Unreal default, corroborated only by a community compose file that calls itself works-for-me and DO NOT USE IN PRODUCTION YET. The operational consequence: upstream tooling offers no way to change the game port, so multiple instances per host are not supported. Configuration is 13 keys under /Script/ACFeature.EHServerSubsystem, but the path forks by platform: AMP registers both a WindowsServer and a LinuxServer ServerSettings.ini while the official egg writes only the LinuxServer one, so editing the wrong directory has no effect at all. Among AMP's 15 parameters the FieldName ServerName appears twice (one entry declared as an ini key, one mapped to the command-line SteamServerName), yet none of metaconfig's 13 mappings include ServerName — so in practice it only reaches the command line as -SteamServerName, with AMP's parameter format reading verbatim -{0}="{1}" (quoted). For the player cap AMP states only MinValue=1 (App.MaxUsers=5) while the official egg says between:1,10. The admin surface is standard input (AdminMethod=STDIO, AdminPortRef=0, RemoteAdminPassword empty); there is no networked remote-management port, no upstream artifact lists any console command, and SupportsLiveSettingsChanges=False, so changing a setting means editing the ini and restarting. Three runtime readings coexist: native Windows, native Linux (the route both AMP and the official egg take, so this title does not need Wine), and a third-party Wine egg (grade C, using the Windows appid). On the Windows side AMP additionally pulls component appid 1007 (the Steamworks SDK redistributable) into AstroColony/Binaries/Win64. Anonymous SteamCMD login has two independent sources (AMP semantics and a community repo entrypoint using +login anonymous). There is no grade-A official hosting document: the site is a WordPress marketing site enumerating to 10 pages via its REST API with no hosting section and a blog whose only post dates from 2020, and all three URLs of the official wiki astrocolony.fandom.com return 000. Every hosting fact comes from three artifacts cross-checking each other (the AMP template, the official egg, Steam appinfo), validated against two independent community artifacts (a real production ServerSettings.ini and a Docker repo that declares itself unreliable).
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 Ports & Protocols
| Port | Protocol | Purpose |
|---|---|---|
| 27015 | UDP | Steam query traffic port (visibility in the server list) |
| 7777 | UDP | Game traffic port (inferred; registered by no upstream artifact) |
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.