OFFICIAL FACTS
Patch 1.0.3 makes struggling free easier at Stalk Tiers 0–2, reduces the force of failed grabs, and fixes several issues involving apparent escapes and Civilian movement.
Sources & verification ↓Reading position: —
Reading position stays in this browser.
| Where the rescue stopped | Question to resolve | Useful next record |
|---|---|---|
| Before movement | Was responsibility assigned? | The resident’s landmark and assigned escort |
| Along the route | Did the destination change? | Last confirmed position and new destination |
| At the escape | Is the current requirement complete? | Prompt, location and game version |
| After the result screen | Which result or challenge did you expect? | Exact objective text and final result |
A PLAN TO TRY
Finding someone is only the first state
Use three labels in your own voice communication: located, ready to move, and moving. These are suggested callouts, not game UI states. They help the team distinguish a resident who has merely been found from one actually being escorted. Include a landmark with each message so the next teammate knows where to act. For an outskirts session, prepare an East Haddonfield landmark vocabulary before escorting residents.
Assign a handoff before splitting up
If you leave to search for supplies, tell the group whether someone still needs to handle the resident. A vague “I found one” can make every teammate assume somebody else took over. For a small group, combine duties; for a full group, agree who reports the route and who stays aware of the escort.
Recheck the destination
A route that was merely mentioned earlier may not be usable now. Before moving, confirm what your team has actually observed and whether the destination remains the shared plan. Keep the report short: starting landmark, intended destination, outstanding requirement. Long commentary makes urgent changes harder to hear.
Diagnose an incomplete rescue
If the attempt fails, separate a missing instruction from lost orientation or an apparent NPC pathing problem. Record where progress stopped instead of assigning blame. That distinction tells you whether the next action is communication practice, map learning or a reproducible support report.
After persuasion: choose the next action
Official multiplayer guidance includes requesting police calls, hiding and following. As a planning rule, first check whether your next destination is ready: if it is, assign an escort; if it is not, communicate what is missing before moving. Use the choices currently available in the game rather than assuming every resident presents the same menu.
A rescue handoff that another player can act on
Use a short message with four parts: landmark, what you observed, who is responsible, and the next destination. For example: “Resident at the junction; I have not started moving them; can you take over while I check the exit?” This is an example of team communication, not a map-specific route or an in-game command. Wait for an acknowledgement so that finding a resident does not become an unassigned task.
Resident will not enter the escape: narrow down the failure
First check that the route is currently usable and that the required interaction is complete. Next describe where the resident stopped: on the way, at the entrance, or after an apparent exit interaction. Patch 1.0.1 addressed resident pathing into escapes, so version and location matter when reporting a repeatable issue. That patch note does not prove that every later obstruction is fixed or that every failed rescue is a pathing bug.
When the escort plan changes midway
If the destination changes, tell the escorting player explicitly before redirecting the rest of the team. Name the new landmark and identify who has actually checked it. Do not send a second player to the old destination on the assumption that everyone heard the first message. After the match, compare the last confirmed location and assignment; this separates a communication gap from a problem with the game’s route handling.
Update your grab and rescue expectations
The patch says Civilians have an easier time struggling free from grabs at Stalk Tiers 0–2, and failed grabs create less impact force. It also fixes cases where players appeared to escape but were still executed, and movement could be lost after a grab interaction. This does not remove the need to confirm the route and resident handoff. If a repeatable rescue fails, note whether the problem was the grab, player movement, resident pathing or the exit interaction.
Questions about this guide
Are these three labels official commands?
No. They are a suggested communication convention.
Can this guide guarantee an NPC route?
No. It gives a handoff method, not verified pathing coordinates.
Can I use the same resident rescue route every match?
Use landmarks to communicate, but recheck the current escape and items. The official multiplayer description makes those locations variable.
Does a stuck resident mean the whole match is bugged?
Not enough evidence. Record the point of failure and current objective first; distinguish a missing requirement from a repeatable pathing problem.
What should I report if escorting repeatedly fails?
Include the version, map, landmark, current objective, where the resident stopped and the result of the attempt. Keep a short clip if you can reproduce it; avoid claiming the cause before checking it.
Did 1.0.3 fix every resident pathing problem?
The patch lists specific grab and movement fixes, but does not claim that every resident route or escape issue is resolved. Record the exact location and step that failed.
Your next-match checklist
0/4 completedProgress stays in this browser. No account or cloud sync.
Work through this issue step by step ↗
Sources & verification
Article updated September 23, 2026. Each guide links its official sources and shows its article update date. Planning advice is editorial, not a tested walkthrough or a guarantee of results.
- Multiplayer overview ↗
- Stealth, stalking and scares ↗
- Patch 1.0.1 · September 8 ↗
- Patch 1.0.3 · September 22 ↗