Submissiveness Stat Guide: The Hidden Compliance Counter in No Means Nothing

Submissiveness Is the Stat the Game Uses to Count How Often You Fold

Willpower is the resistance axis. Anger is the aggression axis. Submissiveness is the third leg of the triangle — the compliance axis. Every time the protagonist says "okay" when they could have said "no", the engine writes a + to Submissiveness. Every time the protagonist refuses, the engine writes a -. The HUD never shows the number, but the engine reads it before every gated choice.

This page is the field guide. Every threshold below is reproduced from the same in-game stat configuration and choice-marker table the engine reads at runtime — Level A verified, no community estimates.

Submissiveness at a glance (Level A):
  • Range: 0 to 10
  • Starting value: 0
  • Verified Required gates: Submissiveness >= 1, Submissiveness >= 2
  • Verified upper-bound gate: Anger >= 2, Submissiveness <= 2
  • No standalone ending routes into Submissiveness — it gates which mid-route options appear, and it pairs with Anger to enable the explosion choice

The Two Lower-Threshold Gates

The choice-marker table inside the shipped string bundle lists twenty-six options with a ||Required= ...|| expression. Two of them test Submissiveness.

Submissiveness ≥ 1 — The "I'm Tired, Drop This" Beat

The line "I'm tired, Radek. Can we just drop this?" ships with the marker ||Required= Submissiveness >= 1||. The engine only shows this option if the protagonist has complied at least once before. The game is literally counting — and the line is the engine telling you it knows.

Notice what the gate does not say. It does not say "if RadekRelationship is high" or "if Anger is low". It says "if the protagonist has a non-zero compliance history". That is the only condition. The engine has decided that disengagement is a behavior that only becomes available after the protagonist has practiced compliance.

Submissiveness ≥ 2 — The Capitulation Tier

The second gate, Submissiveness >= 2, opens the lines where the protagonist actively agrees rather than passively disengages. This is the tier where compliance becomes a pattern instead of an isolated beat, and the script flags it as such.

The Upper-Bound Gate: The Anger Explosion

The single most interesting gate in the entire script, mechanically, is the upper-bound Submissiveness gate: ||Required= Anger >= 2, Submissiveness <= 2||. The engine is checking two conditions at once, and one of them is a ceiling, not a floor.

What this means in plain English: the explosion line only becomes available if the protagonist has been angry and has not been compliant. A player who has been saying "okay" to Radek for two days will not see the explosion option even if their Anger stat is high — the engine is checking that the protagonist has the will to back the anger up. Anger without the boundary, in the engine's logic, is just frustration; anger with the boundary is confrontation.

This is the gate that gives the Anger ending its character. "Screw you, Radek! This is exactly the toxic shit I'm trying to avoid"||Required= Anger >= 1|| — is the softer version. The harder version, the one the engine gates behind Anger >= 2, Submissiveness <= 2, is the line where the protagonist has earned the right to escalate by refusing to comply earlier.

What Raises Submissiveness, What Drains It

The forty-eight options in the choice-marker table that carry ||Stat[+-]+|| effects include a Submissiveness axis. The pattern is consistent: compliance raises Submissiveness; refusal drains it.

Lines that raise Submissiveness (verified + markers)

  • "Okay... mom"||Stamina+, Anger+, Submissiveness+||. The earliest compliance beat in the run. The engine is logging the first time the protagonist folds.
  • "Fine. One beer. Then I'm done"||Anger+, Submissiveness+, Willpower-, RadekRelationship++||. The flagship capitulation line. Four stat writes, two of them compliance-shaped.
  • "Yeah... sorry, didn't mean to snap..."||Stamina+, Submissiveness+, RadekRelationship+||. The post-conflict repair line. The protagonist backs off; the engine credits compliance.

Lines that drain Submissiveness (verified - markers)

  • "NO. Respect my no, or I'm leaving"||Stamina-, Submissiveness-, Willpower+, RadekRelationship-||. The unconditional refusal. Submissiveness goes down alongside Willpower going up — the engine treats them as inverse axes in this beat.

Notice that Submissiveness is much easier to raise than to drain. There are three or four times as many Submissiveness+ markers in the script as Submissiveness- markers. The game is structurally biased toward compliance — which is the entire point of the narrative. The protagonist is being pressured; the pressure is real; and the engine has decided that complying is the path of least resistance.

The Pair-Of-Axes Logic: Submissiveness and Willpower

The shipped choice-marker table treats Submissiveness and Willpower as inverse axes on the same beats. The "NO. Respect my no" line writes Submissiveness-, Willpower+. The "Fine. One beer" line writes Submissiveness+, Willpower-. The engine is not tracking two independent stats; it is tracking one axis with two labels.

This matters for route planning. A player who is building toward Willpower ≥ 9 is also, structurally, keeping Submissiveness low. The upper-bound gate Anger >= 2, Submissiveness <= 2 is therefore not an independent constraint — it tends to come along for free on a Willpower run, because a Willpower run has already drained Submissiveness.

Submissiveness and the Endings

Submissiveness does not route into a standalone ending. It is a contributing stat for two of the six endings:

  • 93_Ending_Anger — gated by Anger, but the explosion line that routes into the Anger ending is gated by Anger >= 2, Submissiveness <= 2. Without low Submissiveness, the explosion line is invisible.
  • 13_Wasted — the Beer-overindulgence scripted sequence. The capitulation line "Fine. One beer" raises Submissiveness; repeated capitulation raises it further. The Wasted route is structurally a high-Submissiveness route.

The Fawn-Response Reading

The reason Submissiveness matters beyond the engine is that it is the in-mechanic representation of the fawn trauma response — the fourth response in the classic fight/flight/freeze/fawn quartet. The protagonist who says "okay" to avoid conflict is not weak; they are running a behavior that has been reinforced by prior pressure. The game knows this. The script makes space for it. The Inner Critic lines, in particular, call out the compliance pattern as it forms.

The Psychology Knowledge Base on this site covers the trauma-response framework in depth, and the Gaslighting Recognition Test walks through the same patterns as a player-facing self-assessment. The Submissiveness stat is the engine-level mirror of what those pages describe in clinical language.

Verify It Yourself

Every threshold on this page is reproducible from the shipped choice-marker table. The Stat Threshold Query tool reads the same markers — slide Submissiveness to 2 and the "I'm tired, drop this" line becomes available; slide Anger to 2 and Submissiveness to 2 or below and the explosion gate lights up.

Related pages:

Sources & Further Reading