Day 4 of 7
35 min
Rules, Story, and Win Condition
Day 4 -- make it a real game, not just an idea.
Pixel
When the kid opens the day
“Okay. World? Check. Hero? Check. But right now your game is a vibe, not a game. Today we add RULES. How the player wins. How they lose. What they are allowed to do. By the end of today you have got a real Tiny Design Doc. The kind a developer could actually build from.”
Today’s artifact
Tiny Design Doc -- saved to your Capstone Locker
The lesson, beat by beat
- 1
What makes a fair rule?
~5 min
Pixel says
“Fair rules feel good even when you lose. Unfair rules feel bad even when you win. Quick test: would YOU play this game and feel okay losing? If yes, fair. If no, fix it.”
Kid does
Look at two example rules. Pick which one is fair and explain why in one sentence.
- 2
Write your rules
~8 min
Pixel says
“Use the Recipe Card. Goal: five rules for my game. Details: player promise plus core loop. Examples: a game with rules I think are fair. Limits: a kid should understand them in ten seconds.”
Kid does
Write the prompt. Send. Get five rule options. Pick three.
- 3
Win condition and Lose condition
~7 min
Pixel says
“Every game needs both. Win = what does success look like? Lose = what does failure look like? Both should feel earned. You ran out of time is boring. You ran out of time AND the dragon caught up is way better.”
Kid does
Write one win condition and one lose condition into the Tiny Design Doc.
- 4
The story shape
~8 min
Pixel says
“Even simple games have a shape. Start: you are stuck on a desert island. Middle: a storm is coming. End: build a raft before the wave hits. Three sentences. That is your shape.”
Kid does
Write three sentences for start, middle, end. Pixel offers one piece of feedback per sentence.
- 5
Read it back out loud
~7 min
Pixel says
“Designers read their docs out loud. Sounds weird but it works. Your ear catches things your eye misses. Read your Tiny Design Doc out loud. Did anything sound off? Fix it.”
Kid does
Read aloud. Edit at least one sentence based on the read.
Pixel signs off
“Look at that. A whole Tiny Design Doc. With rules. With win and lose conditions. With a story shape. Tomorrow we build the first playable thing, a prototype you can actually click.”
Show your grown-up
Read someone the Win Condition and the Lose Condition. Ask them: does that sound fair? If they say yes, you balanced it right. If they say too easy or too hard, great, that is data, we tune it.
What goes to the parent dashboard
Your kid wrote a complete tiny design doc: rules, win condition, lose condition, story shape. This is real game-dev work in kid-sized portions.