☰
1. Pick two main characters and a backdrop 2. (Group Activity) Broadcast Blocks 3. Write your first dialogue 4. Make your second character respond 5. Make your first character respond again 6. Add some motion effects 7. Add sound effects 8. Build your story

Project 108: Living Comic

2. (Group Activity) Broadcast Blocks

In Scratch, one sprite's code can't give directions to another sprite's code - or can it? We can use broadcast blocks to send messages from one sprite to another. We're going to be playing a Simon Says game, so everyone get out of their seats!
Starting point file for this challenge
Hint: show steps

Steps

1. Events

Event blocks are how we trigger, or "wake up" code. Code can't run unless something tells it to run. Otherwise, the code will just sit there.

It'd be like giving someone a recipe for cake, but not actually telling them to bake the cake for you!

What's the most common Events block we usually use? What's the event that triggers all the code beneath it to run? 

2. Simon Says ... Or, Broadcast Block Says

Every student is going to pretend to be a different sprite. You all have code to act out, but of course, you can't act out your code until the event says you can!

Everyone pick an event and code block below. 

3. Simon Says ... Or, Broadcast Block Says 2

One person will play as the Simon sprite. The Simon sprite is a totally different sprite who's going to be reading out a list of messages. Or, in Scratch terms, broadcasting a list of events.

The list of messages is below.

Every other sprite should be listening and waiting for their chosen event. When you know your event has been triggered by the Simon sprite, act out your code! If you hear a different event, don't do anything!