Game Design & Development · Tiny-Loop Tutorial · Archetype #9
Tutorial: Quiz Adventure
This is the exact Quiz Adventure archetype from What Makes a Game? — already built and running below. Play it, then swap the question set and avatar using the panel underneath. You can't break the loop itself; that part is locked. Once you've tuned a version you like, you'll build this same architecture two more times: with Scratch's blocks, then from real scratch in JavaScript.
🗺️ The Architecture
Every tiny-loop game starts as a concept, then gets broken into a core loop, a systems list, and a structure — before anyone touches sprites or colors. Here's the Quiz Adventure's architecture. Notice this one is different from the others: almost all of the design work is writing, not programming — the engine is short.
The four systems, in order of execution on every answer:
- Question display system — shows the current question's text and its answer choices as buttons.
- Answer-check system — compares the clicked choice against the question's correct answer.
- Hint/retry system — a wrong answer shows a hint and uses up one retry; running out of retries reveals the answer so no one gets stuck. The buttons lock while the game moves on, so a fast double-click can't skip a question.
- Progress system — a correct (or revealed) answer advances the progress bar to the next question, or ends the quest on the last one.
🎮 Play & Customize
Click an answer, or press 1, 2, or 3. Correct answers advance the quest, and wrong answers give you a hint and another try. Getting it right on the first try earns a ⭐. The choices are shuffled every time you play.
Loading…
Tune the Game (limited, on purpose)
Content settings change how it looks and apply instantly. Rule settings change how it plays, so the round restarts.
Notice what you can't change here: there's no field for "how answer-checking works" or "how the progress bar advances." That's the engine — the part every version of this game shares. You're only tuning content (and writing questions), not rewriting architecture. That's the limit, on purpose.
What these actually touch in the engine: Retries per Question only sets the starting value of retriesLeft each time a question renders — the same retriesLeft <= 0 check in onChoice() decides when to reveal the answer and advance, whatever that starting number is. Question Set swaps in a whole different questions array — onChoice() never looks at whether a question is math, science, or animals, only at choices and correct.
👀 Peek at the Code
The game running above is this code — nothing hidden. It's split into two parts on purpose: a small config & question-set object you just edited with the panel, and a locked engine that reads it.
✏️ Config & Content — this is what the panel above editsconst config = { theme: 'math', avatar: '🧙', retries: 3 }; const questions = [ { text: '5 + 7 = ?', choices: ['10', '12', '13'], correct: 1, hint: 'Count up from 7, four times.' }, // ...more questions ];
👆 This block updates live. Change anything in the panel and the matching value flashes here. There's no separate "demo" version of the code; this is it.
🔒 Engine — locked, shared by every version of this gamefunction onChoice(choiceIndex) { const q = questions[currentIndex]; if (locked) return; // ignore clicks while we're moving on // 1. check the answer if (choiceIndex === q.correct) { locked = true; advance(); // 2. correct: move to the next question, or win return; } // 3. wrong: show the hint, use up a retry retriesLeft--; showHint(q.hint); if (retriesLeft <= 0) { locked = true; advance(); } // 4. out of retries: reveal & advance }
🧪 Remix Challenges
The panel can only turn the knobs the engine exposes. To change the rules, you change the engine. Each challenge edits one system. Try them in your own copy once you've built it in Lesson 2.
TweakWrite your own question setContent only · zero engine changes
Add a fourth entry to questionSets about something you know well. If you follow the same shape (text, choices, correct, hint), the engine runs it without a single change. Writing good hints is harder than it looks: a hint should point at the method, not give away the answer.
{ text: '…', choices: ['A', 'B', 'C'], correct: 1, hint: '…' }TwistA countdownNew system: time pressure
Give each question 10 seconds. When time runs out, it counts as a wrong answer. Now the game rewards fluency as well as knowledge. Is that what you want for a learning game? Different subjects might answer that differently.
TransformBranching questBorrow the Story engine
Instead of a list, store the questions in a graph like the Choose-Your-Own-Adventure tutorial does: a right answer leads to one room and a wrong answer leads to a "training" room with an easier question. You've combined two archetypes into an adaptive quiz.
🛠️ Now Build It For Real
You've played a working Quiz Adventure and seen exactly how it's built. Next, build this same architecture yourself — twice, in two different tools.
🧩 Step 1 — Build It in Scratch
The "Build the Loop with Blocks" section above already shows the exact scripts — backdrop, sprites, Lists, variables (including a "for this sprite only" one), and all nine scripts, block by block, in Scratch's own category colors. Open a Scratch tab side-by-side and copy each script exactly; the game should come to life the same way it does here.
Open a blank Scratch project tab →Want more practice first? The Scratch Team publishes an official Community Quiz project you can open and remix directly.
Open the official Scratch "Community Quiz" project →