A Don't Starve Together server primarily needs three clean foundations: a valid Klei cluster token, a suitable cluster configuration, and deliberately set world or mod options. If you activate Caves, you also plan for a second shard. This guide takes you through ordering, setup, checks, and typical sources of errors.

Requirements

For a Dedicated Server, you need a valid Don't Starve Together license, a Klei account, access to the server dashboard, and the decision whether you want to play only the overworld or also Caves. Token creation runs through the official Klei page for game servers at accounts.klei.com. There you generate the cluster token your server needs to authenticate with Klei.

If you start with a small co-op group, a lean configuration makes sense. In the starting setup, 2-4 GB RAM is planned, with Caves 4 GB. You should understand this information as a planning value: mods, player count, and world size can increase the requirements. At game-serverhosting, technical control is the focus: you consciously manage tokens, configuration files, restarts, and mods instead of relying on an opaque preset. How to choose mods and enable them in the cluster is covered in Don't Starve Together mods.

If you are comparing other co-op setups, you will find similar planning questions in the Rent and Set Up a Valheim Server – Co-op Guide 2026 and in the Rent and Set Up an Enshrouded Server – Co-op Guide.

Order a Server

  1. Go to game-serverhosting
  2. Choose 2-4 GB RAM (with Caves: 4 GB)
  3. The server is set up automatically

After provisioning, you should not immediately mix mods and world options. First set up the token, start the server once without additional changes, and check whether it is visible in Don't Starve Together. Only then is it worth adding Caves, world rules, and Workshop mods. This makes it easier later to identify which change caused an error.

Create a Cluster Token

  1. Start DST → Account → Games → Game Server (Klei Entertainment)
  2. Generate a token at accounts.klei.com
  3. Enter the token in the dashboard

The cluster token is not a cosmetic name, but the connection between your Dedicated Server and the Klei service. Treat it like a credential: do not post it publicly, do not show it in screenshots, and do not publish it in shared configuration examples. If you accidentally exposed a token, create a new token through the Klei page and replace it in the dashboard.

Activate Caves

Caves need a second shard. That means: the overworld and caves run as separate server processes that communicate with each other through the cluster configuration. Therefore, activate Caves only once the base server is running stable.

# cluster.ini
[SHARD]
shard_enabled = true
bind_ip = 127.0.0.1
master_ip = 127.0.0.1
master_port = 10889
cluster_key = secret

The cluster_key must match between the involved shards. Do not use a publicly known example value here in production. If Caves are not reachable, first check whether both shards are started, whether the master port matches, and whether the second shard uses the same cluster data.

World Settings

World settings belong in worldgenoverride.lua. This file affects the generation and rules of your world. Ideally, change it before the first productive game start because many settings no longer apply cleanly retroactively after world generation.

return {
    override_enabled = true,
    overrides = {
        day = "longday",
        season_start = "autumn",
        autumn = "longseason",
        winter = "shortseason",
        beefalo = "often",
        berry = "more",
    }
}

The example makes days longer, starts in autumn, extends autumn, shortens winter, and increases certain resources or creatures. Such options can significantly change the difficulty. For a new group, that is often helpful; for an experienced group, however, it can reduce the survival tension. Therefore, briefly document which values you set so later changes remain traceable.

Install Mods

You add mods through Workshop IDs in dedicated_server_mods_setup.lua. Restart the server after changes and check the logs if a mod does not load.

ServerModSetup("378160973")    -- Global Positions
ServerModSetup("462434129")    -- Wormhole Marks
ServerModSetup("458587300")    -- Season Clock

Do not install too many mods at once. Add a small group first, test joining the server, and then add more mods. Especially after game updates, individual Workshop mods can become incompatible. If players get stuck during connection, temporarily disable the most recently added mods and check whether all clients can load the same mod dependencies.

For other mod- or community-heavy server concepts, you can use the Rent a Team Fortress 2 Server – Community Server Guide as a comparison. If co-op survival with clear server control matters to you, the Rent and Set Up a V Rising Server – Vampire Guide is also a good thematic fit.

Admin Commands

Admin rights and console commands help with operation, but should be used sparingly. Use them mainly for maintenance, rollbacks, and tests, not as a replacement for clean backups.

c_admin("KU_xxxxxxxx")         -- Give admin rights
c_rollback(1)                   -- Roll back 1 day
c_reset()                       -- Reset world
c_godmode()                     -- Invulnerable
c_supergodmode()                -- Immortal + no hunger

Replace KU_xxxxxxxx with the correct Klei user ID. Check admin rights after a restart by using a harmless command or by verifying in the game whether the expected permissions apply. c_reset() resets the world and is accordingly critical. Use such commands only when it is clear what consequences they have.

Check the Result

After setup, you should check four points: the server appears in Don't Starve Together, joining works without mod errors, the desired world options are active, and Caves are reachable if you activated them. It is also worth looking at the server logs right after startup. Errors related to tokens, shards, or mods often show up there earlier than in the game client.

Ask a second person from your group to join as a test. This checks not only your local client, but also whether the server is reachable for others and whether Workshop content is distributed correctly.

Troubleshooting

If the server is not visible, first check the cluster token and restart the server. A missing or invalid token prevents correct authentication. If Caves are missing, check the shard configuration and whether the second shard is actually running. If mods cause problems, remove the most recently added Workshop IDs and continue testing in small steps.

If world options seemingly do not apply, the world may already have been generated previously. In that case, depending on the setting, you need a new world or must consciously continue playing with the existing parameters. Always back up the current state before destructive changes.

Checks, Limits, and a Safe Way Back

The guide “Rent a Don't Starve Together Server – Co-op Guide” applies to the server type described in the article and the version status visible at the time of review. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. Therefore, do not transfer any values unchecked to another game, loader, or server version.

Before making changes to the world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step and check it with the same client and server version you want to play with later.

Checkpoint Expected Result Abort and Rollback
Server start The server reaches the ready-to-use state without a new error message. In case of startup errors, undo the change and restore the latest backup.
Connection test A test account can connect via the address shown in the panel. In case of version or connection errors, compare version, port, and firewall rules again.
Function test The specifically changed function works without damaging existing world or game data. In case of side effects, stop the server and restore backed-up files.

A successful individual test is not a performance or availability guarantee. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document the version, change, and test result so you can understand later deviations.

FAQ

Do I absolutely need a Klei cluster token?

Yes. For a Don't Starve Together Dedicated Server, you need a cluster token from Klei. It is created through the official Klei game server page and entered in the server dashboard.

Should I activate Caves right on the first start?

Only if you really want to play them. Caves require a second shard and increase complexity. For the first check, starting without Caves is often clearer.

Can I add mods later?

Yes. Add the Workshop IDs to dedicated_server_mods_setup.lua and restart the server. Add mods step by step so you can more easily assign errors to a specific change.

When is the best time to change worldgenoverride.lua?

Preferably before the first productive world generation. Many world options take effect when the world is created and cannot always be changed cleanly retroactively later.

What do I do if players get stuck while joining?

First check the logs and temporarily disable the most recently added mods. Then check the token, shards, and whether all required Workshop content is loaded correctly.

How do I handle admin commands safely?

Use admin commands deliberately for maintenance and tests. You should run critical commands like c_reset() only after deliberate checking and ideally after a backup.