Why Your 7 Days to Die Server Lags on Blood Moon (and How to Fix It)

A 7 Days to Die server that runs perfectly for six days and falls over on the seventh is not a broken server. It is a correctly configured server meeting a blood moon it was never sized for. Horde night is by far the heaviest thing the game does: dozens of zombies pathing at once, all of them attacking blocks, all of that block damage replicating to every connected client. The good news is that the settings driving it are few, well understood, and mostly one number that almost everyone misreads. This guide explains what actually costs performance on horde night, which dials to move, and how to work out a zombie count your server can genuinely handle.

The Setting Everyone Gets Wrong

BloodMoonEnemyCount is per player, not per server. That single fact explains most horde night crashes.

The default is 8. On a solo server that means 8 zombies. On an eight player server it means the game is trying to maintain 8 zombies for each of them. Raise it to 16 because “8 felt easy” while testing alone, and on a full server you have asked for up to 128 simultaneous horde zombies, each pathing and chewing on blocks.

The value is capped at 64 in the config editor, and 64 with a full server is far past what any shared machine will hold together.

Warning: BloodMoonEnemyCount is per player. Multiply it by your expected concurrent players before you change it

Tip: Test a raised value with your actual player count online, not solo. Solo testing is what produces the crash on the first real horde night

The Real Performance Levers

Only a handful of settings meaningfully change how hard your server works. These are the ones worth knowing, with the defaults the config editor uses.

MaxSpawnedZombies is the ceiling everything else lives under. Going much past 64 is where a shared machine starts to struggle, and it is worth testing rather than assuming.

Note: MaxSpawnedZombies is map-wide and BloodMoonEnemyCount is per player. They interact, and the map-wide cap wins

Tip: Lowering MaxSpawnedAnimals frees very little compared to lowering zombie counts, spend your effort on the zombie dials

Why Blood Moon Costs So Much More

Understanding the shape of the problem makes the numbers make sense. On a normal night, zombies are spread across the map, most of them far from players and cheap to simulate. On horde night, three expensive things happen at once.

1. Pathfinding converges. Every horde zombie is actively routing toward a player rather than wandering. That is continuous path calculation, not idle behaviour.
2. Block damage becomes constant. Zombies attack structures, and every damaged block is a world change that must be saved and sent to clients.
3. Everything happens in a few small areas. All that load lands on the handful of chunks where players have built, rather than being spread out.

This is why a server with plenty of headroom on day six falls over on day seven. The average load was never the problem; the peak is.

Note: Block damage during horde night is a bigger cost than the zombies themselves on heavily fortified bases

Tip: A base built from thousands of individually damageable blocks is heavier than a compact one, even with the same zombie count

Sizing It For Your Server

The practical approach is to start conservative and raise it once, deliberately, after watching a real horde night.

1. Leave MaxSpawnedZombies at the default 64 to begin with
2. Set BloodMoonEnemyCount so that your realistic peak player count multiplied by it stays at or under that cap
3. Run one blood moon with your normal group online
4. Watch CPU and memory on the server during it rather than after
5. If it held comfortably, raise BloodMoonEnemyCount by a small step and repeat

A worked example: if you usually have six players on, then BloodMoonEnemyCount at 8 asks for up to 48 zombies, which sits under a 64 cap. Raising it to 16 asks for 96, which does not, so the map-wide cap becomes the thing actually limiting your horde and the difficulty will not increase the way you expected.

Tip: If your per-player count multiplied by your player count exceeds MaxSpawnedZombies, raising it further changes nothing except load

Warning: Watch the server during the horde, not afterwards. A server that has already shed its load reads healthy once the dead have despawned

Making Horde Night Easier Without Making It Boring

If your server cannot hold the count you want, there are ways to keep horde night interesting that cost far less.

• Raise BloodMoonRange to 1 to 3 so the horde day is not perfectly predictable. Uncertainty adds tension for free.
• Lower BloodMoonWarning so players get less notice. This costs nothing at all.
• Raise BlockDamageAIBM so the same number of zombies does more damage to structures. Fewer entities, same pressure.
• Increase zombie speed at night rather than zombie count. Movement settings are far cheaper than spawning more.

All four make horde night harder without asking the server to simulate more entities.

Tip: Increasing damage or speed is almost always cheaper than increasing count, and often feels more dangerous

Note: Setting BloodMoonFrequency to 0 disables horde nights entirely. Tell your players if you do, or they will over-fortify for an event that never comes

Using the Presets

The 7 Days to Die Config Editor on Loafhosts ships five curated presets, applied in a single save: Vanilla, Casual PvE, Hardcore, PvP, and Builder. They are a fast way to move a whole set of related settings at once rather than changing twenty fields by hand.

None of the presets touch world generation settings, so every one of them is safe to apply to an existing world. They only need a restart, not a fresh map. Worth knowing what they do to horde night: the Hardcore preset raises the horde count and adds blood moon randomness, while the Builder preset disables blood moons entirely.

Note: Presets never change world generation, so applying one does not require a new world

Note: Player slots and game difficulty are managed from the Server Settings (Startup) tab, so a preset cannot change those

Applying Changes and Confirming They Took

Open your server in the LoafHub panel and pick Config Editor from the sidebar. It gives you serverconfig.xml as a searchable form with each setting’s range and a note on what it does, plus a raw XML mode if you prefer. Settings the panel manages from the Startup tab appear read-only, showing their real runtime value rather than a stale one from the file.

1. Open Config Editor on your server
2. Search for the setting by name, for example BloodMoonEnemyCount
3. Change it and save
4. Restart the server, since 7 Days to Die reads this file at boot
5. Confirm the new value is shown after the restart

Warning: Saving writes to disk but does not apply the change. The server reads serverconfig.xml at boot, so restart before expecting anything different

Tip: Change one dial at a time between horde nights, so you know which change caused the difference

Frequently Asked Questions

Why does my 7 Days to Die server lag only on blood moon?

Because horde night is the game’s peak load. Every horde zombie actively paths toward a player, constantly damages blocks, and all of it happens in the few chunks where players have built. A server that is comfortable on an average night can still be far past its limit at that peak.

Is BloodMoonEnemyCount per player or per server?

Per player. Eight players with the setting at 8 asks the server for up to 64 simultaneous horde zombies. This is the most common reason a value that felt fine in solo testing crashes a full server.

What is the best MaxSpawnedZombies setting?

The default of 64 is a sensible starting point and is roughly where a shared machine begins to struggle if you go much higher. Because it is a map-wide cap, raising BloodMoonEnemyCount above what this allows adds load without adding difficulty.

How do I make horde night harder without lagging the server?

Raise block damage during blood moon, increase zombie movement speed at night, add randomness with BloodMoonRange, or cut the warning time. All of these increase pressure without asking the server to simulate more entities.

How do I turn off blood moons?

Set BloodMoonFrequency to 0 in the Config Editor and restart. Tell your players, because a building-focused server where nobody knows the horde is disabled leads to a lot of wasted defensive work.

Do I need a new world to change these settings?

No. Horde night and spawn settings apply to an existing world, they just need a restart. None of the config editor presets change world generation either, so they are safe to apply to a map you have already been playing.

Why did my setting not change anything?

Either the server was not restarted, since the file is read at boot, or the key is one the panel manages from the Startup tab, in which case the file value is ignored. The Config Editor marks those keys read-only and shows their real runtime value.