- Learnt27 min · instructions, an attract screen, credits
- Basic25 min · finish the cabinet
- Challenge 1–327 min · clear instructions, the arcade test, the full check
- Extrabonus · a fourth game, all your own
Review — where we got to 5 min
Three games, three records, and a name on each one. It just needs a final shine.
- Every screen is a broadcast. Every sprite answers all of them.
- Records live in variables. The flag never changes them. The name of who set each one sits beside it.
Quick-fire
You come back to your project in a month. You have forgotten all of it. What do you need first?
Reveal the answer
You need to know the controls. Until you know which key does what, you cannot see what you built.
Today’s Topic 3 min
- An instructions screen. One line per game, in plain words.
- An attract screen. This is what a machine does when no one is using it.
- Credits. They say where the art and sounds came from.
- Testing with people who have never seen it.
Learning outcome
By the end of this lesson you will be able to:
- Write instructions that a new player could follow. That includes you, next week.
- Make a menu that is fun to look at while it waits.
- Come back to your project fresh. Watch it work, even though you remember nothing.
Learnt — instructions, attract, credits 27 min
1 · How to play
Write one line per game. Use the words a player needs. Do not talk about your code.
- Add a fourth button to the menu. Name it HOW TO PLAY.
- Give it its own message:
howto. - Add a sprite for the page, on a plain backdrop.
- Write one line for each game. Say what to press, and what you are trying to do.
- Show the home button. Hide everything else.
when I receive [howto v]
switch backdrop to [Chalkboard v]
show
say [Jump Dash: press SPACE to hop over rocks. Do not hop into bats.] for (4) seconds
say [Bounce: arrow keys move the paddle. Keep the ball off the floor.] for (4) seconds
say [Star Tap: click the star as many times as you can in 20 seconds.] for (4) seconds
How to use this: Click the green flag and read the three lines. Then click the home button (bottom right) as a player would.
2 · What the machine does while it waits
A real arcade cabinet never sits still. Something on your menu should move. It should say what the best score is.
- Pick one sprite on the menu to be the moving one.
- Find its
when I receive [menu v]. Add aforeverafter the show. - Inside it, glide somewhere and back. Or grow and shrink.
- Every few times round, say the best score of the day. Use
join [Best today: ] (best). - Make sure the menu stack stops the loop on every other screen.
when I receive [menu v]
show
forever
glide (2) secs to x: (-40) y: (100)
glide (2) secs to x: (40) y: (130)
say (join [Best today: ] (join (dash best) (join [ by ] (dash holder)))) for (2) seconds
end
How to use this: Click the green flag and leave it alone for ten seconds. A menu nobody is using should still be worth glancing at.
3 · Whose arcade this is
The credits screen takes five minutes. It is the only place your name appears. It also says where everything else came from.
- Add a credits screen, the same way you added how to play.
- Add your name, and what you made.
- Say where the sprites and sounds came from. Most came from the Scratch library.
- Name the people who tested it for you.
- Do you have an account? Then put the same words in the notes on the sharing page.
How to use this: Click the green flag for the menu, then click a game button. Space hops in Jump Dash; ← and → slide the paddle in Bounce; click the star in Star Tap. The home button (top right) always goes back.
Basic — finish the cabinet 25 min
Two new screens, one moving menu, and then lots of clicking.
Step 1 — how to play
- Add the button, the message and the page.
- Write one line per game.
- Read them aloud to yourself, slowly. Do you have to explain a word as you read? Take that word out.
Step 2 — credits
- Add the screen.
- Add your name, the library, and your testers.
Step 3 — the attract screen
- Give one menu sprite something to do.
- Put the day’s best score in it.
- Check it stops as soon as you leave the menu.
Step 4 — the sweep
- Visit all six screens.
- Come home from each of them.
- Play each game to its ending.
Step 5 — save it properly
- Give the project a real name, not Untitled.
- Save it to your computer as an
.sb3file. Or save it to your account, if you have one. - Open the saved copy and check it still works.
The menu sprite keeps gliding during a game.
Nothing stopped its forever loop. Its other screen stacks need stop [other scripts in sprite v].
The how-to-play text goes by too fast.
Three seconds is too short for a nine-year-old reader. Four or five is fairer.
The credits screen has no way back.
The home button’s stack for that screen says hide. Or it is not there at all.
The saved file does not work when reopened.
Something was still running when you saved it. Press the flag. Go to the menu. Save from there.
Instructions people read
Most instructions are too long, so people skip them. Make yours short.
- One line per game, under fifteen words each.
- The key or the click comes first.
- No word that a new player would have to ask about.
The arcade test
Test it three times, with a gap each time. Act like a person who has never seen it. Keep every script window shut.
- Round 1: play two of your games all the way through. Write down every time you stop to think.
- Fix the worst thing on your list.
- Round 2: leave it for ten minutes. Come back and play the other games.
- Round 3: the next day, play all of it fresh. Go in any order.
- Three rounds, with a real gap between them.
- You play every game at least twice in the three rounds.
- A written list of every time you stopped to think.
- One change made because of the list.
Teacher note — the gap is the tester
Nobody waits for a partner here. What finds the bugs is the gap: a pupil who tests straight after building is testing their own memory, and their memory always knows what to press.
Where a room happens to have several pupils at this stage, rotating projects works beautifully as well — everybody plays the project to their left for four minutes, then moves. Treat that as a bonus, never as the requirement.
The full sweep
Write down each screen, each ending and each button in your project. Then visit all of them. Tick each one as you go.
- A written list, made before you start clicking.
- You visit every item on it.
- You write down anything broken. Then you fix it or make a note.
- You hand in the list with the project.
Teacher note — this is a test plan, and it is worth naming as one
A list written before testing, then ticked off, is exactly what professional testing looks like. Pupils who have done this six times across Level 1 have a habit worth more than any single block.
A fourth game, all your own
Add a fourth button. Behind it, put a game no one taught you. You have one hour. Start from nothing, and use only what you know.
How to use this: Click the green flag, then click the right-hand button to open the fourth game. Click the crystal as often as you can in twenty seconds.
- A game that is not one of the three, and not a copy of one.
- It has a start, a way to lose or to finish, and a score.
- It keeps all the cabinet rules. It has its own names, its menu stack and the home button.
- Its record goes on the scoreboard beside the others.
Teacher notes — what to suggest when a pupil is stuck for an idea
The reliable prompt is to take one block and build a game round it: pick random (1) to (10) gives a guessing game, timer gives a reaction test, next costume gives a matching game.
This is the real assessment of Level 1 and it is worth saying so. Everything needed has been taught; what is left is deciding what to make, which is the part no lesson can hand over.
Going further: Level 2 — clones that carry their own numbers, the mouse as a controller, My Blocks, and games with shops in them.
Summary 4 min
That is Level 1. Forty-eight classes and nine finished projects. And one cabinet with all of them in it.
- Instructions say the key first, in the player’s words.
- A machine no one is using should still do something.
- Credits take five minutes. They say where everything came from.
- A project is finished when a new player can use it without you there.
What Level 1 covered
- Moving, turning, gliding, and the Stage’s coordinates.
- Costumes, backdrops, saying, sound, and two things at once.
- Events, loops, if, if / else, and the questions Sensing can ask.
- Variables as a score, a countdown, a mood and a switch. Also as a speed and a record.
- Clones, broadcasts, screens, menus, and games with front doors and endings.
- Instructions
- What to press and what you are trying to do. Nothing else.
- Attract screen
- What a machine does while it waits for a player.
- Credits
- Who made it, and where everything else came from.
- Finished
- A new player can use it without you beside them.
Next: Level 2. Clones that carry their own numbers. The mouse as a controller. My Blocks, and games with shops in them.