Norbert choice · Official updates checked Aug 2026
Shift At Midnight Norbert Guide: Trade, Attack, or Let Him Go?
- Reading time
- 5 minutes
- Difficulty
- Story-sensitive
- Checked
- 2026-08-29
On this page
Guide details
Before you begin
A focused choice note for Norbert's ID and database mismatch, why ordinary Entity handling does not fit, and the consequences currently documented.
This note covers the current guide's Norbert identification clues, the attack consequence, and the trade-and-release recommendation. It does not claim Norbert can be permanently killed or replace a complete ending walkthrough.
- Status
- Checked against the current Norbert guide
- Edition
- Official updates checked Aug 2026
- Platform
- Story Mode · all listed platforms
- Checked
- 2026-08-29
- Check note
- One focused editorial source supports the ID and NET Database mismatch, later disruption after an attack, and the trade-and-release recommendation.
Before you set out
Prerequisites#
- Expect a light ending-path spoiler: this page explains the safer documented Norbert choice.
- Check both the presented ID and the NET Database result before deciding how unusual the visit is.
- Keep the Norbert decision separate from ordinary customer or Entity checks.
Visual reference
Norbert does not follow the normal Entity branch#
Pocket list 02
What makes Norbert different#
- He presents an ID, so the visit is not simply a customer with no identity material.
- The focused guide says he is absent from the NET Database.
- Attacking does not produce the ordinary Entity reveal described for standard doppelganger handling.
- The supported consequence appears later as disruption, so the attack is not a clean elimination route.
Decision point
Trade with Norbert or attack him?#
Choose based on the outcome you are trying to preserve, not only the database mismatch on the screen.
- Complete the transaction and let him go
- Choose when: You want the currently documented True Ending route.
- Outcome: The focused guide recommends the transaction-and-release choice for that ending path.
- Attack Norbert
- Choose when: You knowingly accept the documented later disruption.
- Outcome: Do not expect a normal Entity reveal or claim a permanent kill; the source describes a later consequence instead.
Route flow
A conservative Norbert decision route#
Read the ID
Confirm that Norbert presents identity material before comparing him with the normal investigation loop.
Check the NET Database
Record the missing match, but do not treat that single clue as proof that the ordinary Entity branch applies.
Keep him out of the normal Entity rule
The focused guide describes different behavior and consequences, so avoid copying the standard response.
Finish the transaction and release him
Use the currently documented recommendation when your goal is the True Ending route.
Field questions
Norbert questions#
- Is Norbert a normal Entity?
- The focused guide says no: his ID and database mismatch lead to a different branch, and an attack does not create the ordinary Entity outcome.
- Should I attack Norbert?
- Not if you want the documented True Ending route. The current recommendation is to complete his transaction and let him go.
- Can Norbert be permanently killed?
- That is not established by the source used here. The documented attack consequence is later disruption, not a confirmed permanent kill.