7 Days To Die Server Settings Explained: Complete V3.4 Configuration Guide

Configuring your 7 Days To Die server allows you to customize everything from player limits and world generation to zombie behavior, Blood Moon difficulty, and multiplayer permissions. However, since V3.0, several settings have changed, meaning older configuration methods may no longer work.

Whether you're self-hosting or using 7 Days To Die server hosting, this guide explains the current server settings, their default values, and how to configure them in V3.4.

How To Access Your 7 Days To Die Server Settings

Most dedicated server settings are stored in a file called serverconfig.xml. Each property contains a name identifying the setting and a value determining how it behaves.

For example, the following property controls how many players can join your server:

<property name="ServerMaxPlayerCount" value="8"/>

Changing the value from 8 to 12 increases the configured player limit to 12.

Self-Hosted Servers

If you're running your own dedicated server, locate serverconfig.xml inside your server's installation directory. Open the file using a text editor, adjust the desired properties, and save your changes.

Always stop your server and create a backup before editing the file. Some installations also use a custom configuration specified through the -configfile= startup argument, so make sure you're editing the correct file.

Dedicated Hosting Servers

With 7 Days To Die hosting, you can edit your configuration directly through our game panel.

1. Log into your game panel.
2. Select your 7 Days To Die server and stop it.
3. Open the Files tab.
4. Locate and open serverconfig.xml.
5. Change the values you want to customize.
6. Save the file and restart your server.

Most server settings can be changed this way without manually connecting through SFTP. Some values may also be controlled by Startup settings, which can take priority over the XML file.

General Server Settings

These settings determine how your server appears in the multiplayer browser, who can join, and how players connect.

Server Identity And Visibility

For private communities, ServerPassword prevents unauthorized players from joining. You can also make your 7 Days To Die server private using a whitelist, while ServerVisibility controls whether your server appears in public searches.

Networking And Player Slots

Be careful when modifying networking settings, particularly on hosted servers where ports may be assigned automatically. Also, the Friends visibility option has limitations on dedicated servers, so a password-protected or unlisted server may be more suitable for private groups.

World Generation And Save Settings

World settings determine which map your server loads, how worlds are generated, and where player progress is stored.

Pay particular attention to GameName, which identifies the save being loaded. Changing this value doesn't rename your existing world and may cause the server to load a different save instead.

Settings such as MaxChunkAge and SaveDataLimit can also affect stored world data, so make sure you have a backup before modifying them. Larger generated maps generally require more server resources, especially during world generation.

Gameplay Settings And SandboxCode

One of the biggest changes introduced in 7 Days To Die V3.0 was the new SandboxCode system. Instead of configuring individual gameplay properties inside serverconfig.xml, numerous options are now stored within a single encoded value.

Which Settings Are Controlled By SandboxCode?

The main gameplay categories include:

• Difficulty: Enemy damage, player damage, and combat difficulty.
• Progression: Experience multipliers and leveling rules.
• Zombies: Spawn frequency, movement speed, and detection.
• Blood Moons: Horde frequency, warning times, and enemy counts.
• Loot: Resource availability, abundance, and respawn intervals.
• Survival: Hunger, thirst, infection, and death penalties.
• World Rules: Day length, environmental conditions, and other sandbox mechanics.

Previously, settings such as BloodMoonFrequency, GameDifficulty, XPMultiplier, and LootAbundance existed as separate XML properties. In V3.x, these are configured through SandboxCode instead.

How To Generate And Apply A SandboxCode

To generate your own SandboxCode:

1. Launch 7 Days To Die and open the new-game setup screen.
2. Select Sandbox Options and customize your preferred settings.
3. Copy the generated SandboxCode.
4. Open your server's serverconfig.xml and replace the existing SandboxCode value.
5. Save your changes and restart the server.

For example:

<property name="SandboxCode" value="YOUR_GENERATED_CODE"/>

You can verify the loaded settings using the console command getsandboxoptions, or its shorter alias, gso.

Different 7 Days To Die sandbox presets can provide useful starting points for casual multiplayer, hardcore survival, and PvP servers.

Multiplayer And Player Protection Settings

These settings control PvP, beginner protection, bedroll behavior, and how players interact within your server.

For private PvE worlds, setting PlayerKillingMode to 0 disables player killing, while public PvP communities may prefer different combat rules.

Performance And Spawn Settings

Performance settings control zombie and animal populations, view distance, and world rendering behavior.

Increasing MaxSpawnedZombies can make large encounters more demanding on your server, particularly during Blood Moons. Higher view distances and additional mesh processing can also increase resource usage.

For most servers, it's best to start with the default settings and make adjustments only when needed.

Land Claim Settings

Land claims allow players to protect their bases and control how protected areas behave while they're online or offline.

These settings are particularly useful for public communities where players aren't always online. Increasing land claim durability can make offline raiding more difficult, while adjusting expiry times helps manage abandoned bases.

Crossplay And Anti-Cheat Settings

These settings are particularly useful for public communities where players aren't always online. Increasing land claim durability can make offline raiding more difficult, while adjusting expiry times helps manage abandoned bases.

For console-compatible servers, ServerAllowCrossplay and EACEnabled must be enabled, IgnoreEOSSanctions must remain disabled, and the maximum player count must not exceed eight. Additional gameplay restrictions may also apply.

With Pine Hosting, you can enable 7 Days To Die crossplay through the Startup tab without manually modifying every crossplay property.

Remote Administration Settings

Remote administration settings control access to the built-in web dashboard, Telnet interface, and administrative permissions.

These interfaces provide powerful control over your server, so access should be restricted to trusted administrators. Always use secure authentication and appropriate firewall rules when enabling remote management.

Twitch Integration Settings

7 Days To Die also includes Twitch integration settings for communities using interactive livestream features.

Twitch interactions can affect gameplay by introducing additional events or enemies. Enabling these features during Blood Moons may also increase server activity and resource usage.

Configure Your 7 Days To Die Server With Pine Hosting

Customizing your server settings allows you to create a survival experience that suits your community, whether you're building a relaxed world for friends or managing a larger public server with customized progression and PvP rules.

With our 7 Days To Die server hosting, you can manage configuration files, create backups, adjust Startup options, and restart your server directly through our game panel.

Choose the settings that work for your group, keep your configuration backed up, and customize your world without having to manage a dedicated machine yourself.