STARRUPTURE · SERVER GUIDE · NOVEMBER 2026

StarRupture Server Settings and Config Files Explained

A StarRupture dedicated server has a small set of settings spread over three files and one in-game screen. This guide explains where each one lives, what it actually changes, and which mistakes cost you a world.

Where settings live

Almost everything lives in three places: the batch file for startup flags, DSSettings.txt for world loading and autosave timing, and the encrypted password files beside the server executable. The in-game Manage Server screen is the fourth piece, but it only works while the remote-control interface is enabled.

The setting that loses worlds

StartNewGame must only be "true" for the first boot of a brand new world. Leave it on, and every restart tells the server to generate a new session again instead of loading the existing save.

The security setting

-RCWebControlDisable and -RCWebInterfaceDisable shut off the TCP remote-control interface used by Manage Server. That interface has no authentication of its own, so if it is reachable from the internet it can be abused to change passwords, tamper with saves or crash the server.

What you cannot change

Dedicated servers run on the 0.3.5 branch until Creepy Jar brings them to Update 3. There is no server-side setting for the player cap, and Update 3 Custom Game options do not apply to dedicated servers yet.

Before you change anything: dedicated servers are on 0.3.5 for now

StarRupture dedicated servers launched as an experimental feature on 6 January 2026. Active support ended on 20 October 2026, and Update 3 released on 19 November 2026 without dedicated server support. Hotfix 0.3.5 (5 October 2026) is the current dedicated-capable version, available on Steam as the v.0.3.5_for_ds branch. On 20 November 2026 Creepy Jar reversed its decision and said it will restore full dedicated server functionality in a future patch for Update 3, with no date yet.

Until that patch arrives, what you can set is what this guide covers: startup flags, the five DSSettings.txt keys, and passwords. Settings may change once dedicated servers move to Update 3. Clients and server must be on the same build to connect, so a dedicated server on 0.3.5 needs players on that same branch too.

Where every StarRupture server setting lives

Everything you can change sits in three files next to the server executable, plus one optional control screen inside the game.

Where every StarRupture server setting lives
Three files in the server root, next to StarRuptureServerEOS.exe
Launch line
SRServerWithLog.bat
-Log · -port=7777
-RCWebControlDisable
-RCWebInterfaceDisable
Port, logging and remote control
World and autosave
DSSettings.txt
SessionName · SaveGameInterval
StartNewGame · LoadSavedGame
SaveGameName
Which world loads on boot
Passwords
Password.json (admin)
PlayerPassword.json (join)
Encrypted, set in Manage Server
In the game: Manage Server
  • Enter the server IP:port
  • Set the admin and join passwords
  • New Game or Load, then Start Game
Works only while the remote-control interface is on. With the two disable flags, DSSettings.txt loads the world instead.
The world itself lives in StarRupture/Saved/SaveGames/<SessionName>/ as AutoSave0.sav and AutoSave0.met.
File or place Location What it controls How you change it
SRServerWithLog.bat Server root, next to StarRuptureServerEOS.exe Startup flags such as logging, game port and whether the remote-control interface is disabled Edit the batch file while the server is stopped, then start the server again
DSSettings.txt Server root, next to StarRuptureServerEOS.exe Which session folder to use, whether to start a new world or load an old one, which save file to load, and the autosave interval Create or edit the file as valid JSON; some host panels generate it for you
Password.json Server root, next to StarRuptureServerEOS.exe Server management/admin password Set in Manage Server; reset by deleting the file while the server is stopped
PlayerPassword.json Server root, next to StarRuptureServerEOS.exe Player/join password Set in Manage Server or your host panel; reset by deleting the file while stopped
SaveGames/<SessionName>/AutoSave0.sav and .met Under StarRupture/Saved/SaveGames/<SessionName>/ The actual world state bound to that session name Created by the server when the world is saved; uploaded manually when importing a save
Manage Server in game Main menu on a client PC Remote start, load and password setup while the remote-control interface is enabled Connect to the server by IP and port, then manage it from inside the game

