The Caught Ending (internally "GotCaught") is one of the darkest outcomes. You attempt to escape but fail, resulting in being trapped in the toxic situation with no way out.
Caught Ending - Trapped
This ending serves as a sobering reminder of the real dangers in manipulative relationships. The game doesn't shy away from showing the consequences of being unable to escape.
It's intentionally disturbing to underscore the stakes of the situation and why boundary-setting matters.
This ending typically happens when:
Conditions:
- Low willpower from consistently poor choices
- Attempt to escape but fail
- Wrong decisions during critical moments
Common Paths to This Ending:
- Agreeing to too many of Radek's demands
- Not establishing any boundaries
- Failing escape sequences or confrontations
- Missing opportunities for help
This Represents:
The worst-case scenario the game wants players to avoid—being completely trapped with no resources, support, or ability to leave.
Exact stat thresholds for each ending (for example the precise Willpower value that admits the Willpower route) are not text-extractable from the available game files — they live inside compiled Yarn dialogue branches and C# method bodies that could not be fully decompiled. The community consensus is that high sustained Willpower, low Submissiveness, and a strong RadekRelationship trajectory are the steering signals. Treat any specific number you see elsewhere as community-sourced, not verified.
Choose to run in the bath sequence
Fail the 10-second LockDoor task
The bath scene is the central fork of five endings. Every timing value below is read directly from the config asset — the 4.5-second knock delay, the 2-second task delay, and the 10-second LockDoor task window are all A-level verified. Failing the LockDoor task is the mechanical trigger that drops the route into the GotCaught ending.
Scene loads. Bath dialogue node Ending_Bathroom_Start is queued.
DialogueDelayOnStart 5.5s pauses the scene before the bath sequence opens — the player has a brief window to settle before the knock arrives.
KnockDelayOnStart (4.5s) fires the knock that opens the bath sequence.
After the knock, the player faces the central choice: run, stay, confront, or resolve. This single decision routes into one of five endings.
Player chooses: run, stay (Labyrinth), confront (Anger), or resolve (Willpower).
If the player runs, the LockDoor task begins after a 2-second delay.
LockDoorTaskDuration is exactly 10 seconds — confirmed line-by-line in Bath Config.asset. The player must complete the task inside this window or the route falls into GotCaught.
LockDoor task resolves: success routes to RanAway, failure routes to GotCaught.
The Wasted ending sits outside this flow — it triggers earlier from excessive drinking at Radek's place and never reaches the bath scene.
11_Finale_1_BathSceneChoose to run
Why it matters: Branches into the escape attempt
11_Finale_1_BathSceneMiss the 10-second LockDoor window
Why it matters: Falls into Caught
Common on a first attempt at the bath sequence
No achievement is tied directly to this ending
Useful as a practice run for the Escape route
Open the full transcript for any scene below to see how each choice nudges the route toward Caught Ending.
Use our interactive ending calculator to plan your perfect playthrough
Try the Ending Calculator →