Nightwater Progression Unlocks

02

Decisions for Nightwater Progression Unlocks

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

1. Capture the action and interface state immediately before an unlock.
2. Separate milestone, biome, technology and minigame sources.
3. Retest unlock conditions after release instead of preserving a demo assumption.

03

How to use this field guide

Read every row as a claim with a source and freshness state. An empty registry is preferable to a confident-looking table filled with names, thresholds or recipes that have not been checked.

For nightwater progression unlocks, 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. Identify the entity in the current build.
2. Capture the biome, interface or unlock context.
3. Attach an official source or labeled observation.
4. Leave every unknown field empty rather than assuming it.
5. Publish a detail page only when it changes a player decision.

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.