Home
// Digital Technology - Year 8 //

RETRO ARCADE BUILDERS

Over the next 10 stages you will design, draw and code your own retro arcade game in MakeCode Arcade, flash it onto a real GameGo handheld, playtest it until it feels great, then put it in front of the whole class on Arcade Night. You are the designer. You are the pixel artist. You are the coder.

🎨 Pixel Art
🧩 Block Code
📟 GameGo Ready
🏆 Arcade Night
Your Arcade Kit
🕹️
Game Engine
arcade.makecode.com - Microsoft MakeCode Arcade runs in your browser, nothing to install. Sign in with your school Microsoft account (card below) so your games also save to the cloud, then click New Project.
📟
The Console
The TinkerGen GameGo: a pocket handheld with a 1.8 inch 160 x 128 colour screen, direction buttons, A and B, a Menu button, a Reset button and a rechargeable battery. 16 GameGos live in the class dock and are shared: grab one, use it, put it back.
💾
Save Routine
End of every stage: type your game's name in the Name and Save box at the bottom of the editor and click the save icon. A .png file lands in Downloads with your whole game inside it. Start of every stage: Home, Import, Import File, choose that .png.
🎨
Art Studio
Click any grey box in a sprite or tilemap block to open MakeCode's own pixel editor. The Gallery tab has ready-made art to start from. In Stage 09 you'll make your arcade card in Canva.
🔌
Flash Station
To put your game on a GameGo: Download in MakeCode, choose TinkerGen GameGo, then drag the .uf2 file from Downloads onto the GameGo's drive. Full steps are in Stage 04.
⚠ For teacher: the GameGos charge over their micro-USB cable. Charge the dock before Stage 04 and before Arcade Night.
🧠
AI Co-Op
copilot.microsoft.com - ask it "How do I do X in MakeCode Arcade blocks?" when you're stuck, or to help you name your game.
⚠ AI often mixes up MakeCode Arcade with micro:bit MakeCode or Scratch. Check every block name against the real Toolbox!
// Primary Objective

Build a complete retro arcade game - a hero, a world, enemies, a way to win and a way to lose - that runs on a real handheld console and is fun enough for the class to queue up for on Arcade Night.

Design a game in one of four genres, with your own pixel art for the hero, the enemies and the world
Program movement, collisions, score, lives, spawners and win and lose rules with MakeCode Arcade blocks
Flash your game onto a GameGo and test how it really feels on hardware buttons
Playtest with classmates, log the bugs, fix them, then show it off on Arcade Night
// Marking Key & Rubric
Criteria Insert Coin
(0-1)
Player One
(2-3)
High Score
(4)
Hall of Fame
(5)
Score
Game Design Genre or goal unclear, game cannot be finished Clear genre, a hero, something to collect or dodge, and an end Clear win and lose rules that match the design sheet, fair difficulty A game people want to replay: difficulty ramps up and every rule feels deliberate / 5
Programming Hero moves only with heavy teacher support Movement, overlaps and score work using code you built Spawners, lives and win and lose events all work with few bugs Clean, well-organised blocks using events, timers, random and conditions confidently / 5
Art & Polish Default or missing art, no feedback when things happen Own or edited sprites, a world that fits the genre Consistent pixel art plus sounds and effects on key events Title screen, juice and art that make the game feel finished / 5
Testing & Showcase No bug log, game not ready for Arcade Night Bug log started, game flashed and played on a GameGo Top bugs fixed using playtest evidence, station ready on the night Fixes clearly backed by playtests, helpful host who gives and takes feedback well / 5
Total / 20
Scroll sideways to see every column
Stage Select
Week 1
01
🕹️ Press Start
▾
// STAGE OBJECTIVEGenre chosen and design sheet started. A player sprite moving on screen, saved as a .png in your Downloads.
  • Open arcade.makecode.com and sign in (Sign In, top right, then Continue with Microsoft). Click New Project and name it after yourself for now (e.g. jess-arcade)
  • Tour the editor: the Game Window on the left (it has its own joystick and A and B buttons, and your arrow keys work too), the Toolbox of block drawers in the middle, and the Workspace on the right where you build
  • Pick your genre. Every genre uses the same core skills, so pick the one you'd most like to play:
