Home
// Digital Technology - Year 9 & 10 //

TEXT ADVENTURE QUEST

Over the next 10 sessions you'll be a game developer: design a text-based video game in Twine, give the player choices, items, health and dice, playtest it with a partner and ship it as a single HTML game the whole class plays on Arcade Day.

🔀 Story Paths
🗝️ Items & Stats
🎲 Dice & Luck
🕹️ Arcade Day
The Developer's Kit
🧵
The Engine
twinery.org/2 - Twine, the free tool for making story games. It runs in the browser, so there is nothing to install and no account to make.
⚠ Twine keeps your story only in that browser on that laptop. Use the Save Routine below every lesson.
For teacher: Twine's default story format is Harlowe, and every code box on this page was played through in Harlowe 3.3.9. Students do not need to change any format setting.
💾
The Save Routine
Start of every lesson: Library tab, Import, pick your newest archive file, Import Selected Files.
End of every lesson: Library tab, Archive. The file lands in Downloads or Desktop, which follow you to any laptop.
📖
Code Reference
Harlowe manual - look up any command that starts with a bracket, like (set:) or (if:).
🎨
Design Studio
Canva - your Game Design Sheet, story map and cover art all get designed here.
🧠
AI Assistant
copilot.microsoft.com - ask it questions when you are stuck.
⚠ AI often writes code for other Twine formats like SugarCube or Chapbook. Tell it you are using Harlowe, and test everything it gives you.
🕹️
The Arcade
Your finished game is one HTML file made with Build, then Publish to File. On Arcade Day everyone's games are in the hand-in work folder on the S drive to play.
// Primary Objective

Design, write, code and ship your own text-based video game - from a blank passage to Arcade Day.

Design a hero, a goal, an obstacle and three endings before you write a word
Write a branching story with choices, merges, loops and secrets
Code items, health and dice rolls using variables and if statements
Ship one HTML game and test it on real players
// Marking Key & Rubric
Criteria Tutorial
(0-1)
Side Quest
(2-3)
Main Quest
(4)
Legendary
(5)
Score
Story & Writing Story is unfinished or hard to follow, with only a few passages Clear opening, middle and endings, choices make sense, some spelling mistakes Engaging second-person writing with a clear goal and setting, and three distinct endings Memorable world and voice, every choice matters and the writing keeps players curious to the last passage / 5
Branching & Structure Mostly one straight path, fewer than 8 passages, dead ends with no way out At least 12 passages with real choices, a merge or a loop, and at least 2 endings 15 or more passages, a planned story map, three endings and no accidental dead ends Paths cross and merge cleverly, hidden routes reward exploring and every ending feels earned / 5
Code & Logic Links only, with no variables or conditions Uses at least one variable and one if and else, such as an item that unlocks a path An item, a stat and a dice roll all work correctly, with variables set up in the Start passage Items, stats and luck work together to change the story, and the names and code are tidy / 5
Testing & Polish No playtest evidence and bugs left in the game Played through, fixed some bugs, a partner has tested it and some text styling used Bug log with fixes, every path tested, a custom look and cover art Plays cleanly from every start, partner feedback clearly improved it and the final file works perfectly on Arcade Day / 5
Total / 20
Scroll sideways to see every column
Quest Log
Week 1
01
🎮 Meet the Quest
▾
// SESSION OBJECTIVEGenre chosen and a one-page Game Design Sheet in Canva with your hero, goal, obstacle, setting and three endings.
  • Learn the brief: you are a game developer. Over 10 sessions you will design and build a text-based video game where the player reads a scene, picks a choice, and the story changes. You will ship it as one HTML file that plays in any browser
  • Learn what a text adventure is: there are no graphics, and the story is told in words. Colossal Cave Adventure and Zork were made in the 1970s and are among the very first. Modern choice-based games still use the same idea
  • Research text-based and choice-based games online. Search for "text adventure" and "interactive fiction", then write down 3 things you like about how the choices are shown
  • Read the six genres below and choose the one for your game. You can borrow ideas from the others, but pick one main genre
  • Decide the four pieces every game needs: your hero (who is the player?), the goal (what must they do?), the obstacle (what stops them?) and the setting (where is it?)
  • Plan three endings and write one sentence for each: a win, a lose and a twist nobody sees coming
  • In Canva, make a one-page Game Design Sheet with your game title, genre, hero, goal, obstacle, setting and your three endings
