7 Days to Die Artwork

Wiki & Guides

7 Days to Die

Zombie Survival · Voxel · The Fun Pimps

Rent 7 Days to Die Server

serverconfig.xml in 7 Days to Die V3.0: SandboxCode explained

serverconfig.xml after V3.0: how the new SandboxCode replaces the gameplay properties, which server settings remain and which legacy values are all gone.

Last updated July 20, 2026 · RespawnHost

On this page

What changed about serverconfig.xml in V3.0?

V3.0 “Dead Hot Summer” radically slimmed down serverconfig.xml: around two dozen gameplay properties were removed and replaced by a single new property — the SandboxCode. Difficulty, XP rate, day length, loot, blood moons and friends are no longer set individually in the XML; you configure them in the in-game sandbox menu, and the code it generates goes into the config. What remains in serverconfig.xml are genuine server properties like name, password, player count and map.

How does the SandboxCode work?

The V3.0 sandbox menu bundles around 150 gameplay options and 11 presets (the default is “Undead Matinee”, alongside Madmole’s Mayhem, Bite Club with permadeath, Chibi Mode and more). Every combination can be exported as a shareable code — and that exact code is what the dedicated server uses:

  1. Launch 7 Days to Die and open the sandbox menu (for example via a new single-player game).
  2. Pick a preset and tweak the options — difficulty, XP, loot, blood moon rhythm, day length and more.
  3. Copy the sandbox code the menu generates for your settings.
  4. Enter the code as the value of the SandboxCode property on your server — at RespawnHost directly in the panel under Configuration.
  5. Restart the server. Done.

Warning: silent fallback to Adventurer

An old serverconfig.xml containing the removed legacy properties throws no error — the values are simply ignored and the server quietly runs on Adventurer defaults. If your server feels "off" after the V3.0 update (difficulty, XP, day length), a missing SandboxCode is almost always the cause.

The V3.0 sandbox menu: pick your settings, copy the code, paste it into the server config

Which properties remain in serverconfig.xml?

You still configure these server properties directly (a selection of the most important — the definitive reference is the serverconfig.xml bundled with your installation):

PropertyMeaning
ServerNameName in the server browser
ServerPasswordPassword (empty = open to everyone)
ServerMaxPlayerCountMaximum player count (crossplay: max 8, see the crossplay guide)
ServerVisibilityVisibility in the server browser
GameWorldMap: Navezgane, PREGEN01–03 or RWG — see Maps & wipes
WorldGenSeedSeed for random world generation
WorldGenSizeRWG world size (4096–10240, default 6144)
EACEnabledEasy Anti-Cheat on/off (mandatory true for crossplay)
RegionServer region for the browser
ServerAllowCrossplayAllow crossplay with consoles
IgnoreEOSSanctionsIgnore EOS sanctions (must be false for crossplay)
LandClaimSizeSize of the land claim area
SandboxCodeNew in V3.0: all gameplay rules as one code from the sandbox menu

Which legacy properties were removed?

These formerly common gameplay properties no longer exist in V3.0 — the SandboxCode takes over their job (a selection):

  • GameDifficulty
  • XPMultiplier
  • DayNightLength and DayLightLength
  • LootAbundance and LootRespawnDays
  • The BloodMoon* family (frequency, range, enemy count …)
  • The zombie movement properties (Zombie*Move)
  • EnemySpawnMode / enemy difficulty
  • BlockDamage* (player, AI, blood moon)
  • DeathPenalty, DropOnDeath, DropOnQuit
  • AirDrop* (frequency, marker)
  • Storm frequency and biome progression

If a tutorial or forum post recommends one of these properties, it’s a pre-V3.0 guide — the value no longer has any effect.

Tip

Keep your SandboxCode as a text snippet (note, Discord pin). After a wipe or on a second server you can paste it back in seconds — and share it with your community so everyone plays by identical rules.

Frequently asked questions

Where do I edit serverconfig.xml at RespawnHost? Directly in the panel under Configuration — the key properties, including SandboxCode, are available as fields, no manual XML editing required.

Do I need to generate a new code for every rule change? Yes — you change gameplay rules by reconfiguring in the sandbox menu, copying the new code and entering it. That’s what makes the code shareable: build once, use everywhere.

Why is my server running on Adventurer after the V3.0 update? Your config wasn’t migrated: the old gameplay properties are ignored, and without a SandboxCode the Adventurer defaults silently apply. Generate the sandbox code, enter it, restart.

Are the roughly two dozen removed properties documented anywhere? The most reliable reference is the serverconfig.xml bundled with your V3.0 installation — anything that no longer appears there has been removed.