Day 4 of 7
40 min
Find The Core Loop
Day 4 -- the one thing the player does, over and over, that stays fun.
Pixel
When the kid opens the day
“Pitch? Locked. Promise? Locked. Today we find the loop. The loop is the thing the player does over and over for hours and it does not get boring. Mario -- run, jump, stomp, repeat. Stardew -- water, harvest, sell, upgrade, repeat. The Witness -- look, notice, solve, gasp, repeat. Today we find YOURS. This is the heart of the whole game. If the loop is bad, the game is bad. If the loop is good, everything else gets easier.”
Today’s artifact
Core Loop Diagram -- the 3-to-5-step cycle, saved to your Capstone Locker
The lesson, beat by beat
- 1
What a loop actually is
~6 min
Pixel says
“A loop is not a level. A loop is not a story. A loop is a thing you DO, then a thing that HAPPENS BACK, then a NEW thing you do, and around and around. Three to five steps. Each step makes the next one matter. If your loop has eight steps, it is too complicated. Trim it.”
Kid does
Watch a 60-second annotated clip of three game loops (3-step, 4-step, 5-step). Count the steps in each.
- 2
Reverse-engineer a game you love
~7 min
Pixel says
“Now pick a game you have played a lot. Any game. Tell me the loop in three to five steps. Just verbs. Verbs are the heart of game design. Run. Jump. Catch. Sell. Build. Verbs only.”
Kid does
Type the loop of a game they love, in verbs only. Pixel checks that it is 3-5 steps.
- 3
Prompt AI for YOUR loop
~10 min
Pixel says
“Recipe Card time. Goal -- three possible core loops for [your game]. Details -- here is my pitch and my promise. Examples -- here is the loop of a game I love. Limits -- verbs only, 3 to 5 steps, each step must matter to the next. Go.”
Kid does
Write the prompt. Send. Read the three loop options AI returns.
- 4
Pick and refine
~8 min
Pixel says
“Pick the loop that feels most like YOUR game. Now stress-test it. Ask -- if I did this loop for an hour, would I still want to do it? If yes, keep it. If no, cut a step or change a verb. The pros rewrite loops twenty times before locking. You only have to rewrite once today.”
Kid does
Choose one loop. Tweak one step. Pixel asks them to read the final loop out loud.
- 5
Draw it as a circle
~5 min
Pixel says
“Now draw it. Use the Loop Diagram template. Step one at the top, then arrows around to step two, step three, step four, back to step one. Real designers draw their loops as circles. That is how you know it is a loop and not a list.”
Kid does
Fill the Loop Diagram template -- circular arrows, one verb per node.
- 6
Save the diagram
~4 min
Pixel says
“Save it. The loop is the engine. We do not change the loop after today unless the game tells us we have to. And it might. Games are alive that way.”
Kid does
Click Save. Core Loop Diagram lands in the Capstone Locker under Week 2 / Day 4.
Pixel signs off
“You have a core loop. That is the engine. Tomorrow we figure out the world this loop lives in -- and the character who runs it. See you Friday.”
Show your grown-up
Show your grown-up your Loop Diagram. Walk them through one full cycle -- 'I do this, then this happens, then I do this, then this happens, then I do this again.' If they get the loop after one walkthrough, you nailed it.
What goes to the parent dashboard
Your kid mapped their game's core loop today -- the 3-to-5-step cycle the player will repeat. This is the single most important design decision in a game. Ask them to walk you through one loop. If you find yourself wanting to play it after, that means the loop works.