Star Rupture Server Configuration
Searchers often find long Star Rupture INI examples that look authoritative but are not backed by the current setup article. This guide gives a safe configuration workflow and marks the boundary between a documented launch option and a setting that must be verified in the installed manager or package.
Confirmed by the official article: the experimental server tool, StarRuptureServerEOS.exe, and a -Log -port=7777 launch example. A complete public table of ServerName, AdminPassword, difficulty, SaveSync, or web-panel keys is not published there.
Confirmed in the shipped build (dedicated server build 25336501, observed 2026-09-24): the server reads DSSettings.txt from its install folder on every boot, with the keys SessionName, SaveGameInterval, StartNewGame, LoadSavedGame and SaveGameName, all string values. Passwords are set from the game client's Manage Server screen and kept encrypted in Password.json and PlayerPassword.json. The file format is on save persistence after restart.
Configuration audit
| Area | Safe action | Do not assume |
|---|---|---|
| Binary | Use the executable present in the current server package. | An older StarRuptureServer.exe is interchangeable with the EOS binary. |
| Port | Keep launch port, firewall, router/provider mapping, and client entry consistent. | A generic 27015/27016 table applies. |
| World and saves | Name the world folder under StarRupture/Saved/SaveGames as SessionName in DSSettings.txt next to the executable; back the world up while stopped. | A restarted server loads the last world by itself when that file is missing (it waits for Manage Server instead). |
| Access | Set the admin and join passwords from the game client's Manage Server screen, then test with a second account. | A -ServerPassword launch option or a password key in a config file sets them. |
| Gameplay | Change one supported setting, restart, and test. | Difficulty multipliers from another Unreal game belong here. |
Known-good launch baseline
.\StarRuptureServerEOS.exe -Log -port=7777Add only an option confirmed by the current package or official documentation. Save the exact command in your maintenance notes.
Safe setting-change workflow
- Copy the current save and record the build.
- Record the launch command and manager values.
- Change one setting group.
- Restart cleanly and inspect the log.
- Join and test the intended behavior.
- Keep the old copy until the group has played successfully.
When a setting is ignored
- Check that you edited the active instance, not a template.
- Check whether the panel overwrites manual edits at start.
- Confirm the server was stopped before editing.
- Compare the process working directory with the path inspected.
- Return to the known-good baseline if the world stops loading.
For a wrong world after reboot, use restart persistence. For a moved world, use save transfer.
Planned updates are not configuration APIs
Update 2: Quality of Life shipped on 2 September 2026, with hotfixes on 4 September (0.3.2) and 14 September (0.3.3). A shipped update is still not a configuration API: a production or building feature becomes a server setting only when the build and its documentation expose one, so check the official setup article before adding a key from a patch note.
References
Host Star Rupture with Supercraft when you want launch values, restarts, and backups in one panel.