The standard Keep the Door Locked run has one official finish line: the ENDING 1 badge says you got through ten days. Current English and mobile walkthrough videos also identify Day 1–10 as the complete normal route. What the public official sources do not establish is a fixed list of daily visitors, rules, anomalies, or button presses. The safest walkthrough is therefore a repeatable process for each event, with the live screen deciding the details.
Complete the Beginner Guide first if you have not made a full camera-and-rule decision. This page assumes you can locate the door, current rules, and camera interface in your build.
Run objective: preserve a consistent inspection routine across ten days. For every knock, leave the door locked, identify the claim, read the current rule, check the cameras, scan the room, decide once, and reset your view for the next event.
Start the run with a clean baseline
Join the official Place ID 124338404742585 under Hotel Room Services. Let the room and interface load before interacting. Locate the rule display, cameras, door control, and any visible Sanity or day-state indicator. Confirm the door begins in the expected locked state.
Choose a camera starting view and a room scan order. The goal is to remove unnecessary decisions later. When pressure rises, you should not be deciding which feed to check first or where to look for the room state; those steps should already be routine.
Read every current instruction. Do not rely on a previous attempt’s wording. Public walkthroughs demonstrate recorded runs, while the official description does not guarantee that rules or encounters remain in one order.
Repeat this cycle for every visitor event
First, read or hear the entire request. Identify the specific claim and what the visitor wants you to do. Do not unlock while the request is still being delivered.
Second, match the current rule to an observable condition. If the rule does not apply, do not stretch it. Third, sweep the relevant camera views and classify what you see as support, contradiction, or unknown. The Cameras and Rules guide explains that evidence model in detail.
Fourth, scan the room and door. Official badges confirm several anomalies that can coexist with the visitor loop. Keep visitor evidence and room evidence separate so one does not become a false explanation for the other.
Fifth, make one deliberate door decision. Read any response before pressing again. After the event, reset the camera, re-check the door, note rule or room-state changes, and prepare for the next knock.
Treat Days 1–10 as phases, not a memorized script
For the early days, prioritize control familiarity and correct evidence classification. Move slowly enough to understand how the current build presents claims, rules, and camera information. A successful early choice is valuable because you know why it worked, not because you can copy it later without checking.
In the middle of the run, protect the routine. Longer sessions encourage shortcuts: skipping a feed, assuming a repeated appearance means the same answer, or forgetting the room scan. Reset between events even when the previous decision felt easy.
Late in the run, avoid changing a working process merely because the ten-day goal feels close. The official badge establishes the finish condition but does not promise that Day 10 is mechanically identical to an earlier day. Re-read the live rule and use current evidence through the final event.
This phase model is deliberately more durable than a day-by-day visitor script. If the game randomizes, updates, or reorders events, the inspection method still answers the player’s real question: what should I do before deciding?
Visual full walkthrough
TheKacperosEN’s current community walkthrough is useful for seeing the room, interface, event pacing, and one complete route. Compare every recorded choice with the rule and evidence in your current session.
Use the video for visual orientation rather than as an official script. Pause before each commitment and identify the rule, camera observation, and room state that support it. If you cannot explain the recorded choice from visible evidence, do not turn it into permanent advice.
A separate mobile Day 1–10 recording by Retro NOBY confirms that a full route is demonstrated on touch controls. Exact button locations and responsiveness remain build-specific, so mobile players should prioritize clear panel changes over matching video speed.
Handle anomalies without losing the visitor decision
The official badge list names a window anomaly, room hider, door breaker, shadow figure, and toilet anomaly. When the room changes, pause the visitor conclusion and identify which problem you are responding to. Do not assume that an anomaly makes the person outside safe or unsafe.
The badge descriptions reveal narrow outcomes but not complete counters. Spotting, surviving, banishing, checking a stage, and advancing a stage are not interchangeable actions. Open the Anomalies index for the official wording and keep unsupported response steps out of the run plan.
After an anomaly, rebuild your baseline: confirm the door state, camera view, active rule, and visible status. This is especially important if the event forced the camera or player view away from the visitor evidence.
Sanity and long-run state
The official Losing It badge confirms that Sanity can reach zero, but no public official explanation defines its causes, recovery, threshold warnings, or persistence. Watch any visible indicator after events and record changes without assigning a cause from one occurrence.
For an Ending 1 attempt, avoid deliberately pushing an unknown state merely to test the badge. Complete the ten-day objective first, then use a separate run to isolate Sanity behavior. Mixing a completion attempt with several unverified secret tests makes failure harder to diagnose.
Recover from a failed run
Classify the final mistake before restarting. A claim error means the visitor’s words were misread. An evidence error means a camera clue was missed or overinterpreted. A rule error means the condition or response was applied incorrectly. A room-state error means an anomaly or status change was ignored.
Change one part of the process on the next attempt. If the camera sweep was inconsistent, fix the sweep; do not also invent a new visitor list. If the rule was misread, slow down at the rule step. Focused corrections create a more reliable route than copying an unexplained answer.
The official sources do not explain checkpoints, save behavior, or whether every failure resets the same amount of progress. Observe the current restart screen and record what it actually offers.
Ending 1 completion check
The authoritative completion signal is the official Ending 1 badge or the game’s corresponding end state, not merely reaching a screen that resembles the end of a video. Roblox describes the badge as getting through ten days. Once awarded, preserve the result before starting a different ending route.
For the alternative objectives, use Ending 2 for the golden skeleton and Ending 3 for the strange grandma’s key. Do not combine those routes with a normal run unless current evidence establishes that their prerequisites are compatible.
Walkthrough FAQ
Is every day fixed?
No official source reviewed here promises a fixed encounter or rule order. Follow the current rule and evidence rather than a memorized daily answer.
How many days are required for Ending 1?
Ten. That objective is stated directly by the official Ending 1 badge.
Does the video prove every correct choice?
It demonstrates one current community run. Use it for visual learning and corroboration, while treating the live game as the authority for your session.
Is the route the same on mobile?
A current mobile Day 1–10 walkthrough exists, but official public material does not define permanent platform control layouts or timing differences.