The Reacher is the HOUSE 13 window threat. Its official Roblox Badge gives one direct rule: the window can be shut right up until it climbs through. When the event begins, identify the affected window, move there, and use the live close interaction before the crossing completes. Do not wait for a guessed number of seconds or search for a combat item.
Prepare every relevant window
Before pressure builds, walk to each window the game lets you interact with. Learn the shortest route from the visitor decision area and note any doorway, dark stretch, or room that can become unsafe. Use location names a squad can understand—front, rear, hall, or a visible room landmark—instead of “over here.”
Check the live interaction prompt once. Inputs can differ across keyboard, controller, touch, and later versions. The official Badge describes the action, not a fixed key. If the window begins in a particular state, learn what closed looks like so you do not run to the correct place and perform the opposite action.
Keep the route clear. The Hitcher makes time in darkness dangerous, while the Nester can claim a room. A route that worked earlier may stop being safe. Identify an alternate approach if the house layout permits one, and never blindly cross a claimed room to save a window unless the current run clearly shows that is the safer choice.
Reacher response sequence
Solo route
Stay close enough to reach windows without abandoning a stranger mid-check for too long. If the Reacher warning begins during a visitor decision, preserve what you observed, close the window, then resume the decision only if the game still allows it. The official window deadline is clearer than any assumed visitor timer, but the live interface should decide when events overlap.
Afterward, check the window state and your route back to light. Do not stand at the window waiting for another animation if the event has visibly resolved; that leaves the visitor area and other hazards unattended. Repeat the same movement on later nights so the response becomes automatic.
Squad roles and callouts
Assign one house watcher to windows and closets while the visitor caller remains at the door. The watcher calls the window location, another player acknowledges only if they are taking it, and the responder confirms closure. Avoid sending the entire team. More bodies can block the view, create conflicting interactions, and leave the house’s other responsibilities uncovered.
If the assigned watcher is dealing with darkness or a claimed room, pass the role explicitly. “Rear window, Sam taking it” is a complete handoff. Silence is not. On longer Medium and Hard runs, rotate responsibility at a calm moment rather than during an active climb.
Why a close attempt may fail
A late interaction is the most direct possibility: the Badge says the opportunity lasts until the Reacher climbs through. The player may also be at the wrong window, may have followed an outdated key prompt, or may have crossed an unsafe route and lost time. In a group, two players may assume the other is responding.
Do not publish an exact countdown based on one attempt. Record the mode, night, first visible or audio cue, window, action, and result. Repeat the same situation before treating a cue as universal. The public Badge does not state spawn frequency, damage, recovery, multiplayer ownership, or whether timing changes by mode.
Recovery checklist
After a failure, shorten the physical route before changing the whole strategy. Move the watcher closer, improve the window name, and practice the live close prompt. If the route passes through darkness, establish a recognized lit-room path. If the Nester claimed the usual room, reroute immediately rather than testing the same unsafe path again.
Check whether the run continues and what the game displays, but do not assume the Reacher always causes the same failure result across all modes. If a revive appears, record whether it returns the window and room to a safe state. Infinite Revives exists as a gamepass, but its listing does not describe threat-specific resets.
What is official and what still needs testing
The entity name, Badge ID 1594464231618439, window context, and ability to close the window until entry are official. Warning sounds, exact window set, timer, animation stages, damage, frequency, mode scaling, team synchronization, and recovery state still need current gameplay evidence.
Use the Threats Dex to compare this window response with the Hitcher and Nester, and the Walkthrough to place it inside a complete night routine.