Launcher server list, direct-connect address format (IPv6 needs square brackets), ss14:// link semantics and favorites; what the launcher does on version mismatch
Admin Permissions & Governance · Space Station 14
Multiplayer RP · Social Deduction / RP
The full AdminFlags table (verified bit by bit from source, including the empty 1<<17 and Host=1<<31), the three +HOST bootstrap paths with the official Danger wording, every panic bunker key plus the official preset choices, prototype-driven whitelists, the complete hub tag set with inference rules, the three-strike system and 18+ duties, and a core admin command index
Player tools (5)
Instant interactive calculations and recipe plannersConnection Triage
TriageUnauthenticated GET /status self-check with per-field decoding (players / soft_max_players / panic_bunker / tags), the three auth modes, whitelists, NAT hairpinning, the hub advertise error signature and country-block fallbacks
Atmos Gas Lab
CalcPV=nRT algebra with source-code constants (R=8.314462618, 1 atm=101.325 kPa, 2500 L cell volume), partial pressures for the 9 gases, tank-fill target solving; algebra only, no engine simulation
Power & SMES Budget
CalcSMES 8 MJ / 16 MJ (verbatim from prototypes), 150 kW supply, 5-150 kW adjustable charge rate; deficit endurance, time-to-full and the stock 5 kW 26.7-minute figure; joules/watts only, never Wh
Chem Reaction Bench
CalcStoichiometric scaling from reaction prototypes (target output to required inputs), limiting-reagent detection and leftovers; minTemp / electrolysis mixer conditions shown explicitly; no molar-mass conversion (ReagentPrototype has no MolarMass field)
Server admin and config generation (5)
Config files, startup scripts and command wizards for running a serverPort Matrix
HostUDP 1212 game netcode + TCP 1212 HTTP status API (status.bind can be split off), optional metrics 44880, outbound 443 (hub / auth / ipify), optional Postgres 5432; status.connectaddress required behind a reverse proxy
Firewall & NAT
Hostufw / iptables / firewalld / Windows netsh rules generated per real protocol (TCP and UDP as a pair), multi-instance port planning, the UPnP option with official success/failure log signatures, and the outbound dependency list
Deploy & Update
HostOpens with "SS14 does not use SteamCMD" plus five pieces of evidence; official builds page / GitHub Releases six-platform zips, .NET 10 Runtime (not ASP.NET Core), VC++ Redistributable, chmod +x, update = copy the data folder, Watchdog production deploys and fork packaging
TOML generation from a verified key whitelist (every default taken from source CVarDefs), a Wizard’s Den baseline preset, paste-in preflight (unknown key / type / range / trailing comment violations reject the whole output), secrets left blank and never echoed, and the five ways to specify CVars
The full AdminFlags table (verified bit by bit from source, including the empty 1<<17 and Host=1<<31), the three +HOST bootstrap paths with the official Danger wording, every panic bunker key plus the official preset choices, prototype-driven whitelists, the complete hub tag set with inference rules, the three-strike system and 18+ duties, and a core admin command index
Space Station 14 Ports & Protocols
| Port | Protocol | Purpose |
|---|---|---|
| 1212 | UDP | Main game netcode (required for clients to connect) |
| 1212 | TCP | HTTP status API (required for the launcher; a bare client can skip it) |
Space Station 14 Dedicated Server Install (SteamCMD)
This game does not ship its server via SteamCMD — download it from the official source.
https://docs.spacestation14.com/en/general-development/setup/server-hosting-tutorial.html
Space Station 14 Config file paths
server_config.tomlbuild.jsondata/ (--data-dir; preferences.db, server.db)logs/ ([log] path)SS14.Watchdog appsettings.yml (production only)
Server notes
SS14 has a real dedicated server but lives entirely outside the Steam ecosystem: server zips come from the official builds page (https://central.spacestation14.io/builds/wizards/builds.html) or GitHub Releases (latest tag v2026.07.27.1, 2026-07-28; SS14 ships continuous builds, so the builds page runs ahead), and the runtime is the .NET 10 Runtime - the tutorial warns in bold not to install the ASP.NET Core Runtime instead (only SS14.Watchdog needs ASP.NET Core 10). Windows also needs the VC++ Redistributable (otherwise "Unable to load DLL libsodium"), and Linux/macOS must rerun chmod +x Robust.Server after every update. No dedicated-server appid exists (appid 1255460 is just the free base game). Ports: one instance uses a single port number by default (1212) but UDP and TCP must be opened as a pair - UDP 1212 carries the game netcode (net.port), TCP 1212 carries the HTTP status API (status.bind follows it by default; required by the launcher - disabling status.enabled makes the launcher unable to connect). hasServerList=false here means "this site has not implemented the SS14 HTTP status probe, so no live status query is offered", not "the game has no server list" - the SS14 list comes from the developer-run Robust Hub (hub.spacestation14.com): set hub.advertise = true and follow the hub rules (three-strike system, [18+] naming, standard tags) to get listed. It does not answer Steam A2S; the old steam_a2s protocol registration has been removed. Optional ports: metrics 44880 (localhost-only by default) and PostgreSQL 5432 (when database.engine="postgres"); outbound 443 must reach hub/auth/ipify, with official fallback domains for blocked countries. Configuration lives in server_config.toml (TOML; comments need their own line); CVars can also be set via --cvar, ROBUST_CVARS, ROBUST_CVAR_-prefixed env vars and the runtime cvar command; --config-file and --data-dir move config and data (SQLite preferences.db, logs) out of the install directory, and updating = copying the data folder plus server_config.toml. For production the official recommendation is SS14.Watchdog (auto updates, monitoring, crash restarts, REST administration; "restarting every 30 seconds" is the official troubleshooting entry for a misconfigured BaseUrl). Initial admin is a chicken-and-egg problem with three official exits: localhost connections get +HOST automatically (console.loginlocal), console.login_host_user, or promotehost from the server console - +HOST hands over the entire machine, per the official Danger wording. No real server was started, no hub was contacted and no live session was established here.
FAQ
- Which Space Station 14 server-admin tools are available?
- We list 5 tools for Space Station 14: Port Matrix, Firewall & NAT, Deploy & Update, server_config.toml Builder, Admin Permissions & Governance. All of them run straight in your browser.
- Which ports does Space Station 14 need open?
- Space Station 14 defaults to 1212/UDP, 1212/TCP. Use the actual instance configuration and allow only the listed protocols and ports. Check the host firewall, router forwarding and game visibility settings.
- Where are the Space Station 14 config files?
- Common paths for Space Station 14 config files are server_config.toml, build.json, data/ (--data-dir; preferences.db, server.db). Stop the server before editing, otherwise it overwrites your changes on exit.
- 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.