How to Change 7 Days to Die Settings on an Existing World
Which 7 Days to Die serverconfig.xml settings apply to an existing save (SandboxCode, players, land claims) and which make a new world (GameWorld, seed, size).
Updated Oct 3, 2026 · 5 min read
On this page
To change 7 Days to Die settings on an existing world, stop the server, edit serverconfig.xml and start it again. Gameplay rules (the V3 SandboxCode), the player cap, password, land claims and spawn caps all apply to the save you already have. Four properties do not: GameWorld, WorldGenSeed, WorldGenSize and GameName decide which world and save load, so changing any of them quietly starts a different one. The other trap is a launch option like -GameName= that overrides the file.
What you can change on an existing world
| Setting | Existing world? | Notes |
|---|---|---|
SandboxCode (difficulty, XP, blood moons, loot, zombie speed) |
Yes | Next start. Loot already sitting in opened containers stays as it was |
ServerName, ServerDescription, ServerPassword |
Yes | Next start |
ServerMaxPlayerCount |
Yes | Next start. Crossplay servers stay at 8 or lower |
LandClaimSize, LandClaimCount and the other land claim lines |
Yes | Next start |
MaxSpawnedZombies, MaxSpawnedAnimals |
Yes | Next start |
PlayerKillingMode |
Yes | Next start |
EACEnabled, ServerAllowCrossplay |
Yes | Mods and crossplay limits still apply |
GameWorld |
No | Loads a different map, with its own saves |
WorldGenSeed, WorldGenSize |
No | A random world with a new seed or size is a brand new map |
GameName |
No | A new name starts a fresh save on the same map |

How 7 Days to Die finds your save
This is the part that catches people. The server does not have a "world file" you point at. It builds the save path from two properties:
Saves/<GameWorld>/<GameName>/
With GameWorld=RWG, the game generates a map from WorldGenSeed and WorldGenSize, gives it a name (something like East Nikazohi Territory), stores it in GeneratedWorlds/, and keeps your save under Saves/East Nikazohi Territory/<GameName>/. Change the seed or size and the server generates a new map with a new name. Change GameName and it makes a new save folder next to the old one.
Nothing is deleted. Your old world is still there, it is just not the one loading. Put the old values back and it returns.
| Folder | What it holds |
|---|---|
GeneratedWorlds/<world name>/ |
A random generated map: terrain, towns, prefabs |
Saves/<world name>/<GameName>/ |
Your progress: players, bases, land claims, loot state |
Saves/<world name>/<GameName>/Player/ |
One file set per player |
serverconfig.xml |
Server properties and the SandboxCode |
On Windows the default user data folder is %AppData%\7DaysToDie\, and on Linux ~/.local/share/7DaysToDie/. Hosts often set their own with the UserDataFolder property.
Step 1: Back up first
Copy the whole Saves/<world name>/<GameName>/ folder, plus GeneratedWorlds/<world name>/ for a random world. A big rules change, like a very different loot or zombie profile, changes how a running world feels straight away, so also note down your current SandboxCode so you can paste it back.
Step 2: Stop the server
Run saveworld in the console, then shutdown. The server reads serverconfig.xml only at startup, so edits made while it runs do nothing until the next start.
Step 3: Edit only the value
Each line is a property with a value. Change the value part and nothing else:
<property name="ServerMaxPlayerCount" value="8"/>
<property name="SandboxCode" value="PASTE_YOUR_CODE_HERE"/>
<property name="LandClaimSize" value="41"/>
<property name="GameWorld" value="RWG"/>
<property name="WorldGenSeed" value="ourworld"/>
<property name="WorldGenSize" value="6144"/>
<property name="GameName" value="MyGame"/>
Leave the last four exactly as they are if you want to keep your world. The 7 Days to Die modding wiki explains how the sandbox code is built. Make it in the game's Sandbox Options screen rather than by hand. Since V3, old lines like GameDifficulty and BloodMoonFrequency are ignored, see how to change 7 Days to Die server settings.
Step 4: Check for launch options
7 Days to Die accepts any property on its start line, in the form -ServerMaxPlayerCount=16 or -GameName=MyGame, and those win over serverconfig.xml. Many host panels use this to pass their settings. If a value keeps coming back, or the server loads a world you did not expect, look at the start line before blaming the file.
Step 5: Start and check
Start the server and watch the log for the world name and save it loads. Join and check that your base is where you left it. If the map is new and empty, compare GameWorld, WorldGenSeed, WorldGenSize and GameName with your backup.
Common problems
- The server generated a new world: the seed or size changed, often from a typo or a panel default. Put the old values back.
- Everyone spawned fresh on the right map:
GameNamechanged, so a new save started. The old save is still in its own folder. - The difficulty went back to Adventurer: there is no
SandboxCode, or an old V2 config is still in use. Paste a code. - One value never changes: a launch option sets it. Change it where the start line gets it from.
- The server will not start after editing: a broken XML line, usually a missing quote or
/>. - Console players cannot join after a change: a sandbox value or the player cap went outside the crossplay limits.
Changing settings on GamezServers
On a GamezServers 7 Days to Die server, the join password, sandbox code, world, seed, size, save name, Easy Anti-Cheat and game version are fields in Settings, and the server name, description and player cap come from your dashboard. They are passed as launch options on every start, so they win over serverconfig.xml: change those in the panel. (The sandbox code is only passed when the field is filled in, so an empty field leaves the one in the file in charge.) Changing the save name, world, seed or size starts a different world, and the old one stays on disk. Press Backup before any of it. To pick a new size deliberately, see how to change the world size.
FAQ
Do I need a new world to change 7 Days to Die settings?
No, for gameplay rules, player cap, password and land claims. Only GameWorld, WorldGenSeed, WorldGenSize and GameName load a different world or save.
Can I change the SandboxCode on an existing save?
Yes. Stop the server, paste the new code, and start it. The rules apply to the existing world, though loot already in containers keeps its old roll.
Why did my 7 Days to Die server make a new world?
The seed, size, world or save name changed. Put the old values back and your previous world loads again.
Does changing GameName delete my save?
No. It starts a new save folder beside the old one. Set the old name again to go back.
Skip the setup. Your own 7DTD server.
Then $19.99/mo. Just trying it? $5.00 for 3 days