Code a Story or Quiz

A story or quiz becomes a CODE PROJECT when the reader gets to make choices. Every choice opens a branch, and every branch leads to an outcome. Your job as the coder is to plan those branches before you build them — so no path leads to a dead end.

How a Branching Project Works

A branching project follows a simple loop: show something, ask the player to choose, then jump to whatever happens next. That happens-next part is called a TRIGGER. A trigger is the line of code that fires when a choice or event happens.

1. Show — display a screen, a question, or a story line.
2. Choose — let the player click a button, type an answer, or pick a path.
3. Trigger — the chosen action fires the matching code (jump, score, hint, ending).
4. Repeat or end — loop to the next screen, or stop the game with a result.

Story Branches vs Quiz Logic

Stories use branches to give the reader choice — pick A, pick B, see different endings. Quizzes use logic to score answers — right answers add to the score, wrong answers show a hint. Both ideas are coded the same way: an IF-THEN rule that listens for the player and triggers a response.

• Branch — a path the player can take. Each branch leads somewhere.
• Choice — the button or input the player picks to take a branch.
• Outcome — what happens at the end of a branch (a scene, a score, a screen).
• Score — a number that tracks correct answers or progress.
• Ending — the final screen the player sees (win, lose, retry, kind ending).

Plan Before You Code

Sketch the branches on paper first. Write the topic, the opening line, the two choices, what each one leads to, and the ending. If you can read the plan out loud and it makes sense, the code will too. If the plan has a path with no outcome, fix it BEFORE you open the editor.