game-loop-design

Define the repeating cycle of trigger, action, result, and re-trigger that the player performs every few seconds or minutes. Then attach a meta-loop for between-session retention and a progression layer, giving each element a playtest-verifiable readiness criterion.

The core loop is what the player does every few seconds or minutes during a session, such as draw, play, resolve. The meta-loop answers why the player returns tomorrow, covering rewards, progress, and reasons to start the next session.

Classify every original mechanic as automated, simplified, or replaced, with no mechanic silently dropped. Separately define the digital player composition: AI opponents, matchmaking lobby, or hotseat, since opponents are free at a physical table but costly in software.

Yes. For story-driven or authored-level games, the slice unit becomes a scene, chapter, or level instead of a loop element, and the meta-loop can be marked N/A with justification. An unjustified empty meta-loop is still flagged at review.

A good criterion names an observable fact from a playtest, such as no player skipping a phase across ten sessions, not a general impression like it feels fun. Criteria about onboarding or readability must also specify tester composition, including first-time players.