Story mode / challenge hub

Story challenges

Use one hub for chapter routes, clean-run conditions, and tracking evidence instead of treating every community tip as a guaranteed solution.

Mixed evidence / chapter index

Short answer

Story challenges are best tested one condition at a time. Copy the wording exactly, use a clean chapter run, finish the full result flow, and check the challenge panel after returning to the menu. The current field notes below separate published walkthroughs from chapters that still need a repeatable test.

The official story-mode overview establishes the single-player chapter experience. The detailed steps below combine current site field notes with Steam community guide leads; community evidence is not a universal rule.

Current chapter coverage

Chapter areaCurrent routeEvidence state
PrologueClean-run notes for Smith's Grove, including the no-alert test and result-screen check.Test-ready
Chapter 2Challenge tracker with the conflicting no-alert reports kept separate.Needs verification
Chapter 4Challenge 6 walkthrough with the multi-step stalk, interaction, and tracking sequence.Community walkthrough
Other chaptersRecord objective wording, route, and result before adding a new chapter page.Needs verification

Clean-run protocol

  1. Copy the exact condition.“Alert nobody,” “kill,” “execute,” and “complete the chapter” are different tests.
  2. Choose one objective set.Do not combine a stealth condition with a route that requires noisy or contradictory actions.
  3. Finish the result screen.Let the score and completion flow finish before starting another chapter or closing the game.
  4. Return normally to the menu.Record whether the challenge panel updated, then save the platform and build with the report.

What makes a chapter page useful

01 / ObjectiveExact wordingShow the condition before the steps so the reader can test the right thing.
02 / RouteOrdered actionsSeparate required actions from optional movie-accurate or completionist goals.
03 / FailureWhat breaks itCapture alert state, restart behavior, checkpoint, platform, and result screen.
04 / UpdateVersioned noteKeep community reports dated and avoid turning one player's result into a guarantee.

Story challenges FAQ

What is the safest way to test a story challenge?

Copy the exact objective, start from a clean chapter state, avoid mixing contradictory goals, finish the complete result flow, and check the challenge panel after returning normally to the menu.

Why did my story challenge not count?

It may be a missed wording condition or a tracking issue. Record the chapter, objective, platform, build, result screen, and what appeared in the challenge panel before replaying.

Are all chapter challenge steps verified?

No. This hub links current field notes and keeps untested chapters marked as needs verification instead of filling gaps with guesses.