How to Change 7 Days to Die Server Settings (V3 SandboxCode)

To change 7 Days to Die server settings in V3, you edit two things: serverconfig.xml for server properties like name, password, player count and world, and the new SandboxCode property for gameplay like difficulty, blood moon frequency, loot and XP. You create the SandboxCode in the game's Sandbox Options menu, copy it, and paste it into serverconfig.xml. If your blood moon or difficulty changes stopped working after the V3 update, this is why.

What changed in V3

With V3.0 "Dead Hot Summer" (stable on 29 June 2026), The Fun Pimps added over 150 sandbox options and moved the old gameplay lines out of serverconfig.xml into one code. These properties no longer do anything if you set them in the file:

• GameDifficulty, XPMultiplier, BlockDamagePlayer, BlockDamageAI, BlockDamageAIBM
• DayNightLength, DayLightLength, BiomeProgression, StormFreq
• DeathPenalty, DropOnDeath, DropOnQuit, JarRefund
• EnemySpawnMode, EnemyDifficulty, ZombieFeralSense, AISmellMode
• ZombieMove, ZombieMoveNight, ZombieFeralMove, ZombieBMMove
• BloodMoonFrequency, BloodMoonRange, BloodMoonWarning, BloodMoonEnemyCount
• LootAbundance, LootRespawnDays, AirDropFrequency, AirDropMarker
• QuestProgressionDailyLimit

Old configs do not show an error. A server without a new code simply runs the default, which equals the old Adventurer difficulty. Plenty of groups updated, kept their old file, and only noticed when horde night felt far too easy.

Step 1: Create your SandboxCode in game

1. Launch 7 Days to Die and start setting up a new game.
2. Open Sandbox Options.
3. Pick one of the presets as a starting point, then change what you want. Blood moon settings, zombie speed day and night, loot abundance and respawn, XP, day length, death penalty and airdrops are all in here.
4. Copy the code the menu generates.

You cannot write the code by hand. It is a short string like AAAJABJACJADJARFBNC that encodes every option, so always generate it in the menu.

Step 2: Paste it into serverconfig.xml

Stop the server, open serverconfig.xml (or the copy your start script loads) and set:

<property name="SandboxCode" value="PASTE_YOUR_CODE_HERE"/>

Save and start the server. The new rules apply without a new world, so you can change the blood moon or loot on a running save.

Tip: keep a note of the code and what it contains. When you want to tweak one option later, rebuild the same setup in the menu, change the one thing, and copy the new code.

Step 3: The settings still in serverconfig.xml

Everything that is really about the server stays as normal lines. Change only the value part.

Most changes need a restart. Changing GameWorld, WorldGenSeed or WorldGenSize means a different map, so back up first.

Popular setups

These are all made in the Sandbox Options menu and pasted as one code:

• Classic horde night: blood moon every 7 days, enemy count raised for small groups.
• Casual building server: blood moon less often, more loot, less death penalty.
• Hardcore: zombies run at night, lower loot, drop everything on death.
• Short sessions: shorter day length so a horde comes around more often in real time.

Higher zombie counts and faster zombies cost CPU, especially during blood moons with several bases. If the server rubber bands on horde night, lower the enemy count or the player limit, or give it more headroom.

Crossplay limits

If ServerAllowCrossplay is on, console players can only join when the settings stay inside the official ranges, including blood moon enemy count between 4 and 64, loot abundance at 200% or lower, loot respawn of at least 5 days, day length of at least 10 minutes, XP between 25% and 300%, and block damage values of at least 25%. Keep ServerMaxPlayerCount at 8 or lower, EACEnabled on, no mods and WorldGenSize at 8192 or smaller. PC players can join regardless.

Common problems

• Settings reset to easy after updating: you have no SandboxCode yet, or the old lines are still there. Add a code.
• Changes do nothing: you edited serverconfig.xml but the start script loads another file, or the server was running. Stop it, edit the right file, start it.
• Server will not start after editing: a broken XML line, often a missing quote or />. Compare with an untouched line.
• Console friends cannot join: a sandbox value is outside the crossplay range.

The easy way

On a 7 Days to Die server from GamezServers you edit serverconfig.xml right in the browser, paste your SandboxCode, and click Restart. Take a one click backup first, and upgrade the plan from Settings if bigger hordes need more power. Setting one up takes about a minute, see how to host a 7 Days to Die server.

FAQ

Where is the blood moon setting in 7 Days to Die V3?

It moved into the SandboxCode. Set frequency, range, warning and enemy count in the Sandbox Options menu and paste the code into serverconfig.xml.

Do I need a new world to change the SandboxCode?

No. Paste the new code, restart, and the rules apply to the existing save.

Why is my server on Adventurer difficulty?

It has no SandboxCode, or it has the default one. Old GameDifficulty lines are ignored in V3.

Can I still edit serverconfig.xml by hand?

Yes, for server properties like name, password, world and player count. Gameplay settings go through the code.