How to Create a Starbound Server Guide

From Survival Servers
Revision as of 13:39, 15 October 2026 by Ryan (talk | contribs) ([wiki:ss-claude-11372] Cut filler: notes about the page itself, repeated lines, empty phrases and decorative pictures (Ryan 2026-10-15))
Jump to navigation Jump to search

Starbound ships an official dedicated server, so you can run an always-on universe that your crew joins any time.

Before you start

The dedicated server is a separate free download on Steam (app 533830), but it is not anonymously installable: its licence rides with the base game, so the machine has to sign in to SteamCMD as an account that owns Starbound. The Windows depots total about 320 MB, plus room for your universe, and the server needs one port.

Note: plenty of guides say the server tool installs anonymously. It does not. Anonymous SteamCMD answers No subscription for app 533830.

Installing the server

  1. Install SteamCMD.
  2. Install the server signed in as an account that owns Starbound: steamcmd +login yourname +app_update 533830 validate +quit
  3. Start it from inside its win64 or linux folder: win64\starbound_server.exe on Windows, linux/run-server.sh on Linux.
  4. Forward TCP port 21025 on your router and allow it through the firewall. Forward the same number on UDP as well, and set runQueryServer to true, if you want the server to answer server-list queries.

Note: the working directory matters. The sbinit.config file next to the executable points at ..\assets\, ..\mods\ and ..\storage\ using relative paths, so launching the server from anywhere else quietly loads a different asset and save tree.

Configuration

Settings live in storage/starbound_server.config, a JSON file the server writes for itself on first boot. Two things are worth knowing before you edit it:

  • If the file fails to parse, the server renames it to starbound_server.config.old and boots on stock defaults. The only sign is a warning in storage/starbound_server.log. A single stray comma undoes everything you configured.
  • Edit it while the server is stopped. Starbound rewrites the file on a clean shutdown, so changes made while it is running are lost.

Keys most people change: serverName, maxPlayers (default 8), gameServerPort, serverFidelity, allowAssetsMismatch and the scripting limits that large modpacks need.

Access and admin

Starbound has no plain server password. Access is accounts:

  • serverUsers maps an account name to a password and an admin flag, for example "fred" : { "admin" : true, "password" : "hunter2" }.
  • allowAnonymousConnections decides whether anyone without an account may join at all. Set it to false and only your listed accounts get in.
  • To become admin, give your own account "admin" : true, log in with it, then type /admin in chat.

Source RCON is available but off by default. Set runRconServer to true, give rconServerPassword a value and forward rconServerPort (21026 by default) if you want a remote console.

Mods

Mods are .pak files in the mods folder. There is one trap that catches nearly everybody:

Note: every Steam Workshop item publishes its payload under the identical filename contents.pak. Copy several into mods without renaming them and they overwrite each other, leaving exactly one mod installed. Rename each one to something unique first.

That collision, plus the fact that a bare dedicated server has no Steam subscription to download from, is the whole reason people report that large modpacks such as Frackin' Universe "do not work" on a dedicated server.

The instant alternative

If you would rather skip the licence juggling, the port forwarding and the mod renaming, rent a Starbound server from Survival Servers. Workshop mods install themselves from a browser in the Command Center, the config is rebuilt from your settings on every start so it cannot be broken by a typo, and backups and full FTP access are there from day one.