Setting Up Admins and Using Console Commands
How to grant admin access via adminlist.txt and use remote console commands to manage your server.
Overview
DST server administration is handled through two mechanisms: adminlist.txt for granting in-game remote console access, and the server console itself (accessible via your panel) for running server commands directly. Admins with in-game access can run the same commands as the server console.
adminlist.txt
The adminlist.txt file lives in the cluster root:
/dst/adminlist.txt
Add one identifier per line. Accepted formats:
- KleiID:
KU_abc123def456 - SteamID64:
76561198012345678
Example file:
KU_abc123def456
KU_xyz789ghi012
76561198012345678
Changes to adminlist.txt require a server restart to take effect.
Finding a Player's KleiID
When a player connects to your server, their KleiID is printed to the server console:
[00:05:12]: [Shard] Account 'PlayerName' [KU_abc123def456] connected
Copy the value in square brackets. This is the KleiID to add to adminlist.txt.
In-Game Admin Console
Once listed in adminlist.txt, a player can open the remote console in-game by pressing the tilde key (~) while connected. This opens a console input where they can run Lua commands against the server.
Server Console Commands
The following commands are the most commonly used for server management. These can be run from either the panel console or the in-game admin console.
Announce a message to all players:
c_announce("Server restart in 10 minutes.")
Save the current world state:
c_save()
Gracefully shut down the server:
c_shutdown()
Roll back the world by N days:
c_rollback(1)
This rolls back one day. See the rollback article for backup recommendations before running this command.
Pause the simulation:
c_pause()
Resume the simulation:
c_resume()
Shard Scope
Commands execute on the shard whose console you run them from. If your cluster has both Master and Caves shards and you run c_save() in the Master console, only the Master shard saves. To save both shards, run c_save() in each shard's console separately.
This is especially important for c_shutdown() and c_rollback() — you must run these on each shard if you want both to be affected.
Panel Console vs. In-Game Console
Both consoles accept the same Lua commands. The panel console is accessible whether or not any players are connected, making it better suited for maintenance tasks like saves and shutdowns. The in-game admin console is more convenient for admins who are already in the game and need to respond quickly.
Security Notes
adminlist.txt grants full Lua access to the server process. Do not add untrusted players. An admin can run arbitrary Lua, including commands that wipe worlds or crash the server. Treat admin access with the same caution as server console access.