PlatformerRun and jump across a side-on world with gravity, platforms and a goal at the end of the level.
Top-Down ShooterFly a ship around the screen, fire at waves of enemies and survive. Score decides the winner.
Maze ChaseSteer through a walled maze collecting treats while enemies hunt you down. Clear the maze to win.
Endless RunnerYour hero stays on the ground and jumps over obstacles that rush in. Survive the clock to win.
  • In your book, start a design sheet: game name, genre, your hero, how you win, how you lose, and three things to collect or dodge
  • Build your player with the block layout below. Click the grey box to draw your hero, or open the Gallery tab and pick one, then click Done
  • Test it in the Game Window. Your hero should move with the arrow keys
  • Save: type your game's name in the Name and Save box at the bottom of the editor and click the save icon. Check the .png is in your Downloads
// Block layout to rebuild in MakeCode Arcade
on start
    set mySprite to sprite [ ] of kind Player   ← click [ ] to draw
    move mySprite with buttons
    set mySprite stay in screen <ON>            ← shooter and maze only
💡 HintYou probably won't get the same laptop next stage. Signed in, your game saves to the cloud and waits in My Projects on any laptop. Still save your .png at the end of every stage: it's your backup and the file you submit.
// ASK AI"Give me 5 fun ideas for a simple retro platformer game a Year 8 student could build in MakeCode Arcade, each with a hero, a goal and a danger."
02
🎨 Pixel Art Lab
▾
// STAGE OBJECTIVEHero, enemy and collectible sprites drawn. Platformer, maze and runner: a tilemap world with walls. Shooter: a background chosen.
  • Signed in, open your game from My Projects. If it is not there, import your .png from Stage 01 (Home, Import, Import File)
  • Pixel art rules: a dark outline, 3 or 4 colours, and a shape you can still recognise when it's tiny. Draw your hero properly, then an enemy and a collectible (park them in spare sprite blocks for now - you'll give them jobs in Stage 03)
  • Platformer, maze and runner: from the Scene drawer drag set tilemap to into on start and click its grey box. Set the map size in the bottom left corner of the tilemap editor (a runner fits on 10 x 8, a platformer can be much wider), draw your ground, platforms or maze, then choose the Wall tool and draw over every tile that should block the hero
  • Platformer and runner: add gravity and a jump with the block layout below. Platformers also add camera follow sprite so the screen scrolls with the hero
  • Shooter: no tilemap needed. Pick a dark colour with set background color to, or search the Toolbox for "screen effect" and use start screen star field effect for moving stars
  • Save your .png
// Block layout - platformer and runner world
on start
    set tilemap to [ ]                          ← draw ground, then the Wall tool over it
    set mySprite to sprite [ ] of kind Player
    place mySprite on top of tilemap col 1 row 5
    camera follow sprite mySprite               ← platformer only
    move mySprite with buttons + vx 100 vy 0    ← click + : left and right only
    set mySprite ay (acceleration y) to 400     ← gravity

on A button pressed
    if is mySprite hitting wall bottom then
        set mySprite vy (velocity y) to -200    ← jump
💡 HintIf your hero falls straight through the floor, your ground is only a picture. Tiles don't block anything until you draw over them with the Wall tool in the tilemap editor.
🔍 Google Image Search"retro platformer tileset pixel art"
// ASK AI"What are three tips for drawing a small pixel art character that still looks good at 16 by 16 pixels?"
// LEVEL UPMake your hero walk. From the Animation drawer add animate mySprite frames [ ] interval (ms) 200 loop <ON> to on start, click the frames box and draw 2 to 4 frames that change only the legs. Too fast or too slow? Change the 200.
Week 2
03
💥 Collide & Score
▾
// STAGE OBJECTIVEFirst playable loop: the hero collects for points and loses a life when hit. Project .png submitted.
  • Every sprite has a kind: Player, Food, Enemy or Projectile. Overlap events check kinds, so the kind is how your game knows what just touched what
  • Give your collectible the kind Food and your enemy the kind Enemy (click the kind in the sprite block). Rename each variable from its drop-down so your blocks read clearly, e.g. myFood
  • Maze and platformer: draw one special tile where treats should appear, then use place mySprite on top of random [tile] to drop a treat on one of them
  • From the Sprites drawer drag out on sprite of kind Player overlaps otherSprite of kind and build the two events below. Inside the event, otherSprite means the exact sprite you touched
  • Add set life to 3 to on start. The hearts and score appear on the screen by themselves
  • Playtest: does the score go up by exactly 1 per treat? Do you lose exactly 1 life per hit?
  • Save your .png and submit it
