Game Design & Development · Lesson 1

What Makes a Game?

Game Design MDA Framework Mechanics Dynamics Aesthetics Game History Real Design Docs Tiny-Loop Games

Before you write a single line of code, great games start with a clear design. Learn the four ingredients every game needs, the MDA framework designers use to think about play, and build your own game concept, no code required.

The 4 Ingredients of Every Game

Every real game has four essential things. Game designer Bernard Suits called it "the voluntary attempt to overcome unnecessary obstacles."

🎯

Goals

A clear win or objective. Reach the flag, score 10 points, survive the longest.

Arcade high score screen
Goals provide a clear win state or objective, such as setting a high score, creating motivation to keep playing.
High scores: beat the previous best. Leaderboards create endless motivation to be #1.
📋

Rules

Constraints that limit what you can do. Rules create the challenge.

Chess bishop movement rules
Rules constrain the player's actions, creating the challenge that makes a game interesting.
📊

Feedback

Information showing progress. Score, health bar, sound effects, screen shake.

F1 pit crew reaction time
Instant feedback loops show progress and performance, keeping players engaged and informed.
Instant feedback loops are addictive. Games and sports measure performance the same way.
🖐️

Voluntary Play

Players choose to play. A fun game makes you want to keep playing.

This separates real games from chores or manipulation.
⚠️ Caution on Gamification: Game goals work when players choose them. But apps increasingly gamify real purchases (shopping discounts, streaks, points) to exploit the same addictive loops. When you see game goals tied to real money or personal data, ask: who benefits?

The MDA Framework

Game researchers Robin Hunicke, Marc LeBlanc, and Robert Zubek created MDA in 2004, the most widely used framework for understanding and designing games. It says every game can be analyzed at three levels:

⚙️ Mechanics The rules and actions written in code or on paper. "Press space to jump." These are what the designer controls directly.
→
🌀 Dynamics What actually happens when players interact with the mechanics. Jumping over enemies creates tension and timing puzzles: emergent behavior.
→
✨ Aesthetics The emotional response in the player: fun, excitement, challenge, curiosity, mastery. This is the real goal of game design.

Designers work top-down (decide the feeling first, design mechanics to produce it). Players experience games bottom-up (feel the mechanics, experience the dynamics, have the emotional response).

Super Mario Example: Mechanic: run and jump with momentum physics. Dynamic: timing jumps across gaps creates near-misses. Aesthetic: the thrill of skillful control and overcoming obstacles.

The History of Video Games — Tech vs. Complexity

