What Is a Sandbox Code in 7 Days to Die?

If you opened a current 7 Days to Die dedicated-server config and found one long string called SandboxCode, you did not miss a separate difficulty file. In V3, the game packs most of its gameplay rules into one shareable code.

A Sandbox Code is an encoded preset. It records the choices made in the game's Sandbox Options screen, so the same rules can be moved from a local game to a dedicated server without copying more than a hundred individual settings by hand.

What a Sandbox Code is, and what it is not

The code is a compact bundle of gameplay options. Depending on the choices you make, it can represent rules for difficulty, player and zombie damage, loot, experience, crafting, traders, quests, day length, blood moons, enemy behavior, stamina, movement, vehicles and many other parts of the survival loop.

It is not your server password, world seed, save name or mod list. Sharing a Sandbox Code lets another player reuse your rule set. It does not give them access to your server or copy your world.

How to create a Sandbox Code

1. Open 7 Days to Die and start the new-game setup.
2. Open Sandbox Options.
3. Choose the rules you want for the server.
4. Use the Copy Code button.
5. Paste the result into the dedicated server's SandboxCode property, then restart the server.

This client workflow is also the supported way to inspect an existing code. Paste the code back into the Sandbox Options screen to see the choices it represents. The dedicated server accepts the code, but it does not provide a friendly built-in list of every decoded value.

Which settings stay outside the code?

The Sandbox Code describes how the world plays. The dedicated server still keeps its operational settings separately. Those include the server name and description, password, public listing, map selection, player limit, ports, Easy Anti-Cheat and persistent-profile behavior.

Some familiar rules also remain explicit server properties in V3, including PvP mode and the global zombie cap. That is why a hosting panel may show a short settings form alongside one Sandbox Code field. The two parts are meant to work together.

Can you change the code on an existing world?

Yes. Stop the server, keep a copy of the old code, paste the new one and restart. Rules that are evaluated during play can take effect on the existing save. Changing the code does not select a different map, erase player progress or rebuild terrain that has already been explored.

Make a save backup before a major rules change anyway. A very different economy, loot setup or zombie profile can change the feel of a running world immediately, and keeping the previous code gives you a simple rollback. After a major game update, open the code in the current client and check the options before assuming an older preset still means exactly the same thing.

Common Sandbox Code mistakes

• Pasting a label with the code. Copy only the code itself, with no spaces, quotes or explanatory text.
• Forgetting the restart. The server reads the property when it starts. Saving a panel field alone does not hot-reload the world rules.
• Changing the wrong setting. A code cannot change the selected map, server password or player slots because those live elsewhere.
• Losing the known-good code. Save it before experimenting so a bad balance change takes one restart to undo.
• Trusting an outdated hosting form. A panel built around old individual properties can appear to save changes that V3 now expects in the code.

Using a Sandbox Code on GHosting

On a GHosting 7 Days to Die server, open Settings, paste the value into Sandbox Code, save, and restart the server. The panel writes the code to the generated server configuration while keeping the map, access, player, listing and anti-cheat settings in their own fields.

If you are still choosing hardware, read our 7 Days to Die server requirements guide. When you are ready to play, our 7 Days to Die server hosting includes the Sandbox Code field, file access and automated installation from the start.