Story Path
One scene at a time, the class decides what happens next — and the story forks to a different ending each time.
? How to play — 30 seconds
- Write your scenes. Each scene sets a situation and offers choices; every choice leads on to another scene.
- To create an ending, add a scene with no choices of its own — Story Path marks it 🏁 automatically.
- Give each scene a mood so the screen shifts with the story, and pick where the story begins.
- In class, read the scene aloud and let students vote on the choice (or just tap the one they agree on). Reach an ending, then replay a different path.
When to use this, and what to say afterwards
Best moment: When consequences unfold over time and you want the class to feel a decision rather than discuss it abstractly.
What it looks like in different courses
- CCGLA government meets a rising flood risk, decision by decision.
- CCCHA family navigates a decade of rapid urbanisation.
- CCAIA company decides how far to deploy an imperfect model.
Now ask them — the part that turns the game into learning
- At which fork was the class most divided?
- Replay from that fork and take the other path. What changes, and what does not?
- What did this story make feel inevitable that real life would not have?
Do not use this when: Avoid presenting an authored branch as history. Say plainly that you wrote the consequences, or students will take your scene tree for evidence.
✨ Make these with AI — no typing, paste them straight in
- Copy the prompt below.
- Open any AI chat you already use, upload your slides / reading / handout, and paste the prompt.
- Copy the AI's whole reply and paste it in the box underneath. Your builder fills itself — then edit anything you like.
You are helping a university tutor turn course material into a classroom game. I am uploading my course material (slides, reading or handout). Use ONLY that material and write 8 scenes in a branching decision story set in the world of the material, where each scene ends in a choice that leads to another scene. Return plain text, ONE ITEM PER LINE, in exactly this format: Scene id | Title | What the class sees | Mood | Choice text > id ; Choice text > id Two correct example lines: n1 | The ministry, 6 a.m. | The report lands on your desk: the river is rising and the flood wall will not hold both districts. | tense | Evacuate the old town > n2 ; Hold the wall and warn nobody yet > n3 n2 | Buses at dawn | Four thousand people move in three hours. The wall holds — and the town asks why it was moved for nothing. | calm | Rules: - Separate the fields with the vertical bar | and nothing else. - One item per line. No numbering, no bullets, no headings, no commentary. - Never use a line break inside an item. - Keep every field short enough to read from the back of a lecture room. - Base every item on my uploaded material, not on general knowledge. - Give the first scene the id n1 — it is where the class starts. - Use short ids: n1, n2, n3 … Every id after > must be a scene you also wrote. - A scene with no choices after the mood is an ending — write at least two different endings. - Mood must be one of: dawn, calm, tense, danger, mystery, triumph, defeat. - Separate the two choices with a semicolon, and put > between the choice text and the scene it leads to. - Put the whole answer in ONE code block so I can copy it in one click.
⚠ Before you upload anything, stop and decide what is safe to send.Never upload student IDs, student numbers, grades, marks, results, or anything that could identify a student — and never paste them into the boxes below either. Remember that what you upload may not be yours to give away: publishers' readings, textbook chapters, exam papers, colleagues' slides and material you licensed rather than wrote are usually someone else's property. Many free AI tiers keep what you send and may train on it, so read that tool's own terms first. Protect yourself — when in doubt, upload your own summary or notes instead of the original file.
Build your story
Scene 1