7 Days to Die Blood Moon Not on Day 7? Read Frequency and Range

Read settings before interpreting the sky

The community wiki identifies Frequency as the base interval and Range as a permitted delay. Its settings page also permits disabling Blood Moons. A custom world or dedicated server can therefore make 'every seventh night' false without the game being broken.

Check the setting in the world menu if you own the save. On a server, ask the admin for the effective saved configuration; a player's recollection of the original preset is weaker than current server settings. A warning option can also change when the day number turns red, so do not use the red number alone as a scheduling setting.

1. Record current day and whether a Blood Moon has already occurred in this world.
2. Read Blood Moon Frequency, Blood Moon Range and whether the event is enabled in the actual saved settings or server configuration.
3. If Range is zero, add Frequency to the previous event day to get the next nominal day. For the first event, use the configured first cycle.
4. If Range is nonzero, make a window from previous event day + Frequency through that day + Range. Prepare for the earliest possible night, then keep the base ready until the window ends.
5. If the event still does not appear by the end of the computed window, record the settings, world day, last actual event, multiplayer status and any mods for a specific bug report.

References: 7 Days to Die Wiki: Blood Moon Horde · 7 Days to Die Wiki: Game Settings

Turn the settings into a date window

The table uses wiki examples, not a promise for every custom server. Frequency is relative to the last Blood Moon. Range is an additional delay, not a random number of early days.

References: 7 Days to Die Wiki: Blood Moon Horde · 7 Days to Die Wiki: Game Settings

Worked example: why Day 14 can be quiet

Illustrative calculation: the first event happened on Day 8, not Day 7, with Frequency 7 and Range 1. The wiki's rule makes the next window Day 15 or 16. Standing on a base roof on Day 14 and seeing nothing is therefore consistent with these settings, not proof of a failed spawn.

If the saved values instead read Frequency 7 and Range 0 and the last event was Day 7, Day 14 becomes the expected date. At that point, investigate changed server settings, event disablement or a mod rather than reusing the Range-1 explanation.

References: 7 Days to Die Wiki: Blood Moon Horde · 7 Days to Die Wiki: Game Settings

Keep the variables visible

If several players disagree, log the actual Blood Moon dates in the same save. This avoids treating a late first event as a permanent seven-day calendar. The publisher announcement index gives release context, but it does not validate a particular server configuration or experimentally confirm the next event.

Build / solo or server / mods:
Blood Moon enabled?
Frequency / Range / Warning:
Last observed Blood Moon day:
Earliest next day = last + Frequency:
Latest next day = earliest + Range:
Actual next event day:

Before you play

• Saved Frequency and Range read.
• Last actual event day recorded.
• Next window calculated from last event.
• Server or mod deviations kept separate.

Frequently asked questions

Sources & revision notes

Editorial revision: September 26, 2026. Source notes give the scope of each reference; the revision date is not a gameplay test date. Official documentation describes the publisher's system; community sources can contain errors. Use your installed game's own descriptions when they disagree.

1. 7 Days to Die Wiki: Blood Moon Horde (Community)

   Community-maintained frequency/range examples checked September 26, 2026; world and server settings override the default example.

2. 7 Days to Die Wiki: Game Settings (Community)

   Community-maintained setting definitions checked September 26, 2026; read your own world's saved values.

3. The Fun Pimps: official Steam announcements (Official)

   Publisher announcement index checked September 26, 2026 for release context; this guide does not assert that experimental changes are in the stable build.