Directive8020Live Database
directive 8020 code

Directive 8020 Codes Guide: All Puzzle Codes and Passwords

A spoiler-aware list of Directive 8020 puzzle codes, passwords, safe numbers, terminal entries, and objective numbers. These are not redeem codes; they are fixed in-game solutions used to progress episodes.

Code Sheet Status
Known entries6
Last checked2026-05-19
SchemaFAQPage + ItemList
ConfidenceLaunch-guide informed / Needs route retest
01

Fast Answers

The answer appears before the route explanation, so players can solve the prompt without reading ahead.

Are these redeem codes?

No. Directive 8020 code searches are about puzzle codes and terminal passwords, not redeem codes, gift codes, or free rewards.

Read the code warning

What is Carter's PC code?

Carter's PC accepts 0828, and some routes or regional date formats also accept 2808.

Open Carter code

What is the Anomaly Log Number?

The Anomaly Log Number is currently tracked as 3196, with launch-guide evidence and a retest flag.

Open anomaly code

Where should I go if I am stuck around a code?

Use the walkthrough for route context, then return here for the exact number so you avoid unnecessary spoilers.

Use the walkthrough
02

All Puzzle Codes and Passwords

Episode-ordered answers for keypads, terminals, objective numbers, and late-game serial prompts.

Directive 8020 All Puzzle Codes and Passwords

Use this table as the first useful result for directive 8020 code, directive 8020 codes, Carter PC code, Anomaly Log Number, and Probe Serial Number searches.

Episode 2

Locker code

13576

Reported by launch code guides; direct route retest still pending.

LowLaunch-guide informed / Needs retest
Episode 2

Carter PC code

0828 or 2808

Luna birthday clue: August 28. Some sources list month-first 0828; date-first 2808 is also reported as accepted.

Medium: unlocks a story beat involving Carter and SimmsCross-source launch-guide informed
Episode 3

Kitchen food storage code

0402

Reported as the food storage keypad solution in launch puzzle-code guides.

LowLaunch-guide informed / Needs retest
Episode 5

Diazepam / narcotic synthesis code

168

Chemical synthesis number used for the medical objective.

Medium: tied to the medical routeRoute-informed / Needs retest
Episode 5

Anomaly Log Number

3196

Use this number when the Anomaly Log Number prompt appears.

MediumLaunch-guide informed / Needs retest
Episode 7

Probe Serial Number

2540

Read the damaged serial fragments around the probe and combine the visible digits.

High: appears during a late objectiveCross-source launch-guide informed
03

Not Redeem Codes

This page intentionally blocks fake gift-code intent and keeps the answer tied to real in-game prompts.

The rising query `directive 8020 code` looks like a codes-page keyword, but the player task is different from Roblox or gacha redeem-code intent. Directive 8020 is a cinematic survival horror game, so the useful answer is a compact puzzle-solution sheet.

Use this page when a keypad, terminal, log prompt, chemical cabinet, or probe objective blocks progression. If you are looking for gift codes, free items, or a redeem menu, there is no supported redeem-code loop to track here.

04

Spoiler-Safe Use

Use one row at a time. The code column gives the answer first; the clue explains only as much context as needed.

Read the episode

Stop at your current episode before scanning the full table.

Copy only the number

Use the code cell first, then read the clue if the prompt still does not make sense.

Check evidence

Rows marked retest are launch-guide informed until directly verified in-route.

05

Search Intent Map

The keyword looks transactional, but this game needs a puzzle-solution page, not a redeem-code landing page.

Search query

directive 8020 code

Intent: Find a keypad, terminal, or objective number fast.

Answer: Use the all puzzle codes table above.

Open target section
Search query

directive 8020 codes

Intent: Look for all fixed in-game puzzle solutions.

Answer: Use the full episode-ordered code list.

Open target section
Search query

directive 8020 anomaly log number

Intent: Solve a specific Episode 5 log prompt.

Answer: Try 3196 and check the evidence status.

Open target section
Search query

directive 8020 Carter PC code

Intent: Unlock Carter's terminal in Episode 2.

Answer: Try 0828 first; if your version accepts date-first input, 2808 is also reported.

Open target section
Search query

directive 8020 redeem codes

Intent: Look for free reward codes.

Answer: There is no known redeem-code system for Directive 8020.

Open target section
06

Update Policy

Codes stay on the page only when they solve real prompts. Rumors, cheats, and fake reward codes do not belong here.

This page is updated as a live tracker. A code stays here only if it solves a real in-game prompt or objective number. We do not add rumored cheat codes, console commands, trainer instructions, or fake reward codes.

If a future patch changes a number, the old value should move into the evidence notes with the affected version. That keeps the page useful for launch-build players while giving searchers the current answer first.

07

FAQ

Short answers that feed the page FAQPage schema and cover the fastest code-related queries.

Does Directive 8020 have redeem codes?

No. This page tracks puzzle codes and objective numbers, not redeem codes. Directive 8020 does not have a confirmed gift-code or free-reward redemption loop.

What is the Directive 8020 Carter PC code?

The Carter PC code is tracked as 0828, with 2808 also reported as accepted. The clue points to Luna's birthday on August 28.

What is the Directive 8020 Anomaly Log Number?

The Anomaly Log Number is tracked as 3196. It is listed with a launch-guide evidence label until direct retesting confirms the route.

What is the Directive 8020 Probe Serial Number?

The Probe Serial Number is tracked as 2540. It appears during a late objective, so avoid that row if you are staying spoiler-light.

Can puzzle codes change between playthroughs?

Current launch-guide evidence indicates these codes are fixed, but any version-specific change should be recorded with a patch note and retest status.