01

Read progression as a network

A blocked route is usually a clue to a tool, Shell ability, weapon interaction, or boss reward rather than a signal to grind blindly.

Use the walkthrough as a decision map: what is open now, what is worth postponing, and what reward changes the next route.

02

Keep optional discoveries visible

Optional dungeons, hidden Shells, and side paths belong beside the main route so a player can choose a short detour without restarting the whole area.

If a path is missable or version-sensitive, the page labels the evidence state instead of presenting a guessed order as fact.

03

Boss order is a preparation tool

A boss list is useful only when it explains why the order matters: access, reward, weapon upgrade, map shortcut, or Shell route. Link the arena preparation and the reward’s next use.

04

Progression skeleton: what to do next

Use Marrow Keep as the point where a run changes shape. If the next trip is about a Shell or sidearm, spend the reset on route preparation; if it is about a boss, bring the weapon and healing plan first.

In Fainweald, bundle nearby tasks instead of making one trip for every pin: check Tiel or Proxima, take the nearby sidearm lead, and open the Beacon that shortens the return. Only push into a deeper dungeon when the approach and exit are both readable.

Mammon is the cleanup branch, not a reason to abandon the early checklist. Save long dungeon and boss-adjacent routes for a run with repairs, inventory space, and one fallback weapon.