Blood Moon Lag and What Actually Fixes It

Horde night is a CPU problem, not a memory one. Turn down zombies alive at once, view distance and the blood moon count. Adding RAM will not help.

3 min read · Updated Oct 25, 2026 · By GuavaHost Team

Horde night lag comes from the server doing too much thinking at once, not from running out of memory. Three settings fix it, and buying more RAM fixes none of it.

Why RAM is the wrong lever

The game runs its main loop on a single thread. During a blood moon, zombie pathfinding, block physics and corpse handling all spike at the same moment, all on that one thread. Memory use barely moves. A server with 24 GB and the default settings will stutter on horde night in exactly the same way as one with 8 GB.

This is worth saying plainly because every hosting page you will read suggests more memory for this, and it is the one thing that does not help.

The three settings that do

All three are on the Server settings page in your server's menu. Save, then restart.

Zombies alive at once, whole map. Default 64. The game's own configuration file carries the warning that much above 80 makes a server run at poor framerates, and the setting covers the entire map rather than per player. On a busy server, 48 is a reasonable place to start if horde night is rough.

Maximum view distance. Between 6 and 12, default 12. This has the largest effect of anything on this page, every night of the week and not only on day seven. At 8 instead of 12 the server loads well under half as much world for each player. Your players lose some distant scenery; they keep a server that holds up.

The blood moon count, which is in your Sandbox code rather than in the file. Since the V3.0 update, blood moon frequency, range and enemy count moved out of the server settings and into the code you generate in the game's own Sandbox Options screen. Lowering the per player enemy count there is the direct fix for horde night specifically. 7 Days to Die server settings explains how to make a new code and paste it in.

In what order to try them

1. View distance to 10, then 8 if it is still rough. Restart and play a normal evening on it before judging.
2. Zombies alive at once down, in steps. 64 to 48 is noticeable.
3. The blood moon enemy count in a new Sandbox code, if horde night specifically is the problem rather than every evening.
4. Only then look at the size of the map, and only if your group is spread right across it.

Change one at a time. Changing all three means learning nothing about which mattered.

Things that are not the cause

• Your own frame rate. If the game stutters for you but the server's console is quiet and nobody else notices, that is your machine.
• Memory, as above. Check the Usage card on the Overview tab anyway: if memory really is sitting at the limit, that is a separate problem and how much RAM does a 7 Days to Die server need covers it.
• The number of players, mostly. Eight players standing together cost far less than eight players in eight different places, because it is loaded world that is expensive, not people.

Common questions

Why does the server lag every night, not just on blood moons?

Then it is view distance and how spread out your group is, rather than the horde. A server keeps the world loaded around every player, so a group that has split up across a big map is asking it to hold several separate regions at once. Lower view distance first.

Will a smaller map help?

A little, and less than you would think on current versions. Map size costs generation time and download size more than it costs ongoing performance. View distance is the setting that decides how much of the map is actually in play at any moment.

Is it worth turning off dynamic mesh?

Try leaving it on but limited to land claims first, which is the default and much cheaper than letting the whole map collapse realistically. Turning it off entirely means buildings stop falling down properly, which is a visible loss for a modest gain.

Can I see what the server is struggling with?

The Console tab prints periodic lines with the server's frame rate and the number of entities and chunks loaded. Watch those during a blood moon: if the frame rate drops while memory stays flat, you are looking at exactly the problem this page describes.

• 7 days to die
• performance
• lag
• blood moon
• view distance

Host a 7 Days to Die server From $12.99/mo, with instant setup and DDoS protection.

Still need help? Our team is online 24/7 to answer questions.

Contact support