// Block layout - collect and get hit
on start
    set life to 3
    set myFood to sprite [ ] of kind Food
    set myFood position to x 120 y 60

on sprite of kind Player overlaps otherSprite of kind Food
    change score by 1
    destroy otherSprite + with [disintegrate] effect for 500 ms

on sprite of kind Player overlaps otherSprite of kind Enemy
    change life by -1
    destroy otherSprite
💡 HintScore jumping up by 5 or 10 from one touch? The overlap keeps firing for as long as the two sprites stay on top of each other. Destroy (or move) the sprite you touched inside the event and it fires once.
// ASK AI"In MakeCode Arcade blocks, what is the difference between mySprite and otherSprite inside an overlaps event?"
📤 Submit via ConnectYour game .png from Downloads (first playable version)
// LEVEL UPChase mode: in the Food overlap, swap the destroy block for set otherSprite position to x (pick random 10 to 150) y (pick random 10 to 110) and add start countdown 3 (s). Every treat now jumps somewhere new and you have 3 seconds to reach it, or it's game over.
04
📟 First Flash
▾
// STAGE OBJECTIVEYour game running on a real GameGo. Three playtest notes written from playing it on the hardware.
  • Import your .png, check the game still plays in the Game Window, then save first. Flashing never touches your .png
  • The class has 16 GameGos. Collect one from the dock when it's your turn, flash and test, then return it to the dock for the next person
  • Follow the Flash Station steps below. The first time, MakeCode asks which hardware you have: choose TinkerGen GameGo
🔌 Flash Station Steps
1. DownloadClick Download (bottom left of the editor) and choose TinkerGen GameGo. A .uf2 file saves to your Downloads. If MakeCode asks you to pair or connect a device, close that box
2. Plug inConnect the GameGo to the laptop with its micro-USB cable and press its power button. It shows a drive screen and appears as a drive in File Explorer
3. CopyDrag the .uf2 file from Downloads onto the GameGo drive. Wait - the game starts on the GameGo by itself
4. PlayUnplug and play. Your new game replaces whatever was on the GameGo before
  • Play your game on the GameGo for 5 minutes. In your book write three playtest notes: what feels different on real buttons, what is too easy or too hard, and one thing that surprised you
  • While you wait for a GameGo, keep building in the Game Window: add more treats, enemies or map
💡 TroubleshootingNo drive screen? Press Reset (bottom of the front, to the right of the Menu button). A second flash won't take? Switch the GameGo off and on, refresh the MakeCode page, then try again.
// ASK AI"My MakeCode Arcade game feels too fast on a handheld console. Which numbers in my blocks should I change to slow the hero down?"
// LEVEL UPTune the feel: click the + on move mySprite with buttons and change vx and vy (platformers can also change ay and the jump vy). Flash again and compare with your first notes. Write down the numbers that felt best.
Week 3
05
👾 Enemies & Spawns
▾
// STAGE OBJECTIVEEnemies that keep coming: a timed spawner (shooter and runner) or chasing enemies (maze and platformer). Shooters can fire back.
  • on game update every 1000 ms (Game drawer) runs its blocks again and again on a timer. 1000 ms is 1 second, so 500 ms is twice a second
  • pick random (Math drawer) gives a different number every time, so enemies don't all arrive in the same spot
  • Shooter: build the spawner below. Your ship fires with A, enemies fly in from the right at a random height, and auto destroy removes enemies that fly off screen
  • Runner: use the same timer, but inside it make set projectile to projectile [ ] from side with vx -90 vy 0 and place projectile on top of tilemap col 9 row 5, so obstacles roll in along your ground
  • Maze and platformer: create one or two enemies in on start and use the chaser layout below
  • Playtest, adjust the timer and speeds until it's tough but fair, then save your .png
// Block layout - shooter spawner
on A button pressed
    set projectile to projectile [ ] from mySprite with vx 200 vy 0

on game update every 1000 ms
    set myEnemy to sprite [ ] of kind Enemy
    set myEnemy velocity to vx -100 vy 0
    set myEnemy position to x 160 y (pick random 5 to 115)
    set myEnemy auto destroy <ON>