⚔️ Fantasy QuestDragons, curses and lost relics. Try a magic item that unlocks a hidden path.
🕵️ Mystery CaseA crime, five suspects, one truth. Try clues you collect that change what people tell you.
🚀 Sci-Fi EscapeA broken ship, a failing computer, a countdown. Try a fuel or air stat that drops as you choose.
🏕️ SurvivalStranded with almost nothing. Try health and hunger stats, and dice for risky moves.
👻 Spooky NightA haunted house that fights back. Try choices that hide or reveal doors. Keep it fun, not gory.
⏳ Time TravelChange the past and wreck the present. Try early choices that change the endings.
💡 HintYour game does not need to be huge. Fifteen great passages beat fifty rushed ones. Pick a goal you can explain in one sentence, like "escape the space station before the air runs out".
🔍 Google Image Search"text adventure game screenshot"
// ASK AI"I am making a [genre] text adventure game for school. Give me 5 game ideas, each with a hero, a goal and an obstacle."
02
💾 Set Up Twine
▾
// SESSION OBJECTIVEA practice story with at least 3 passages that plays in Test, and an archive file saved in Downloads or Desktop.
  • Go to twinery.org/2. Twine opens in your browser and there is no account to make. Twine keeps your story only inside this browser on this laptop, and you will use a different laptop in most lessons, so the save routine in the last step is not optional
  • Click the Story tab, then New. Name your practice story Cellar and confirm. Every story needs its own name, so you cannot have two with the same name
  • Double-click your first passage to edit it. Then click the Passage tab, then Rename, and rename it Start
  • Click Copy on the code box below, click inside the Start passage, press Ctrl+A then Ctrl+V to replace everything. After a short pause Twine creates two new passages for you, called Hallway and Wait. Each [[link]] you write makes a passage
  • Double-click Hallway and Wait and write two or three sentences in each. Give Hallway a link of your own that leads to a new passage, for example [[Tiptoe past the guard->Escape]]
  • Play your story: click the Build tab, then Test. Click through every choice and see where each one goes. Close the test when you are done
  • Learn the save routine. Go to the Library screen (the Library button at the top left of the story map), click the Library tab, then Archive. Your browser saves a dated file to your Downloads folder. If it asks where to save, pick Downloads or Desktop, because those two follow you to any laptop. Every lesson starts with Library, Import and ends with Library, Archive
// Start passage - paste this into your first passage
You wake up in a cold, dark cellar. A wooden door is in front of you.

[[Open the door->Hallway]]
[[Stay very still->Wait]]
💡 HintTwine's own guide says browser Twine saves your work to that browser on that computer, and clearing the browser's data loses it. Your archive file is your real copy. If you ever finish a lesson without archiving, your work is stuck on that laptop.
// ASK AI"In Twine using the Harlowe story format, what is a passage and what is a link? Explain with a short example."
Week 2
03
🧭 Write Your Opening
▾
// SESSION OBJECTIVEA new story with a Start passage, an opening scene with three choices, at least 4 passages written and a story map planned.
  • Start routine: open twinery.org/2. If your game is not in your Library, click the Library tab, then Import, choose your newest archive file from Downloads or Desktop, and click Import Selected Files. If your game is already there, skip the import
  • Make a new story for your real game: click the Story tab, then New, and use your game's title as the name. Your practice story can stay in the Library
  • Plan your story map in Canva with boxes and arrows: a Start box, three or four choices coming out of it, where those lead, and your three endings. Aim for about 15 passages in total. Each box is one passage
  • Write in second person and present tense, like "You open the door". Each passage should say what the player sees, what is wrong, and what they can do
  • Rename your first passage to Start and make sure it is the start passage: select it, then click the Passage tab and choose Start Story Here
  • Copy the opening passage below and rewrite it for your own game. Then copy the choice styles box to see the two ways to write a link. The name after -> must match the passage name exactly, spelling and capitals included
  • Write your opening and at least three more passages. Test from the beginning after each new passage so you catch problems early
  • End routine: go to the Library screen, click the Library tab, then Archive. Your browser saves a new dated file to Downloads (or Desktop). This file is your real copy
