Directive 8020 Story Tree and Turning Points Guide
The Story Tree is Directive 8020's route map, and Turning Points are the replay checkpoints you use to change deaths, endings, hidden paths, and 100% completion. The key rule is simple: when you change an old Turning Point, replay forward from that point so the new timeline actually replaces the old one.
BLUF
Short answer: use Turning Points to rewind to the earliest choice that caused the branch, then replay forward. Do not change Episode 2 and jump straight back to an old Episode 5 node expecting the new result to carry over; that later node still belongs to the original timeline.
Key Facts
What to Use the Story Tree For
Most players do not need a theoretical explanation of branching narrative. They need to know which tool solves which problem. Use the Story Tree as your route ledger: it tells you what you have seen, what remains locked, and where a different survivor state or trust choice may open a new path.
| Goal | Best Turning Point use | Why it works |
|---|---|---|
| Save everyone | Rewind immediately after a death, serious injury, or failed identity/trust check. | Survivor state must be repaired before later finale conditions are calculated. |
| All endings | Finish one clean route, then branch from late-game Turning Points and replay forward. | Changing an old node without replaying forward can leave you on the original timeline. |
| 100% Story Tree | Treat every locked node as a route experiment and change one variable at a time. | Reddit players report missing Episode 8 nodes even after 99% chart completion. |
| All deaths | Use a copy branch for failed stealth, failed QTEs, and high-risk trust choices. | Death cleanup can break a good route if you overwrite your clean survival path. |
How Turning Points Change the Game
Older Dark Pictures runs often required full replays to test different choices. Directive 8020 is built around a more visible branching structure. Turning Points let you return to key moments, choose differently, and watch how the Story Tree changes.
That does not make choices meaningless. It makes route testing more practical. If a character dies, the question becomes: which Turning Point caused the death, and how far back do you need to go to change the conditions?
How Rewind Actually Works
The most common player mistake is treating Turning Points like a single-choice editor. They are closer to timeline forks. If you change a past decision, the game needs you to play through the downstream scenes where that decision takes effect. Jumping back to a later node from your old route can put you back on the old route.
| Rule | Do this | Reason |
|---|---|---|
| Changed choices start a new timeline | If you alter Episode 2, replay forward from Episode 2 for that result to exist in Episode 5. | Reddit threads show players losing changed outcomes after jumping back to old later nodes. |
| Do not change multiple variables at once | Keep exploration, QTEs, and relationship choices the same while testing one branch. | This lets you identify the real cause of a death, ending, or locked path. |
| Use late Turning Points first for endings | After one complete run, test finale and Episode 7-8 branches before replaying early chapters. | Most ending cleanup depends on final survivor state and late trust/identity outcomes. |
| Use earlier Turning Points for missing chart nodes | If a future node will not unlock, replay from the earliest character split, death, or stealth outcome that can feed it. | Some 100% Story Tree paths need a different upstream survivor state. |
When to Rewind
Rewinding too often can ruin tension, but refusing to rewind can waste hours if you are targeting a specific route. Choose your style before starting.
- Blind run: do not rewind until you reach an ending.
- Save everyone: rewind after any death, serious injury, or irreversible separation.
- All endings: finish one route, then branch from late-game Turning Points first.
- Trophy cleanup: change one branch at a time and record what unlocked.
Branch Signals to Track
Not every line of dialogue is equally important. Prioritize choices with visible state changes or mimic-related risk.
- A character dies, is injured, or becomes separated.
- A relationship visibly improves or worsens.
- A trust decision happens after someone was isolated.
- A clue changes what dialogue options are available.
- The Story Tree marks a node as unexplored or locked.
- A finale or ending changes because of an earlier crew state.
Decision Tree, Flowchart, and Destinies
Players searching for a Directive 8020 decision tree or flowchart usually want a clean way to test routes, not another long paragraph. Keep one route map with four fields: the Turning Point, the choice, the immediate result, and the later Destiny or ending impact.
| Route tool | How to use it | Search intent served |
|---|---|---|
| Decision Tree | Use the in-game Story Tree as the canonical map of branches you have seen and branches still locked. | Best for "directive 8020 decision tree" and "all paths" searches. |
| Flowchart | Record one row per Turning Point: episode, scene, changed choice, immediate result, later result, and replay note. | Best for players who want a visual route map without spoilers. |
| Destinies | Track long-term character direction separately from casual dialogue tone and momentary relationship shifts. | Best for "all destinies" and choice-consequence searches. |
| All Turning Points | Capture exact node names episode by episode before claiming a complete list. | Best for 100% Story Tree and completionist searches. |
Decision Tree Source Check
| Player question | Source | Status | Player note |
|---|---|---|---|
| Turning Points and Story Tree are official replay systems. | Official / Steam feature copy | Official | Use for rewind, hidden paths, and route testing explanation. |
| Changed Turning Points must be replayed forward to preserve the new timeline. | Reddit player troubleshooting | May change | Use as a practical warning because this is the main confusion in player threads. |
| Some 100% Story Tree gaps depend on earlier episode survivor and stealth states. | Reddit completionist thread | May change | Use for 100% chart guidance, but keep exact node claims conservative until captured in-game. |
| Turning Points are useful for save-everyone and all-ending replay behavior. | TechRadar developer interview | Official | Supports the save-everyone and all-endings intent behind this page. |
| Exact all-turning-points and all-destinies lists still need route capture. | In-game Story Tree verification | Not announced | Treat exact node names as provisional until screenshot or video confirmation is available. |
| Choice examples from transcript are useful but not final canon by themselves. | Private transcript notes | May change | Use transcript notes as early route clues, then confirm them in the Story Tree. |
Best Route Testing Method for 100% Story Tree
- Complete a chapter and open the Story Tree.
- Write down all visible Turning Points and locked branches.
- Pick one branch and replay from the earliest relevant node.
- Keep QTE results and exploration consistent while changing only one choice.
- Compare survival, relationship, evidence, and ending-state changes.
If an Episode 8 path stays locked, do not only replay the last finale choice. Work backward to the latest survivor split, stealth failure, or character-death condition that can change who reaches the finale. That is the pattern completionist threads are already troubleshooting.
Frequently Asked Questions
Q: What are Turning Points in Directive 8020?
Turning Points are replay checkpoints in Directive 8020 that let you return to important branches, change choices, save crew members, and fill missing Story Tree paths.
Q: Why did my changed choice not carry forward after I jumped back to a later scene?
A changed Turning Point starts a new timeline from that checkpoint. To make the new choice count later, replay forward from the changed point instead of jumping back to an old later node.
Q: Is the Story Tree useful for all endings and 100% completion?
Yes. The Story Tree is the best tool for all endings, deaths, collectibles cleanup, and 100% chart work because it shows which branches are still locked or unexplored.
Q: Should I rewind immediately after every mistake?
Not always. If you want a natural first playthrough, finish your first ending before rewinding. If you are saving everyone or hunting trophies, rewind after major deaths, locked branches, or missed evidence.
Q: Can Turning Points replace a full replay?
Turning Points reduce full replays, but they do not let you surgically edit one old choice and keep every later scene unchanged. Some trophies and ending variants still require replaying a long chain forward.