Labyrinth Ending

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.

1. 1
   11_Finale_1_Bath+0.0s

   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.

   ↓
2. 2
   11_Finale_1_Bath+5.5s → knock at ~4.5s

   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.

   ↓
3. 3
   11_Finale_1_BathPlayer choice

   Player chooses: run, stay (Labyrinth), confront (Anger), or resolve (Willpower).

   StayLabyrinthResolveWillpowerConfrontAngerRun (succeed)EscapeRun (fail)Caught
   ↓
4. 4
   11_Finale_1_BathLockDoorTaskDelayOnStart 2s → 10s window

   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.

   ↓
5. 5
   11_Finale_1_BathTask outcome

   LockDoor task resolves: success routes to RanAway, failure routes to GotCaught.

   SuccessEscapeFailureCaught

The Wasted ending sits outside this flow — it triggers earlier from excessive drinking at Radek's place and never reaches the bath scene.