Design

Core Loops and Mechanics: Finding the Thing Players Repeat

Every game that holds attention has a small cycle of actions at its centre. Finding that cycle early is the cheapest design decision you will make.

Mechanics, then gameplay

Game mechanics are the rules and procedures that guide the player and define how the game responds to what the player does. Gameplay is the pattern that emerges when a person actually engages with those rules. You design the first; you can only observe the second. That gap is why paper designs so often feel different once they are playable.

What a core loop is

The core loop is the shortest sequence of actions the player repeats for the whole game. In a platformer it may be see gap, judge jump, land. In a farming game it may be plant, wait, harvest, spend. Everything else, including story, upgrades and art, sits on top of that loop and gives it variety and meaning.

A useful test: describe your loop in one sentence made of verbs. If you need the word "and" more than twice, you are probably describing two games.

Three layers of loop

  • Second to second. The feel of a single action: a jump, a card played, a block placed. This is where input response, animation and sound matter most.
  • Minute to minute. A level, a round, a day. Here the player sets a small goal and reaches it.
  • Session to session. Why the player returns tomorrow: a new area, a build to try, a story thread left hanging.

Small teams usually have time to make one of these layers excellent. Choose it deliberately and make the other two merely sufficient.

Prototype the verb, not the game

  1. Grey boxes only. No art, no menus. One room, one verb.
  2. Play it for ten minutes. If the bare action is not pleasant with rectangles, art will not rescue it.
  3. Change one variable at a time. Jump height, cooldown length, hand size. Note what each change did.
  4. Add the second verb only when the first feels right.

Feedback closes the loop

An action without a visible, audible result does not feel like an action. For each verb, list what the game does in reply: an animation, a sound, a number that changes, a small pause on impact. Players read these replies as the rules of the world, so keep them consistent. If a red flash means damage in level one, it should not mean a pickup in level three.

Common loop problems

  • The dominant strategy. One approach beats all others, so players stop making decisions. Look for it in playtests and weaken it or give alternatives a reason to exist.
  • The dead wait. Time in which the player has nothing to decide. Shorten it or put a small choice inside it.
  • The hidden rule. Something important the game never communicates. If testers are surprised by a death, the rule is hidden.

Write your core loop on a sticky note and put it on the monitor. When a new feature is proposed, ask whether it makes that loop better. If it does not, it goes on the "after launch" list.

// Kit Farrowdale // revised 2026-11-12