on sprite of kind Projectile overlaps otherSprite of kind Enemy
    destroy otherSprite + with [fire] effect for 500 ms
    change score by 1
// Block layout - maze and platformer chaser
on start
    set myEnemy to sprite [ ] of kind Enemy
    place myEnemy on top of random [ ]          ← a tile far from the hero
    set myEnemy follow mySprite + with speed 30
💡 HintA chaser at speed 30 is slow, 80 is scary. Start slow, playtest, then speed it up. In a maze a chaser can get stuck on walls - that's normal, and it gives the player a chance.
// ASK AI"In MakeCode Arcade, what does 'on game update every 1000 ms' do, and how is it different from 'forever'?"
// LEVEL UPMake every enemy different: replace -100 in the velocity block with pick random -120 to -60 (shooter), or replace -90 in the projectile block with pick random -110 to -70 (runner). Playtest: is random speed harder or just unfair?
06
🏁 Win & Lose
▾
// STAGE OBJECTIVEA clear way to win and a clear way to lose. Every run ends on a WIN or GAME OVER screen. Project .png submitted.
  • Losing is already built in: when life reaches 0, MakeCode ends the game with GAME OVER by itself. The same happens when a countdown runs out, unless you add an on countdown end block
  • Now add a way to win that matches your design sheet, using the layout below:
    Platformer and maze: draw a goal tile (a flag, a door, an exit) and use the tile overlap event
    Shooter: reach a target score with on score 20
    Runner: survive the clock with start countdown plus on countdown end
  • The game over block has a WIN/LOSE switch: click it to choose
  • Play your game all the way to a win and all the way to a loss. Both screens must appear
  • Save your .png and submit it
// Block layout - pick the win rule for your genre
on sprite of kind Player overlaps [ ] at location   ← platformer, maze: your goal tile
    game over <WIN>

on score 20                                          ← shooter
    game over <WIN>

on start
    start countdown 60 (s)                           ← runner: survive 60 seconds
on countdown end
    game over <WIN>
💡 HintTest the win yourself before anyone else plays. If you can't reach the goal tile or the target score in a fair attempt, nobody else will either. Make it winnable first, then make it hard.
// ASK AI"What makes a good win condition in a short arcade game? Give me examples from classic arcade games."
📤 Submit via ConnectYour game .png with a working win and lose
// LEVEL UPTake over the loss: add on life zero (Info drawer). Inside it put splash "So close!", then game over <LOSE>. Once this block exists, MakeCode only ends the game when your code says so - leave out the game over block and see what happens.
Week 4
07
✨ Juice It
▾
// STAGE OBJECTIVEAt least four pieces of juice added - a sound, a sprite effect, a camera shake and a screen effect - each tied to an event in your game.
  • Juice is the extra feedback that makes a game feel alive: a sound when you grab a coin, a shake when you get hit, sparks when an enemy pops. The rules don't change, the feel does
  • Find the moments that matter in your game: collecting, getting hit, defeating an enemy, winning
  • Add the juice blocks below to your existing overlap events. Sounds come from the Music drawer, effects and camera shake are in Sprites and Scene, or search the Toolbox
  • Shooter and runner: add start screen star field effect (or another screen effect) to on start for a moving background
  • Flash it to a GameGo and check the sounds and shake on the hardware, then save your .png
// Block layout - juice added to your events
on sprite of kind Player overlaps otherSprite of kind Food
    change score by 1
    play sound [ba ding] [in background]
    destroy otherSprite + with [disintegrate] effect for 500 ms

on sprite of kind Player overlaps otherSprite of kind Enemy
    change life by -1
    camera shake by 4 pixels for 500 ms
    mySprite start [fire] effect + for 500 ms
    play sound [power down] [in background]
    destroy otherSprite