The useful mental model is simple: the batch file starts the server process, DSSettings.txt tells it which world to bind to on boot, the save files hold the world itself, and the password files decide who can join and who can administer the server.

Two ways to run it: Manage Server mode or DSSettings mode

Run mode How the world starts Security position Best use
Manage Server mode The server boots and waits; a player connects through Manage Server to start a new game or load a save Uses the built-in TCP remote-control interface Short-lived private testing on a machine not exposed to the internet
DSSettings mode The server reads DSSettings.txt on boot and starts or loads the named world automatically Remote-control interface can be disabled with startup flags Any rented or internet-reachable server

The remote-control side is the important bit. Manage Server talks to the server’s built-in Unreal Remote Control web interface over TCP. On recent builds that is TCP 7777; on older builds it used TCP 30010 for HTTP and TCP 30020 for WebSocket. That interface has no authentication of its own, so if someone can reach it they can interfere with administration: change admin or join passwords, tamper with saves, or crash the server.

The mitigation is plain: add -RCWebControlDisable and -RCWebInterfaceDisable to the launch line, and never forward TCP 7777, 30010 or 30020. The trade-off is also plain: Manage Server stops working by design, so world loading must come from DSSettings.txt instead. For any server reachable from the public internet, that is the better trade. It removes a control path, but it also removes the exposed TCP surface that causes the problem.

If you rent a server, check that your provider has the interface disabled; most did this in early 2026. If a panel offers a switch to re-enable in-game server management, treat that as re-opening a known risk, not as a harmless convenience.

DSSettings.txt explained, key by key

This file does not exist by default. You create it yourself, or your host’s panel generates it. It must sit next to StarRuptureServerEOS.exe, and it must be valid JSON with straight quotes and commas in the right places.

{
  "SessionName": "MyServer",
  "SaveGameInterval": "300",
  "StartNewGame": "false",
  "LoadSavedGame": "true",
  "SaveGameName": "AutoSave0.sav"
}
Key Value What it does Why it matters / common mistake
SessionName String, for example "MyServer" Names the session and the save folder under StarRupture/Saved/SaveGames/<SessionName>/ This is how the server decides which folder to look in. Change it, and you point the server at a different world folder. The old world is not deleted; you have just stopped pointing at it. Keep it to 20 characters or fewer.
SaveGameInterval String seconds, default "300" Sets how often the server autosaves Shorter intervals reduce rollback after a crash but increase save activity. Longer intervals reduce save frequency but increase worst-case progress loss after a bad exit.
StartNewGame "true" or "false" Tells the server to generate a new world on startup This is the setting that catches people. It is only for the first boot of a new world. Leave it on, and every restart asks the server to create a fresh world again.
LoadSavedGame "true" or "false" Tells the server to load an existing save file from the selected session folder Use this for normal day-to-day restarts. Never set this and StartNewGame to "true" together.
SaveGameName Usually "AutoSave0.sav" Chooses which save file inside the session folder to load Normally this stays at AutoSave0.sav. If the filename does not match what is actually in the folder, the server cannot load that save.
  • All five values are strings, so they stay inside quotes.
  • Watch the Windows extension trap: DSSettings.txt can easily become DSSettings.txt.txt.
  • Always stop the server before editing. A clean Ctrl+C shutdown lets it close gracefully instead of leaving you dependent on the last autosave.
  • Some host panels rewrite DSSettings.txt each time the server starts. On those services, change the panel value, not the file, or your edit will be replaced on boot.

SaveGameInterval: what it trades

Use the autosave interval to balance two costs: disk writes now versus rollback later. Each save means the server has to serialise the current world state and write it to disk. On a larger factory world that can mean more frequent brief hitches if you save very often, because the work is happening repeatedly. A longer interval reduces that churn, but after a crash the maximum lost progress is the length of the interval.

