Dont Starve Together commands let experienced players adjust difficulty, manage servers, and debug worlds without starting over, but they require understanding authoritative versus non-authoritative setups to avoid unintended consequences. This reference explains how to access the console, the difference between server and client commands, and how to run frequently used commands safely in both singleplayer and multiplayer sessions. You will learn how to enable developer mode, protect your world with passwords, and apply commands that persist through updates for long-term, stable play. Use this guide as a durable resource rather than a one-time quick fix.
What Are Dont Starve Together Commands and Why They Matter
In Dont Starve Together, commands are developer-facing tools that send direct instructions to the game engine, typically accessed via the in-game console. They can change weather, adjust resources, alter creature behavior, or enforce server rules. Commands matter because they let you maintain control over persistent worlds, run dedicated servers, and troubleshoot issues without corrupting saves. Understanding execution context—whether a command runs on the server, client, or both—reduces risk and ensures consistent results in multiplayer sessions.
How to Enable the Console in Dont Starve Together
Enabling the Console for the Current Session
To open the console temporarily, press the tilde key (~) on PC. If the console does not appear, the game may be running in a non-authoritative client, where many server-only commands are blocked. On consoles, enable developer mode in the title screen options or pause menu. Mobile players can usually activate the console through an on-screen keyboard shortcut when the game has focus. These methods work for both singleplayer and multiplayer, but server commands will only execute where permitted by the server configuration.
Making Console Access Persistent Across Launches
You can make the console always available by creating or editing the settings.ini file in your saves folder and adding console_enabled = true under the [SETTINGS] section. For server hosts, place the same setting in the server’s configuration files to ensure remote console access when running dedicated instances. Be cautious when enabling the console on public servers, as it increases the risk of accidental or intentional misuse. Use password protection and user permissions to limit who can execute powerful commands.
Essential Server Commands for Hosts and Admins
Server commands manage the running instance, control players, and enforce rules. They require authoritative access, meaning you must run them on the server or from a remote console connected to the server. These commands do not work on clients that are not hosting or authorized to execute server-level actions. Use them to kick troublemakers, set game modes, or adjust world parameters without restarting the server.
Commonly Used Server Commands
| Command | Effect | Context |
|---|---|---|
| c_give("itemcode", amount) | Grants items to the player who runs it or a target if specified | Client or Server, depending on permissions |
| c_spawn("prefab", count) | Spawns entities at the player’s position | Client or Server, depending on permissions |
| GetPlayer().components.health:SetInvincible(true) | Makes your character invincible | Client only, singleplayer or non-authoritative client |
| theworld.components.weather:ChangePrecipitation() | Triggers immediate weather changes | Server or authoritative client |
| RunScript("scriptname.lua") | Loads and executes external Lua scripts | Server only, for authoritative control |
| GetPlayer().components.sanity:SetPercent(100) | Resets sanity to 100% | Client only, or server if targeting specific players |
| GetPlayer().components.hunger:SetPercent(100) | Resets hunger to 100% | Client only, or server if targeting specific players |
Client Versus Server: Understanding Command Authority
In Dont Starve Together, commands are either client-specific or server-enforced. Client commands affect only your local view, such as toggling visual settings or manipulating your own character’s components. Server commands influence the shared world and require elevated privileges, typically executed on the dedicated server or through an authorized remote console. Misunderstanding this boundary can lead to confusion when a command works locally but appears to do nothing in multiplayer. Always verify the authority level before assuming a change is global.
Best Practices for Using Commands Safely
- Back up your worlds before testing new commands, especially those that modify structures, items, or biomes.
- Use sandbox mode or a separate testing world to experiment with powerful item-spawning commands.
- Coordinate with server admins before applying scripts or remote execution tools to shared instances.
- Limit console access with strong passwords and avoid exposing management interfaces to public networks.
- Check patch notes when updating, as some commands may be deprecated or require parameter changes.
Persistence and Compatibility Across Updates
Dont Starve Together evolves with updates that can change command behavior, parameters, or availability. Commands tied to debugging or testing are more likely to change than core world-management commands. To improve durability, store custom scripts in dedicated folders, document parameter values, and test changes in a backup copy of your world. When upgrading, review known issues and migration notes to anticipate where commands may no longer function as expected.
Troubleshooting Common Command Issues
Command Not Working
If a command fails silently, first confirm whether you are on an authoritative server or a client. Server-only commands will not work from a non-authoritative client even if the console is open. Verify user permissions, ensure the server is configured to allow remote console access, and check for typos in the command syntax. Some commands require specific conditions, such as being near an entity or having the correct player focus.
World Desync or Unexpected Behavior
Running powerful world-altering commands on clients in multiplayer can cause desync, where clients see different states than the server. To reduce risk, apply major changes on the server or during singleplayer sessions, and communicate planned modifications to all players. If desync occurs, restarting the server and loading a recent backup often resolves inconsistencies.
Conclusion
Dont Starve Together commands are versatile tools that, when used with care, enhance long-term control over gameplay, difficulty, and world management. By understanding the difference between client and server execution, enabling the console responsibly, and following best practices, you can maintain stable, resilient worlds across sessions and updates. Treat this reference as an enduring guide to command syntax, execution context, and safety measures for both hosts and players.