Story branches / guide 02

Endings, choices, and consequences

The story is built around limited time and meaningful decisions. This page records what the official previews establish and leaves exact ending names and requirements open until they are reproduced in the retail build.

Research state / 30 Aug 2026Multiple endings confirmed

Short answer

Multiple endings are confirmed, but the exact number and unlock conditions are not confirmed in the pre-launch material checked for this MVP. Do not trust a complete ending table until it includes a reproducible save, phase, prerequisite, choice, and result.

What is already confirmed.

Rebel Wolves and platform-holder previews repeatedly frame action, inaction, time, hunger, and day/night approach as meaningful parts of the story. That is enough to build the test model; it is not enough to publish hidden thresholds or a named ending checklist.

Confirmed / systemAction and inaction matterIgnoring an opportunity can become part of the world state.
Confirmed / routeTime is a decisionQuests and major activities move Coen toward the deadline.
Open / retail testExact ending tableNames, count, prerequisites, and combinations remain unknown.

The ending evidence matrix.

Use one row for each reproducible outcome. A route can be useful before its ending label is known if the preceding state and result are clear.

Evidence fieldMinimum recordPublish ruleState
Route identityFamily, revenge, alliance, or other player priorityUse the player-facing objective, not an invented labelFramework
Trigger stateQuest, day, phase, NPC, and prerequisiteMust load from a named save or repeatable starting stateNeeds verification
Choice chainCritical action and any earlier decisions that matterOne screenshot or one playthrough is a lead, not proofNeeds verification
Ending resultFinal scene, family state, allies, and unlocked trophyRecord the version and repeat the result before publishingPost-launch

How to test a claimed ending.

  1. Start from the same save.Keep the day, phase, quest state, relationship state, and version fixed before changing one decision.
  2. Change one meaningful variable.Compare help versus ignore, day versus night, restraint versus feeding, or one alliance against another.
  3. Follow the delayed result.A dialogue reaction is not necessarily an ending branch. Continue until the relevant quest, character, or finale state is visible.
  4. Repeat before naming the rule.Re-load the baseline and repeat the choice. If another condition changes the result, publish the branch rather than a false single requirement.

Save-point policy.

Keep a manual save before a quest with a visible time cost, a major alliance decision, a point of no return, or a finale approach. The exact save behavior and number of slots must be checked in the retail build; this page does not promise a universal perfect-save route.

BeforeBaseline saveRecord day, phase, quest, and current objective.
ChoiceBranch saveWrite the exact action before committing.
AfterOutcome savePreserve the visible result and later follow-up.
ProofVersion notePatch, platform, date, and evidence source.

Endings FAQ

How many endings does The Blood of Dawnwalker have?

Multiple endings are confirmed. The exact number and requirements are not confirmed in the pre-launch sources used for this MVP, so the answer stays open until direct retail testing.

Do choices really change the ending?

Official material says choices, time, and inaction shape the story. The precise effect of an individual choice must still be tied to a verified quest and save state.

Can I save everyone in one playthrough?

The publisher says players will not have time for everyone, while developers describe a majority of the game as possible within the deadline. A complete all-survivors route is not verified here.