7 Days to Die V3.3 and V3.4 Server Settings

7 Days to Die V3.4 is stable. This V3.3-based reference explains serverconfig.xml, SandboxCode and safe setup steps, with V3.4 compatibility notes.

7 Days to Die zombie survival game artwork
Source: coop-legends.de

Overview

7 Days to Die V3.4 became stable on October 26, 2026. Since V3.0, dedicated-server gameplay rules such as difficulty, XP and blood moon settings have been encoded in SandboxCode instead of the old collection of individual serverconfig.xml properties. The examples below were originally documented for V3.3; compare them with the sample configuration shipped with your installed V3.4 server before applying changes. See the official V3.4 release for the stable-branch change.

What belongs in serverconfig.xml?

The server starts from the active XML settings file specified by its launch setup, often a serverconfig.xml copy. Its properties can include ServerName, ServerDescription, ServerPassword, networking, slots and world selection. Hosting panels sometimes maintain their own configuration copy. Verify the actual -configfile= argument or provider settings before editing: changing a different copy may have no effect.

What changed with SandboxCode?

Version 3.0 moved numerous gameplay options—including difficulty, XP multiplier, day/night length, zombie movement, loot and blood moon settings—into one encoded SandboxCode value. The exact code depends on the rules chosen through the game's Sandbox Options interface. Generate and copy the code there rather than inventing a string or using a pre-V3.0 list of separate properties.

How to change server settings safely

  1. Confirm the dedicated-server version and branch, and back up both world and active XML file.
  2. Find the actual configuration file loaded at startup. Make a copy before changing it.
  3. Adjust only the supported server properties, preserving XML syntax and quotation marks.
  4. Use the game's Sandbox Options interface for gameplay rules and paste the resulting string as the SandboxCode value.
  5. Stop and restart the server so changes take effect. Check the startup log for parsing errors or an invalid code.
  6. Test connections, permissions and the intended difficulty before allowing normal play to resume.

Common configuration mistakes

A malformed tag may break startup, a code the server cannot parse can cause unexpected rules, and editing an overwritten default file may achieve nothing. Compare a customized file with the sample shipped in your current server installation after updates. Avoid publishing server passwords, Telnet credentials or admin interfaces. The technical modding wiki is a useful detailed reference but explicitly carries version caveats; treat your installed configuration file and current patch notes as final authorities.

Related: 7 Days to Die dedicated-server setup.