Night 3 is an official completion milestone, but its public walkthrough evidence is thinner than Night 1 and Night 2. The Completed Night 3 badge and the earlier UPD3 title prove the shift exists. They do not prove a patient total, ending, class requirement, or fixed list of new anomalies. The useful route is therefore to carry forward the task-led patient protocol and treat every changed instruction as meaningful.
Confirm the current update context
The official experience has advanced to UPD4 as of this checkpoint, while the first detailed Night 3 coverage was written during UPD3. Read the current title and opening prompts before relying on that older route. A changed update does not erase the Night 3 badge, but it can alter wording, branches, or balance.
Close Shop and Classes panels before entering. Make sure your platform prompts are visible and that you know how to release a held tool. Night 3 should test patient decisions, not menu focus.
Start every case from the objective
Do not import Night 2’s observed twelve-case target. Process the patient attached to the current task, place them where requested, and establish the form or visible context. Use the available diagnostics in a stable order, then follow the patient-specific treatment while the case remains consistent.
After each interaction, read the task again. New wording can signal that the branch changed, that another tool is required, or that a decision is waiting. Confirm the case ended before calling anyone else.
Cross-check without naming unsupported entities
Use descriptive evidence: impossible measurement, identity mismatch, visual change, unusual behavior, or night-vision observation. A named anomaly page is useful only when the name and mechanic are supported. For this checkpoint, the Anomalies hub keeps shapeshifter and faceless claims inside a currently documented index rather than inventing a Night 3 roster.
If a device appears normal but the patient contradicts the form or behaves impossibly, recheck another category. If a dramatic visual appears with no supporting evidence, account for hallucination and sanity pressure. The goal is a defensible action, not a perfect taxonomy.
Control the pace of the shift
Night 3’s main public uncertainty is exactly why pace matters. Finish the active case, complete cleanup or recovery prompts, and reorient before calling the next patient. Repeated tool sweeps and abandoned branches increase confusion.
Solo players should choose a compact movement route and a class that addresses a known bottleneck. Groups should assign one player to task reading, one to the requested station, and one to make the final interaction. Clear roles make changed prompts easier to notice.
Fix a stalled Night 3 task
Return to the active patient, bed, requested diagnostic or treatment, form/computer decision, and cleanup. Do not search for a hidden Night 3-only object unless the objective points to one. If the task fails in a fresh server at the same step, capture the exact wording and update title for a responsible bug report.
At the end, use the completion prompt or badge feedback. Do not stop at a copied patient count. The official badge is the stable milestone; the live task is the route to it.
What not to carry from Night 2
Do not assume twelve patients, a fixed faceless spawn, a particular ending scene, or a permanent device exception. Keep the general skills—case boundaries, evidence comparison, sanity pacing, and task reading—while allowing the actual content to change.
Likewise, do not buy a class solely because a code page lists a high price or calls it best. Current third-party class detail can guide a role choice, but it does not prove a Night 3 requirement.
Night 3 FAQ
Is Night 3 available?
Yes. The official universe includes a Completed Night 3 badge.
How many patients are in Night 3?
No safe exact total is published for this checkpoint. Follow the live objective and completion feedback.
Did Night 3 add a specific anomaly?
The public source set does not support a complete creator-owned Night 3 roster. Use observed evidence rather than assigning every event a name.
Does Night 3 have a unique ending?
The completion badge does not establish ending count or branch conditions.
What should I prepare for Night 4?
Keep the same protocol, review the UPD4 tracker, and read Night 4 without assuming the UPD3 route remained unchanged.