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.
- Place the copied world into the format/location expected by the current package; do not rename files blindly.
- 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. |
| 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. |
Do not publish these as universal facts
- A fixed
DSSettings.txtschema without checking the current package. StartNewGame=falseas a universal Star Rupture setting.- 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.