SaveGameInterval and the most progress a crash can cost
Value in DSSettings.txt (seconds) → worst-case lost play time
“120”
2 minutes
“300” · default
5 minutes
“600”
10 minutes
“900”
15 minutes
Shorter intervals mean more frequent disk writes and, on large factory worlds, more frequent brief save hitches.
Each step up halves how often the server saves but widens the rollback window by the same amount.

300 is a sound default because it keeps rollback bounded without turning every few minutes into a save-heavy cycle. If players complain about short pauses exactly when saves happen, a longer interval can help. If the bigger problem is losing too much work after an unexpected stop, a shorter interval helps instead. For planned maintenance, always stop cleanly with Ctrl+C so you are not relying on the timer at all.

How the server decides which world to load on boot

The boot order matters more than the settings list. This is the part that decides whether the server returns to the right world or comes back empty.

What the server does when it boots
StarRuptureServerEOS.exe starts from SRServerWithLog.bat
Is DSSettings.txt in the server root?
No
Empty start mapThe server waits until someone uses Manage Server to start or load a world.
Yes
Is StartNewGame “true”?
Yes
New worldA fresh world is generated in SaveGames/<SessionName>/. Set it back to “false” after the first save.
No
Is LoadSavedGame “true”?
No
Nothing to loadSet LoadSavedGame “true” so the server binds to your save.
Yes
Does SaveGameName exist in the SessionName folder?
No
Wrong folder or fileCheck the SessionName spelling and that AutoSave0.sav and .met are there.
Yes
Your world loads and autosaves every SaveGameInterval seconds
Most “my world vanished” reports end at one of the orange boxes: a flag left on, or a SessionName that points at a different folder.

Without DSSettings.txt, the server starts to an empty start map and waits for someone to create or load a world through Manage Server. With DSSettings.txt, it reads SessionName, then either generates a new world or loads the named save file from that session folder.

  1. First boot of a new world: stop the server, set StartNewGame to "true" and LoadSavedGame to "false", then start it. Join the server, press Esc and Save so the world is actually written into SaveGames/<SessionName>/. Disconnect, stop the server, then flip the file back to StartNewGame "false" and LoadSavedGame "true" before the next restart.
  2. Load an existing world after restart: keep the same SessionName, set LoadSavedGame to "true", StartNewGame to "false", and leave SaveGameName at "AutoSave0.sav" unless you have a specific different file. On boot, the server looks in that session folder and binds itself to that save.
  3. Upload a single-player or co-op save: take the source files from Steam\userdata\<SteamID>\1631270\remote\Saved\SaveGames or C:/Users/<you>/AppData/Local/StarRupture/Saved/SaveGames. Create SaveGames/<SessionName> on the server, upload the .sav and matching .met, rename them to AutoSave0.sav and AutoSave0.met, then start with LoadSavedGame "true" and StartNewGame "false".

SessionName is also how you keep several worlds side by side. Each session name points to a different save folder, so switching the name switches the world the server will load next boot. That is useful, but it also means a typo looks exactly like “my world vanished” when the server is really just looking in the wrong folder.

The launch line and the two password files

SRServerWithLog.bat flag by flag

Flag What it changes Why it matters
-Log Opens server logging Keep this on. The log tells you whether the server loaded a save, started a new world, complained about remote control, or bound to the wrong port.
-port=7777 Sets the game network port This must match the UDP port you forward in the router or firewall. If the file says one port and the network forwards another, players cannot reach the server correctly.
-RCWebControlDisable Disables the remote-control layer used by in-game management This closes part of the exposed TCP control path. The cost is that Manage Server no longer works.
-RCWebInterfaceDisable Disables the web interface side of remote control Always add it together with -RCWebControlDisable. The two flags are one fix: the first stops remote commands, the second stops the web interface that serves them.
start "" .\StarRuptureServerEOS.exe -Log -Port=7777 -RCWebControlDisable -RCWebInterfaceDisable

