7 Days to Die Blood Moon: How to Optimize Server Performance

Every 7 days (by default), 7 Days to Die spawns a zombie horde that targets every connected player. It’s the defining feature of the game - and the single biggest performance challenge for server administrators.

Blood moon lag is the most common complaint we hear from 7DTD server owners. The good news is that most of it is fixable through settings. The key insight is understanding that blood moon performance is a CPU problem, not a RAM problem - and knowing which settings actually move the needle.

Why Blood Moons Are Hard on Servers

During a normal gameplay cycle, the server manages ambient zombie spawns, animal AI, player inventory, and world updates. The load is spread out and generally manageable.

During a blood moon, everything spikes at once:

• Zombie spawns - The server generates a horde for each connected player simultaneously
• Pathfinding - Every zombie runs AI pathfinding to navigate to players and find structural weaknesses in bases
• Block destruction - Zombies attack structures, triggering physics calculations for each damaged block
• Corpse management - Dead zombies leave corpses that the server tracks until cleanup

The critical detail: 7DTD’s zombie AI is largely single-threaded. Adding more CPU cores doesn’t proportionally help. What matters is single-core clock speed and having enough headroom for the spike.

Settings That Actually Affect Blood Moon Performance

Not all settings are the same. Here are the ones that make a measurable difference, ranked by impact. All of these are edited in serverconfig.xml via File Manager or SFTP.

1. BloodMoonEnemyCount (Highest Impact)

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

This controls the maximum number of alive zombies per player during a blood moon. The default is 8, meaning a 4-player server could have up to 32 blood moon zombies active simultaneously (plus any regular ambient spawns).

Performance impact is roughly exponential. Going from 8 to 12 per player doesn’t add 50% more load - it can effectively double it, because more zombies means more pathfinding, more block damage calculations, and more corpse management happening in parallel.

2. MaxSpawnedZombies (High Impact)

<property name="MaxSpawnedZombies" value="64" />

This is the global zombie cap - the maximum number of zombies that can exist on the server at any time, blood moon or not. It acts as a ceiling on BloodMoonEnemyCount.

If MaxSpawnedZombies is 64 and you have 8 players with BloodMoonEnemyCount 8, the math says 64 blood moon zombies - but the server will cap at 64 total including ambient spawns. In practice, during blood moons, most of that budget gets allocated to horde zombies.

For servers experiencing blood moon lag: Try reducing MaxSpawnedZombies to 40-50. The horde will feel slightly thinner, but the performance improvement is noticeable.

3. MaxSpawnedAnimals (Medium Impact)

<property name="MaxSpawnedAnimals" value="50" />

Animals compete for the same processing budget as zombies. Reducing MaxSpawnedAnimals to 30-40 frees up resources during blood moons, and most players won’t notice fewer deer and chickens while they’re fighting hordes.

4. ServerMaxAllowedViewDistance (Medium Impact)

<property name="ServerMaxAllowedViewDistance" value="12" />

View distance affects how many chunks the server loads and updates for each player. During blood moons, loaded chunks still process ambient spawns, terrain updates, and entity management even though the focus is on the horde.

Reducing this from 12 to 8-10 can improve blood moon performance, especially on servers with many players spread across the map.

5. Zombie Speed Settings (Low-Medium Impact)

Zombie speed affects how frequently pathfinding updates run. Faster zombies recalculate paths more often.

For blood moon-specific zombie speed, the relevant settings in serverconfig.xml control night-time and blood moon behavior. Running zombies at “walk” or “jog” speeds during blood moons reduces the pathfinding frequency compared to “sprint” or “nightmare” speeds.

Beyond Settings: Operational Optimizations

Schedule Restarts Before Blood Moons

7DTD’s memory leak means server performance degrades over time. A server that’s been running for 3 days will handle a blood moon worse than one that restarted that morning.

Best practice: Schedule a restart a few hours before blood moon night in game time. If your blood moon frequency is 7 (default) and your day length is 60 minutes, that’s roughly every 7 real-time hours of gameplay.

On WinterNode, use the Schedule Manager to automate daily restarts during off-peak hours. Our scheduled restarts guide covers the setup.

Player Base Design Matters

This is a player-side optimization, but worth mentioning because it has a significant server-side impact:

• Open-field horde bases perform better than city bases - fewer surrounding structures means fewer chunks to process
• Simple geometry outperforms complex traps - fewer block damage calculations per zombie
• Elevated/moat designs where zombies path through a limited number of corridors concentrate pathfinding into simpler routes
• Avoid bases near traders or cities - these areas have dense POI data that adds background load

Corpse Cleanup

Dead zombies leave corpse entities that the server tracks. During an intense blood moon with high enemy counts, corpses can pile up and add to the server’s entity management burden.

There’s no serverconfig.xml setting for corpse despawn time (it’s handled by the game engine), but killing zombies efficiently and keeping the active count manageable helps prevent corpse buildup from compounding performance issues.

Blood Moon Lag Diagnostic Checklist

If your server lags during blood moons, work through this list:

1. Check BloodMoonEnemyCount - Is it above 8? Try reducing to 6
2. Check MaxSpawnedZombies - Reduce to 40-50
3. When did the server last restart? - If it’s been 24+ hours, restart and test again
4. How many players are connected? - More players = more simultaneous hordes
5. Where are players based? - City bases or complex trap systems add load
6. Are you running mods? - Some mods add background processing that compounds during blood moons
7. Check RAM usage - If the server is near its memory limit, it may be swapping, which tanks performance

The Realistic Expectation

Blood moons will always be the most demanding thing your server does. Some level of increased load during horde nights is normal and expected. The goal isn’t zero lag - it’s keeping the game playable and enjoyable during the most intense moments.

With the right settings for your player count and server resources, blood moons should feel like an exciting challenge rather than a frustrating slideshow.

Get your 7 Days to Die server → WinterNode servers run with no CPU limits, so your server has the headroom it needs when blood moon night hits. All plans include automatic backups of your server files every 12 hours and full configuration access.