💡 HintMore juice isn't always better. If the screen shakes every second, players stop noticing it - and some feel sick. Save the big effects for the big moments.
// ASK AI"What is 'game juice' and what are five simple examples I could add to a retro arcade game?"
// LEVEL UPGive your hero a voice: in the Enemy overlap add mySprite say "Ouch!" + for 500 ms. Then add use effect [ ] for <WIN> (Game drawer) to on start and pick a new win effect from its drop-down. Playtest: which piece of juice does your tester notice first?
08
🐞 Playtest & Patch
▾
// STAGE OBJECTIVETwo classmates have played your game on a GameGo. Bug log written, top 3 bugs fixed and a new .png saved.
  • Flash your latest game to a GameGo and swap with a classmate
  • Silent playtest: the tester plays, you watch and say nothing. No hints, no "you're meant to...". Where they get stuck is your data
  • Write a bug log in your book or a Word document with four columns: What happened, Where, How bad (1 to 3), Fixed?. Count "too hard", "boring" and "didn't know what to do" as bugs too
  • Repeat with a second tester
  • Fix the worst bugs first. Change one thing, test it, then move to the next - if you change five things at once you won't know which one helped
  • Save your .png
💡 HintNever argue with a tester. If they say it's confusing, it's confusing - even if you think it's obvious. They're showing you exactly what a stranger will do on Arcade Night.
// ASK AI"My testers say my MakeCode Arcade game is too hard in the first 10 seconds. Give me three ways to make the start easier without making the whole game easy."
// LEVEL UPAdd a second level: on score 10, use set tilemap to [ ] with a new, harder map, then place mySprite on top of tilemap col 1 row 5 so the hero starts fresh. Shooter: add a second on game update every 3000 ms spawner that sends a bigger, slower enemy, and use on score 10 to start screen [blizzard] effect so players know things just got harder. Playtest both levels.
Week 5
09
🖼️ Cabinet Art
▾
// STAGE OBJECTIVETitle screen, how-to-play text and custom win and lose messages added. Arcade card made in Canva. Final game .png submitted and flashed.
  • Real arcade cabinets had art on the front so you knew what you were about to play. Your game gets the same: a title screen and instructions
  • Add the block layout below to the very top of on start. splash pauses the game until the player presses A, and show long text shows a box they scroll with A
  • Write your own win and lose messages (keep them short, the screen is only 160 pixels wide)
  • Make an arcade card in Canva for your station on Arcade Night: game name, your name, genre, the controls (which button does what) and how to win. Download it as a PNG or PDF
  • Final check: play from the title screen to a win, and from the title screen to a loss. Flash it to a GameGo one last time
  • Save your final .png, zip it with your arcade card and submit
// Block layout - top of on start
on start
    splash "PIXEL PANIC" + "Press A to start"
    show long text "Arrows move. A jumps. Grab 20 coins to win!" [bottom]
    use message "CITY SAVED!" for <WIN>
    use message "GAME OVER!" for <LOSE>
    ...your existing blocks...
💡 HintWrite instructions for someone who has never seen your game and won't read much. One line: what to press and what to do. If a tester asks "what do I do?", your instructions need work.
// ASK AI"Suggest 5 catchy retro arcade titles for a game where a robot collects batteries in a maze. Keep each under 12 letters."
📤 Submit via ConnectZip of your final game .png and your arcade card
10
🏆 Arcade Night
▾
// STAGE OBJECTIVEYour game played by the class at its station. Awards voted. Final reflection submitted.
  • Set up your station: your final game flashed onto a GameGo, your arcade card next to it. If every GameGo is taken, run your game full screen in the Game Window on your laptop
  • Two rounds: in round 1 half the class hosts and half plays, in round 2 you swap. Hosts stay quiet and watch, just like the silent playtest
  • Play at least 6 games. For each one, note one thing you loved and one thing you'd change
  • Awards, voted by the class: Best Overall, Most Fun, Best Pixel Art and Best Juice
  • Write your final reflection: what you're proudest of, the hardest bug you fixed, and what you'd add with one more week. Submit it through Connect
  • Return every GameGo to the dock
💡 HintWatch the first 10 seconds of every player at your station. That's where most players decide if they like a game - and it's the best feedback you'll get all term.
// ASK AI"Help me write a short reflection about building my first video game: what I'm proud of, a bug I fixed and what I'd add next."
📤 Submit via ConnectFinal reflection
🏆

Arcade Night Awaits

After 10 stages your game goes on show. Every station gets played, every builder hosts, and the class votes for the games that earn a place in the Hall of Fame.

🕹️ Every game played
🗳️ Class-voted awards
📟 Real handheld play

Click New Project, pick your genre // Stage 01

SYSTEM ONLINE // YEAR 8 DIGITAL TECHNOLOGY RETRO ARCADE BUILDERS // 10 STAGES