StarRupture servers run one active save at a time. Which save is running is controlled either:
- from the client (Manage Server), or
- automatically via DSSettings.txt (recommended once you know what you’re doing)
This guide is written with LOW.MS hosting in mind. If you have not got a server yet, you can host your own StarRupture server with us.
Option A: Change saves using “Manage Server” (most common)
Use this when you want to:
- Start a brand-new world
- Switch to a different save
- Re-load the correct save after a restart
Steps
- In the LOW.MS Control Panel, ensure the server is Running
- Launch StarRupture
- Go to Manage Server
- Enter your Server IP and Port
- Enter your Server Management password
- Choose one:
- New Game to create a new save, or
- Load Game to select an existing save
- Click Start Game
- Return to main menu and join via Join Game → Dedicated Server
Tip: If you change saves, always join through Join Game after starting the session.
Option B: Use DSSettings.txt to auto-load a save (set-and-forget)
If your server restarts often (updates, scheduled restarts, crashes), DSSettings is a huge quality-of-life win because it can:
- auto-create a save (first run), or
- auto-load a named save every boot
See: DSSettings.txt Configuration Guide for examples.
Where saves live (useful for backups & troubleshooting)
On your server, saves are stored under:
StarRupture/Saved/SaveGames/<SessionName>/
The <SessionName> folder comes from your session name (or DSSettings SessionName).
Each save is a pair of files with the same name:
AutoSave0.sav(the world itself)AutoSave0.met(the save's metadata)
Always move, copy or back up both files together. A .sav without its matching .met will not load properly.
Upload your single player save to your server
You can carry on a solo world with friends by uploading it to your server.
On your PC, open your local save folder:
C:\Program Files (x86)\Steam\userdata\<your Steam ID>\1631270\remote\Saved\SaveGames(If Steam is installed somewhere else, look under that Steam folder instead.)
Find the save you want and copy both of its files (the
.savand the.met). If there are several, the most recently modified pair is your latest progress.In the LOW.MS Control Panel, Stop the server. Uploading while it is running can corrupt the save.
Open the File Manager (or connect via FTP) and go to
StarRupture/Saved/SaveGames/. Open your session folder, or create one named after your session if it does not exist yet.Upload both files into that folder.
Rename them to
AutoSave0.savandAutoSave0.met. Local games often number their saves fromAutoSave1, but the server looks forAutoSave0. If the folder already holds anAutoSave0pair you want to keep, download it first as a backup.Start the server, then load the save using Option A above (Manage Server → Load Game), or point DSSettings.txt at that session name.
Take your server world back to single player
It works the other way round too, so nothing is lost if you stop renting the server: the world you and your friends built can carry on as your solo game.
In the LOW.MS Control Panel, Stop the server so the latest progress is written to disk.
Open the File Manager (or FTP) and go to
StarRupture/Saved/SaveGames/<SessionName>/.Download the latest
.savand.metpair.Copy both files into your local save folder:
C:\Program Files (x86)\Steam\userdata\<your Steam ID>\1631270\remote\Saved\SaveGamesIf a save with the same name is already there, rename the downloaded pair first (for example
AutoSave5.savandAutoSave5.met, keeping the two names identical) so you do not overwrite your existing solo save.Launch StarRupture and load the save from the single player menu.
Tip: Download your save before cancelling your server. Once a service is terminated its files are removed.