All Nightwater Endings

02

Decisions for All Nightwater Endings

The useful question is not how to fill every field today, but which claim changes the next player action. These page-specific decisions keep all nightwater endings practical while the full release remains gated.

1. Maintain four private slots because the official total is confirmed.
2. Keep names and requirements hidden until they can be repeated in the release build.
3. Separate an ending observation from a theory about its trigger.

03

How to use this field guide

Keep mechanical progression separate from interpretation. Record official premise, direct observations and theories in different layers, and leave spoiler gates closed until the player chooses to open them.

For all nightwater endings, follow the in-game state first and use this page to organize decisions, not to override evidence shown by your build.

04

A practical field workflow

This sequence keeps observations reproducible and makes release-day corrections straightforward.

1. Keep the page spoiler-safe by default.
2. Record the official premise before interpretation.
3. Describe a clue without converting it into a requirement.
4. Track endings and secrets privately until evidence is repeatable.
5. Reverify all completion paths after launch.

05

What remains deliberately open

Exact recipes, thresholds, rates, capacities, unnamed entities and hidden completion conditions stay unpublished until an official source or repeatable current-build check supports them. In every table, an unknown is an evidence state—not a zero, a negative answer or missing work.