// Opening passage - a scene, a problem, then choices
Rain hammers the old lighthouse. The lamp at the top has gone dark, and a ship is heading straight for the rocks.

What do you do?

[[Climb the stairs->Top of Stairs]]
[[Search the cellar->Cellar]]
[[Call for help->Radio]]
// Two ways to write a choice
[[Climb the stairs->Top of Stairs]]
[[Radio]]
💡 HintWhen you rename a passage, Twine updates the links that point to it for you. Keep passage names short and different from each other, like Cellar and Top of Stairs, so you can spot them on your map.
// ASK AI"Here is the opening of my [genre] text adventure: [paste it]. Give me feedback on how to make the player want to keep reading. Do not rewrite it."
📤 Submit via ConnectYour story map, downloaded from Canva as an image
04
🌿 Branch & Merge
▾
// SESSION OBJECTIVEAt least 10 passages, three endings, at least one merge or loop, and a draft HTML file that opens and plays in the browser.
  • Start routine: open twinery.org/2. If your game is not in your Library, click the Library tab, then Import, choose your newest archive file from Downloads or Desktop, and click Import Selected Files. If your game is already there, skip the import
  • Write the middle of your game. Every passage needs at least one choice, except your endings. Grow your story to at least 10 passages by the end of the lesson
  • Add a merge: two different paths that lead into the same passage. Add a loop: a choice like Go back that returns the player to an earlier passage
  • Write your three endings: a win, a lose and a twist. Copy the ending box below and rewrite it for each one. Change Start in the link to the name of your first passage if it is different
  • Check for dead ends: click through your game and make sure every passage that is not an ending has a way forward
  • To test one passage without playing from the start, select it and click the Passage tab, then Test From Here
  • Publish a draft: click the Build tab, then Publish to File. Twine makes an HTML file that opens in a web browser. Find it in Downloads and double-click it to check your game plays
  • Swap slot (last 10 minutes): trade laptops with a partner. They click the Build tab, then Play, and try your game while you watch quietly and write down where they hesitate or get lost
  • End routine: go to the Library screen, click the Library tab, then Archive. Your browser saves a new dated file to Downloads (or Desktop). This file is your real copy
// An ending passage - paste it, then rewrite it for your game
''YOU WIN!''

The ship turns away from the rocks just in time. The whole town is safe, and the lamp glows again.

[[Play again->Start]]
💡 HintA story that only ever goes forward is a book. A story with merges and loops is a game. Merges also save you time: two paths can share one passage.
// ASK AI"I am writing a text adventure in Harlowe. Suggest 3 different ways my [genre] story could end: one win, one lose and one twist."
📤 Submit via ConnectYour draft game file (Build tab, Publish to File)
// LEVEL UPAdd a secret ending. On a passage that looks like a dead end, add one hidden choice such as [[Look behind the painting->Secret Room]], then write the Secret Room passage. How will players find it?
Week 3
05
🗝️ Items & Variables
▾
// SESSION OBJECTIVEOne item the player can collect and use to unlock a new path, working correctly when tested from the start.
  • Start routine: open twinery.org/2. If your game is not in your Library, click the Library tab, then Import, choose your newest archive file from Downloads or Desktop, and click Import Selected Files. If your game is already there, skip the import
  • Learn the idea: a variable is a named box that remembers something. $hasKey can remember whether the player picked up the key. (set:) puts something in the box, (if:) checks it, and (else:) runs when the check fails
  • Set your variables in the Start passage only. Copy the Start box below and read it: false means the player does not have the key yet
  • Copy the Ground Floor and Cellar boxes. Look at [[[Take the key->Take Key]]]: the outer brackets make a hook that (if:) can hide, and the inner double brackets are the link. The link only appears while $hasKey is false
  • Copy the Take Key box. Its (set: $hasKey to true) is what gives the player the key
  • Copy the Lamp Door box. The door only opens when the player has the key. It also needs a passage called Lamp Room, so write one
  • Play from the start with Build, then Test. Harlowe shows a Debug View panel that lists your variables. Watch $hasKey change from false to true when you take the key. Do not use Test From Here today, because your Start passage sets up the variables
  • Add one item and one locked path to your own game. Use your own names, like $hasMap or $hasPassword
  • End routine: go to the Library screen, click the Library tab, then Archive. Your browser saves a new dated file to Downloads (or Desktop). This file is your real copy
