W2.03.3Rule invariancedesign

Adjustment must retain a predictable rule core

Aliases: invariant rules · predictability · adaptive systems · player model

What it is

Rule invariance requires an adaptive system to retain the consequential causal rules players use to understand, predict, and practice while changing task pressure. Enemy count, resource slack, and hint strength may vary; identical input should not receive a different hit, damage, physics, or win adjudication without a disclosed condition. Variable difficulty needs an invariant rule core so learning continues to transfer.

Why it happens

Player strategy is a compressed model of rules. If adaptation repeatedly alters that model's basic relations, past success stops being evidence for the future: players cannot develop skill or diagnose failure. Retaining the core limits adaptation to "how much pressure is this situation?" rather than "how does this world work?" Players can still improve through position, timing, and resource choice while the system controls practice load. The clearer the boundary, the more adjustment serves learning rather than replaces it.

Where it stops holding

Some games center changing rules, random affixes, or narrative world shifts. Their core is not every value staying fixed, but stable generation rules, warning, and response tools. Accessibility may also remap inputs or extend windows without changing a goal's causal structure. The test is whether players can know, before a consequential commitment, what rules are stable, what may change, and under which conditions.

Applying it

  • List the adjudications each dynamic adjustment must never change, and the pressure variables it may; treat the former as a combat, movement, and win-condition contract.
  • When rule variants are play, display affixes, scope, and duration before commitment and provide counterplay rather than an after-the-fact explanation.
  • Audit replay or logs for consistent adjudication under equal conditions, especially hits, damage, cooldown, and resources.
  • Verification: before an adjustment occurs, ask testers to predict an action's outcome and its uncertainty source. An unpredictable part caused by hidden adaptation crossed the rule core.

Related

  • Same group: W2.03.1 Adaptive difficulty maintains challenge · W2.03.2 Noticing adjustment dismantles achievement
  • Nearby: W1.03 Rules and constraints · W2.01 Matching skill and challenge · W3.02 Input buffering and forgiveness
  • Search terms: rule invariance · predictability · adaptive systems · player model

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/W2.03.3