Blood Moon lag is usually an entity-load problem on the server’s main thread, not an internet-speed mystery. Each player increases the number of zombies the game must spawn, simulate and network at once. Start by measuring a normal night against a Blood Moon, then lower BloodMoonEnemyCount and, if necessary, the multiplayer cap MaxSpawnedZombies in small steps. Check view distance, heavy mods, save-disk latency and network symptoms before buying hardware.
Playing with friends? Godlike.Host runs hosted 7 Days to Die servers from 10 data-center locations, with free DDoS protection.
Why the server stutters on Blood Moon
During an ordinary night, the server has a relatively stable entity workload. A Blood Moon creates a synchronized surge: zombie spawning, pathfinding, damage checks, block interaction, loot and movement updates all arrive together. The work is concentrated on the game’s main thread, so a machine can show moderate total CPU usage while one core is saturated. When that thread cannot finish a tick on time, players see delayed actions, frozen zombies, rubber-banding and falling TPS.
As an Amazon Associate I earn from qualifying purchases.
The setting BloodMoonEnemyCount is the number of zombies alive simultaneously per player during a Blood Moon. In multiplayer, MaxSpawnedZombies can override that per-player result with a map-wide ceiling. The Official 7 Days to Die Wiki describes the latter as applying to the entire map and warns that changing it has a “huge impact on performance.” The referenced Alpha 20.5 b2 configuration extract lists defaults of 8 for BloodMoonEnemyCount and 64 for MaxSpawnedZombies; treat those as version-specific defaults, not permanent rules.
There is no universal Blood Moon value or guaranteed TPS target that works for every world. Party size, mod scripts, view distance, CPU architecture, world age and crossplay traffic all change the workload. A measured, one-variable-at-a-time loop is safer than copying a number from another server.
#1 Best Overall
- MEET THE NEXT GEN: Consider this a cheat code; Our Samsung 990 PRO Gen4 SSD helps you reach near max performance with lightning-fast speeds; Whether you’re a hardcore gamer or a tech guru, you’ll get power efficiency built for the final boss
- REACH THE NEXT LEVEL: Gen4 steps up with faster transfer speeds and high-performance bandwidth; With a more than 55% improvement in random performance compared to 980 PRO, it’s here for heavy computing and faster loading
- THE FASTEST SSD FROM THE WORLD'S FLASH MEMORY BRAND: The speed you need for any occasion; With read and write speeds up to 7450/6900 MB/s you’ll reach near max performance of PCIe 4.0 powering through for any use
- PLAY WITHOUT LIMITS: Give yourself some space with storage capacities from 1TB to 4TB; Sync all your saves and reign supreme in gaming, video editing, data analysis and more
- IT’S A POWER MOVE: Save the power for your performance; Get power efficiency all while experiencing up to 50% improved performance per watt over the 980 PRO; It makes every move more effective with less consumption
Match the symptom to the bottleneck
| What players report | First investigation | Why it fits |
|---|---|---|
| Stutter only on Blood Moon or horde night | Spawn counts and party size | The synchronized entity surge can saturate the main thread even when normal nights are smooth. |
| The whole server slows as several players join | Single-thread CPU load and shared-vCPU limits | More players add simulation and networking work; a shared virtual core may be the ceiling. |
| Lag spikes every few minutes | World-save writes and save-directory latency | Periodic disk activity can pause the server independently of Blood Moon spawning. |
| Rubber-banding or desynchronization | Network path, upload capacity and round-trip time | Packets arriving late or being queued look like simulation lag to players. |
| One player has low frame rate while everyone else is smooth | That player’s client graphics settings and hardware | A client rendering problem does not imply that the dedicated server is overloaded. |
| Performance worsens during a long session | Thermal throttling and background processes | Clock speeds can fall after sustained load, while backups, updates or scans compete for resources. |
Build a baseline before changing settings
Record one normal night and one Blood Moon with the same players online. Use the host operating system’s per-core CPU view, memory and disk-latency counters, a ping or equivalent RTT check from representative players, and the 7 Days to Die server log. Note the exact game version, player count, mod list and configuration values. A baseline turns “it felt laggy” into evidence that can identify the limiting resource.
- Record the workload. Write down online players, approximate world activity, Blood Moon start time and the number of zombies visible. Keep the party size stable for the first comparison.
- Watch CPU by core. Total utilization can hide one fully occupied core. A repeatable spike on one core during the horde is evidence for a main-thread limit.
- Record RAM use and paging. Note whether memory pressure or swap activity appears as the horde begins. Do not assume adding RAM helps if the main thread is already CPU-bound.
- Measure storage behavior. Watch latency and queueing for the drive that contains the world save. Correlate periodic spikes with save messages in the server log.
- Check the network separately. Compare RTT and packet loss during a quiet period and during the Blood Moon. Ask whether all players experience delay or only users on one route.
- Save a configuration copy. Back up
serverconfig.xmland record every value you change, the restart time and the next horde-night result.
Use the next Blood Moon as the test window. Change one variable at a time; otherwise an improvement cannot be attributed to a particular fix.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Tune Blood Moon spawning safely
Understand the two controls
BloodMoonEnemyCount scales the simultaneous Blood Moon population per player. More players therefore increase the potential entity count even when the setting is unchanged. MaxSpawnedZombies is a map-wide multiplayer limit; it can become the controlling value when the per-player calculation would exceed the cap. The official configuration description explicitly calls this setting high impact, so large jumps can change both performance and the feel of the horde.
Rank #2
- Ideal for high speed, low power storage
- Gen 4x4 NVMe PCle performance
- Up to 6,000MB/s read, 4,000MB/s write
- Includes Acronis cloning software
- 5-year limited warranty
Use a controlled reduction loop
- Open the server’s
serverconfig.xmlwhile the server is stopped, or use the administration method provided by your host. Keep the backup made during baseline collection. - Lower
BloodMoonEnemyCountby a small step rather than jumping to a minimum. Choose a value that preserves the intended challenge for your actual party size. - Restart the server if your platform requires a restart for configuration changes. Confirm in the startup log that the new value was loaded.
- Run the next Blood Moon with a comparable number of players. Record per-core load, log behavior, responsiveness and player experience.
- If TPS still falls, check whether
MaxSpawnedZombiesis the active multiplayer ceiling. Reduce that cap gradually, restart, and test again. - Stop reducing when the main-thread spike is acceptable and the horde remains playable. Do not alter both settings in the same test cycle.
Lower counts reduce entity work immediately, but they also reduce the number of simultaneous enemies and therefore the pressure on players. Communicate the change to the group before the next horde night. A cap that is too low can make a large party feel strangely quiet even though the server is healthy.
Version and platform limits
An official cross-platform help extract lists ServerMaxPlayerCount up to 8 and BloodMoonEnemyCount from 4 to 64 for cross-platform dedicated servers. These limits and labels can change between game versions and platforms. Confirm the current version’s configuration reference before pasting values, and validate that the server accepted them after restart.
Reduce secondary server work
Lower server view distance when the world is crowded
ServerMaxAllowedViewDistance controls how much of the world the server must maintain for connected players. The server reference classifies view distance as high impact for memory and performance. Lower it for crowded or crossplay servers after spawn tuning, especially when several players are spread far apart. This can reduce memory and simulation work without changing the Blood Moon count, but players may see less distant terrain and activity.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #3
- SPEED UP PROJECTS. Launch creator applications fast with uncompromising PCIe 4.0 read speeds up to 7,100MB/s,[2] (1TB and 2TB[1] models) and write speeds up to 6,700MB/s[2] (1TB[1]-4TB[1] models).
- CREATE AND STORE MORE. Make more room for your 4K videos and high-resolution images with capacities from 500GB[1] up to 4TB[1] on M.2 2280 built with our trusted 8th generation SANDISK BiCS QLC 3D CBA NAND.
- IT GOES WHERE YOU GO. With an all-new power efficient design, your drive delivers high performance with low power, giving you more time to be productive while on the go.
- UNCOMPROMISED RELIABILITY. With up to 1,200 TBW[3] (4TB[1] model) endurance rating, your drive is designed for creators.
- KEEP YOUR DRIVE UPDATED. Monitor your SSD’s performance and check for updates with the downloadable SANDISK Dashboard application.[5]
Audit mods and large prefab packs
Disable or remove one suspect mod at a time, beginning with mods that run frequent scripts, add complex entities or replace large world-generation systems. Large prefab packs can increase world and save activity even when they are not visible during the horde. The performance guide’s practical advice is to remove the worst heavy-script offender rather than spend hours chasing many tiny tweaks. Keep a separate test copy of the world so a mod removal does not damage the live save.
Protect the save directory
Place the world save on a fast NVMe SSD when possible. NVMe storage can shorten save and load operations and help with periodic disk-induced spikes; it cannot cure a CPU-bound Blood Moon. Keep adequate free space, exclude the active save from real-time scans only when your security policy permits it, and avoid running backups, compression or updates on the same disk during horde night.
Hardware and hosting capacity
The performance guide prioritizes strong single-core performance because 7 Days to Die still leans heavily on one main thread. More total cores do not automatically solve a saturated game thread, particularly on a shared virtual CPU. Sustained clock speed matters as well: a processor that throttles under heat can perform worse late in a long session.
Rank #4
- HUGE SPEED BOOST: Get random read/write speeds that are 40%/55% faster than 980 PRO; Experience up to 1400K/1550K IOPS, while sequential read/write speeds up to 7,450/6,900 MB/s reach near the max performance of PCIe 4.0*
- BREAKTHROUGH POWER EFFICIENCY: Use less power and get more performance; Enjoy up to 50% improved performance per watt over 980 PRO, plus optimal power efficiency with max PCIe 4.0 performance**
- SMART THERMAL CONTROL: Samsung's own nickel-coated controller delivers effective thermal control; With its slim size, 990 PRO is a perfect fit for desktops and laptops that meet the PCI-SIG D8 standard***
- THE CHAMPION MAKER: Up to 65% improvement in random performance enables faster loads for an ultimate gaming experience on PS5 and DirectStorage PC games****
- SAMSUNG MAGICIAN SOFTWARE: Get the most out of your SSD with Samsung Magician's advanced yet intuitive optimization tools; Monitor drive health, protect valuable data, and receive important updates for your 990 PRO
| Capacity guidance | Qualification | What it helps |
|---|---|---|
| 16–24 GB RAM | Recommendation for modded servers in the 2026 7 Days To Die Wiki performance guide | World, mod and operating-system memory headroom |
| 32 GB RAM | Recommendation for large crossplay servers in the same guide | Larger player populations, crossplay overhead and heavier worlds |
| 20–30% CPU headroom | Guidance for horde nights and large crossplay parties | Room for Blood Moon spikes instead of running continuously at the limit |
| 10 Mbps upload per 8 players | Minimum crossplay upload guidance from the 2026 performance guide | Outgoing world and entity updates; it is not a substitute for low latency |
RAM headroom prevents paging and gives mods room to operate, but it does not replace main-thread performance. Likewise, meeting the upload figure does not guarantee smooth play if the route has high RTT, packet loss or queueing. Check the measured bottleneck before upgrading.
Network checks for rubber-banding
When only movement and hit confirmation arrive late, compare network evidence with server CPU timing. Test from more than one player location if possible. A stable server log and comfortable CPU headroom alongside rising RTT points away from the host processor. Check the server’s upload saturation, router queueing, Wi-Fi interference and the route between the affected player and host. If every player sees delayed simulation at the same instant and one core is pegged, return to spawn and script tuning instead of replacing network equipment.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A practical order of operations
Use this sequence so an inexpensive, reversible change is tested before a hardware purchase:
Best Value
- This product has been replaced by our latest generation. Please search for the SANDISK Optimus GX 7100 NVMe SSD
- HIGH-OCTANE GAMING. Experience speeds up to 7,250MB/s read and 6,900MB/s write (1-2TB models), with up to 35% faster performance than previous generation.
- PURPOSE-BUILT. Designed for serious on-the-go gamers, with a PCIe Gen4 interface and SANDISK’s next generation TLC 3D NAND.
- MORE TIME TO CLEAR THAT CHECKPOINT. Built with laptops and handheld gaming devices in mind, with up to 100% more power efficiency over the previous generation.
- DO MORE WITH DASHBOARD. Ensure your drive is optimized for prime performance with the downloadable WD_BLACK Dashboard (Windows only).
- Reproduce and record. Capture normal-night and Blood Moon CPU-per-core, RAM, disk latency, RTT and logs.
- Control party size for the test. Record how many players are online; player count directly changes the potential Blood Moon population.
- Reduce
BloodMoonEnemyCount. Make a small edit, restart if required, and test the next comparable horde. - Check
MaxSpawnedZombies. If the cap is still producing a main-thread spike, reduce it gradually and test separately. - Lower
ServerMaxAllowedViewDistance. Prioritize this for crowded or crossplay worlds with memory or broad-area simulation pressure. - Remove the heaviest script or prefab pack. Test on a copy and change one mod at a time.
- Fix storage and background contention. Move saves to NVMe when disk latency is the culprit and schedule scans or backups outside horde night.
- Upgrade or relocate hosting only after evidence. Choose stronger single-core performance, dedicated rather than shared CPU time, sufficient RAM and the required upload capacity.
Choosing the right fix for common server setups
Small vanilla party
Start with the two spawn controls and verify that a single core, rather than disk or network, is peaking. Keep view distance unchanged unless the baseline shows broad-area memory pressure. A modest count reduction usually preserves more of the original design than a large map-wide cap reduction.
Modded server
Collect a baseline with the complete mod list, then disable the most script-heavy suspect on a test copy. If the horde becomes smooth without changing counts, the mod is the efficient target. Retain enough RAM for the mod set, but still check the main thread because memory capacity cannot compensate for excessive per-tick work.
Large crossplay group
Check all three constraints together: spawn population, view distance and network upload. The guide recommends 32 GB RAM, 20–30% CPU headroom and at least 10 Mbps upload per eight players for crossplay. Confirm the platform’s player and Blood Moon ranges before editing, since cross-platform limits may differ from older PC configurations.
Shared virtual server
Look for a repeatable slowdown whenever several players connect, even outside Blood Moon. If one virtual core reaches its limit while neighboring cores are idle, noisy neighbors or a shared-vCPU ceiling may be responsible. Ask the host for dedicated CPU time or move to hardware with stronger single-core performance only after saving your baseline evidence.
Common mistakes and recovery
- Changing both spawn settings at once: restore the backup or revert one value, then retest so you know which control helped.
- Copying Alpha 20.5 b2 defaults into a newer build: treat the 8 and 64 figures as historical references and verify the current version’s accepted range.
- Judging by total CPU percentage: switch to per-core monitoring; a main-thread ceiling can hide behind a low overall average.
- Buying RAM for a CPU spike: confirm paging or memory pressure first; otherwise the upgrade may not change Blood Moon TPS.
- Blaming the server for one player’s low FPS: compare the other players’ experience and inspect that client’s graphics load.
- Editing while the server is running: stop it, preserve a known-good copy, and verify the loaded value in the startup output.
- Removing a mod from the live world without a copy: test on a duplicate save because prefab and script dependencies can alter world data.
What a successful test looks like
After each change, compare the same observations: the highest per-core CPU load during the horde, log timing, disk latency, RTT, visible rubber-banding and player count. Improvement means the main-thread spike is lower or shorter and the server remains responsive at the intended party size. If only one player improves, investigate that player’s client or route rather than declaring the server fixed. If no metric changes after a spawn reduction, check whether the map-wide cap, a mod script, disk writes or networking is the actual limiter.
Keep the final configuration, test date, game version and mod list with the server’s administrative notes. Re-test after a game update, a major mod change or a larger party because each can move the bottleneck.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
