Game Core Loop Design: 30 Seconds, 5 Minutes, 5 Hours

Q: What is a core loop in game design?

A core loop is the repeating cycle of actions a player performs. In practice a good game has three nested loops: a short one of around 30 seconds covering what your hands do, a medium one of around five minutes covering a session goal like clearing a room or finishing a run, and a long one over hours covering progression, story or mastery. The exact timings vary by game. What matters is that all three exist and that each one produces something the next one uses.

Q: How do I know if my 30-second loop is fun?

Strip out every reward, number and progress bar, put the player in a plain greybox room and watch whether they keep playing for a couple of minutes because the action itself feels good. Celeste passes this test easily: jumping and dashing is fun in an empty room. If players stop immediately, fix input response, movement and feedback before building any progression systems, because rewards cannot make an unpleasant action enjoyable for long.

Q: How long should a mobile game session be?

Short enough to finish while waiting for something, so design the medium loop to feel complete in one to a few minutes and to survive interruptions. An endless runner's session is a single run, which may last only ninety seconds, and it still needs a clear goal, rising tension and a payoff screen. Sessions sized for PC, around twenty minutes or more, tend to get abandoned on phones because players are interrupted before reaching the payoff.

Q: Should I design the long progression loop first?

No, and it is one of the most common mistakes in small teams. Skill trees, crafting and upgrade systems are easy to write in a design document, so they get built first, but they are expensive and cannot rescue a short loop that is not fun. Prove the 30-second loop in a greybox, then shape the medium loop with real playtests, and only then invest in the long loop that brings players back over days and weeks.

Q: How should the three loops connect to each other?

Each loop should produce something concrete that the next loop consumes. In a small roguelite, coins from the 30-second combat loop buy an upgrade in the 5-minute floor loop, and a permanent currency from each run buys new starting weapons in the long loop. The important arrow goes backwards: the long loop should change the short loop with new verbs or tools, not just bigger numbers, otherwise hour five plays the same as minute five.

Q: How can I measure loop timing during playtests?

Log timestamps at key moments. In Unity, a small component using Time.time can record the gap between short-loop beats, such as kills or landed jumps, and the time at which each session goal completes. If players go twenty seconds without a short-loop beat, pacing is off; if a five-minute run takes fifteen, the medium loop is too long. Debug logs are enough to start, and you can move to proper analytics later. In the browser, performance.now() does the same job.

Q: What are common core loop anti-patterns?

Building the long loop first; progression that only adds bigger numbers; loops that sit side by side without feeding each other, like crafting that never changes combat; short loops that rely on inputs the game never teaches; and medium loops sized for PC on a phone. In a PawScooty play-test, untaught swipe controls and a 60-coin star goal that a normal run did not reach were the main reasons the build scored 5.2 out of 10 in my own review.

Q: Can AI help design a core loop?

Partly. An AI assistant is useful on paper: describe your three loops and ask it to find unlabelled connections or ways the long loop could change the short one, and it will produce many options quickly, some of them good. It also writes simple telemetry code and summarises playtest logs well. It cannot tell you whether the 30-second loop feels good, because that needs hands on a controller and someone watching the player's face during a real session.

Satyam Kumar

Back to Blog

architecture

Your Core Loop Has Three Clocks: Designing What Players Do Every 30 Seconds, 5 Minutes and 5 Hours

By Satyam KumarOctober 24, 202610 min read

core gameplay loop game core loop design game loop timescales moment to moment gameplay session design progression design player retention design indie game design greybox prototyping game feel celeste design hades run structure stardew valley progression roguelite design unity playtest telemetry endless runner design pawscooty

Your Core Loop Has Three Clocks: Designing What Players Do Every 30 Seconds, 5 Minutes and 5 Hours

Frequently Asked Questions

Share this article

Twitter LinkedIn WhatsApp

Satyam Kumar

Founder & AI Architect, AppScale LLP

AI & Cloud Architect. Helping teams build systems that scale to millions.

LinkedIn GitHub

Your Core Loop Has Three Clocks: Designing What Players Do Every 30 Seconds, 5 Minutes and 5 Hours

Frequently Asked Questions

Share this article

Comments

Leave a comment