Understanding the DST Server Directory Structure
A map of every file and folder in a DST server installation and what each one controls.
Overview
A DST server installation has a specific directory layout that must be respected for the server to function correctly. Understanding where each file lives is essential before editing configuration, installing mods, or performing a world wipe.
Full Directory Tree
/dst/
├── cluster_token.txt # Klei authentication token
├── cluster.ini # Cluster-wide settings
├── adminlist.txt # KleiIDs/SteamID64s with admin privileges
├── whitelist.txt # KleiIDs/SteamID64s allowed to connect (requires mod)
├── dedicated_server_mods_setup.lua # Mod download list (Steam Workshop IDs)
└── Cluster_1/
├── Master/
│ ├── server.ini # Master shard settings (port, shard identity)
│ ├── leveldataoverride.lua # World generation overrides for overworld
│ ├── modoverrides.lua # Mod enable/configure for Master shard
│ └── save/ # World save data for Master shard
└── Caves/
├── server.ini # Caves shard settings
├── leveldataoverride.lua # World generation overrides for caves
├── modoverrides.lua # Mod enable/configure for Caves shard
└── save/ # World save data for Caves shard
Cluster Root Files
cluster_token.txt — Contains only the Klei server token. No quotes, no labels, no extra whitespace. Required for browser listing.
cluster.ini — Cluster-wide configuration: server name, password, game mode, player limits, shard topology. Applies to the entire cluster regardless of shard count.
adminlist.txt — One KleiID or SteamID64 per line. Grants in-game remote console access to listed players. Example:
KU_abc123def456
76561198012345678
whitelist.txt — Same format as adminlist.txt. Not enforced by the vanilla server; requires a Workshop mod such as "Whitelist+" to function as an access gate.
dedicated_server_mods_setup.lua — Lists Workshop mod IDs to download via SteamCMD. Applies cluster-wide at startup.
Shard Folders
Each shard (Master, Caves) is a subdirectory under Cluster_1/. The directory name matches the value passed to the -shard startup flag. You can rename these (e.g., Caves to Underground), but the name in the folder must match the -shard argument and the shard_name value in that shard's server.ini.
server.ini — Shard-specific configuration: port number, shard identity (master vs. slave), connection to the master shard.
leveldataoverride.lua — Optional file that overrides world generation parameters for that shard. Changing this file and restarting the server regenerates the world for that shard (save data is destroyed).
modoverrides.lua — Controls which mods are active and their per-mod configuration for that specific shard. Mods must be configured in both Master/modoverrides.lua and Caves/modoverrides.lua if you want them active on both shards.
save/ — Contains the serialized world state. Delete this folder to wipe that shard's world. The folder is recreated automatically on next startup.
Important Notes
cluster_token.txtandcluster.inilive in the cluster root (/dst/), not insideCluster_1/.dedicated_server_mods_setup.luaalso lives in the cluster root.- Each shard has its own
modoverrides.lua— changes to one shard's file do not affect the other. - The
save/folder should be backed up before any rollback or wipe operation.