Game Loops: Core, Secondary, Tertiary
Every game has a loop structure — a cycle of actions, feedback, and rewards that keeps players engaged. Understanding loop hierarchy is one of the most powerful analytical tools in game design.
The three loops:
- ▸Core loop (~30 seconds) — the fundamental moment-to-moment action. In your platformer: run, jump, avoid enemies, collect coins. This must be fun on its own, in isolation. If the core loop is boring, nothing else saves it.
- ▸Secondary loop (~5–15 minutes) — a cycle of goals that frames the core loop. Level progression, unlocking abilities, completing areas. Gives meaning to the core loop.
- ▸Tertiary loop (~sessions/days) — the meta-progression. Permanent upgrades, story, achievement, mastery. What brings players back tomorrow.
Why this matters:
Most indie games fail at the core loop level. They have interesting tertiary concepts (great story! cool upgrade tree!) built on a boring 30-second experience. The inverse — a brilliant core loop with thin meta-progression — can still succeed (Geometry Dash, Flappy Bird).
The engagement curve: Each loop has an engagement arc. Core loops need a peak every ~30 seconds. Secondary loops need a climax every ~10 minutes. If you map out when players get rewards in your game and see long flat sections, those are where players quit.
Analytical exercise: Play your own game for 5 minutes. Every time you feel a small burst of satisfaction, note the timestamp. Plot these. Is the distribution even? Or are there long dead zones?
Game to Study
Dead Cells
Dead Cells has no secondary loop (no persistent level structure) — only core and tertiary. How does it compensate? Why does this work for a roguelike but would fail for a traditional platformer?
Unity Tip
Track your own core loop: add a simple `GameAnalytics.cs` script that logs a timestamp every time the player collects a coin, kills an enemy, or dies. After a play session, look at the gaps.
Someone pitches you a game: 'It's a farming game with deep lore, seasonal events, and a massive skill tree.' You play for 10 minutes and quit. Diagnose the problem using loop theory — which specific loop failed and how?