The batch file is small, but it decides two things the server cannot recover from later in boot: which network port to bind to, and whether remote management exists at all. After each game update, re-check the file. Updates can reset the command-line arguments, which is why port changes and hardening flags sometimes “mysteriously” disappear after patching.

There is also a Steam account wrinkle. If the server is launched from the Steam client, you cannot run the server tool and the game at the same time on two different PCs with the same Steam account. The practical way around that is the batch-file or SteamCMD route. If the server was installed through SteamCMD, Steam must be closed or logged out on the server machine before you can manage it in game.

Passwords: admin and join

StarRupture uses two separate passwords: one for server management and one for players joining the world. They are stored as encrypted files beside the executable: Password.json for admin access and PlayerPassword.json for the join password. Because they are encrypted, you cannot just type a new plain-text password into those files.

Normally you set both from Manage Server. To reset one, stop the server and delete the matching file, then start the server and set it again. Deleting either password file does not delete the world. If no join password is set, anyone who knows the public address can connect. On a hardened rented server where Manage Server is disabled, set or change the join password from your host’s panel instead.

Ports and what to forward

There is only one game traffic port to think about, and one mistake to avoid.

What to forward, and what to keep closed
Game traffic: forward this
Players
Join Game → Dedicated Server
UDP 7777
Your server
Remote-control interface: never forward
The internet
TCP 7777, 30010, 30020
Closed at the router or firewall
Use the same UDP port number you set with -port. Recent builds serve the remote-control interface on TCP 7777; older builds used TCP 30010 and 30020.
Players only ever need the UDP game port. Nothing on the TCP side needs to be reachable from outside.

Forward UDP 7777, or whatever value you set with -Port. Do not forward TCP 7777, TCP 30010 or TCP 30020. The UDP port is for actual game traffic; the TCP ports belong to the remote-control interface that should stay closed on a public server.

Players join by public IP:port through Join Game > Dedicated Server; there is no browser listing to discover your server automatically. If you are self-hosting and need the router or firewall basics, read our guide to self-hosting a game server and then make sure the forwarded UDP port matches the one in the batch file exactly.

What you cannot set on a dedicated server

The dedicated server branch is sparse by design, and it has had no updates since 0.3.5. That means there are limits you cannot tune around with config edits.

Which settings exist where
SettingDedicated server (0.3.5)Co-op on Update 3
Loads the world on boot with nobody logged inYesNo
Friends join through Steam invitesNoYes
Separate admin and join passwordsYesNo
World online without the hostYesNo
Custom Game options (20+ rules)NoYes
More than 4 playersNoNo
Update 3 released on 19 November 2026 without a dedicated server. Dedicated servers and their players stay on the 0.3.5 branch until Creepy Jar’s promised patch.
The dedicated server gives you control over the world file; co-op gives you control over the rules.
  • The online cap is up to 4 players including the host. There is no setting that raises it.
  • Dedicated servers on 0.3.5 do not have world-rule or difficulty switches beyond the small dedicated config surface described above.
  • Update 3 Custom Game options are for single-player and co-op on the newer version, not for dedicated servers. Those options include things like building costs, building stability, power requirement, enemy behaviour, survival depletion and fire wave frequency, but they do not carry over to the dedicated branch.
If you need… Stay on dedicated 0.3.5 Move to co-op Update 3
A world that stays online without a player hosting Yes No, co-op depends on the host session
The current dedicated config and familiar server files Yes No
Update 3 Custom Game rules No Yes
Update 3 features today No Yes

If the priority is an always-on world that people can join by address, keep the dedicated server on 0.3.5 and accept that the configuration is fixed until dedicated support reaches Update 3. If the priority is the newer rule set from Update 3, move the group to co-op instead and follow the process for joining a StarRupture server and playing with friends. If you are still deciding where to rent, our StarRupture server hosting comparison compares UK locations, prices and what each plan includes.

Need a rental that does not hide the basics?

Look for clear control over the startup line, a visible place to manage DSSettings.txt, and a panel that keeps the remote-control interface disabled unless you knowingly turn it back on.

