Escape is a confirmed Loop [ALPHA] objective. The official description tells players to escape, and the official EXIT badge says “Escape through the EXIT.” This proves a named EXIT and a successful outcome. It does not publish a fixed location, Day, opening condition, mission dependency, party credit rule, or guaranteed route.
Treat escape as five separate steps: discover the EXIT, preserve the route, inspect its state, satisfy the current conditions, and verify the result after crossing.
Discover without committing
When you find something labeled EXIT, stop and name the nearest landmark. Trace the return route back one junction before interacting. Read the current mission and inspect the EXIT’s visible state, prompt, nearby objects, and interface feedback.
Do not assume a familiar-looking door is active or that every exit-shaped object is the official EXIT. The live label and result matter.
Separate location from activation
Finding the EXIT does not prove it is ready. If no action occurs, reread the mission and inspect the current room for a named requirement. Do not invent a key, switch, timer, or mission order just because another game uses one.
When an interaction changes the EXIT, record what happened immediately before the change. Repeat under similar conditions before publishing it as an opening rule.
Preserve the route while doing the mission
Return to the mission from a known landmark and avoid adding unrelated branches. If the EXIT is far from the objective, leave a simple sequence of landmarks rather than relying on visual memory under pressure.
When the Day changes, do not assume the EXIT remains in the same state or place. Recheck the mission and map. “Every Day is different” makes old route notes useful clues, not guarantees.
Approach under entity pressure
If an entity cue begins near the EXIT, stop optional activation tests and protect the retreat line. An escape attempt is not successful until the result confirms it. Rushing an unknown entity interaction at the door can erase a long run.
Use the Entities Dex for verified boundaries. Do not assume an EXIT is a safe zone, blocks damage, or removes an entity unless the current build proves it.
Solo escape plan
In solo, decide an earlier exit threshold. When the mission is complete or the EXIT becomes usable, weigh optional Collections and Items against the risk of losing the route. Mark the door, complete one necessary condition at a time, and return directly.
After crossing, record the result before starting another Day. Check whether the EXIT badge awards, what happens to Inventory and Coins, and whether the run continues or resets.
Co-op escape plan
Regroup at the last landmark before activation. Compare the visible EXIT state on every screen. Decide who interacts and who watches the route. Cross in a controlled order if the current game permits it, then compare each player’s result.
Do not assume one player’s crossing extracts everyone or awards every badge. Record distance, life state, late joins, and who crossed when results differ.
When the EXIT does not work
Check the exact label, current mission, required count or condition if shown, and whether the interaction prompt is available. Compare the state before and after the last mission action. If co-op, let the player whose objective differs inspect or interact.
Repeat once before treating it as a bug. If rejoining, first record the route and resource state because persistence is not publicly guaranteed.
Escape mistakes
- Treating the first door-like object as the official EXIT.
- Leaving without recording the return route.
- Assuming the EXIT is active because it was active in a video.
- Inventing an opening requirement from another game.
- Calling the area safe from entities without evidence.
- Crossing before the group compares state.
- Assuming badge and resource credit is shared.
Escape FAQ
Where is the EXIT?
No fixed location is established by public first-party evidence. Use the current Day’s label, mission clues, and landmarks.
How do I open it?
The official text confirms escape through the EXIT but not a universal activation rule. Read the live mission and nearby prompt, then test one condition at a time.
Does escaping end the run?
That result is not defined publicly. Record the current transition, Day, Inventory, Coins, and badge outcome after crossing.
Does one escape count for the team?
Do not assume it. Compare every player’s result and badge state in the current build.
Evidence status: Escape as a core objective and successful escape through a named EXIT are Official. Location, activation, mission dependency, safe-zone behavior, run result, and co-op credit need in-game testing.