Don't Starve Together Dedicated Server Guide 2026

Don't Starve Together turns Klei's survival game into a cooperative (or competitive) multiplayer experience where up to six players share a world full of seasonal hazards, boss monsters, and the constant threat of starvation. Running a dedicated server lets your group play on a world that persists around the clock, with optional caves, full mod support, and admin controls that the built-in hosting mode cannot offer. This guide covers cluster setup, cave servers, world generation, mod installation, admin commands, and everything else you need to host DST in 2026.

Why run a dedicated DST server

Don't Starve Together offers two multiplayer modes: hosting from your game client, or running a dedicated server. Client hosting ties the world to the host's computer and internet connection. When the host closes the game, everyone is out. Performance depends on the host's hardware, and there is no way to run caves as a separate shard.

A dedicated server solves these limitations. The world stays up 24/7 regardless of who is playing. You can run a cave shard alongside the overworld, giving players access to the full game content. Server-side mods run without the host needing to be in-game. For any group that plays more than casually, a dedicated server is the right approach.

Understanding the cluster system

DST uses a "cluster" architecture where one or more server shards run together. The simplest setup is a single overworld shard. A more complete setup includes both an overworld shard and a cave shard, connected through sinkholes and stalagmites so players can move between them.

Each cluster has a root directory containing:

• cluster.ini: the main configuration file for the entire cluster (name, password, game mode, max players).
• cluster_token.txt: your server authentication token from Klei.
• Master/: the overworld shard directory, containing server.ini and worldgenoverride.lua.
• Caves/: the cave shard directory with its own server.ini and worldgenoverride.lua.

Both shards run as separate processes but communicate through a shared cluster key. On a single machine, the overworld typically listens on port 10999 and the caves on port 10998. Players see one server in the browser; the game handles shard transitions transparently.

Setting up the server step by step

1. Install SteamCMD and download the DST dedicated server: steamcmd +login anonymous +force_install_dir /home/dst/server +app_update 343050 validate +quit.
2. Generate a server token. Log into your Klei account at accounts.klei.com, navigate to the DST game page, and generate a server token. Save it as cluster_token.txt in your cluster root directory.
3. Create the cluster directory structure. Under ~/.klei/DoNotStarveTogether/MyCluster/, create cluster.ini, a Master/ folder, and optionally a Caves/ folder.
4. Configure cluster.ini:

[GAMEPLAY]
game_mode = survival
max_players = 6
pvp = false

[NETWORK]
cluster_name = Your Server Name
cluster_description = Your server description
cluster_password = yourpassword
cluster_intention = cooperative

[MISC]
console_enabled = true

[SHARD]
shard_enabled = true
bind_ip = 127.0.0.1
master_ip = 127.0.0.1
master_port = 10888
cluster_key = YourSecretKey

5. Configure each shard's server.ini. The Master shard is marked as is_master = true, the Caves shard as is_master = false. Each needs a unique server_port.
6. Start both shards. Run the dedicated server binary once for each shard, pointing to the correct shard directory.

On a managed panel like HostValues game hosting, the cluster setup, token management, and shard launching are handled through the interface. You configure world settings and mods without touching config files directly.

Cave server setup

Caves are one of the best parts of DST. They add underground biomes with unique resources, ruins, and the Ancient Fuelweaver boss. Running caves requires a second shard process, which effectively doubles the resource usage of your server.

The cave shard's worldgenoverride.lua must include:

return {
    override_enabled = true,
    preset = "DST_CAVE",
}

And its server.ini needs:

[NETWORK]
server_port = 10998

[SHARD]
is_master = false
name = Caves

[ACCOUNT]
encode_user_path = true

Memory for caves: budget roughly 1.5x what the overworld uses. If your overworld runs comfortably on 2 GB, adding caves pushes total cluster memory to around 5 GB. Both shards need to run simultaneously, so ensure your hosting plan has enough RAM for both.

World generation settings

DST's world generation is highly configurable through worldgenoverride.lua. You can control resource density, biome sizes, boss difficulty, seasonal settings, and more.

