Skip to content

04 //Academy

From playing games to building them.

Game development turns a familiar pastime into a design problem: rules, movement, difficulty and feedback all have to be decided by the person making it.

01 //What learners build

Four things, in order.

  • 01Design and rules

    A game is a system of rules that creates an experience.

    What can the player control? What is the objective? What happens on a mistake? How do they win? Learners design these before building anything.

  • 02Movement and physics

    Code that creates movement which feels believable.

    A character jumps, an object falls, two things collide, a player stops at a wall. Behind every one of those behaviours is a piece of logic.

  • 03Levels and challenge

    Difficulty is something a designer deliberately shapes.

    Too easy becomes boring; too hard becomes frustrating. Learners experiment with obstacles, goals, rewards, pacing and increasing challenge.

  • 04Playtesting

    A game gets better by listening to the people who play it.

    The creator knows how it works; the player doesn't. Learners watch someone else play, find where they get confused or stuck, and change the game.

02 //The game development journey

Imagine, design, build, play, improve.

How a learner moves through the path

  1. 01

    Imagine

    What could this game be? Start with an idea, a mechanic or an experience.

  2. 02

    Design

    What are the rules? Define the objective, controls, challenges and feedback.

  3. 03

    Build

    How do we make it work? Turn the design into code, movement, levels and interactions.

  4. 04

    Play

    Is it actually fun? Put the game in someone's hands.

  5. 05

    Improve

    What should change? Use what happened during playtesting to make the next version better.

03 //Games are systems

Every action has a consequence.

A player presses a key. The character moves, touches an obstacle, and the game responds. That whole experience comes from a chain of instructions.

The chain behind a moment of play

  1. 01

    Input

    The player acts.

  2. 02

    Rules

    The game decides what that action means.

  3. 03

    Behaviour

    Something in the world changes.

  4. 04

    Feedback

    The player is told what happened, through sound, animation or score.

04 //What learners explore

Design and code together.

  • 01

    Game design — turning an idea into rules, objectives and interactions

  • 02

    Programming — controlling characters, objects and game behaviour

  • 03

    Movement — responsive character and object movement

  • 04

    Physics — gravity, collisions, speed and interaction

  • 05

    Level design — spaces that guide and challenge the player

  • 06

    Game logic — scoring, lives, timers, goals and game states

  • 07

    Feedback — sound, animation and effects that communicate what happened

  • 08

    Playtesting — observing real players and improving from what they do

05 //Learning through builds

Every concept should become playable.

  • 01Build 01

    Interactive mini game

    A simple game with a player, an objective and rules. Controls, events, goals and feedback.

  • 02Build 02

    Movement challenge

    A character that moves, jumps and interacts with the environment. Movement, speed, gravity, collisions.

  • 03Build 03

    Obstacle course

    A level with hazards and increasing challenge. Level design, difficulty and progression.

  • 04Build 04

    Score and reward system

    Points, lives, collectibles or other rewards. Variables, game states and feedback.

  • 05Build 05

    Complete game

    Mechanics, level design, feedback and challenge combined into a playable experience.

  • 06Final challenge

    Build a game someone else wants to play

    The learner decides what the game is, how the player wins, what makes it challenging, and why anyone would play it again. Then builds it.

06 //The learner progression

From player to creator.

  • 01Explorer

    “How does this game work?”

    Discovering game mechanics and interactive systems.

  • 02Designer

    “What should happen?”

    Creating rules, objectives and challenges.

  • 03Builder

    “How do I make it work?”

    Using programming to create mechanics and interactions.

  • 04Playtester

    “What happens when someone else plays it?”

    Observing real players and identifying improvements.

  • 05Game creator

    “I have an experience I want people to play.”

    Designing, building and refining an original game.

07 //What parents can expect

A creative problem-solving skill.

  • 01

    Creativity

    Turning stories, ideas and imagination into interactive experiences.

  • 02

    Programming

    Applying coding concepts where the result is immediately visible.

  • 03

    Problem solving

    Games require thinking about rules, systems and consequences.

  • 04

    Design thinking

    Considering the experience from another person's perspective.

  • 05

    Persistence

    Debugging and balancing a game requires repeated experimentation.

  • 06

    Communication

    Playtesting teaches learners to explain ideas and listen to feedback.

08 //What learners leave with

Don't just ask whether it works. Ask whether it's fun.

A technically working game can still be frustrating, confusing or boring. Learners begin thinking from the player's perspective — and that is the move from programmer to designer.

An understanding of game design
And experience turning rules into code.
An introduction to movement and physics
And experience designing levels and challenges.
Practice receiving and applying feedback
“I didn't just play the game. I built the world.”

Other paths

  • 01

    Coding

    Coding starts with logic a learner can see and moves into written code, so the step from blocks to a real language feels like the next sentence rather than a new subject.

  • 02

    AI

    AI is explored by using it and taking it apart: training something simple, seeing where it gets things wrong, and asking why.

  • 03

    Robotics

    Robotics connects a program to the physical world, where a mistake is visible immediately: the motor turns the wrong way, the sensor reads nothing, or the robot simply refuses to do what you told it to.

Every game starts with a question

What if?

That question becomes a mechanic. The mechanic becomes a rule. The rule becomes code. And the code becomes a game.