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.
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 | Identify the active path from the manager, package, or logs; back it up while stopped. | A guessed Game.ini or DSSettings.txt is read automatically. |
| Access | Use controls exposed by the current manager and test a second account. | Unverified whitelist, admin-password, or command syntax is supported. |
| 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 and Hotfix 0.3.2 followed on 4 September. 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.