Computing · Year 3 · Events and Actions: Interactive Games · Summer Term

Using Multiple Events and Conditions

Creating more complex interactions by combining multiple event listeners and conditional statements.

• National Curriculum Attainment Targets
• KS2: Computing - Programming
• KS2: Computing - Algorithms

About This Topic

Using multiple events and conditions allows Year 3 students to build interactive games where characters respond to several inputs at once, such as jumping on an up arrow and running on left-right arrows. They combine event listeners, like key presses or mouse clicks, with conditional statements to create rules, for example, only allowing a jump if the character is on the ground. This topic aligns with KS2 programming objectives by developing skills in sequencing actions and using logic to control program flow.

In the Events and Actions unit, students progress from single-event programs to complex ones that simulate real games. They analyze how conditions prevent errors, like characters flying endlessly, and design programs where events control speed, direction, or scoring. This fosters computational thinking, including decomposition of game mechanics and evaluation of program effectiveness.

Active learning shines here through collaborative coding and iterative testing. When students pair program, test on shared devices, and debug together, they spot flaws in conditions quickly and refine logic through peer feedback. Hands-on game play reveals how multiple events create smooth interactions, making abstract concepts concrete and boosting confidence in programming.

Key Questions

1. Analyze how multiple events can make a character jump and run simultaneously.
2. Design a program that uses different events to control different aspects of a game.
3. Evaluate the importance of clear conditions in event-driven programming.

Learning Objectives

• Design a simple game character that responds to at least three different user inputs simultaneously.
• Analyze a given code snippet to identify how multiple event listeners trigger distinct actions.
• Evaluate the effectiveness of conditional statements in preventing game-breaking errors, such as a character moving through walls.
• Create a program that uses a combination of key presses and mouse clicks to control different game elements.
• Explain the logic behind chaining multiple conditions to create a complex character behavior.

Before You Start

Introduction to Event Listeners

Why: Students must understand how to detect and respond to a single user action before they can combine multiple events.

Basic Conditional Statements (If Statements)

Why: Students need a foundational understanding of 'if' statements to build more complex logic with multiple conditions.

Key Vocabulary

Event Listener	A function or command that waits for a specific user action, like a key press or mouse click, to happen before running other code.
Conditional Statement	A programming structure, often an 'if-then-else' statement, that checks if a condition is true before running a specific block of code.
Boolean Logic	A type of logic that uses true or false values, often used within conditional statements to make decisions in a program.
Simultaneous Events	When a program can detect and respond to more than one user input or internal event happening at the same time.

Watch Out for These Misconceptions

Common Misconception

Events always happen one after another in a fixed order.

What to Teach Instead

Events run in parallel based on user input, not sequence. Pair testing shows simultaneous key presses allowing jump and run together. Discussing shared screens helps students see real-time responses and adjust mental models.

Common Misconception

Conditions are optional and programs work without them.

What to Teach Instead

Conditions define when events trigger, preventing chaos like perpetual motion. Group debugging reveals glitches without if-statements. Collaborative fixes build understanding that logic gates control reliable interactions.

Common Misconception

More events always make a better game.

What to Teach Instead

Too many events overwhelm without clear conditions. Whole-class reviews of overloaded programs highlight confusion. Students learn through iteration to select relevant events for purposeful design.

Active Learning Ideas

Pair Coding Challenge: Multi-Control Character

Pairs use block-based software to code a sprite that jumps on spacebar, moves left-right on arrows, and changes colour if touching an edge. First, brainstorm controls together. Then code, test, and swap roles to add one condition each. Share working games with the class.

35 min·Pairs

Small Group Debug Relay: Condition Fixes

Divide code with multiple events into stations, each with a bugged condition, like endless jumping. Groups rotate, fix one issue per station using test runs, and note changes. Regroup to combine fixes into a full game.

45 min·Small Groups

Whole Class Game Design Share: Event Mapping

Students sketch game ideas with multiple events on paper first. Code individually, then present to class for votes on best conditions. Class votes and suggests improvements before final tweaks.

50 min·Whole Class

Individual Extension: Custom Condition Game

Each student adds two personal conditions to a base game template, such as scoring only if moving fast. Test against self-set goals and record video explanations of event interactions.

25 min·Individual

Real-World Connections

• Video game developers use multiple events and conditions constantly to make characters jump, run, shoot, and interact with the game world in response to player commands.
• Robotics engineers program robots to react to various sensors and commands simultaneously, such as a robot vacuum cleaner avoiding obstacles while cleaning a floor.

Assessment Ideas

Exit Ticket

Provide students with a short code snippet that uses two event listeners and one conditional. Ask them to write down what will happen when the user presses a specific key, and what will happen if they click the mouse.

Quick Check

Observe students as they work on their game designs. Ask targeted questions like: 'What event is this code listening for?' or 'What needs to be true for the character to jump?' Note which students can articulate the relationship between events and conditions.

Discussion Prompt

Pose a scenario: 'Imagine a character in a game needs to pick up a coin, but only if it's standing on the ground. How would you use events and conditions to make this happen?' Facilitate a brief class discussion on their proposed solutions.

Frequently Asked Questions

How do you introduce multiple events in Year 3 computing?

Start with familiar single-event games, then layer on a second event, like adding run to jump. Use visual block coding to drag events onto sprites. Model live coding on a projector, pausing for predictions, so students see immediate feedback and build incrementally toward complex interactions.

What block-based tools work best for this topic?

ScratchJr or Scratch suit Year 3 perfectly, with intuitive blocks for key events and if-then conditions. Provide templates to focus on logic, not setup. These tools offer instant testing, letting students experiment safely and share projects via QR codes for home extension.

How can active learning help teach events and conditions?

Active approaches like pair programming and relay debugging make abstract logic tangible. Students physically manipulate blocks, test in real-time, and discuss failures, which reveals misconceptions faster than solo work. Group shares build evaluation skills as peers critique conditions, fostering resilience and deeper understanding through collaboration.

How to assess understanding of conditions in games?

Observe during testing: do students predict outcomes correctly? Use rubrics for self-assessment on whether conditions work as intended. Collect short videos of games with explanations of one event-condition pair. This captures both creation and evaluation skills from the national curriculum.