Overview
DST provides two mechanisms for restricting server access: a cluster password set in cluster.ini, and a whitelist.txt file. The password is enforced natively by the server. The whitelist file exists in the server but is not enforced by the vanilla server — it requires a Workshop mod to function as an access gate.
Setting a Server Password
Open Cluster_1/cluster.ini and add the password under [NETWORK]:
[NETWORK]
cluster_name = My Private Server
cluster_password = yoursecretpassword
Players attempting to join will be prompted for the password in-game before they can connect. An empty cluster_password value (or omitting the key entirely) leaves the server open.
Passwords are case-sensitive. There is no length limit enforced by the game, but keep it practical for players to type.
A server restart is required for password changes to take effect.
Removing the Password
To make the server public after it was private:
[NETWORK]
cluster_password =
Leave the value blank (no space after =). Restart the server.
whitelist.txt
whitelist.txt uses the same format as adminlist.txt — one KleiID or SteamID64 per line:
KU_abc123def456
KU_xyz789ghi012
76561198012345678
The file is located at:
/dst/whitelist.txt
The vanilla server does not enforce this file as an access gate. Players not on the whitelist can still connect to an unpassworded server. The file is read by the server for informational purposes only unless a mod adds enforcement logic.
Enforcing the Whitelist with a Mod
To use whitelist.txt as a true access control list, install a Workshop mod that hooks into connection events and kicks players not on the whitelist. A commonly used mod for this purpose is available on the Steam Workshop — search for "Whitelist" or "Whitelist+" and check the mod's description to confirm it reads whitelist.txt.
Install the mod following the standard process:
- Add the Workshop ID to
dedicated_server_mods_setup.lua - Enable it in both
Cluster_1/Master/modoverrides.luaandCluster_1/Caves/modoverrides.lua - Restart the server
With the mod active, only players listed in whitelist.txt (or admins in adminlist.txt) can connect.
Combining Password and Whitelist
You can use both simultaneously. The password acts as the first gate — any player who knows the password can attempt to connect. The whitelist mod then checks if the authenticated player is on the approved list and kicks them if not. This layered approach is useful for semi-private servers where you share the password with your community but want finer control over who actually gets in.
Admin Access and Whitelisting
Admins listed in adminlist.txt bypass whitelist mod enforcement in most implementations. Verify this behavior with the specific mod you use. This means admins can always connect regardless of whitelist status, which is intentional for server management.