Stationeers admin works through a shared secret. Set it on the server, use the same value in game, and your commands are executed by the server.
Set the admin secret
- Stop the server.
- In the panel open Files and edit
settings.xml. - Find the auth secret line. On a new server it is often present but empty:
Replace it with an open and close pair holding your secret:<ServerAuthSecret /><ServerAuthSecret>a-long-password-here</ServerAuthSecret> - Save and start the server.
Leaving the self closing tag in place is the usual mistake. It must become a proper pair or the value is not read.
Keep this different from the join password. Anyone with the secret can run server commands.
Run commands in game
Join the server, open the in-game console and prefix server commands with serverrun:
serverrun save "myworld"
serverrun kick playername
serverrun ban playername
Your client authenticates using the same secret, which you set in the client's settings so it is sent with the command.
Commands worth knowing
save "savename"writes the world immediately. Run this before any manual stop.kickandban, with the player name.listplayersto see who is connected.noticeto broadcast a message before a restart.
The panel console
The panel Console section is attached to the server process directly, so it accepts server commands with no secret at all and shows everything the server logs. For a forced save before a restart, it is the fastest route.
Always save before stopping
Stationeers writes the world on the save interval and on a clean shutdown. Run a save, then use the panel's Stop and wait for the server to report it is offline. Killing the process loses everything since the last save, and in Stationeers that can be a lot of atmospheric work.
If commands are refused
- The secret must match exactly on both sides, including case.
- Check the tag became a proper open and close pair in
settings.xml. - The server must be restarted after the edit.
- If your change vanished, you edited the file while the server was running.





