Game DesignGame design decisionBeginner~6 min

Core loop

Snapshot

~75 sec

A core loop is the smallest repeating cycle that keeps a player deciding: intent → action → result → re-entry. If players cannot find that cycle in the first minutes, they do not feel a game - they feel a pile of features.

You will learn

Name the four beats of a readable core loop in one invented session.
Spot when a feature sits outside the loop instead of feeding it.
Rewrite a broken re-entry so the next intent of the same kind is obvious.

Target outcome

You can sketch one playable loop and explain where a stuck player loses the next intent.

01
Four beats every readable loop needs
- Intent
  The player wants something specific in this moment.
- Action
  They spend attention on one available move.
- Result
  Something changes in a way they can notice.
- Re-entry
  They are invited back into another intent of the same kind.
02
The four-beat core loop
A core loop is only a loop if re-entry returns the player to a fresh intent of the same kind.
1. Intent
  The player wants something specific in this moment.
  commits
2. Action
  They spend attention on one available move.
  produces
3. Result
  Something changes in a way they can notice.
  reveals
4. Re-entry
  They are invited back into another intent of the same kind.
renewsRe-entry → Intent
A core loop is only a loop if re-entry returns the player to a fresh intent of the same kind.
Reading order
1. Intent
  The player wants something specific in this moment.
2. Action
  They spend attention on one available move.
3. Result
  Something changes in a way they can notice.
4. Re-entry
  They are invited back into another intent of the same kind.
Connection explanations
1. Intent → Action (commits)
  Intent without a clear available action is a wishlist, not a loop beat.
2. Action → Result (produces)
  An action must leave a readable change or the player cannot learn the loop.
3. Result → Re-entry (reveals)
  Result should renew the same kind of intent, not dump the player into a different game.
4. Re-entry → Intent (renews)
  Re-entry closes the cycle only when the next intent matches the same kind of decision.
Continue next
Teach the loop in the first session
Once the loop is readable, design how the first sitting rehearses it before adding forks.

Feature pile compared with a closed loop

Approach	Clarity	Repeatability	Why try again
Feature pileMenus and systems appear without a shared returning beat.	The player cannot say what they are supposed to do next.	Each screen feels like a new errand, not a cycle.	Curiosity dies after the first novelty wears off.
Closed loopOne invented activity returns the player to a fresh attempt.	The next intent is visible after every result.	The same kind of decision recurs on purpose.	The player wants another try because the re-entry is honest.

Anti-pattern
Adding systems before the loop is readable
New currencies, menus, and modes cannot rescue a missing re-entry. If the player does not know why to try again, more systems only multiply confusion.
Diagnose a stuck first session
A prototype has a shop, a daily board, and three modes, but playtesters quit after two minutes saying they do not know what to do. What is the most likely missing beat?
Expected reasoning
Re-entry. The session never returns them to a clear next intent of the same kind, so the shop and modes read as disconnected destinations instead of tools inside a loop.

Core loop

You will learn

Target outcome

Visual walkthrough

Four beats every readable loop needs

Intent

Action

Result

Re-entry

The four-beat core loop

Intent

Action

Result

Re-entry

Reading order

Connection explanations

Feature pile compared with a closed loop

Diagnose a stuck first session

Play one invented core loop