// Start passage - your variables live here
(set: $hasKey to false)
(set: $playerName to "Sam")

Rain hammers the old lighthouse, $playerName. The lamp above has gone dark, and a ship is heading for the rocks.

[[Step inside->Ground Floor]]
// Passage: Ground Floor - a hub the player comes back to
A cold, echoing hall. Stairs lead up to the lamp room and a hatch leads down to the cellar.

[[Climb the stairs->Lamp Door]]
[[Search the cellar->Cellar]]
// Passage: Cellar - an item the player can take once
Damp and dark. On a hook by the wall hangs a small brass key.

(if: $hasKey is false)[[[Take the key->Take Key]]]
(else:)[You already have the key.]

[[Back upstairs->Ground Floor]]
// Passage: Take Key - the passage that gives the item
(set: $hasKey to true)
You slip the key into your pocket. It is cold and heavier than it looks.

[[Back to the cellar->Cellar]]
// Passage: Lamp Door - the item opens a new path
The door to the lamp room is locked tight.

(if: $hasKey is true)[The brass key turns with a click. [[Enter the lamp room->Lamp Room]]]
(else:)[You need a key.]

[[Back down->Ground Floor]]
💡 HintNever write a link back to your Start passage from the middle of the game. Start sets your variables, so going back there resets them and the player loses their key. Only link to Start from an ending, for Play again.
// ASK AI"In Twine with the Harlowe story format, how do I make a link that only appears when a variable is true? Show me a short example using (if:)."
// LEVEL UPAdd a second item. In your Start passage add (set: $hasTorch to false). Make a passage that runs (set: $hasTorch to true). Then change the door check to (if: $hasKey is true and $hasTorch is true). The door now needs both items.
06
❤️ Stats & Dice
▾
// SESSION OBJECTIVEA health stat that changes, a Game Over ending that works, and a dice roll that decides what happens in at least one passage.
  • Start routine: open twinery.org/2. If your game is not in your Library, click the Library tab, then Import, choose your newest archive file from Downloads or Desktop, and click Import Selected Files. If your game is already there, skip the import
  • Learn the idea: variables can hold numbers too. Copy the new Start box, which adds (set: $health to 10). $health written inside your text shows the number to the player
  • Copy the Loose Board box. (set: $health to it - 3) means take 3 away from the number that is already there. (if: $health <= 0) checks whether health has run out and jumps to the Game Over passage
  • Copy the Game Over box. Its Try again link goes to Start, which resets your health and items. This is the right place to link back to Start
  • Learn about luck: (random: 1, 6) picks a whole number from 1 to 6, like rolling a die. Copy the Big Wave box. It rolls, shows the roll, and decides what happens
  • Play from the start with Test and watch $health and $roll in the Debug View. Play the wave passage several times: does it always go the same way?
  • Add a stat and a dice roll to your own game. A stat could be health, courage or fuel. A dice roll could be a fight, a lock to pick or a risky jump
  • Swap slot (last 10 minutes): trade laptops with a partner and try to lose their game on purpose. Tell them which choices were the most dangerous
  • End routine: go to the Library screen, click the Library tab, then Archive. Your browser saves a new dated file to Downloads (or Desktop). This file is your real copy
// Start passage - now with a health stat
(set: $hasKey to false)
(set: $health to 10)
(set: $playerName to "Sam")

Rain hammers the old lighthouse, $playerName. The lamp above has gone dark, and a ship is heading for the rocks.
Health: $health

[[Step inside->Ground Floor]]
// Passage: Loose Board - a trap that costs health
You step on a loose board. A rusty spike swings out of the wall!

(set: $health to it - 3)
You lose 3 health. Health left: $health

(if: $health <= 0)[(go-to: "Game Over")]
[[Keep going->Ground Floor]]
// Passage: Game Over - and a way to try again
''GAME OVER''

The storm wins this time. Health left: $health

[[Try again->Start]]
// Passage: Big Wave - a dice roll decides what happens
A huge wave crashes against the tower. Can you hold on?

(set: $roll to (random: 1, 6))
You roll a $roll.

