7 Days to Die Server Lag Fix (Blood Moon and Rubberbanding)

7 Days to Die server lag is almost always the server's CPU falling behind on zombies and world loading, worst on blood moon nights. The fixes that help most are lowering ServerMaxAllowedViewDistance from 12 to 8, keeping MaxSpawnedZombies at 64 or below, turning off DynamicMeshEnabled if it is on, keeping the blood moon enemy count in your SandboxCode sensible, and restarting the server daily. If the server runs out of memory on a big random world, it needs more RAM.

Quick fix

1. Run mem in the console to see memory use. Close to the limit means you need more RAM or a smaller world.
2. Set ServerMaxAllowedViewDistance to 8 in serverconfig.xml.
3. Check MaxSpawnedZombies is 64 or lower.
4. Set DynamicMeshEnabled to false.
5. Lower the blood moon enemy count in your Sandbox Options and paste the new SandboxCode.
6. Restart the server once a day.

Why does 7 Days to Die lag on blood moon?

On a horde night the server spawns waves of zombies for every player and pathfinds each one through your base, block by block, while they break things. That is heavy work, and it scales with:

• Enemy count per player. Double the count, roughly double the work.
• Players in different places. Four players in four bases means four separate hordes, each pathing through a different base.
• Base design. Zombies recalculate paths constantly through complex bases with lots of blocks to break.

7 Days to Die leans on a few busy threads, so single core speed matters more than core count.

Which serverconfig.xml settings reduce lag?

These properties are still in serverconfig.xml in V3:

Stop the server, edit the value part of each line and start it again:

<property name="ServerMaxAllowedViewDistance" value="8"/>
<property name="DynamicMeshEnabled" value="false"/>

The SandboxCode settings that matter for lag

Since V3, gameplay settings such as blood moon frequency and enemy count, zombie speed and loot moved into the SandboxCode. Old lines like BloodMoonEnemyCount in serverconfig.xml are ignored. To change them, open Sandbox Options in the game, adjust, copy the new code and paste it as the SandboxCode value. Details in how to change 7 Days to Die server settings.

For lag, look at:

• Blood moon enemy count. The classic default was 8 per player. Groups of four with good bases can handle more, but every step up costs CPU. If horde nights lag, come down first.
• Zombie speed at night and on blood moons. Sprinting hordes reach and break into bases faster, which means more pathing work at once.
• Enemy spawn and density. Higher density means more zombies everywhere, all the time.

Is it the world size?

Random generated worlds (GameWorld set to RWG) come in sizes like 6144, 8192 and 10240. Bigger worlds take longer to generate on first start, use more memory and give players more room to spread out, which is the expensive part. For a small group, 6144 is plenty. Changing WorldGenSize means a new world, so decide before you start.

Fix memory problems

Run mem in the server console. It shows memory in use. If it climbs toward the limit:

• Restart daily. Long uptimes build up memory.
• Avoid huge worlds on small machines.
• Overhaul mods add many new items and entities, and need clearly more RAM. See how to install mods on a 7 Days to Die server.
• Upgrade the RAM. 8 GB suits vanilla with friends, 12 to 16 GB a big world, overhaul or larger group.

To restart cleanly:

say "Restart in 5 minutes"
saveworld
shutdown

Lag for one player only

If only one player rubber bands, check their connection and their PC. Low end PCs struggle on blood moons too, and that looks like lag. Have them lower their own view distance and verify game files in Steam. For home hosting, forward TCP 26900 and UDP 26900 to 26902, and do not run the server on Wi-Fi.

Base design tips that reduce horde lag

• Simple paths. Zombies pathfind through the cheapest route. A clear, predictable approach means less recalculation than a maze of half broken blocks.
• One horde base. If everyone defends one base, the server runs one horde area instead of several.
• Repair between waves, so the server is not tracking hundreds of damaged blocks.

The easy way on GamezServers

On GamezServers you edit serverconfig.xml in the Files tab and paste the SandboxCode into the Sandbox code setting, then press Restart. The Memory stats button runs mem for you, and Save world runs saveworld. If a plan is too small for your world, upgrade from Settings. It is prorated and the world stays. Plans are 8, 12 and 16 GB, see 7 Days to Die server hosting. For more ideas, see why is my game server lagging.

FAQ

Why does my 7 Days to Die server lag only on horde night?

Blood moons spawn waves of zombies for every player and pathfind them through bases. Lower the blood moon enemy count in your SandboxCode, and keep players defending together.

Does view distance affect 7 Days to Die server performance?

Yes. ServerMaxAllowedViewDistance caps how far players can load. Dropping it from 12 to 8 noticeably reduces server load.

How much RAM does a 7 Days to Die server need?

8 GB for vanilla with a small group. 12 to 16 GB for big random worlds, overhaul mods or more than 8 players.

Why is my BloodMoonEnemyCount change not working?

Since V3 it is part of the SandboxCode and the old line is ignored. Change it in Sandbox Options and paste the new code.

Does restarting the server help with lag?

Yes, if the lag builds up over time. A daily restart clears memory that piles up during long uptimes.