Here's a pattern worth noticing: the earliest video games needed some of the most advanced, expensive technology on the planet, yet the games themselves were almost absurdly simple. Today, the technology to make a game fits in a browser tab, and it can build something wildly complex. Step through six decades (press an era, or use the ← → keys) and watch the two bars flip.

  1. The Lab Era

    Room-sized computers built from thousands of vacuum tubes, costing more than a house, owned only by university physics labs and the military.

    Tennis for Two (a glowing dot bouncing over a line on an oscilloscope) and Spacewar! (two ships orbiting a star on MIT's $120,000 PDP-1). ▶ Watch it below

    Access
    Games
  2. The Home TV Game

    Engineer Ralph Baer, working at Sanders Associates, believed the television already sitting in every living room could do more than show broadcasts. His team built a series of prototypes, nicknamed the "Brown Box", that turned an ordinary TV into a game screen using nothing but transistor logic, no computer required.

    Sanders licensed the Brown Box to Magnavox, which released it in 1972 as the Magnavox Odyssey: the first video game console ever sold for the home.

    Access
    Games
  3. Coin-Op & Custom Circuits

    Arcade cabinets ran on hard-wired logic: the original Pong had no CPU or software at all, just custom circuitry built for that one game.

    Pong, Breakout, Space Invaders: one screen, one mechanic, rules you could learn in five seconds.

    Access
    Games
  4. 8-bit Cartridges

    Home consoles ran on 8-bit CPUs with kilobytes of memory: the entire original Super Mario Bros. fits in about 40 kilobytes total.

    Super Mario Bros., Tetris, The Legend of Zelda: bigger worlds built from small, repeating rule sets.

    Access
    Games
  5. The Jump to 3D

    Dedicated 3D graphics chips and CD-ROMs arrive, letting entire rendered worlds fit on a single disc, a huge leap past cartridge memory limits.

    Myst, Super Mario 64, Final Fantasy VII: real 3D space, still hand-built scene by scene.

    Access
    Games
  6. Studios & Engines

    Licensed engines and broadband internet save teams from building tools from scratch, but a top-tier game now needs 50–500 people and years of budget.

    World of Warcraft, Halo, Grand Theft Auto: massive and persistent, reachable only with serious money and staff.

    Access
    Games
  7. The Solo-Dev Breakthrough

    Free engines like Unity and GameMaker put professional-grade tools on a single laptop.

    Minecraft, coded almost entirely solo by Markus Persson, became one of the best-selling games ever made.

    Access
    Games
  8. No-Code & Block Coding

    Scratch, MakeCode, and Roblox Studio bring drag-and-drop game logic to classrooms and bedrooms, no syntax required.

    Millions of student- and hobbyist-made games, some played by more people than big-budget releases.

    Access
    Games
  9. Describe It, Build It

    An AI assistant can write working game code, generate art and music, and debug your logic from a plain-English sentence in a browser tab.

    One student can prototype a physics-based, multi-level, scoring game in an afternoon, something that once needed a whole studio.

    Access
    Games
Barrier to Entry: how hard/expensive it is to access the tech Achievable Game Complexity: what a designer can actually build with it
Tennis for Two (William Higinbotham, Brookhaven National Laboratory, 1958). The "court" is an oscilloscope screen and the ball is a dot traced by an analog computer that works out gravity as it flies. There is no score, no sprites and no memory: the most advanced lab equipment of its day, spent on one bouncing dot.
The Big Flip: In 1962, it took MIT's $120,000 PDP-1 (one of the most powerful computers on Earth) and a team of grad students to make two dots orbit a star. Today, you can open a free tab, describe a game in plain English to an AI, or drag a few Scratch blocks together, and build something far more complex than Spacewar! in an afternoon. The technology got radically easier to access while the games it can build got radically more complex. You're designing games at the exact moment that flip finished happening.
From workshop to arcade: Nolan Bushnell had played MIT's Spacewar! as a college student, and in May 1972 he watched a demo of the Magnavox Odyssey's table-tennis game. Months later he and Ted Dabney founded Atari and shipped Pong, whose first cabinet, installed in a Sunnyvale bar, jammed because customers stuffed it with too many quarters. When Atari sold a home version in 1975, Magnavox sued for patent infringement: Baer had documented every prototype so thoroughly that Atari settled rather than fight it in court. One idea, traced on paper from one workshop to the next.

Real Artifacts: The Ralph Baer Prototypes

These are the actual objects behind the "1966–1972" era above, photographed and preserved by the Smithsonian's National Museum of American History.

TV Game Unit #1 shown with the Heathkit alignment generator used to test it, 1967
Baer's very first test unit, the TV Game Unit #1 (1967), shown with the alignment generator he used to put a controllable dot on a screen.
📺TV Game Unit #1
Baer's First Working Prototype · 1967

Baer's very first test unit, shown with the alignment generator he used to put a controllable dot on a television screen for the first time in history.

The Brown Box prototype console with two wood-grain controllers, 1967–68
The Brown Box (1967–68): The finished prototype Sanders licensed to Magnavox, the first system built to play multiple different games on a TV.
📦The Brown Box
First Multiplayer Console Prototype · 1967–68

The finished prototype Sanders licensed to Magnavox: the first system ever built to play multiple different games on an ordinary television.

Magnavox Odyssey console, box art, and controllers, 1972
Magnavox Odyssey (1972): The first home console ever sold. It proved a home console could exist.
🕹️Magnavox Odyssey
First Home Console Ever Sold · 1972

Fewer than 200,000 units sold (weak marketing left many shoppers thinking it only worked on Magnavox TVs), but it proved a home console could exist.

The Brown Box lightgun accessory, 1967–68
The Brown Box Lightgun (1967–68): An add-on peripheral showing Baer's team was already thinking about accessories.
🔫The Brown Box Lightgun
Shooting-Game Accessory · 1967–68

An add-on peripheral Baer's team built for the Brown Box, evidence they were already designing a game library, not just one game, around a single machine.

Video game history text and object photographs (this section): National Museum of American History, Smithsonian Institution — "The Father of the Video Game: The Ralph Baer Prototypes and Electronic Games." Images used under the Smithsonian's Open Access (CC0) initiative.

Before the Code: Real Games at the Drawing Board

Every game on the timeline above, no matter how technically advanced, started the same way: a sketch, a typed page, a hand-drawn map. None of these teams opened a code editor first. They organized a rough idea into architecture (a concept, a list of systems, and a structure connecting them) and only then started building. Here are four real, documented examples you can go verify yourself.

Link with shield and sword in the classic art style of The Legend of Zelda, standing before a landscape with mountains and water
Miyamoto's Cave Memory (1986): The Legend of Zelda started not with a plot, but with a childhood memory of exploring a real cave.
🕳️The Legend of Zelda
Miyamoto's Cave Memory · 1986

Shigeru Miyamoto didn't start Zelda with a plot. He started with a childhood memory of getting brave enough to explore a real cave near Kyoto. That single feeling became the design goal for the entire game: make the player feel that same nervous curiosity.

"When I was a child, I went hiking and found a lake." — Shigeru Miyamoto

Read the full story →
Grim Fandango artwork
Grim Fandango (1998): A masterpiece of adventure game puzzle design, mapped out on paper before a single line of code was written.
✏️Grim Fandango
Puzzle Design Document · 1996

LucasArts' design team mapped every puzzle in Grim Fandango on hand-illustrated, sketch-covered pages, working out how each clue connected to the next before any of it was programmed. The Video Game History Foundation has preserved and published the actual document online.

See the real design document →
Original Minecraft Cave Game prototype screenshot showing a blocky stone cave structure on grass under a blue sky
Minecraft "Cave Game" Prototype (2009): The very first public test video was just a cave you could walk through.
🕹️Minecraft
"Cave Game" Prototype · May 2009

Minecraft began as a one-week experiment Notch called "Cave Game," inspired by Infiniminer and Dwarf Fortress. The very first public test video didn't even let you place a block yet. It was just a cave you could walk through. Everything else was added on top of that tiny first architecture.

See the earliest prototype history →
Narbacular Drop gameplay screenshot showing early portal mechanics
Narbacular Drop (2005): The student project that caught Valve's attention and eventually became the award-winning game Portal.
🎓Portal
Narbacular Drop · 2005

Portal didn't start at Valve at all. It began as Narbacular Drop, a student senior project built by a small team at DigiPen. Valve saw it at a student showcase and hired the entire team on the spot to rebuild the idea. Your class project could be someone's Portal.

See the original student project →

From concept to architecture: every one of these documents did the same four things, just in different formats.

🌱ConceptOne sentence: what's the feeling or fantasy? (Miyamoto's cave. Hall's moon base.)
→
🔁Core LoopWhat does the player do, over and over? Walk. Solve a clue. Flap through a gap.
→
🧩Systems ListBreak the loop into parts: movement, scoring, enemies, puzzles, sound.
→
🗺️Structure DiagramMap how the pieces connect: level order, puzzle chain, dungeon layout.
Go Deeper (with a teacher): The Video Game History Foundation's public archive holds real design documents, sketches, and prototypes from decades of games, free to browse. It's exactly the kind of primary-source research a historian would do, just aimed at games instead of wars or treaties.

Game Genres & Core Mechanics

Genres cluster games by their dominant mechanic. Click any genre to see its defining mechanic.

Click a genre above to explore its core mechanic.

Tiny-Loop Games — Design Fast, Finish Strong

For a single-day build (a camp, a class period, a jam), the games that actually get finished are tiny-loop games: one mechanic, one win/lose condition, and one variable a student can customize. Big "adventure game" ideas explode in scope fast: a maze with an inventory and a boss fight is three unfinished projects wearing a trenchcoat. Start from one of the ten archetypes below instead of inventing a new genre from scratch.

The Tiny-Loop Test: Can you say your game idea in one sentence with exactly one verb? "Move to catch falling batteries" is a tiny loop. "Explore a world, collect items, upgrade gear, and defeat a boss" is not. That's four games glued together.
Open Tutorial vs. Use as Starting Point: Every archetype except Dodging has a full Open Tutorial, a working, customizable version of that exact game plus its architecture, then a path into Scratch and real JavaScript. (Dodging gets its own complete build, JS and Scratch both, in Lesson 2.) Every archetype also has Use as Starting Point, which loads its concept into the design workshop below so you can write a pitch for it right away.
Visual Direction: These demos should still feel like Mr. Scandrett's ClassroomOS first and a game arcade second. Graphics need to support comprehension: the player, goal, hazard, score, and restart path should be readable within a few seconds. Use simple shapes, clear contrast, and restrained motion that explains the mechanic. If outside assets are useful, prefer CC0/public-domain classroom-friendly sources such as Kenney or carefully licensed OpenGameArt files, copy only the assets actually used, and keep attribution manageable.
Device Rule: A finished tutorial must run on desktop, Chromebook, iPad, iPhone, and Android browsers with ordinary HTML, CSS, Canvas, and JavaScript. Do not require installs, plugins, WebGL-only rendering, hover-only controls, or a physical keyboard. Keyboard controls are still useful on desktop, but every playable demo needs tap or touch controls with large targets and no accidental page scrolling during play.
#1 Easiest
⭐Catch Game
Best: K–5 Scratch · MakeCode · Godot · Pygame

Kids understand it instantly: the safest pick for a one-day camp.

  • Move player left/right
  • Spawn falling objects
  • Good item touched → +1 score
  • Bad item touched → −1 life
e.g. Catch the Stars · Robot Collects Batteries · Frog Eats Flies
Open Tutorial →
#2
💥Dodging Game
Best: 2nd–8th Scratch · MakeCode · Godot

Teaches collision, timing, and tension as difficulty ramps up.

  • Player movement
  • Enemy movement (chase, fall, or fly)
  • Collision = lose a life
  • Score/timer climbs while surviving
e.g. Dodge the Meteors · Don't Touch the Lava · Bee Avoids Birds
#3
🖱️Clicker Game
Best: K–6 Scratch · HTML/JS · MakeCode

Extremely easy to build: add an upgrade to make it feel like a real game.

  • Click/tap the sprite
  • Score increases
  • Upgrade makes score increase faster
e.g. Cookie Clicker · Gem Miner · Pizza Empire
Open Tutorial →
#4
🧩Maze Game
Best: 3rd–8th Scratch · MakeCode · Godot

Great logic lesson, but hand out a maze template so drawing walls doesn't eat the whole day.

  • Arrow-key movement
  • Walls block or reset the player
  • Touch the goal tile to win
  • Optional: key/door mechanic
e.g. Escape the Lab · Mouse Gets Cheese · Knight Finds the Key
Open Tutorial →
#5
🐦Flappy Clone
Best: 4th–8th Scratch · MakeCode · Godot

Very satisfying, but scrolling obstacles trip up true beginners. Best once students know the basics.

  • Gravity pulls down
  • Key press = jump/flap impulse
  • Scrolling obstacles
  • Collision = game over
e.g. Flappy Bat · Rocket Through Asteroids · Dragon Through Towers
Open Tutorial →
#6
🏓Pong / Paddle Game
Best: 4th–8th Scratch · MakeCode · Godot · Python

Teaches angles, velocity, and reflection. Simplify the bounce math for younger kids.

  • Ball moves every frame
  • Bounces off walls and paddle
  • Score when the ball passes a side
e.g. Space Pong · Air Hockey · Magic Shield
Open Tutorial →
#7
🫧Top-Down "Shooter"
Best: 4th–8th Scratch · MakeCode · Godot

Keep it nonviolent: pop balloons, clean trash, zap viruses, spray out fires.

  • Player movement
  • Projectile spawns and travels
  • Target disappears when hit
  • Score +1 per hit
e.g. Clean the Ocean · Wizard Shoots Spells · Firefighter Sprays Flames
Open Tutorial →
#8
🎵Rhythm Tap Game
Best: 5th–12th Scratch · MakeCode · Godot

The coolest fit for a music/STEAM camp, but bring a starter engine so it finishes in a day.

  • Notes fall toward a target line
  • Press the matching key at the right time
  • Score is based on timing accuracy
e.g. Drum Hero · Piano Tap · Beat Bot
Open Tutorial →
#9
❓Quiz Adventure
Best: K–6 Scratch · Slides · PowerPoint · Twine

Very easy and classroom-friendly, with more design and writing than coding.

  • Question appears
  • Correct answer advances
  • Wrong answer gives a hint or a retry
e.g. Math Dungeon · Science Quest · Animal Rescue Quiz
Open Tutorial →
#10
📖Choose-Your-Own-Adventure
Best: 2nd–8th Scratch · Twine · Slides · Canva

Best for mixed-ability teams: writers, artists, and coders can all contribute a piece.

  • Scene is presented
  • Player picks choice A or B
  • Each choice leads to a different outcome
e.g. Lost in Space · Forest Temple · Time Travel Lab
Open Tutorial →
Strongest overall pick, "Robot Rescue" (Catch + Dodge hybrid): A robot collects batteries while avoiding water drops. Students customize the robot sprite, battery sprite, hazard sprite, background, score goal, speed, sound effects, and win message. Core loop: move left/right → battery falls (touch it, +1 score) → water falls (touch it, −1 life) → score 10 to win, 0 lives to lose. One design gives you programming, art, logic, debugging, and student personality without letting the project sprawl.

Quick picks by grade band:

K–2Catch, Clicker, Quiz Adventure
3rd–5thCatch, Maze, Dodging
6th–8thFlappy Clone, Shooter, Pong
High SchoolRhythm, Platformer, Shooter, Godot Microgame

Design Workshop — Build Your Own Game Concept

Fill in the fields below to generate a game design pitch. You don't need to know how to code yet. Start by thinking like a designer. Click "Use as Starting Point" on any tiny-loop archetype above to load a template here, then customize it.

Game Design Document (Mini)

Identify the Elements

For each scenario, identify what game design element is being described.

1. In a racing game, a sound effect plays and the screen flashes green whenever you pass a checkpoint.

2. In chess, you cannot move your king onto a square that is under attack.

3. The objective of Pac-Man is to eat all the dots on the screen without being caught by a ghost.

4. A player quits a mobile game because it started feeling like homework, just chores to collect daily rewards.