Commonly adjusted settings:

• Season length: default seasons last 15 to 20 days each. Longer summers and winters add challenge; shorter ones reduce the survival pressure for newer players.
• Resource density: increase berry bushes, saplings, and flint for a more forgiving experience, or reduce them for hardcore survival.
• Mob frequency: adjust hound attack frequency, spider density, and boss respawn timers to match your group's skill level.
• Starting season: autumn is the default and most forgiving start. Spring or winter starts create an immediate survival challenge.
• World size: small, medium, default, large, or huge. Larger worlds spread resources thinner but give more room for base building.

You can also use world presets: "Together" is the default balanced experience, "Endless" disables the kick-on-death mechanic and allows unlimited respawning, and "Wilderness" scatters players randomly on each respawn for a more chaotic experience.

Installing mods

DST supports both client mods (cosmetic, UI enhancements) and server mods (gameplay changes). Server mods need to be installed on the server and listed in the cluster's mod configuration.

To install server mods:

1. Find the mod's Workshop ID on the Steam Workshop page (the number in the URL).
2. Add the Workshop ID to dedicated_server_mods_setup.lua in the server's mods directory: ServerModSetup("workshop-ID").
3. Configure the mod in Master/modoverrides.lua (and Caves/modoverrides.lua if it should apply underground too).
4. Restart the server. It downloads and enables the mod automatically.

Popular DST server mods include Global Positions (shows all players on the map), Combined Status (extended HUD information), Geometric Placement (grid-based building), and Increased Stack Size. For quality of life without changing core gameplay, these are near-universal.

Players joining a modded server automatically download the required server mods. No manual installation needed on the client side.

Admin commands and player management

DST has a built-in admin system. Add player Klei User IDs to adminlist.txt in the cluster directory to grant admin rights. Admins can use the in-game console (press ~) to run commands:

• TheNet:Kick(userid) and TheNet:Ban(userid): remove or permanently block a player.
• c_rollback(count): roll the world back by a number of save snapshots. Essential when a griefer burns down the base.
• c_reset(): regenerate the world entirely (use with caution).
• c_announce("message"): broadcast a message to all connected players.
• c_save(): force an immediate save.

For moderation without being in-game, some mods add Discord integration or remote console access, though DST's native remote management options are more limited than games like Rust or Minecraft.

Hardware requirements

DST's server is lighter than most survival games, but caves double the process count. Each shard runs independently, so two cores minimum is recommended for an overworld-plus-caves setup.

Performance and maintenance tips

• Restart periodically. Every few in-game days, or on a fixed real-time schedule, restart the server. DST servers accumulate state over long sessions, and periodic restarts keep things responsive.
• Limit world age. Very old worlds (100+ days) with massive bases and thousands of placed objects run slower. If performance degrades significantly, consider a seasonal reset.
• Prune disconnected player data. Players who join once and never return still have their data stored. Periodically clean up inactive player files.
• Keep mods minimal. Every server mod adds processing overhead. Run only the mods your group actually uses.
• Monitor shard communication. If players experience lag when transitioning between overworld and caves, check that both shards are running on the same machine (or at least the same local network) to minimize inter-shard latency.

Frequently asked questions

Can I add caves to an existing server?

Yes. Create the Caves directory structure, add the cave shard configuration files, enable shards in cluster.ini, and start the cave shard alongside the existing overworld. The overworld itself does not need to be regenerated. Sinkholes and stalagmites are already present in the overworld terrain; they just need a cave shard to connect to.

How do I get a Klei server token?

Log in at accounts.klei.com with the account that owns Don't Starve Together. Go to the Games tab, find DST, and click "Game Servers." Generate a new token and save it as cluster_token.txt in your cluster root directory. Each cluster needs its own token.

Why does my server show as offline in the browser?

Common causes: the server token is missing or expired, the ports are blocked by a firewall, or the server crashed during startup due to a mod conflict. Check the server log file in the cluster directory. It usually contains a clear error message pointing to the issue. Regenerate the token if it has expired.