Blood moon lag on a 7 Days to Die server almost always comes down to one thing: how many zombies your server has to spawn, path, and simulate at once on a single CPU core. This guide covers the exact settings that move the needle in V3.0 (Dead Hot Summer), where those settings now live, and why buying more RAM will not fix it.
Why blood moons tank server performance
On a normal night your server spawns a handful of wandering zombies. On horde night it spawns a continuous stream that actively hunts every player's base, and each of those zombies runs AI pathfinding against your base geometry many times a second. In 7 Days to Die, spawning and pathfinding run on a single thread, so blood moon load is bound by one CPU core's clock speed, not by how many cores you have and not by RAM.
It gets heavier than the numbers suggest. During a blood moon the world zombie cap climbs to roughly 1.9x your MaxSpawnedZombies value, so a server set to 64 can be simulating around 120 zombies at peak. When that one core saturates, the server's simulation loop slows down and every player rubber-bands at once.
Blood moon lag is a CPU problem, not a RAM problem
This is the single most misunderstood thing about 7 Days to Die hosting. A 7 Days to Die server sits comfortably in about 6 to 8 GB, so unless you were genuinely running out of memory, adding more RAM does nothing for horde-night frame rate. The bottleneck is per-core clock speed, which is exactly why we run 7 Days to Die on high-clock Ryzen 9 hardware.
Size your memory correctly so the server is never starved, but do not expect more GB to raise your blood moon performance. Use our 7 Days to Die RAM calculator to pick the right amount for your player count and map, and see plans on the 7 Days to Die server hosting page.
The single biggest lever: Blood Moon Count
In V3.0, blood moon behavior lives in your world's Sandbox Code, not in serverconfig.xml. The setting that matters most is Blood Moon Count (BloodMoonEnemyCount): the maximum number of zombies alive per player during a horde. The default is 8, and the options run 4, 6, 8, 10, 12, 16, 24, 32, and 64.
Above 12 the cost climbs fast. Nearby players share a group cap of about 30 zombies, and the world cap scales to roughly 1.9x MaxSpawnedZombies, so raising this setting is the quickest way to bury your CPU. If your server chugs on horde night, drop Blood Moon Count to 6 before you touch anything else. Solo and small servers can usually keep 8. Larger groups fighting from one base should stay at 6 to 8 rather than chasing a "more zombies is more fun" number.
Build or edit your code with our free 7 Days to Die Sandbox Code generator, then paste the result into the SandboxCode field in your panel. A value of A means all defaults.
The global cap: MaxSpawnedZombies
MaxSpawnedZombies lives in serverconfig.xml and is editable in the Config tab of your DoomHosting panel. The default of 64 is the baseline world cap, and blood moon pushes the effective ceiling to about 1.9x that (roughly 120 zombies). Lowering it to 50 hard-caps how many zombies can ever exist at once, which is the bluntest way to guarantee headroom, at the cost of a thinner horde. Reach for this only if Blood Moon Count alone did not fix the lag.
Two neighbours in the same file give you a little more room:
MaxSpawnedAnimals(default 50): dropping to 30 to 40 frees resources the horde can use.ServerMaxAllowedViewDistance(default 12): lowering to 8 to 10 reduces how much of the world each client keeps loaded and simulated.
Tame the settings that multiply pathfinding
These all live in the Sandbox Code and quietly decide how expensive each zombie is:
- Zombie BM Speed (
ZombieBMMove): at Sprint or Nightmare, zombies recompute their path constantly. Setting blood moon speed to Run or Jog visibly cuts CPU during the horde. - Zombie Digging (
AllowZombieDigging): digging zombies path through terrain in three dimensions, which is far more expensive than surface pathing. Turn it off if you are squeezing out every frame. - Feral Sense and AI Smell: wider senses mean more zombies actively pathing toward players at the same time. Default or Night is lighter than All.
- BM Block Damage: not a performance dial by itself, but a base being torn apart triggers constant block updates, so extreme values add load on top of everything else.
Base design matters more than any slider
The server runs pathfinding against your actual base every tick, so the shape of your base is a performance setting whether you think of it that way or not. A dense, multi-layer maze made of hundreds of individual blocks gives the pathfinder far more to chew on than a simple, open kill-corridor. Fewer path nodes means cheaper AI.
Keep horde bases clean and geometric, avoid enormous block-count fortresses if the server is already near its limit, and spread player bases out so blood moon groups do not all stack on a single point.
Operational fixes that actually help
- Restart before horde night. 7 Days to Die accumulates memory over long uptimes. A restart on the morning of the horde clears the cruft so the server meets the blood moon fresh. Our panel can schedule restarts for you.
- Stay on the current build. Every patch ships AI and spawn optimizations. If you are behind, follow our V3.0 update guide.
- Let corpses expire. Corpse block piles and loot bags are entities the server tracks. The default timers are fine, so do not set corpses to never disappear.
Blood moon tuning checklist
- Blood Moon Count at 6 to 8 in the Sandbox Code, never higher on a busy server.
- MaxSpawnedZombies at 50 to 64 in the Config tab.
- Blood moon zombie speed at Run, not Sprint or Nightmare.
- Zombie Digging off if you are still dropping frames.
- Restart the server before the horde.
- Simple base geometry, bases spread apart.
- Confirm you are on the latest V3.0 build.
Frequently asked questions
Will more RAM fix my blood moon lag? No. 7 Days to Die blood moon performance is bound by single-core CPU speed. Add RAM only if the server is genuinely running out of memory, which you can check with the RAM calculator. More GB will not raise horde-night frame rate.
How many blood moon zombies is too many? Above 12 per player scales hard. For a busy server, 6 to 8 is the sweet spot. The 64 option is a novelty that will lag almost any host.
Where do I change blood moon settings in V3.0? Blood Moon Count, frequency, and zombie speed all live in the Sandbox Code, which you build with our Sandbox Code generator. The global MaxSpawnedZombies cap lives in serverconfig.xml, editable in your panel's Config tab. For a full walkthrough of every blood moon setting, see how to configure blood moon settings.
Does lowering the cap make blood moons boring? A little, so lower the per-player Blood Moon Count first and only touch the global cap if you have to. Most players never notice 8 versus 10 zombies, but the server does.
Ready for a horde night that holds up? Rent a 7 Days to Die server tuned for blood moons on high-clock Ryzen 9 hardware.