Curriculum topic

Events and Commands

Programs need a reason to begin and a precise instruction about what should happen next. Events provide the reason; commands provide the action.

Why it matters

A small idea that returns in larger systems.

Without events, a game cannot tell the difference between waiting and acting. Without commands, a robot has no sequence to follow. This topic gives students the basic grammar of interactive systems: when something happens, do something observable.

Real-world connection

An elevator button, a pedestrian crossing, and a game controller all wait for an event. The systems differ, but each must connect an input to a dependable sequence.

The connection shows where the idea returns; it does not claim every advanced application is taught in this first topic.

Math and logic kernel

The structure beneath the project.

Trigger

An event that starts a response.

Sequence

Commands run in an intentional order.

Cause and effect

A visible action should have an identifiable cause.

Specificity

A useful command says exactly what changes.

Small examples

Make one relationship visible at a time.

1

Green flag

Start a Scratch scene from a known state.

2

Key press

Move or act only when a chosen key is pressed.

3

Button input

Make a simulated or physical output respond.

4

Message received

Start one part of a project when another part is ready.

Program connections

Where this topic appears.

Active now

Scratch & Game Design

Beginner-friendly programming through original games, animations, simulations, and interactive stories.

Active now

Robotics

Commands, sensors, simple electronics, simulations, and physical systems organized around Sense, Decide, Act.

Available later

Roblox Studio / Lua

A future bridge from visual programming to Lua, 3D objects, events, and larger game systems.

Common mistakes

Useful clues, not reasons to stop.

Commands in the wrong order

The output happens before the setup is complete.

No clear trigger

Code exists but nothing tells it to run.

Too many jobs in one event

A single script becomes difficult to test.

Assuming instant completion

The next command begins before an animation or movement has finished.

Lesson and projects

Use the idea inside a working system.

Open Lesson