Events
Events are things that happen — a key pressed, a mouse clicked, a window closed. The program listens for them each frame rather than waiting.
Python for Kids · Class 8 · Module 8 of 9
Graphical Game Build
From typed commands to something you can actually play with a keyboard.
8 sessionsSessions 57–64
4 weeksTypical pace
Foundation to IntermediateLevel
Class 8Python & Coding
The big idea
A graphical game runs on a loop that never stops: read what the player did, update the world, draw the new frame, repeat — around sixty times a second.
Why it matters
The game loop is the same architecture behind animation, robotics and real-time systems. Seeing it once explains a whole category of software.
Unpacked
What you will actually learn
Three core ideas, each taught with worked examples and then practised until it feels obvious.
Collision logic
Collision logic asks whether two rectangles overlap. Almost every hit, catch and bump in 2D gaming is that one check.
Game loop
The game loop ties it together: input, update, draw, repeat. Anything that happens in a game happens inside that cycle.
Did you know?
Games measure work in frames. At 60 frames per second, everything — physics, input, drawing — must finish in under 17 milliseconds.
Common mix-up
“Use time.sleep() to slow the game down.” Sleep freezes everything, including input. Games control speed with a clock and a frame rate instead.
Session by session
Your 8-session journey
Sessions 57–64 of the 72-session year, at two one-hour sessions per week.
- 1
Warm-up and big picture
Where this module fits, what you will build, and a hands-on starter that gets everyone curious about events.
- 2
Events
Guided teaching on events, worked through together with the teacher.
- 3
Events — practice lab
Independent practice, small challenges and one deliberate mistake to diagnose.
- 4
Collision logic
Guided teaching on collision logic, building directly on the previous two sessions.
- 5
Collision logic — practice lab
Applied tasks that combine events and collision logic in one piece of work.
- 6
Game loop
Game loop introduced and practised, completing the toolkit needed for the project.
- 7
Project build
Guided build session for the module project: Playable arcade-style game.
- 8
Test, present and reflect
Finish, test against the checklist, present the work and explain the decisions behind it.
Project lab
Playable arcade-style game
Every module ends with something the student built themselves and can demonstrate. This is the piece that goes into their portfolio and gets explained out loud at the end of session 64.
Try this at home
Add one feature that changes how your game feels rather than what it does — a screen shake, a particle burst, or a rising difficulty curve.
It is finished when
- It works from start to finish without breaking
- You can explain every part of it in your own words
- You tested it and improved at least one thing afterwards
- Someone else used or understood it without your help
By the end of this module
Students finishing Module 8 can:
- Explain and use events without prompting
- Explain and use collision logic without prompting
- Explain and use game loop without prompting
- Build and finish playable arcade-style game
- Test your own work and correct what you find
- Talk an adult through what you made and why
Word bank
The vocabulary introduced here, in plain language:
- event
- An input or occurrence a program responds to.
- collision
- Two objects overlapping in game space.
- frame rate
- How many times per second the screen updates.
Module challenge
Think you have got this?
0 XPLevel 1 · Curious Beginner
6 quick questions drawn from this module — vocabulary, the project you build, and a myth-or-fact round. Every wrong answer explains itself, so a mistake still teaches you something.
Your child's free trial is one message away.
Tell us your child’s class and what they enjoy. We will suggest the closest program fit—no pressure and no upfront payment.