Stationeers Server Console Commands (Save, Kick, Ban, Pause)
Useful Stationeers dedicated server console commands: save, status, kick, ban, say, pause, cleanupplayers, deletelooseitems, storms and serverrun from a client.
Updated Oct 7, 2026 · 5 min read
On this page
A Stationeers dedicated server takes commands typed straight into its console: save to save the world, status to see the server state and players, kick <clientId> and ban <clientId> to remove players, say to message everyone, pause true to freeze the game, and cleanupplayers to clear dead or disconnected bodies. Type help list to see everything your build supports. Players can run the same commands from their own game with serverrun <command> if the server and client share a ServerAuthSecret.

Two ways to run commands
In the server console. Anything you type into the dedicated server's console window runs on the server directly. On a home server that is the terminal or command window running rocketstation_DedicatedServer. On a hosted server it is the live console in the control panel.
From a client with serverrun. RocketWerkz added a way for players to send commands from their own game:
- The server has a
ServerAuthSecretset in itssetting.xml(or on the-settingslaunch line). - The player sets the exact same secret in their own client settings.
- In the in game console, they prefix commands with
serverrun:
serverrun save "Mars Base"
serverrun kick 76561198000000000
Messages with a missing or wrong secret are rejected. Some community guides also note the game gives little or no feedback in game when the command works, so check the result (for example, the save file time) rather than waiting for a message.
The server console is the more dependable of the two, and it is where we will work for the rest of this guide.
Finding the full list
The command list changes between versions, so start every session on a new build with:
help list
That prints every command. For the details of one:
help save
Everyday commands
| Command | What it does |
|---|---|
save |
Saves the current world |
save <name> |
Saves to a named save |
save list |
Lists saves |
status |
Shows server state and connected players |
say <message> |
Sends a message to all players |
pause true / pause false |
Pauses and unpauses the game for everyone |
version |
Shows the game version |
quit |
Quits the server immediately, without prompts |
Save before you quit. quit does what it says, immediately. If you stop the server this way after an hour of work since the last autosave, that hour is gone. Make save a habit before quit, before restarts and before updates.
Kicking and banning
| Command | What it does |
|---|---|
kick <clientId> |
Removes a player from the server instantly. They must be in the world |
ban <clientId> |
Bans a player. Works even when they are offline |
ban refresh |
Reloads the ban list without restarting |
The client ID is the player's Steam ID, shown in status and in the log when they connect. Bans go into a blacklist file in the save path. To unban, remove the ID from that file and run ban refresh.
Cleaning up the world
Long running bases collect clutter that costs the server time every tick.
| Command | What it does |
|---|---|
cleanupplayers dead |
Removes dead player bodies |
cleanupplayers disconnected |
Removes bodies of players who left |
cleanupplayers all |
Both |
deletelooseitems |
Deletes every item lying in the world that is not in a slot |
cleanupplayers disconnected is the friendly one to run after a busy session, especially on servers where people drift in and out. deletelooseitems is powerful: every dropped ingot, ore chunk and forgotten tool on the floor goes, including things a player meant to come back for. Warn the crew, save first, and take a backup.
World and weather
| Command | What it does |
|---|---|
stormbegin / stormend |
Starts or stops a weather event |
suntime <0 to 1> |
Sets the time of day. 0 is sunrise, 0.5 is sunset |
regeneraterooms |
Rebuilds the room data for the world |
difficulty <name> |
Changes difficulty |
stormend is the polite way to rescue a crew caught outside on Mars. regeneraterooms is a repair tool for when a sealed room stops reading as pressurised after a big rebuild; save first.
Settings from the console
The settings command reads and changes values in the server's settings file while it runs:
settings list
settings print
settings ServerMaxPlayers 6
Values you change this way are written to the settings file, but some only take effect after a restart. If a server panel manages those values, it may overwrite them at the next start, so change them in the panel instead.
A good routine for a long running station
statuswhen you log in, to see who is on.saya warning before anything disruptive.savebefore cleanups, updates or restarts.cleanupplayers disconnectedafter busy sessions.- Back up the save folder weekly. Our backup guide shows the habit.
Commands on a hosted Stationeers server
On a GamezServers Stationeers server, type any of these into the live console in the control panel. The panel also holds the map, start location and condition, difficulty, station name, auto save and its interval, max players and Auto Pause, so day to day settings do not need the settings command at all. One click backups pair well with deletelooseitems and regeneraterooms. If you are moving an existing base onto the server, see moving a Stationeers save to a dedicated server.
FAQ
How do I save a Stationeers dedicated server?
Type save in the server console. Add a name to save under a different save.
How do I kick or ban a player in Stationeers?
Use kick <clientId> or ban <clientId> in the server console, with the player's ID from status.
Can I run server commands from my own game?
Yes, with serverrun <command>, if your client and the server have the same ServerAuthSecret.
How do I pause a Stationeers server?
Type pause true in the console, and pause false to resume. For automatic pausing when nobody is online, use the Auto Pause server setting.
Skip the setup. Your own Stationeers server.
Then $9.99/mo. Just trying it? $2.50 for 3 days