Players infer rules through experimentation
Aliases: hypothesis testing · experimentation · learnable rules · player inference
What it is
Rule inference through experimentation describes how players facing an uncertain interaction system do not wait for a tutorial to state the rules; they form hypotheses ("fire should burn wood"), design tests (move the fire source close to the wood), observe outcomes, and then revise or confirm the hypothesis. The process is hypothesis testing, and it is the cognitive foundation of discoverability design—much of the pleasure of game rules comes from "I figured it out" rather than "I was told."
Why it happens
Players enter a game carrying real-world experience and genre conventions that form prior expectations. The pleasure of game rules comes from two directions: rules matching expectations are absorbed frictionlessly at minimal cost, while rules deliberately deviating from expectations create surprise—but the deviation must remain inferable from interaction outcomes. Inference needs three conditions: a hypothesis can be formed (the player can think of something to try), a test can be executed (an input path exists and is cheap), and a result can be read (the outcome clearly maps to whether the hypothesis held). Break any one and the inference chain collapses—players either give up or brute-force every random combination.
Where it stops holding
Inference-based learning costs time and cognitive resources, and not every scene deserves the expense. Narrative-driven games should lower inference cost on the critical path: if players stall on reasoning rather than challenge, narrative pacing suffers. Inference also requires rule-system consistency: elements of the same kind must follow the same rules, otherwise the player's mental model is repeatedly overturned and inference turns from pleasure into frustration. Finally, inference assumes a willing experimenter—achievement-oriented players may take the shortest path and never try "useless" interactions, making hidden mechanics permanently invisible to them.
Applying it
- Audit every rule meant to be discovered: confirm players can form a hypothesis from real-world experience or genre conventions, have a low-cost way to test it, and receive outcome feedback that clearly points to whether the hypothesis held.
- When a rule deviates from common sense, use environmental or non-verbal cues (colour, shape, material) to narrow the hypothesis space.
- Verification: have someone who has never seen the game play for twenty minutes; log their first hypothesis for each key rule, their testing path, and the inference outcome. Rules where hypotheses cannot form or tests cannot execute need more cues or lower interaction cost.