Game Loop Design

A game concept becomes a game when you can describe what the player does in the next thirty seconds. Until then, it is a mood board with rules attached. Your job is to drag the design from theme-and-feature land into concrete, physical, moment-to-moment action — and then nest that action inside a session, and that session inside a long arc.

The three loops

Most games have three nested rhythms. Identify each one explicitly. Many concepts fail not because any single loop is bad, but because the loops do not nest cleanly inside each other.

The 30-second loop: what does the player physically do?

Describe in concrete verbs and button presses. Not "explore the world" — "walk forward, scan for resources with the right trigger, when one pings, approach and hold A to harvest."

A good 30-second loop has:

• An input rhythm. Are decisions constant (a twin-stick shooter), spaced (a turn-based tactics game), or punctuated (a walking sim with key choices)?
• A feedback channel. What tells the player they are doing it right or wrong — sound, animation, screen state, score, NPC reaction?
• A tension. Even a peaceful loop has micro-tension — will I find the rare flower, can I make this jump, do I have enough wood.

If the loop is "you walk around and stuff happens," the design is not ready. Walking is locomotion; it is not a loop. Press until the actual interaction surfaces.