Compare StarRupture hosts

Symptom, likely cause, first fix

Symptom Likely cause First fix
Server comes back with a fresh world after restart StartNewGame was left "true", or SessionName now points at a different folder Stop the server, set StartNewGame to "false", LoadSavedGame to "true", and restore the correct SessionName
Server is online but nobody can play; it sits on an empty start map No world was loaded on boot If remote management is still enabled, start or load a world through Manage Server; otherwise create DSSettings.txt so the server loads a world automatically
Edit to DSSettings.txt does nothing Invalid JSON, wrong filename such as .txt.txt, or the host panel rewrote the file on startup Check quotes and commas, confirm the exact filename, then change the value in the panel instead of the file if your host regenerates it
Manage Server no longer connects The RC disable flags are active Use DSSettings.txt for world loading and your host panel for join-password changes; do not reopen the interface on a public server just for convenience
Join password is refused, or the admin password is forgotten The encrypted password file holds a different value than expected Stop the server, delete PlayerPassword.json for the join password or Password.json for admin, then start and set the password again
Passwords changed by themselves, or the log shows LogRemoteControl: Warning: Deserialization error ... before crashes The TCP remote-control interface is exposed and being abused Add both RC disable flags, stop forwarding TCP 7777/30010/30020, then reset the passwords
Port change is ignored after an update The update reset SRServerWithLog.bat Re-edit the batch file, put the chosen -Port back, and verify the same UDP port is forwarded
Cannot manage the server while Steam is open Steam is still logged in on the server machine, or the same account is in use the wrong way Close or log out of Steam on the server machine and use the batch-file or SteamCMD launch route instead of the Steam client
Uploaded save is not loading Wrong folder, wrong session name, missing matching .met, wrong filename, or load flags still set for a new world Put the files in SaveGames/<SessionName>, rename them to AutoSave0.sav and AutoSave0.met, then boot with LoadSavedGame "true" and StartNewGame "false"
Players cannot connect after switching branches Client and server builds do not match Make sure both sides are on the same build; dedicated servers remain on the v.0.3.5_for_ds branch, not Update 3

StarRupture server FAQ

Where is the StarRupture server config file?

There is no single all-in-one config. The main server settings file is DSSettings.txt in the server root beside StarRuptureServerEOS.exe, but the launch line lives in SRServerWithLog.bat and passwords live in separate encrypted files. If you rent a server, the panel may write DSSettings.txt for you from its own settings page.

What does DSSettings.txt do?

DSSettings.txt tells the dedicated server which session folder to use, whether to create a new world or load an existing one, which save file to load, and how often to autosave. In practice, it is the file that turns the server from “waiting for someone to manage it in game” into “boots directly into the correct world every time”.

How do I change the autosave interval on a StarRupture server?

Edit SaveGameInterval inside DSSettings.txt while the server is stopped. The value is in seconds and is stored as a quoted string, with "300" as the default. Shorter intervals reduce rollback after a crash, but they make the server write saves more often and can mean more frequent brief hitches on larger worlds.

Can I increase the player limit on a StarRupture server?

No. The online cap is up to 4 players including the host, and there is no dedicated server setting that raises it. If a panel seems to offer a player-cap box, that does not create a supported higher limit on this game.

Do Update 3 custom game settings work on a dedicated server?

No. Update 3 Custom Game options belong to the newer single-player and co-op path, not the dedicated server branch. For now dedicated servers remain on the separate 0.3.5 branch, so those rule changes are not something you can enable through DSSettings.txt or the launch line.

More StarRupture server help

Get your friends connected, compare hosts, or brush up on running a server at home.

Steps, file names and launch flags follow Creepy Jar’s official dedicated server setup article and Steam announcements, and reflect StarRupture dedicated servers on version 0.3.5 as of 21 November 2026. Host panels label the same settings in different ways; if your panel writes DSSettings.txt for you, follow the panel where it differs from this guide.

Similar Posts