No Means Nothing paces the protagonist's three workdays with three sit-down sessions at the psychologist's office - Meeting 1 between Day 1 and Day 2, Meeting 2 between Day 2 and Day 3, and Meeting 3 between Day 3 and the move to Radek's place. Every transition on this page is the literal NextSceneName field shipped on the matching Psychologist_Meeting config asset, so the flow chart is not a fan reconstruction - it is the route trunk the game itself walks.
Each Psychologist_Meeting asset is a PsyhologistConfig ScriptableObject with three serialized fields - DialogueDelayOnStart, DialogueNode, and NextSceneName. The session scene roots an SContext_Psychologist that holds the config reference, and the SP_Psychologist scenario point runs a DialogueStartDelay coroutine for the configured delay before opening the dialogue node. When the dialogue closes, the scenario point loads the scene named in NextSceneName. All three meetings ship the same five-second delay and the same hand-off pattern, only the dialogue node and the downstream scene change.
The flow chart below traces the protagonist's path from the first workday through to the endings split. Workdays are the daytime shift scenes, the three meeting scenes sit between them, and the finale fork at Radek's place is where the bath LockDoor task and the labyrinth resolve into the four ending scenes.
Each meeting ships its own PsyhologistConfig asset with a unique dialogue node and a unique next-scene hand-off. The structure repeats - five seconds of ambient quiet, the session dialogue, then a scene load - but the content and the downstream shift differ each time.
Sits between the first workday and the second workday. The protagonist leaves the job floor, talks through what just happened, and the next morning picks up the second shift.
Sits between the second workday and the third. The session revisits the protagonist's framing of the prior day and adjusts which choices read as available on Day 3.
Sits between the third workday and the finale at Radek's place. Whatever the protagonist has built across the three sessions carries into the confrontation with Radek.
Skipping any of the three sessions is treated by the route as the protagonist refusing professional support. The Willpower and Labyrinth resolutions are gated behind the work the sessions do - players who skip report being unable to reach those routes even with otherwise qualifying stats.
The community consensus is that the three meetings are not optional side content. Each session feeds the protagonist's stat trajectory and which late-game choices read as available. Players who skip Meeting 3 in particular tend to land on the Anger or Caught routes regardless of intent.
How this is verified: Not directly readable from the in-game config fields. The chain itself is A-level; the consequences of skipping are community-sourced and should be treated as C-level guidance.
The four shipped ending scenes all live downstream of the third meeting's hand-off into Radek's place. Whether the protagonist reaches the calmer resolutions or the more confrontational ones is shaped by what the three sessions have built. The scene references are A-level; the framing of which route skip-players tend to land on is community-sourced.
The three sessions sit on the main route trunk - scene 21_Psychologist between Day 1 and Day 2, scene 22_Psychologist between Day 2 and Day 3, and scene 23_Psychologist between Day 3 and Radek's place. The config assets name the next scene in each case, so skipping is not a route the game wires. Players who try to refuse or rush the sessions report the calmer resolutions locking off.
Three. The build ships 21_Psychologist, 22_Psychologist, and 23_Psychologist as full Unity scenes, and the matching Psychologist_Meeting_1, _2, and _3 config assets drive the dialogue and the hand-off to the next workday (or, after Meeting 3, to 10_RadeksPlace).
Community players who skipped sessions, especially Meeting 3, report losing access to the Willpower and Labyrinth resolutions regardless of their stats. The mechanism is not directly readable from the config fields - the chain itself is verified, the skip consequences are community-sourced and marked C-level on this page.
The Psychologist_Meeting_3 config sets NextSceneName to 10_RadeksPlace. That hand-off is the route trunk's pivot into the finale - the bath fork and the labyrinth both live downstream of Radek's place.
All three Psychologist_Meeting config assets set DialogueDelayOnStart to 5. The SP_Psychologist scenario point runs a DialogueStartDelay coroutine for that duration before opening the dialogue node, giving the scene a beat of ambient quiet before the conversation begins.
The Psychologist character rig, face materials (Base, Neutral, Angry, Sad), and three ambient tracks (amb_Psychologist_1/2/3) exist in the build, but the script only wires the three sessions into the route trunk. There is no fourth session or free-talk mode shipped.
