Tracked buildv1.003

Version-stamped guides

The 30-Day Time System in The Blood of Dawnwalker, Explained

Updated 2026-09-04

On this page

Quick Answer

Sourced 2026-09-04, build 1.003

The Blood of Dawnwalker runs on a 30-day calendar. Time moves in discrete segments — the game's hourglass icon shows what an action costs before you commit. Fast travel, waiting and day-night switches spend segments; wandering and searching don't (developer interviews + in-game UI). When the days run out, the story doesn't end. Public sources disagree on per-action costs — this page documents every claim.

Thirty days to do everything — that's the pitch, and it's the real rules of the game, not a marketing timer. The calendar only advances when you spend it: each action shows its price in segments on the hourglass icon before you confirm. That design turns time into the game's true currency, and this page is its public ledger. One warning up front: the internet is full of confident numbers for segment costs, and they contradict each other. We document every claim with its source and date — and leave the cell empty where nobody reliable has one.

The 30-second answer: the 30-day limit is an in-game calendar — actions with an hourglass icon spend time segments (fast travel, waiting, day/night switches, learning some skills); walking and searching are free. At day 30 the story doesn't end — the world continues and consequences land (per Rebel Wolves interviews). Exact per-action costs are disputed across public sources; this page lists each claim with its source and date.

How the Calendar Actually Moves

Four mechanics hold across every reliable source:

  • The clock is action-driven, not a real-time countdown. Walking, watching, listening — none of it moves the calendar. Only marked actions settle a cost.
  • Every cost is previewed. The hourglass icon displays what an action spends before you confirm. There is no hidden timer — the UI itself is the contract.
  • The count is days and nights. Sources consistently describe the budget as 30 days plus 30 nights — a two-axis calendar, not one bar.
  • It is a per-playthrough mechanic. The limit lives inside your run; outside the game, real time is yours. Save, close the launcher, come back tomorrow — the calendar waits.

What's Free

Each line carries its sourcing state — the same ◐ Sourced label the rest of the site uses, checked 2026-09-04:

  • Walking, exploring, gathering — ◐ Sourced (multiple guides agree)
  • Ordinary fights that don't settle a marked task — ◐ Sourced (multiple)
  • Climbing a tower to reveal the map — ◐ Sourced
  • Fast travel between activated shrines — ◐ Sourced (three sources point the same way; it still heads our re-check list, noted honestly)
  • Reading the map and planning a route — ◐ Sourced

Free movement pairs with the toolkit that shaves it further: the wolf-form Shapeshift travels fast over open ground, and the night-senses Focus scan cuts search time after dusk.

What Spends Segments

The timed side of the ledger, with each claim's source:

  • Starting or advancing a marked quest — ◐ Sourced (multiple)
  • Settling camp, rescue and treasure activities — ◐ Sourced
  • Repairing a broken shrine — ◐ Sourced
  • Learning most skills — ◐ Sourced (four sources agree this costs segments; the per-skill amounts are the site's core open question — every skill page in our database carries its cost as sourced, or ?). The night-only opener Ravenous Flock is a typical entry: its row shows what the community knows and the ? where nobody has documented the learning cost yet.
  • Skipping time forward at a shrine — ◐ Sourced, single detailed source (allthings.how's shrine write-up); still flagged for a second source

Waiting itself is the boundary case: Game8's wording says time can be skipped at shrines, but whether plain waiting — or sleeping — settles a cost is undocumented in public sources. Marked ? rather than filled.

Every Action's Cost — What Public Sources Say

Here is the disagreement, laid out the way our conflicts system holds it — no averaging, no picking a winner:

ClaimSourceStatus
Each day and each night splits into 10 notches; most activities cost one or twoallthings.how (Sep 3, 2026)Registered, unconfirmed
The prologue's whole budget totals 8 — with about 17 needed to do every taskGameRant / TheBigLead (Sep 3, 2026)Registered, unconfirmed
The full calendar is 480 units (30 days × 16)Wiki shorthand — no primary source tracedRegistered, unconfirmed
A mod stretches the calendar to 90 daysNexus Mods — Better Story TimerMod, not the game's rule

Notice the terms: notches, segments, units — sources don't even share a vocabulary yet, and the numbers don't convert into each other. Our policy is to adopt none of them. When a first-party check happens, the game's own hourglass UI becomes the measuring stick, and every time_cost field in the database gets its real value — until then, ? is the honest entry.

Mods Change the Numbers — This Site Tracks Vanilla

Nexus Mods hosts calendar tweaks — the best-known one stretches 30 days to 90 — and their existence tells you something useful: if the game shipped with a built-in extension, nobody would need one. Vanilla has no documented way to extend the calendar; every "extra time" claim traces back to a mod or to nothing. This site documents vanilla public sources only, so mod numbers stay out of the database — including the ones that circulate as if they were the game's rules.

What Happens on Day 30

The calendar does not end the story — every reliable source agrees on the shape of it:

  • Day 30 is Brencis's coronation, the deadline the prologue sets.
  • When it passes, the people you were trying to save are executed — the consequences land.
  • The game continues: the goal shifts from saving them to avenging them, and the world moves on without the deadline's pressure.
  • The "saved them" achievement locks itself out on that path — the one mechanical echo.

That design is why the community treats segments as currency: the calendar doesn't kill your run, it just prices the version of the story you get. Keep the specific beats spoiler-free here — the pages update as documentation matures.

Sources

Sources

Frequently asked questions