(if: $roll >= 4)[You grip the rail and the wave passes. [[Climb higher->Lamp Door]]]
(else:)[The wave knocks you off your feet! (set: $health to it - 2)Health left: $health [[Get up->Ground Floor]]]
💡 HintThe passage names in quotes, like "Game Over", must match your passage exactly. Twine updates links when you rename a passage, but it does not update names you typed inside code, so check them if you rename something.
// ASK AI"In Twine with the Harlowe story format, how do I subtract from a number variable and check if it has reached zero? Give me a short example."
// LEVEL UPMake the wave harder: change (if: $roll >= 4) to (if: $roll >= 5). Which rolls win now, and is that fewer or more than before? Then add a health potion passage that runs (set: $health to it + 4).
Week 4
07
🛠️ Build Day
▾
// SESSION OBJECTIVEA complete playable game with at least 15 passages, three endings, an item, a stat and a dice roll, and draft 2 published.
  • Start routine: open twinery.org/2. If your game is not in your Library, click the Library tab, then Import, choose your newest archive file from Downloads or Desktop, and click Import Selected Files. If your game is already there, skip the import
  • Open your Game Design Sheet and check your game against it: hero, goal, obstacle, setting, three endings
  • Use this build checklist: at least 15 passages, three endings, one item that opens a path, one stat that changes, one dice roll, and every non-ending passage has a choice
  • Write the passages you still need. Keep each one short and give the player a reason to click
  • Make sure your lose ending can actually happen, and your win ending needs the item or the luck you built. A game where you cannot lose is not a game
  • Play your game from the start twice, taking different routes each time. Watch your variables in the Debug View
  • Read your writing slowly and fix typos and passages that are hard to follow. Check that every passage name in a link is spelled exactly the same as the passage
  • Publish draft 2: click the Build tab, then Publish to File, and double-click the file in Downloads to check it plays
  • End routine: go to the Library screen, click the Library tab, then Archive. Your browser saves a new dated file to Downloads (or Desktop). This file is your real copy
💡 HintIf you are stuck for ideas, look at your three endings and work backwards: what would the player have to do to reach each one? Those choices are passages you still need.
// ASK AI"Here is a passage from my text adventure: [paste it]. Check it for spelling and grammar mistakes only and list them. Do not rewrite it."
📤 Submit via ConnectYour draft 2 game file (Build tab, Publish to File)
// LEVEL UPAdd a score. In Start add (set: $score to 0). In a passage where the player does something clever, add (set: $score to it + 10). In your win ending write Final score: $score.
08
🎨 Style Your Game
▾
// SESSION OBJECTIVEText styles used in a few key passages, a stylesheet that makes your game look like yours, a title screen and a Credits passage.
  • Start routine: open twinery.org/2. If your game is not in your Library, click the Library tab, then Import, choose your newest archive file from Downloads or Desktop, and click Import Selected Files. If your game is already there, skip the import
  • Learn text styles: copy the styles box into a spare passage and click Test. Bold, italic, headings, colour and shaking text all come from small codes in your text
  • Add styles to your own game with care: use them for danger, magic or endings, not on every line. Text that shakes all the time is hard to read
  • Give your game a look. Click the Story tab, then Stylesheet, and paste in the stylesheet box below. Change the colours to suit your genre and press Test to see it. Keep the text easy to read: bright on dark, or dark on light
  • Turn your Start passage into a title screen: add a heading with # YOUR GAME TITLE and a one-line hook above the first choice. Keep the (set:) lines at the top
  • Add a Credits passage after your endings that says who made the game and which tools you used
  • Play your game from the start to check the styles and the stylesheet work on every passage
  • Swap slot (last 10 minutes): trade laptops with a partner and ask them which part of your game looks the best, and which part is hardest to read
  • End routine: go to the Library screen, click the Library tab, then Archive. Your browser saves a new dated file to Downloads (or Desktop). This file is your real copy
// Text styles - paste into any passage to try them
''Bold text'' and //italic text// look different.

# A big heading

(text-colour: red)[Danger! The floor is cracking.]

(text-style: "shudder")[The whole tower shakes...]

[[Keep going->Ground Floor]]
// Story Stylesheet - paste into the Stylesheet box
tw-story {
  background: #050b08;
  color: #39ff88;
  font-family: monospace;
}

