1. Back Up
Copy current config, save path, and mod list before editing serverconfig.xml.
Backup
Server Config
7DTD serverconfig.xml guide.
Backups, EAC, player limits, world settings, MODs, SandboxCode, and restart checks.
V3.0 note: Dead Hot Summer moves many old difficulty and world-rule settings into Sandbox Options. Back up first, recreate old settings in-game, copy SandboxCode, and test before reopening the server.
Edit Order
Small, reversible changes
Config changes affect joining, EAC, performance, world rules, and player trust. Record each change before 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 risk 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
V3.0 SandboxCode
Save old values, generate SandboxCode, and test 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 checks
| 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
Common config questions
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.