How to Create a Starbound Server Guide

From Survival Servers
Jump to navigation Jump to search

Starbound has an official dedicated server, so you can run a universe that stays online for your friends to join any time.

Before you start

The dedicated server is a separate free download on Steam (app 533830), but it can't be installed anonymously. Its licence comes with the base game, so the PC has to sign in to SteamCMD with an account that owns Starbound. The Windows server files take 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 doesn't. Anonymous SteamCMD returns 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 show up in server lists.

Note: The folder you start it from matters. The sbinit.config file next to the server program points at ..\assets\, ..\mods\ and ..\storage\ with relative paths. Start the server from anywhere else and it loads a different set of assets and saves, with no warning.

Configuration

Settings are in storage/starbound_server.config, a JSON file the server writes on its first start. Two things to know before you edit it:

  • If the file has an error, the server renames it to starbound_server.config.old and starts with the default settings. The only sign is a warning in storage/starbound_server.log. A single stray comma undoes all your settings.
  • Edit it while the server is stopped. Starbound rewrites the file on a clean shutdown, so changes made while it's running are lost.

Settings 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's one trap that catches nearly everybody:

Note: Every Steam Workshop item uses the same file name, contents.pak. Copy several into mods without renaming them and they overwrite each other, leaving only one mod installed. Give each one a unique name first.

That's why people report that large modpacks such as Frackin' Universe "don't work" on a dedicated server. Mods overwrite each other, and a plain dedicated server has no Steam subscription to download them from.

The instant alternative

To skip the Steam sign-in, the port forwarding and the mod renaming, rent a Starbound server from Survival Servers. Workshop mods install from a browser in the Command Center. The settings file is rebuilt from your settings on every start, so a typo can't break it. Backups and full FTP access are there from day one.