Level 2: Broadcasting Spells

Official Raspberry Pi Project

This lesson is based on the official Raspberry Pi Foundation project. Open it alongside this guide to access the starter project, step-by-step instructions and community remixes.

How to use it: Click the link above, then click See Inside on the Scratch project to explore the finished version. Use Remix to get your own copy to edit.

What You Will Build

Use broadcast and receive blocks to trigger magical effects between sprites.

What You Will Learn

By the end of this project you will be able to:

• Use Events blocks to start scripts and respond to clicks
• Combine Motion, Looks and Sound blocks to create behaviours
• Use variables to track game state and scores
• Apply the specific Scratch concepts introduced in Level 2

You Will Need

Step-by-Step Guide

1. Create a magical backdrop (castle, forest, night sky).
2. Add a wizard sprite and several effect sprites (sparkles, stars, flames).
3. When the wizard is clicked: broadcast [spell1].
4. Create separate scripts on each effect sprite: when I receive [spell1].
5. Each effect sprite should react: play a sound, change color, move or grow.
6. Add 3 different spells, each with a different broadcast message.
7. Add buttons or keyboard triggers for each spell type.
8. Use set [ghost] effect to [50] to make effects fade in/out.
9. Add a spell name display using a variable.
10. Make spells reset after 2 seconds using wait [2] secs then clear graphic effects.

Extension Challenges

Try these after completing the main project:

• Chain broadcasts so one spell triggers another automatically.
• Add a spell counter that limits how many times each can be used.
• Create a ‘spell backfire’ that reverses all effects.

Reflection Questions

1. Which Scratch blocks did you use most in this project?
2. What would you add or change if you had more time?
3. How could you reuse the ideas from this project in a different context?

Share Your Work

When your project is complete, click Share in Scratch and post the link to your class or the Techbase community.