7 Days to Die serverconfig.xml: the settings that matter
By Benjamin D. · PDG
· 5 min read

Contents
A 7 Days to Die serverconfig file controls the world name, the password gate, the zombie difficulty, and whether Easy Anti-Cheat runs at all, and getting even one of these wrong is usually why a shared world refuses to show up for friends. This guide walks through the serverconfig.xml fields that actually matter, the UDP ports your group needs open, EAC behavior, admin rights through admins.xml, and how to keep your save data safe.
Locating and editing the serverconfig.xml file
The serverconfig.xml file sits in the same install folder as the server executable, alongside the Data and Saves directories. On a dedicated machine it is usually under the SteamCMD install path; on a panel it shows up directly in the file manager without needing a separate FTP client.
Edit it as plain XML, one <property> tag per setting, then restart the process for the changes to apply. The game does not reload this file while running.
<property name="ServerName" value="Nexus Survivors" />
<property name="ServerPassword" value="" />
<property name="ServerPort" value="26900" />
Keep a backup copy of the file before editing it. A single malformed tag or missing quotation mark stops the process from launching, and the error logs rarely point at the exact line.
Players who prefer skipping the manual file editing entirely can start from a preconfigured environment through 7 Days to Die server hosting, where the panel exposes serverconfig.xml directly in the browser.
The 7 Days to Die serverconfig settings that matter
Out of the dozens of properties in the file, eight of them decide whether a shared world is playable, visible to friends, and fair once the first blood moon hits.
| Setting | What it does | Why it matters for a shared world |
|---|---|---|
| ServerName | The label shown in the server browser | Makes the world easy to find among favorites |
| ServerPassword | Gates connections behind a password | Keeps the world private to your group only |
| ServerPort | The UDP port the world listens on | Must match the port you forward or open |
| ServerVisibility | 0 public, 1 friends only, 2 not listed | Controls who can even see the world exists |
| EACEnabled | Toggles Easy Anti-Cheat | Blocks most mods and tools when set to true |
| GameDifficulty | Scales zombie damage from 0 to 5 | Needs raising for larger coop groups |
| BloodMoonEnemyCount | Horde size per player on blood moon nights | Scales with player count or the base gets overrun |
| LandClaimSize | Radius protected by a land claim block | Prevents friendly fire griefing between players |
Set ServerVisibility to 1 and fill in ServerPassword for a private friend group. Leaving both at default public settings is the most common reason random players end up joining a world meant for a small crew.
Opening the UDP ports your group needs
7 Days to Die uses UDP exclusively for game traffic, not TCP. The ServerPort value in serverconfig.xml, 26900 by default, needs to be open on the firewall, and the game also queries three ports above it for the Steam server browser.
| Port range | Protocol | Purpose |
|---|---|---|
| 26900 | UDP | Main game traffic, matches ServerPort |
| 26901 to 26903 | UDP | Steam query and server browser listing |
| 8080 and 8081 | TCP | Web dashboard and Telnet, only if enabled |
If a friend sees the world in their favorites list but the connection attempt times out, the UDP range is almost always the culprit rather than the password or the version mismatch. Check the firewall rule before touching anything else in the file.
Choosing the right EAC mode for your group
EACEnabled set to true runs Easy Anti-Cheat on both the server and every connecting client. It blocks cheats, but it also blocks most client side mods, since the anti-cheat flags modified game files on connection.
Set it to false if the group plans to run mods, XML overhauls, or custom UI packs together. A modded world with EAC on will reject every modded client at the connection screen with an authentication error.
A vanilla group with no plans for mods should leave EAC on. It costs nothing in performance and removes one entire category of cheating from console commands and item duplication exploits.
Granting admin rights without handing out full control
Admin rights live in a separate file, admins.xml, not in serverconfig.xml. Each entry maps a Steam ID to a permission level from 0, full control, up to 1000, almost no extra power beyond a regular player.
<adminTools>
<admins>
<admin permission_level="0" platform="Steam" userid="7656119XXXXXXXXXX" />
<admin permission_level="100" platform="Steam" userid="7656119YYYYYYYYYY" />
</admins>
</adminTools>
Reserve permission level 0 for yourself or a co-admin you trust completely, since that level can kick, ban, teleport, and spawn items through console commands. Give moderators a mid-range level that allows kicking disruptive players without granting item spawning.
Keeping world saves and backups safe
World data lives in the Saves folder, named after GameName and WorldGenSeed from serverconfig.xml. Changing either value points the server at a brand new, empty save rather than resetting the existing one, which is a common source of confusion after an edit.
Copy the full Saves folder somewhere outside the install directory on a regular schedule, ideally before any mod update or config change. A corrupted database file in that folder is unrecoverable without a prior copy.
On a panel environment, scheduled backups handle this automatically and restore from a snapshot in a few clicks, which matters more for survival worlds than almost any other setting in this guide.
Conclusion
Set ServerVisibility and ServerPassword first if the world is meant to stay private, then decide on EACEnabled before anyone installs a mod, since switching it later forces every player to reconnect. Back up the Saves folder before touching WorldGenSeed. Everything else in serverconfig.xml can be tuned later without breaking the group's access.
FAQ
How many players can join a 7 Days to Die serverconfig world at once?
The limit comes from ServerMaxPlayerCount in serverconfig.xml, which has no hard engine cap but performs best in the single digits to low twenties depending on CPU and RAM available to the process. Raising it without matching hardware usually causes chunk loading stutter during blood moon hordes rather than outright crashes.
Can I change the world seed without losing my current save?
No. WorldGenSeed is part of the save folder name along with GameName, so changing it creates a completely new, empty world rather than regenerating the existing one. The original save stays untouched on disk and can be restored by reverting both values back to their previous entries.
Does 7 Days to Die support players connecting from different operating systems?
Yes, as long as every client and the server run the same game build and patch version. The engine does not distinguish between Windows and Linux clients at the network layer, so mismatched versions, not the operating system, are the usual reason a connection gets rejected.



