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.
Need to log into Minecraft Education, Canva, or any other app that asks you to sign in? Most school and app accounts use the same login: your username is [email protected] (add a number if your name needs one, e.g. firstname.lastname2), and your password is the same one you use to log into your school computer.
Every project has at least one thing to hand in. Log into connect.det.wa.edu.au with your firstname.lastname and computer password, then head to your class and open the Submission section. Handing in more than one file? Zip them together first - total size must stay under 50MB.
Design, write, code and ship your own text-based video game - from a blank passage to Arcade Day.
| 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 | ||||
Cellar and confirm. Every story needs its own name, so you cannot have two with the same nameStartHallway and Wait. Each [[link]] you write makes a passage[[Tiptoe past the guard->Escape]]You wake up in a cold, dark cellar. A wooden door is in front of you.
[[Open the door->Hallway]]
[[Stay very still->Wait]]
Start and make sure it is the start passage: select it, then click the Passage tab and choose Start Story Here-> must match the passage name exactly, spelling and capitals includedRain 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]]
[[Climb the stairs->Top of Stairs]]
[[Radio]]
Cellar and Top of Stairs, so you can spot them on your map.Start in the link to the name of your first passage if it is different''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]]
[[Look behind the painting->Secret Room]], then write the Secret Room passage. How will players find it?$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 failsfalse means the player does not have the key yet[[[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(set: $hasKey to true) is what gives the player the keyLamp Room, so write one$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$hasMap or $hasPassword(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]]
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]]
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]]
(set: $hasKey to true)
You slip the key into your pocket. It is cold and heavier than it looks.
[[Back to the cellar->Cellar]]
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]]
(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.(set: $health to 10). $health written inside your text shows the number to the player(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 passageTry again link goes to Start, which resets your health and items. This is the right place to link back to Start(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$health and $roll in the Debug View. Play the wave passage several times: does it always go the same way?(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]]
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]]
''GAME OVER''
The storm wins this time. Health left: $health
[[Try again->Start]]
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]]]
"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.(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).(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.# YOUR GAME TITLE and a one-line hook above the first choice. Keep the (set:) lines at the top''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]]
tw-story {
background: #050b08;
color: #39ff88;
font-family: monospace;
}
tw-link {
color: #ff8a3d;
}
tw-link:hover {
color: #ffd23f;
}
"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.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.
Then choose your genre // Session 01