Directive 8020 All Endings: Best, Secret and Death Spiral

All Known Ending Names and What to Test

Players searching for Directive 8020 endings usually need ending names, route direction, and a clear warning about unconfirmed triggers. Use this table as the route map: it separates known named outcomes from exact branch triggers that still need controlled Story Tree capture.

Ending Matrix: Which Variable Should You Test?

Use the ending matrix before replaying. It keeps best, bad, worst, secret, and explanation routes separate so you do not overwrite the clean save you need for later cleanup.

How to Read the Tracker

The tracker is intentionally conservative. It does not claim that a specific character dies from a single choice unless the route is mapped in the Story Tree. Use it to decide whether a branch is clean enough to preserve, risky enough to test separately, or too unstable for your best-ending base save.

Ending Count and Completion Facts

The key completion numbers help players understand the scale of the ending hunt. They also keep quick references precise: five reported main endings, forty-four death scenes, sixty-five collectibles, and eight episodes to track.

Transcript-Based Finale Conditions

The full-game transcript makes the finale easier to map because it separates the final outcome into message choice, survivor state, contamination risk, Andromeda safety, Oracle information, and the cycle reveal. These notes are spoiler-heavy and should be used after one completed route.

Spoiler Topics Players Search After the Ending

After finishing a route, most players need more than a list of outcomes. Use this section for spoiler-heavy questions about the finale, Cycle 13, the Booster Ring, and how named ending families connect to the choices you made earlier.

What Determines an Ending?

In Directive 8020, an ending should not be treated as one final choice. Supermassive's anthology structure usually builds endings from accumulated conditions: who is alive, what they know, how they relate to each other, and which late-game branches remain available. Directive 8020 adds one more layer: whether you correctly handle a creature that can imitate the crew.

Best Ending Route: Safe Principles

A complete best-ending route requires full chapter testing, but the safest principles are clear from the game's systems. You want the most living characters, the strongest evidence base, and the fewest decisions made from panic or blind trust.

• Keep characters together when possible: isolation creates mimic risk and missed witnesses.
• Verify before trusting: do not follow an isolated character without a reason.
• Preserve relationships: hostile crews are less likely to rescue each other.
• Explore optional clues: evidence can unlock safer dialogue and accusation options later.
• Pass QTEs and stealth checks: mechanical failures can close ending routes immediately.

Ending Route Test Plan

Use this sequence to turn one completed playthrough into a full endings guide. It keeps the route clean and prevents false conclusions from multiple changed variables.

Bad Ending and Worst Ending Triggers

The worst routes in this style of game usually come from cascading failures. One death removes a witness, the missing witness makes a later trust decision harder, and a bad trust decision creates another death. When testing endings, treat these as likely red flags:

• Trusting a character who recently returned from isolation without enough evidence.
• Choosing speed over evidence before a major accusation or rescue.
• Letting two characters with poor relationships decide each other's fate.
• Ignoring a route that lets the crew communicate or regroup.
• Failing late-game action sequences after a long survival chain.

Failure Recovery: What to Do When a Route Breaks

A broken route is still useful if you label it correctly. Use failed branches for bad-ending cleanup, but protect one clean survivor route for best-ending and secret-ending tests.

How to Use the Story Tree Efficiently

The Story Tree is the main reason Directive 8020's ending hunt should be less painful than older anthology entries. After every chapter, look for branches that are locked, deaths that appear connected to earlier choices, and paths that have not been explored.

1. Finish a chapter, then check which branch the Story Tree marked as a Turning Point.
2. Write down the choice, the character state, and whether a death or relationship shift followed.
3. Only rewind to the earliest relevant Turning Point, not the most recent scene.
4. Change one variable at a time, so you know what actually altered the route.
5. Save full alternate branches for after your first complete ending.

Ending Tracker Template

Use this simple structure while playing. It turns your first run into a route map you can reuse for best ending, bad ending, and trophy cleanup.

• Chapter / scene: where the branch happened.
• Turning Point: the exact decision or action sequence.
• Choice made: what you selected.
• Immediate result: death, relationship change, clue, or route change.
• Long-term result: what changed by the end of the chapter.