Star Rupture Local-to-Dedicated Save Transfer
Players ask how to keep an existing local world when moving to a dedicated server. The safe answer is a controlled file transfer, not a promise that a named “SaveSync” setting or universal save path exists in every build.
Before touching files: the dedicated server is experimental. Keep the original local save untouched and make a second copy for the import test.
Local-to-dedicated workflow
- Finish the local session and exit normally.
- Make a dated copy of the complete local save folder or archive.
- Launch a blank dedicated world once so the server creates its own data structure.
- Stop the server and identify its active save directory from the manager, working directory, or logs.
- Copy the world folder, with its
.savand.metfiles together, intoStarRupture/Saved/SaveGames/. The folder name is the session name. - Point
DSSettings.txtin the install folder at it:SessionNameset to that folder name,"LoadSavedGame": "true","StartNewGame": "false","SaveGameName": "AutoSave0.sav"(the file's own name). The format is on save persistence after restart; build 25336501 loaded a world this way on 2026-09-24. - Start privately and check the log for load errors.
- Join with one trusted account, check the base and inventory, disconnect, and restart.
- Only replace production after the staged copy survives a restart.
Dedicated-to-local rollback
- Stop the server cleanly and copy the full world.
- Record the build and keep the server archive as rollback.
- Use the current local game's supported open/import workflow on a separate profile.
- If the local client does not recognize the archive, do not alter the original or invent a conversion step.
When the imported world looks new
| Symptom | Check first |
|---|---|
| Blank world | Wrong working directory, save, or instance selected, or SessionName not matching the folder. If the log shows LoadGameNoLevelLoad failed to load save, the file could not be read and the server opened a fresh world instead: stop it before anyone plays and restore the copy. |
| Progress missing | The save may contain more than one file; restore the complete copy. |
| Server will not start | Return to the clean server-generated copy and inspect the log. |
| Players cannot join | Check build compatibility and endpoint separately from save integrity. |
Still not established
- Built-in cloud sync, checksum, or host-migration behavior not described by current official documentation.
Pair this with restart persistence, backups, and configuration checks. For managed migration help, launch Star Rupture hosting with Supercraft.