Current live baseline StarRupture admin guide: Manage Server flow, Password.json and PlayerPassword.json resets, DSSettings.txt save loading, and safer ways to
Current admin-command SERPs mix trustworthy server docs with fake UE-style cheat pages. Use this block to separate the confirmed server-management baseline from community-mapped commands before you touch a live save.
Current live baseline admin control is still server management plus config files. Search results also surface tilde-cheat pages, but community reports continue to show that many players cannot open a general developer console at all.
If the world is not started or the wrong save is loaded, command lists will not rescue the session. Connect first, use Manage Server to create or load the world, then test any admin actions on your exact build.
Community-mapped hosts commonly require encrypted JSON files in the server root, not a plain-text password pasted into a random config. Wrong casing or the wrong folder can make the server ignore both files.
On current community-mapped setups, DSSettings.txt usually controls StartNewGame, LoadSavedGame, and autosave timing. Stop the server first, back up the save, and confirm the actual file path before you flip any flags.
If you're searching for StarRupture admin commands or StarRupture console commands, start with this trust boundary:
The current live baseline is server management first, command list second. Official setup guidance confirms the dedicated server workflow, but there is no broad public developer console baseline we can safely treat like a universal cheat sheet. Most real admin work still happens through Manage Server, password files, DSSettings.txt, backups, and restarts.
This guide is built for the current live baseline, not copied UE-style console lists.
Password.json and PlayerPassword.json, and the values are usually encrypted password strings instead of plain text.DSSettings.txt is still the safest place to think about save-loading behavior and autosave timing, but you should cross-check your current install path before editing a live save./kick, /ban, and similar command examples as community-mapped admin actions, not guaranteed universal syntax.Many "admin command" problems are really "world never started" or "wrong save loaded" problems.
Use this baseline flow first:
If you skip the session step, the process can look healthy while players still see broken persistence or an empty world.
If you need the narrower setup path first, open:
Password.json and PlayerPassword.jsonOne of the biggest SERP problems in this topic is outdated advice that tells you to paste plain-text passwords into a random .ini.
On current community-mapped server setups, the more reliable baseline is:
Password.json for server management / admin accessPlayerPassword.json for the join passwordThat means a broken password workflow is often one of these:
Before you rotate passwords on a live server:
DSSettings.txt: Treat It as Save-Loading and Session ControlDSSettings.txt is still a core admin surface, but current public guides disagree on the exact path and syntax. The safest current framing is:
DSSettings.txt near the root of your server directoryOn community-mapped current builds, the file is often used for things like:
StartNewGameLoadSavedGameSaveGameNameExample structure to cross-check against your current host docs:
{
"SessionName": "MyStarRuptureServer",
"StartNewGame": "false",
"LoadSavedGame": "true",
"SaveGameName": "AutoSave0.sav",
"SaveGameInterval": "300"
}
Treat that as a community-mapped baseline, not a promise that every host exposes the exact same keys or file path.
| Task | First place to verify | Why |
|---|---|---|
| Start or load the world | Manage Server | Session state is more important than memorizing commands |
| Reset admin access | Password.json | Many hosts store the management password here |
| Reset join password | PlayerPassword.json | Keeps player access separate from admin access |
| Change save target or autosave timing | DSSettings.txt | Safer than guessing a command syntax from a copied list |
| Back up or restore the world | Filesystem or host panel | This is the real recovery path when a session breaks |
| Kick / ban / unban | Host docs or in-game admin UI | Syntax is often community-mapped and build-specific |
The safest current answer is:
So if you need a command list, use this workflow:
That is slower than copying a random list, but much safer.
Minimum recommended:
Servers can still degrade over long uptime windows, especially if the save grows or autosaves get heavy.
On Linux (systemd example):
# Restart daily at 04:00
0 4 * * * systemctl restart starrupture
On Windows, use Task Scheduler or your host panel to run the restart during off-peak time.
Server not showing in browser
Passwords do not work
Password.json vs PlayerPassword.jsonHigh lag spikes
Use the free StarRupture Production Calculator to get exact machine counts, power draw, and raw material requirements for any item.