Anomalies

Keep the Door Locked Toilet Anomaly Guide

Do not let a familiar fixture become the room change you overlooked.

Last updated:

Toilet Anomaly Guide

Check familiar places deliberately

The toilet anomaly is a confirmed anomaly in Keep the Door Locked. Its lesson is broader than one fixture: an ordinary part of the hotel room can be important when the game asks you to watch cameras and follow rules. Players often spend all of their attention on the door because it feels urgent. A dependable room sweep gives the toilet a specific place in the routine so it is not dismissed as background.

Use a fixed scan order whenever you have a safe camera check: window, toilet, visible room space, doorway, then any visitor or rule prompt. Consistency makes changes easier to notice. If the toilet looks different, do not instantly invent a cause or solution. Check again when possible, compare it with a remembered baseline, and write an observation in the anomaly checklist. Notes should describe what you saw rather than declare an unverified trigger.

Avoid split-attention mistakes

The toilet anomaly can arrive when another problem is demanding attention. A staged window anomaly may tempt you to watch only the camera view outside. A possible room hider may make the room feel occupied. A door breaker can make the entrance feel unsafe, while the shadow figure tests visual recognition. These are reasons to slow your decisions, not reasons to ignore one signal for another.

The all anomalies guide is the full confirmed list. Read it once between runs, then use the individual pages as short reminders. If you want to prioritize immediate danger, consult the threat ranking; it compares identification difficulty and decision pressure rather than pretending every anomaly has one fixed response.

Keep visitors and progression in context

A toilet check does not answer whether the person outside the door should be trusted. The strange grandma, kindness reward visitor, pizza rat with a baseball bat, Dream Room, Juan, and dog easter eggs are covered in the visitors guide. Door choices still need to account for the current room evidence. Use the visitor trust ranking as a reference, not an automatic rule.

Sanity and the Blood Money goal belong in your wider run review. After an anomaly, note whether the event changed your route, delayed a door decision, or affected progress. Mark actual achievements in the badge tracker and confirmed ending progress in the ending tracker. The three known ending goals are 10 days, golden skeleton, and the grandma-key ending; this page does not claim the toilet anomaly directly unlocks any of them.

New players should first read hotel survival basics. The central habit is modest but effective: revisit the same room locations in the same order, verify suspicious changes, and do not confuse a rushed reaction with useful information.

Logging stages safely

Write down what you saw before and after each escalation. Use the Anomaly Checklist so Flush of Fear attempts stay controlled. If sanity dips, stop pushing stages and recover using the Sanity Guide before the next knock arrives.

FAQ

Frequently Asked Questions

Quick answers about the hotel room, visitors, and endings.

Is the toilet anomaly confirmed?

Yes. It is one of the confirmed hotel-room anomalies, making it a required stop in a consistent camera and room sweep before the next difficult door decision.

What should I write in my checklist?

Describe the visible change, when you saw it, whether a later camera check confirmed it, and what competing door or room event was happening at the time.

Does this anomaly decide whether a visitor is safe?

No. Visitors and room anomalies are separate evidence sources that must be considered together.

How can I make a toilet-anomaly check more consistent?

Put it in the same place in every room sweep: inspect the window, inspect the toilet, scan the visible room, evaluate the doorway, then compare the current camera view with the last one. Record any difference with neutral language and return for a second check when the run safely allows it.