Use this walkthrough as a decision route rather than a fixed room script. Before entering a chapter, identify the weapon action you trust, the survival mistake you are trying to prevent, and the inventory space that must remain usable. During the chapter, stop at the first safe moment to record a change in enemy pressure, reward shape, or progression message. This makes the route useful even when a later update changes exact encounters.
The first pass
On a first visit, prioritize information over speed. Observe how a room telegraphs danger, where a safe retreat exists, and whether enemies punish standing in one place. Use the simplest reliable attack while learning. A spectacular interaction that requires you to watch several timers can hide the chapter’s actual lesson and make a death difficult to diagnose.
At the first reward, ask which choice improves the next three minutes rather than the entire imagined run. If the inventory is already crowded, a smaller compatible improvement may be better than a stronger piece that breaks the layout. Note the choice and the reason. On a second run, compare the same decision against the same checkpoint.
Mid-chapter corrections
If rooms are taking too long, check range and target selection before adding raw damage. If the player is losing health while attacks connect, change the approach angle or recovery rhythm. If rewards cannot be placed, read the Inventory Guide and identify which spaces are essential. When a correction changes the whole build, mark the run as a new test instead of comparing it to the original plan without context.
Chapter transition
Before a transition, record the exact message or label visible in the game. Do not assume that a community route’s “chapter two” has the same name or gate as a launch build. If the next area is unavailable, capture the conditions you can reproduce: completed chapter, save state, solo or co-op, and version. Send unresolved questions to the Updates page only after checking official notes.
Spoiler and co-op etiquette
Keep optional discoveries in the Secrets Guide, behind a spoiler label. In co-op, tell teammates the plan before a reward choice and leave a fallback if someone does not know the route. A walkthrough that only works when four players follow a perfect order should be labeled as a coordinated route, not a universal chapter requirement.
Add the date and the displayed chapter label to the note. A future player may search the same phrase after a patch, and the editor can then distinguish a changed route from a changed recommendation.
A second-pass route
On the second pass, keep the same entry plan and change one decision at a time. Compare the first dangerous room, the first reward, and the transition message. If the route improves, write down which change mattered. If it does not, preserve the result; a failed hypothesis can stop another player from repeating an unhelpful detour.
If a chapter appears to require a named item or hidden action, do not infer it from a single locked screen. Check the visible message, search current official notes, and test a clean save or an equivalent route when safe. The Official Updates Guide explains how to mark the evidence while the condition remains unresolved.
At the end of the route, publish the failure point as carefully as the success point. Note whether the run ended in a room, reward choice, transition, or boss. That label sends the reader to the right supporting guide and prevents a generic “chapter difficulty” explanation from hiding the real decision.