Updating Don't Starve Together Server
How to update your DST server files via SteamCMD and handle mod compatibility after game updates.
Overview
DST server updates are delivered via SteamCMD using the same AppID as the initial install (343050). The server must be stopped before updating. Post-update, verify mod compatibility before bringing the server back online for players.
Update Command
Run the following SteamCMD command to update the server files:
./steamcmd.sh \
+force_install_dir ./dst \
+login anonymous \
+app_update 343050 validate \
+quit
The validate flag checksums all existing files against the Steam manifest and re-downloads any that are corrupt, missing, or outdated. Always include validate to ensure a clean update rather than an incremental patch that may leave stale files.
Pre-Update Checklist
Before running the update command:
- Stop all shard processes — Master and Caves, if applicable. Updating while the server is running can corrupt save files or result in incomplete updates.
- Back up your save folders — Copy
Cluster_1/Master/save/andCluster_1/Caves/save/to a safe location. - Note your current mod list — Check Workshop pages for any mods that may not yet support the new game version.
Updating Through the Panel
Most WISP/Pterodactyl eggs include an update button or reinstall option that runs the SteamCMD update command for you. This is equivalent to running the command manually. Confirm with your panel documentation whether a reinstall preserves your Cluster_1/ folder and config files, or whether it wipes them.
If the panel's reinstall is destructive, run the SteamCMD command manually in the panel console instead.
Post-Update Steps
After SteamCMD completes:
- Check the DST changelog — Klei posts patch notes on the game's Steam page and forums. Review for any breaking changes to dedicated server configuration.
- Verify mod compatibility — Open each mod's Workshop page and check for recent updates or compatibility notices. Mods that have not been updated may crash the server on load.
- Test with mods disabled — If you are unsure about mod compatibility, start the server once with an empty or minimal
modoverrides.luato confirm the base server is functioning, then re-enable mods. - Check
cluster.iniandserver.ini— Major updates occasionally add new required configuration keys. Missing keys typically fall back to defaults, but review patch notes for any mandatory changes.
Mod Auto-Update Behavior
SteamCMD does not automatically update Workshop mods when you update the base game. Mods update the next time the server starts and SteamCMD fetches the Workshop content. This happens because the mod download is triggered by dedicated_server_mods_setup.lua at server startup, not by the game update command.
If a mod update breaks your server, you can roll back the mod by downloading an older version manually from the Workshop (if the author provides one) or by temporarily disabling the mod.
Keeping the Server Up to Date
DST updates frequently. Set a maintenance window for updates — at minimum, check for updates weekly. Klei publishes update notices in-game and on the Steam news feed for DST. Running an outdated server version can prevent newer clients from connecting.
To check the currently installed server version, look at the server console output on startup:
[00:00:01]: Don't Starve Together: 619045 WIN32_STEAM
The number is the build ID. Compare this against the latest build reported on SteamDB for AppID 343050.