Tools / 7 Days to Die
7 Days to Die 3.0 SandboxCode Studio
V3.0 "Dead Hot Summer" deleted the legacy gameplay properties from
serverconfig.xml and replaced them with one opaque SandboxCode
(30 properties folded into ~150 sandbox options). Paste your V2.6
serverconfig.xml and get the full migration plan: what still works, what
moved (and the exact sandbox option to set), what is dead - plus a cleaned 3.0-ready
config and a rules page for your players.
Honest scope: the SandboxCode encoding is not publicly documented, so this tool never invents codes. It maps every legacy property to its sandbox option and value; you generate the code itself in the in-game Sandbox Options menu or the 7d2d.net SandboxCode generator.
What 7 Days to Die 3.0 changed for servers
V3.0 "Dead Hot Summer" (stable June 29, 2026) made the biggest
serverconfig.xml change in the game's history. The legacy gameplay
properties - GameDifficulty, XPMultiplier,
LootAbundance, the BloodMoon* and ZombieMove
families, DropOnDeath, AirDropFrequency, and roughly two
dozen more - no longer work as individual lines. They are replaced by a single
property:
<property name="SandboxCode" value="AAAJABJACJADJARFBNC" />That string encodes the new Sandbox Options - about 150 settings across Player, Entities, World, Resources, Crafting, Traders, Tasks, and Misc groups. Only options changed away from their defaults are serialized, so short codes mean few changes, and the default value above equals the old Adventurer ruleset. The encoding itself is not human-readable and is not documented; the supported way to produce a code is the in-game menu (or the 7d2d.net SandboxCode generator).
What still lives in serverconfig.xml: server identity and passwords,
ports and visibility, player slots, telnet and the web dashboard, EAC, world
generation (GameWorld, WorldGenSeed,
WorldGenSize), land claims, dynamic mesh, Twitch integration, and the
performance caps. This tool keeps those, drops the dead ones, and turns the moved
ones into a menu checklist.
How to migrate a 2.6 server to 3.0
- Paste your V2.6
serverconfig.xmlabove and run the migration plan. - Back up your save and old config, then stop the server.
- Update the server to V3.0.
- Replace
serverconfig.xmlwith the cleaned version (re-add your passwords - the tool blanks them on purpose). - Recreate your ruleset from the checklist in the in-game Sandbox Options menu or
the 7d2d.net generator, copy the
generated code, and paste it over the placeholder
SandboxCodevalue. - Start the server and verify difficulty, XP, blood moons, and loot in-game. Post the generated rules page so players know what changed.
FAQ
Does my V2.6 serverconfig.xml still work on 3.0?
Partly. Infrastructure properties (ports, slots, passwords, telnet, land claims, world generation) still work. The gameplay properties were removed - if you leave the old lines in place, V3.0 ignores them and silently runs the default Adventurer-equivalent ruleset.
Can this tool generate my SandboxCode?
No, on purpose. The encoding is not publicly documented, so any code produced outside the game would be a guess - and a wrong ruleset on a live server is worse than a placeholder. The tool gives you the exact option-by-option checklist instead, and the cleaned config carries the documented default until you paste your real code.
Is it safe to paste my config here?
Detected passwords are blanked in the generated output and stripped before anything is stored. Best practice is still to redact secrets before pasting.
I am starting fresh on 3.0 - do I need this?
No. Generate a new world with the 7 Days to Die world generator and set your sandbox options in-game on first boot. This tool is for carrying an existing 2.6 ruleset forward. Still on 2.6? The server config generator writes the classic property lines.
Related tools
Pair the migration with a fresh map from the 7 Days to Die world generator (V3.0 worlds validated to load, preview before download), or tune a server that is staying on 2.6 with the server config generator. Sources for the property fates: the V3.0 release notes and the 7d2d.net migration guide. Mappings the sources leave ambiguous are marked "verify" in the results.