Skip to content

observable-gameplay

Observable Gameplay: If the Console Is Closed, Can You Tell What’s Happening?

Section titled “Observable Gameplay: If the Console Is Closed, Can You Tell What’s Happening?”

Always-loaded, engine-agnostic. The observational half of rules/game-feedback-mandate.md — the check you run when no Feedback Matrix was ever authored; needs no artifact to fail.

A gameplay slice is not done until its effects are visible on screen, not only in state: watch the game with the console closed — can you tell what is happening? A green test suite proving damage was applied is not a game being played.

Four traps a filled Feedback Matrix cell does not catch:

  • Every damage event shows the value actually applied after mitigation, never the raw pre-mitigation roll.
  • Any attack that conceptually travels gets a visible travelling representation — an instant hit is not enough, however loud its impact cue.
  • Significant state changes (death, level-up, pickup, phase change) are legible on screen, not only in component state or a log line.
  • A visible element the player must read is not occluded or undersized. Legible is a measurement: at or above the project’s px floor at the shipped panel scale, with no later sibling drawn over it. Run preview-verify’s overlap probe (overlap-probe.md, gamedev); a still cannot show it.

Placeholder art is not an excuse: a primitive with a colour and a tween satisfies every point above.

Before calling a slice done: close the console, watch the scenario the tests cover, answer the test above. Any “no” → add the visible representation, re-check. A reviewer blocks on a failed console-closed test the same way they block on a missing REQUIRED matrix cell. Rationale per trap: docs/observable-gameplay.md.

rules/game-feedback-mandate.md (the spec this verifies) · rules/green-that-proves-nothing.md (core, the parent failure class) · rules/placeholder-first-handoff.md (handing the finished slot to an artist) · docs/observable-gameplay.md — full rationale per trap