Map a game's core loop and the short, medium and long-term goals that keep players playing.
Why it matters
Players spend most of their time repeating a small set of actions. If that repetition is satisfying, they will forgive a lot; if it is not, no amount of story or art will save the game. Designers call that repeated cycle the core loop, and mapping it is one of the first things you do when analysing or planning a game.
The core idea
A core loop is the shortest cycle of actions a player repeats, where the result of one cycle feeds the next. It is usually written as verbs:
explore -> fight -> collect loot -> upgrade gear -> explore (harder area)
A good loop has three qualities:
- Clear action: the player knows what to do next.
- Feedback: each step gives a visible result (a number goes up, a door opens, a sound plays).
- Progression: the output of the loop changes the next pass, so it is not identical every time.
Loops inside loops
Most games nest loops of different lengths, and each layer has its own goal:
| Layer | Time scale | Example (a farming game) |
|---|---|---|
| Moment-to-moment | seconds | water a crop, hear the sound, see it sparkle |
| Core loop | minutes to a day in game | plant -> water -> harvest -> sell -> buy seeds |
| Meta loop | sessions to weeks | expand the farm, unlock a new area, finish a festival |
Short-term goals keep hands busy; medium-term goals give a reason to finish the session; long-term goals give a reason to come back tomorrow. When a game feels aimless, one of these layers is usually missing.
Worked example: mapping a puzzle game
Take a match-three puzzle game.
- Moment-to-moment: swap two tiles -> match three -> tiles clear with a satisfying effect.
- Core loop: start level -> make matches to meet the goal within limited moves -> win or lose -> earn stars -> next level.
- Meta loop: collect stars to unlock new worlds; complete a themed event.
- Resources: moves (spent per swap), stars (earned per level), lives (spent on failure).
Now look for the quit point. A player who fails the same level five times has no new information and no progress: the loop has stalled. A designer might add a small reward for near-misses, a hint after repeated failure, or an alternate level path.
Goals: make them visible
Players chase goals they can see. Useful goal design follows a few rules:
- Show the next goal before the current one ends. A visible "next upgrade costs 50 coins" gives the next loop a purpose.
- Mix certain and uncertain rewards. Fixed rewards build trust; occasional surprises add excitement.
- Let players choose some goals. Optional challenges and side quests support different motivations (more on that in the next lesson).
Common mistakes
- A loop with no output. If finishing a cycle changes nothing, players feel they are running in place.
- Too many resources in the core loop. Five currencies in the first ten minutes overloads a new player. Introduce them one at a time.
- Only long-term goals. "Reach level 50" is meaningless at level 1 without smaller steps along the way.
- Confusing the loop with the plot. Story beats are not the core loop. The loop is what players do repeatedly.
- Loops that reward the wrong thing. If the fastest way to progress is a boring exploit, players will do it and then blame the game for being boring. Reward the behaviour you want.
Quick recap
- The core loop is the shortest repeated cycle of player actions, written as verbs.
- Good loops have clear actions, feedback and progression.
- Games nest moment-to-moment, core and meta loops with short, medium and long-term goals.
- Find the quit point in a loop and change one rule to fix it.
Try it
Open the Do tab and map the core loop and goals of a game you know well.