1. Back Up
Copy current config, save path, and mod list before editing serverconfig.xml.
Backup
Server Config
Adjust 7 Days to Die server config without breaking players, saves, EAC, or mods.
Use this serverconfig.xml guide to sort settings by risk, keep backups, explain rule changes, and connect config edits to troubleshooting checks.
V3.0 server note: Dead Hot Summer moves many old difficulty and world-rule settings into the sandbox option system. For V2.6 save continuity, recreate legacy settings in the in-game Sandbox Options menu, copy the generated SandboxCode, and paste it into the V3.0 serverconfig.xml field after backing up.
Safe Edit Order
Change server settings in small, reversible steps.
Server config edits can affect visibility, joining, EAC behavior, performance, world rules, and player trust. Record each change before the restart.
2. Edit Low-Risk Fields
Start with name, description, password, message, region, and player-facing rules.
Low risk3. Review High-Risk Fields
Treat EAC, world generation, progression, save paths, and mod requirements as high impact.
High risk4. Restart and Test
Restart once, join from a clean client, and confirm the server appears as expected.
Verifyserverconfig.xml planning table
| Config area | Common user question | Safe handling |
|---|---|---|
| Identity | How do players find the server? | Keep server name, description, region, and password rules clear. |
| Access | Why can't players join? | Check password, whitelist, player cap, version, EAC, and mod requirements. |
| EAC | Should EAC be enabled? | Make the rule visible and avoid changing anti-cheat settings casually. |
| World and save | Will config changes affect the world? | Back up before touching world, seed, save, difficulty, or progression settings. |
| Mods | Do players need the same mods? | Document server-side, client-side, and both-sides requirements. |
| Performance | Why is the server lagging? | Track player count, region, hardware, mods, restarts, and recent updates. |
V3.0 SandboxCode
Do not treat V3.0 serverconfig.xml like older versions.
The V3.0 release notes describe a migration path for legacy server settings. Document old values, generate a SandboxCode, and test the result before opening the server.
1. Snapshot old config
Save the old serverconfig.xml, mod list, save folder path, and visible rules before changing anything.
Backup2. Recreate settings
Use the V3.0 sandbox options menu to recreate the old difficulty, loot, zombie, quest, world, and death rules.
Sandbox3. Copy SandboxCode
Paste the generated code into the V3.0 serverconfig.xml SandboxCode property instead of guessing removed legacy fields.
Migration4. Test before advertising
Start the server, join cleanly, verify rules, then ask one player to test from outside the host network.
VerifyV3.0 config areas that deserve extra review
| Area | Why it matters after V3.0 | Safe handling |
|---|---|---|
| SandboxCode | Replaces many older world-rule fields and can silently change the server experience. | Generate from known settings, save the code, and test one restart. |
| Death and item degradation | New repair and degradation options can change how punishing deaths and repairs feel. | Tell players before a season starts; do not surprise live communities. |
| Loot and progression | Sandbox options can affect loot abundance, magazines, crafting, quests, and skill pacing. | Pair changes with rules text and reset expectations. |
| Zombie and Blood Moon rules | Difficulty, speed, enemy density, and Blood Moon settings shape performance and player trust. | Change one axis at a time and record the reason. |
| MOD compatibility | Server-side mods and overhaul packs may depend on version-specific XML or progression behavior. | Use a separate test world and publish exact mod requirements. |
Config FAQ
Most server config problems are communication problems first.
Why is the server not showing up?
Check status, ports, firewall, listing delay, region filters, version, and server name before rewriting config.
Troubleshooting guideWhen should I change EAC settings?
Only after you understand player impact and server rules. Treat EAC as a high-risk setting, not a quick fix.
How do mods affect config?
Mods may require player instructions, load-order notes, server-side installation, or a fresh save. Pair config changes with the mod install guide.