Server management
StarRupture has two systems for managing a server - an in-game server manager, and configuration files on the server.
AMP’s uses and controls the server’s configuration files. The in-game server manager is disabled and cannot be used.[1] (The server’s “admin password”, which is otherwise used to connect to the server manager, is therefore redundant.)
All configuration is done in AMP’s settings under Configuration>StarRupture.
Creating a world
When a StarRupture server is first created, there is no world on the server.
It is not possible to join a server that has no world created.
A new world can be created by:
- enabling Start New Game
- disabling Load Save Game (if it is otherwise enabled)
Then, when in-game, a first save of the world can be generated by joining the server, clicking ESC, then Save. More information is here.
Generating a first save enables the server’s automatic backup system, and also allows the world to be loaded again on a later restart, rather than a new world being generated each time.
Loading an existing world
Once a world has been created and a save file generated, that world can be loaded the next time the server is started, if desired.
This can be done by:
- disabling Start New Game
- enabling Load Saved Game
- setting Save Game Name to the save file name to be loaded
- setting Session Name to the session name (world name) to be loaded
Worlds and saves are stored in StarRupture/Saved/SaveGames.
More information is here.
Joining the server
StarRupture servers can only be joined in-game using the public (external) IP of the server. This is a game design.
For servers that are hosted within a NAT network (most home-hosted servers), this requires:
- port forwarding on the network’s router; and
- (for game clients within the network to be able to connect to the server) NAT hairpin/loopback to be enabled on the router
Note that for home internet connections that are on CG-NAT (Carrier Grade Network Address Translation), port forwarding is not possible.
The server manager automatically cannot be used if configuration files are used. In addition, the entire server manager has been disabled in AMP due to security vulnerabilities discovered in the system. ↩︎