tw-link {
  color: #ff8a3d;
}

tw-link:hover {
  color: #ffd23f;
}
💡 HintColours have to be readable. If your partner squints, change them. Very dark text on a very dark background is the most common style bug in student games.
// ASK AI"In Twine with the Harlowe story format, how do I make some text red, or make it shake? Give me one short example of each."
// LEVEL UPTry a different shaking style: change "shudder" to "rumble", then to "sway". Which fits your game best? Change the two hex colours in your stylesheet to a palette that suits your genre.
Week 5
09
🐞 Playtest & Debug
▾
// SESSION OBJECTIVEA bug log with fixes, every path tested, feedback from a partner acted on, cover art designed and a final game file published.
  • Start routine: open twinery.org/2. If your game is not in your Library, click the Library tab, then Import, choose your newest archive file from Downloads or Desktop, and click Import Selected Files. If your game is already there, skip the import
  • Give your game to a partner. They play the whole thing from the beginning while you stay silent and write down where they get stuck, confused or bored
  • Make a bug log with three columns: passage name, what went wrong, and how you fixed it. Add every bug, from your own testing and your partner's
  • Hunt for the usual bugs: a passage with no choices that is not an ending, a link that goes to the wrong place, a variable that resets because a link goes back to Start, a passage name spelled two different ways, and an item you can pick up twice
  • Fix every bug and test again from the start. Use the Debug View to check your variables
  • Two stars and a wish: your partner gives you two things they liked and one thing they wish was different. Act on the wish if you can
  • In Canva, design cover art for your game: the title, your genre, your name and a one-line hook. This is the poster for Arcade Day
  • Publish your final file: Build tab, then Publish to File. Double-click it in Downloads and play it once from the very start to check it works
  • End routine: go to the Library screen, click the Library tab, then Archive. Your browser saves a new dated file to Downloads (or Desktop). This file is your real copy
💡 HintThe best testers do the unexpected: pick the last choice first, click back and forth, and try to break things. Every bug you find now is one your classmates will not find on Arcade Day.
// ASK AI"Here is my bug log for my Twine text adventure: [paste it]. Which kinds of bugs are most common in choice-based games, and how could I check for them?"
📤 Submit via ConnectYour bug log and your cover art (from Canva)
10
🕹️ Arcade Day
▾
// SESSION OBJECTIVEFinal game submitted, at least 3 other games played with feedback, awards voted and reflection submitted.
  • Start routine: open twinery.org/2. If your game is not in your Library, click the Library tab, then Import, choose your newest archive file from Downloads or Desktop, and click Import Selected Files. If your game is already there, skip the import
  • Publish your final game: click the Build tab, then Publish to File. Double-click the file in Downloads and check it opens in your browser and plays from the start
  • Submit your game file through Connect (see the Submitting via Connect box above). Your teacher will collect every game into the hand-in work folder on the S drive so the whole class can play them
  • Arcade rules: this is a showcase. Play properly, make your choices honestly, and do not spoil endings for other players
  • Play at least 3 other games. Open them from the hand-in work folder on the S drive by double-clicking the file, and try to reach a different ending each time
  • After each game, write a two stars and a wish for the creator: two things that worked and one thing you wish was different
  • Vote for your class awards when your teacher says. Your teacher will tell you the categories
  • Complete your final reflection: which variable or idea was hardest to get right, what you would add with another five weeks, and how is writing a text game different from a game with graphics?
  • Submit your reflection through Connect
💡 HintThe best players read every passage instead of clicking quickly. If your game has a secret ending, do not say where it is: let people find it.
// ASK AI"Help me write a short reflection about what I learned building a text adventure game in Twine over five weeks."
📤 Submit via ConnectYour final game file (Publish to File), your cover art and your final reflection
🕹️

Arcade Day Awaits

After 10 sessions, from your first passage to your final Publish to File, the classroom becomes an arcade. Every game was written, coded and tested by the person who made it, and now everyone gets to play.

🕹️ Play 3+ games
🗳️ Class-voted awards
💬 Two stars, a wish

Then choose your genre // Session 01

SYSTEM ONLINE // YEAR 9-10 DIGITAL TECHNOLOGY TEXT ADVENTURE QUEST // 10 SESSIONS