Star Rupture Dedicated Server Setup
This is the practical setup path for the current Star Rupture dedicated-server tooling. Creepy Jar's own support article labels the feature experimental. Keep a backup and verify each launch after updates.
Verified starting point
- Steam server app:
3809400 - Executable named by the official guide:
StarRuptureServerEOS.exe - Official example:
start .\StarRuptureServerEOS.exe -Log -port=7777
Install the server package
Use the Steam dedicated-server tool or SteamCMD. Keep the install directory explicit and pull the dedicated-server app rather than the client:
force_install_dir C:\StarRuptureServer
login anonymous
app_update 3809400 validate
quitIf the files or executable differ from this example, compare the current package with the official article before changing the command.
Launch the EOS executable
@echo off
cd /d C:\StarRuptureServer
start .\StarRuptureServerEOS.exe -Log -port=7777The official article uses 7777 as an example and says the chosen port must match the forwarded/router/firewall port. It does not establish a universal Star Rupture query or RCON table.
Run the first external join test
- Allow the chosen port in the host firewall.
- Forward it to a stable LAN address when home-hosting.
- Confirm the process is listening.
- Test from outside the host network.
- Record the build, endpoint, and result.
Managed hosting should expose the external address and port in its panel. Do not copy ARK, Terraria, or generic Unreal port tables into this game.
Check persistence before inviting the group
- Launch a blank test world once.
- Join with one trusted client and create a harmless test change.
- Stop cleanly, back up the actual save path, and restart.
- Confirm the same world is loaded.
- Only then import an existing world or invite the full crew.
The manager or package determines the data path. Do not assume a guessed Game.ini or DSSettings.txt will be read.
Steam account caveat
Creepy Jar notes that launching through the Steam client on another PC can be affected by the same-account limitation. The batch/SteamCMD route is the better starting point for an unattended machine. Capture logs before changing several variables at once.
Update and rollback
- Read the official announcement stream.
- Stop cleanly and copy the active save.
- Update the same server app and record the new build.
- Test world loading, one join, saving, and restart persistence.
- Keep the pre-update copy until a real session succeeds.