Making Games Autumn 2026

Study Hub From Intro To Game Loops

A simple guide for the lectures you missed: what each class was about, the important words, the roles in a game team, and your Prototype 1 game, Cup Catch.

Visual Lecture Slides

01Aug 24

Course Mindset

The course teaches process: make small games, test them, learn from players, and improve.

1Player
2Prototype
3Feedback
02Aug 28

Design Language

Use clear words: mechanic, rule, goal, challenge, progression, player experience, and loop.

1Mechanic
2Goal
3Progression
03Aug 31

Game Teams

Games are made by roles working together: designers, producers, programmers, artists, sound, writing, QA.

1Roles
2Team
3Communication
04Sep 4

Game Loops

A loop shows what the player repeatedly does and how actions connect to outcomes and rewards.

1Action
2Outcome
3Repeat

All Materials From Start To Now

August 24

  • Intro Slides - Rego
  • MakingGamesIntro_24082026
  • Course structure, prototypes, expectations, players, resources, and vocabulary.

August 28

  • MakingGamesGameDesignTerminology_28082026
  • Greg Costikyan - I Have No Words & I Must Design
  • Priscilla Lo et al. - What is a game mechanic?
  • Anna Anthropy and Naomi Clark - Verbs and objects
  • Game Maker's Toolkit - How to Think Like a Game Designer
  • Adam Millard - Leveling Up Progression Systems

August 31

  • Roles in Game Development lecture
  • Tracy Fullerton - Game Design Workshop, Team Structures
  • Prototype 1 Intro
  • Design pillars: physical, two-player, laugh-out-loud, radically simple.

September 4

  • Prototype 1 Playtesting & Showcase
  • MakingGames2026_GameLoops_04092026
  • Recommended reading: Emmanuel Guardiola on gameplay loops
  • Exercise: draw your Prototype 1 gameplay loop and explain it to another person.

Full Teaching Pack

Read this like a private lesson. Each lecture is split into subjects, simple meaning, examples, exercise, and the one idea you must remember.

August 24

Intro Lecture

complete notes

Games Business Today

Many people can make games now because tools are easier, but this also means there is strong competition. A game being good is not always enough; teams also need planning, testing, communication, and understanding of players.

Easy example

A simple mobile game may compete with thousands of other games, so the team must know who it is for and why someone would play it.

Course Goals

The course teaches you to work with players, work with teammates, organize development, use resources wisely, and understand what your game wants to become.

Easy example

For Cup Catch, the game wants to be fast, physical, funny, and easy to learn. That tells you not to add complicated rules.

Good Process Before Good Game

At the beginning, the teachers care a lot about process. This means making, testing, learning, changing, and explaining your choices. You do not need to make the best game in the class.

Easy example

If a playtester says the distance is too hard, you can change the distance. That is good process.

Course Structure

Before autumn break, you make several small prototypes. After autumn break, you work in teams on a bigger project with supervision, workshops, guest lectures, playtesting, and showcases.

Easy example

Prototype 1 is physical. Later prototypes use tools such as Twine, PuzzleScript, Playdate, or larger engines.

Resources

Resources are not only money. They include time, skill, technology, team energy, materials, teacher feedback, and what you personally want to learn.

Easy example

Cup Catch uses very few resources: one cup, paper, two players, and a few minutes of testing.

Designer Vocabulary

The class started building a shared language. This matters because designers need words to explain games clearly instead of only saying fun, boring, or good gameplay.

Easy example

Instead of saying Cup Catch is fun, say the short loop creates quick tension and immediate feedback.

Class exercise

Students thought alone, discussed in pairs or groups, and shared expectations and game design terms with the class.

Must know

You are not expected to already know everything. The point is to learn by making and by speaking clearly about design.

August 28

Design Lecture + Exercises

complete notes

Mechanics

A mechanic is an action the player can do because the rules allow it. Good mechanic words are verbs: move, jump, choose, inspect, drop, catch, score, trade, collect.

Easy example

Cup Catch mechanics are drop, catch, switch roles, and score points.

Core Mechanics

A core mechanic is the main repeated action. It is what the player does again and again, and it gives the game its identity.

Easy example

In Cup Catch, catching the falling ball with the cup is the core mechanic.

Rules

Rules define what is allowed, what is forbidden, and how the game reacts. Rules make the mechanic understandable and fair.

Easy example

The ball must be dropped from shoulder height, and the catcher can only use the cup.

Goals

A goal tells the player what they are trying to achieve. Without a goal, the player may not know why they are acting.

Easy example

The goal in Cup Catch is to be the first player to reach 5 points.

Challenge And Flow

Challenge is what makes the goal difficult. Flow happens when the challenge is not too easy and not too hard, so the player feels focused and involved.

Easy example

If players stand too close, Cup Catch becomes too easy. If they stand too far, it becomes frustrating.

Progression And Gates

Progression means the game changes over time. A gate is something that blocks progress until the player does something, learns something, gets a resource, or reaches a condition.

Easy example

In Cup Catch, simple progression can be rounds getting harder by increasing distance after each point.

Verbs And Objects

A clear design method is to ask: what verbs can the player do, and what objects do those verbs affect?

Easy example

Verb: catch. Object: paper ball. Tool: cup. Result: point or miss.

Class exercise

The class practiced using terminology to describe games. The important habit is explaining what the player does and how rules create experience.

Must know

Do not explain only story or theme. Explain player action, goal, challenge, feedback, and loop.

August 31

Roles In Game Development + Prototype 1 Intro

complete notes

Game Designer: Systems

This role protects the rule system. They think about mechanics, balance, game logic, progression, and whether the game works as a system.

Easy example

For Cup Catch, a systems designer decides score limit, distance, switching rule, and difficulty.

Game Designer: Experience

This role protects player experience. They care about feeling, clarity, controls, UI, accessibility, testing, and whether players understand what to do.

Easy example

For Cup Catch, an experience designer watches if players laugh, understand the rules, and feel the distance is fair.

Producer

The producer protects time and teamwork. They schedule tasks, keep milestones realistic, support team health, and make sure people deliver.

Easy example

For Prototype 1, a producer would make sure the rules text, playtest, image, and submission are finished before Friday.

Programmer And Tech Lead

Programmers build systems. Tech leads guide technical decisions, code structure, tools, builds, and the development pipeline. For analog Prototype 1, these roles matter less, but later they become central.

Easy example

In a digital version of Cup Catch, programmers would code falling physics, scoring, input, and reset.

Secondary Roles

Other roles include level designer, artist, sound designer, composer, narrative designer, writer, QA tester, localization, marketing, and more.

Easy example

Even Cup Catch could use a visual designer for a clean rules sheet and a tester for finding unclear rules.

Team Structures

A team works better when responsibilities are clear, communication is regular, and everyone understands how their work affects others.

Easy example

Changing a rule affects testing, writing, player experience, and maybe production timing.

Design Constraints

Constraints are limits that help creativity. If everything is possible, it is easy to get lost. Prototype 1 gives strong limits so you can focus.

Easy example

Physical, analog, exactly two players, funny, and radically simple are constraints that led to Cup Catch.

Design Pillars

Design pillars are short principles that guide decisions. They help you decide what belongs in the game and what should be removed.

Easy example

If a new Cup Catch rule is not simple, physical, two-player, or funny, you probably remove it.

Class exercise

The lecture connected roles to later course work, then introduced Prototype 1 and its design pillars.

Must know

A role is a responsibility. A design pillar is a decision guide. A constraint can help creativity.

September 4

Prototype 1 Playtesting + Showcase + Game Loop

complete notes

Unsupervised Playtesting

Playtesting is when real people try your game. Your job is to observe what they do, where they hesitate, what they enjoy, and what rule they misunderstand.

Easy example

If players in Cup Catch keep asking how far apart to stand, the rules need a clearer distance.

Showcase

A showcase is a chance to share the prototype, not to prove it is perfect. You can explain the idea, let people play, and learn from their reactions.

Easy example

You can say: this is a very small physical reaction game about catching a falling paper ball with a cup.

Core Gameplay Loop

A gameplay loop shows the repeated player activity: action, result, feedback, reward, and next action.

Easy example

Cup Catch: prepare, drop, catch or miss, score, switch, repeat.

Why Loops Help Designers

Loops show how game parts connect. If you change one part, the rest can change too. This helps you predict design problems.

Easy example

If catching gives 2 points instead of 1, the game becomes shorter and maybe less fair.

Examples From The Lecture

Pac-Man, Papers Please, Hay Day, Animal Crossing, and Sushi Hands show that very different games can still be explained as loops.

Easy example

Pac-Man loops movement, eating, avoiding, and clearing. Hay Day loops planting, waiting, harvesting, producing, and upgrading.

Loop Exercise

The class exercise was to draw the gameplay loop of Prototype 1 and show it to another person to see if it makes sense.

Easy example

Draw Cup Catch as six boxes with arrows: prepare -> drop -> catch/miss -> score -> switch -> repeat.

Class exercise

Draw your Prototype 1 gameplay loop on paper, explain it to one person, listen to their comments, and improve the drawing or rules.

Must know

A loop is not decoration. It is a practical tool for understanding what players repeatedly do.

How To Study This Course

Before Class

Read the lecture card, learn the key words, and prepare one simple sentence you can say out loud.

During Exercises

Focus on the action. Ask what the player does, what the rule is, and what feedback they receive.

When You Are Nervous

Use Cup Catch as your safe example. It is simple enough to explain every major term.

After Class

Write three notes: one new term, one example, and one question you still have.

Concept Map

This is the easiest order for understanding almost every lecture.

1

Player

The person taking action

2

Mechanic

The action they can do

3

Rule

The limit around the action

4

Goal

The reason to act

5

Challenge

The difficulty or obstacle

6

Feedback

The result the player sees or feels

7

Loop

The repeated cycle of action and result

Readings And Videos Explained

Costikyan - Critical Vocabulary for Games

Reading
  • Do not use vague words like gameplay without explaining what creates it.
  • Games need interaction, goals, struggle, structure, and meaning inside the game.
  • A game is interesting because the player tries to achieve something under rules and obstacles.

Lo et al. - What Is A Game Mechanic?

Reading
  • Game mechanic is a difficult term, and different people define it differently.
  • For class, think of mechanics as player actions allowed by rules.
  • Describe mechanics as small verbs, not broad genres or stories.

Anthropy & Clark - Verbs And Objects

Reading
  • A useful way to design is: what verbs can the player do, and what objects do those verbs affect?
  • Example: catch paper ball, drop paper ball, switch roles, score point.
  • This helps you describe a game clearly even if you are not a gamer.

Game Maker's Toolkit - Think Like A Game Designer

Video
  • Look at games by asking why design choices work.
  • Break a game into actions, rules, feedback, goals, and player decisions.
  • Design is not just having ideas; it is testing why an idea creates an experience.

Adam Millard - Progression Systems

Video
  • Progression is more than numbers going up.
  • Good progression can give new choices, new mastery, new areas, or new understanding.
  • Progression should keep the player engaged without overwhelming them.

Fullerton - Team Structures

Reading
  • Game teams need different roles and clear responsibilities.
  • Designers must communicate with producers, programmers, artists, QA, and others.
  • Inclusive teamwork matters because good ideas can come from anywhere in the team.

Guardiola - Gameplay Loop

Recommended
  • A gameplay loop models repeated player activity.
  • It helps designers understand what the player does again and again.
  • Use loops to explain how mechanics connect to outcomes and motivation.

What To Understand First

This course is not asking you to already be a gamer. It is teaching you how to think like a game maker. That means you look at a game as a system of actions, rules, goals, challenges, players, and feedback.

Player

Who is this game for?

Action

What does the player do?

Loop

What repeats again and again?

Quick Exam Brain

  • Use terms clearly: mechanic, goal, rule, challenge, progression, loop.
  • When explaining your game, describe what players do, not only the story.
  • Keep prototypes small so you can test and improve them fast.
  • When playtesting, ask normal questions. Do not ask players to analyze mechanics for you.

Beginner Roadmap

1. Understand The Game As Actions

Do not begin with story, graphics, or whether you are a gamer. Begin with the player action. In Cup Catch the actions are drop, catch, switch, and count points.

2. Connect Actions To Rules

A rule gives shape to the action. For example: the ball must be dropped from shoulder height, the catcher may only use the cup, and players switch after every drop.

3. Add A Goal And Challenge

The goal is to reach 5 points. The challenge is timing, hand-eye coordination, and the uncertainty of the falling paper ball.

4. Explain The Loop

A loop is the repeated pattern of play. Cup Catch repeats: prepare, drop, catch or miss, score, switch, and try again.

Simple sentence to remember

A game is a set of player actions, controlled by rules, aimed at a goal, made interesting by challenge, and repeated through a loop.

The Basic Game Design Picture

When you explain any game, move from small to big. Start with the player's action, then connect it to rules, goals, challenge, and loop.

Mechanic

What the player does

Rule

What controls that action

Goal

Why the player does it

Challenge

What makes it difficult

Loop

What repeats during play

How Game Roles Work Together

Each role protects one part of the game. The best teams talk often because every change affects other people.

Systems

Rules + mechanics

Experience

Player feeling

Producer

Time + tasks

Programmer

Working systems

Artist

Visual clarity

Sound

Mood + feedback

Deep Lecture Notes

August 24

Intro Lecture

easy notes

What The Course Is Really About

The course is not only about playing games. It is about learning how games are made: how ideas become prototypes, how players react, how teams communicate, and how designers improve a game through feedback.

Prototype Thinking

A prototype is a small test version of an idea. It does not need to look finished. Its job is to answer a question, such as: is this mechanic fun, clear, too easy, too hard, or confusing?

Player, Game, Resources

A game always has players, rules, actions, goals, limits, materials, and time. Resources can be physical objects, player attention, team time, money, skills, or information.

What You Should Take From It

You are allowed to start simple. Your first job is to make something playable, observe people using it, and learn how to talk about why it works or does not work.

What you can say in class

I understand the course as a making-and-testing course. A prototype is not a final game; it is a small experiment that teaches us something.

August 28

Design Lecture + Exercises

easy notes

Game Mechanics

A mechanic is something the player can do inside the rules. Use simple verbs: move, jump, trade, choose, drop, catch, block, collect, inspect, combine, talk, or build.

Core Mechanics

The core mechanic is the action the player repeats most and remembers the game for. In Pac-Man it is moving through a maze while eating pellets and avoiding ghosts. In Cup Catch it is trying to catch the falling paper ball.

Goals And Challenge

A goal gives the player direction. Challenge makes the goal interesting. If there is no challenge, the action can feel pointless. If the challenge is too high, the player may feel lost or frustrated.

Progression

Progression means the game changes over time. It can be harder levels, new abilities, new rules, more pressure, better player skill, new information, or a change in strategy.

What you can say in class

A clear way to explain a game is: the player does an action, under rules, toward a goal, while facing a challenge.

August 31

Roles In Game Development + Prototype 1

easy notes

Why Roles Matter

Games are made by teams because a game needs many kinds of work: rules, code, art, sound, planning, writing, testing, and communication. A role means responsibility, not superiority.

Design Roles

Systems designers care about rules, balance, numbers, and mechanics. Experience designers care about how the player feels, understands, learns, and moves through the game.

Production Roles

A producer helps the team decide what to do now, what can wait, who is responsible, and whether the team is using time realistically. This is especially important in student projects.

Prototype 1 Constraints

Prototype 1 is physical, analog, exactly two players, laugh-out-loud, and radically simple. These limits are helpful because they force you to focus on one clear playable idea.

What you can say in class

The constraints helped me make Cup Catch simple: two players, one cup, one paper ball, clear scoring, and a repeated loop.

September 4

Playtesting, Showcase, And Game Loop

easy notes

Playtesting

Playtesting means letting real people play and watching carefully. You look for confusion, boredom, laughter, tension, unfairness, unclear rules, and moments where the game becomes interesting.

Game Loop

A game loop is the repeated cycle of player activity. It shows what the player does, what result happens, what feedback they receive, and why they want to continue.

Why Loops Are Useful

Loops help you see the whole system. If you change one rule, the difficulty, score, rhythm, and feeling can all change. Designers use loops to understand cause and effect.

Cup Catch Loop

Cup Catch has a very clean loop: prepare, drop, catch or miss, score, switch, repeat. Because the loop is short, players understand the game quickly.

What you can say in class

My game loop is short on purpose. The player immediately understands the action, result, and next turn.

Lectures Step By Step

August 24

Intro Lecture

Course mindset, prototypes, players, teamwork, and what a game wants to be.

  • The course is practice-oriented: you learn by making games, testing them, and improving them.
  • Making a game is not only coding. It also includes design, teamwork, planning, testing, and communication.
  • A prototype is a small playable experiment, not a perfect final game.
  • A good process matters more than making an amazing game at the beginning.
Remember: Ask: who is the player, what does the game want to become, and what resources do I have?

August 28

Design Lecture + Exercises

Game design language: mechanics, goals, rules, challenge, progression, and gates.

  • A mechanic is usually an action the player can do, such as drop, catch, move, trade, jump, or guess.
  • A core mechanic is the repeated action that gives the game its identity.
  • A goal tells the player what they are trying to achieve.
  • Challenge makes the goal meaningful, but the difficulty should fit the player.
  • Progression is how the game changes over time: player skill, abilities, levels, story, resources, or choices.
Remember: Explain a game by saying: the player does X, to reach Y, but Z makes it difficult.

August 31

Roles + Prototype 1 Intro

Game development roles and the physical two-player prototype assignment.

  • Game Designer: Systems works with rules, mechanics, balance, and game logic.
  • Game Designer: Experience focuses on player feeling, usability, controls, UI, and playtesting.
  • Producer organizes time, tasks, milestones, communication, and team health.
  • Programmers and tech leads build and organize the technical systems.
  • Prototype 1 must be physical and analog, exactly two players, funny, and radically simple.
Remember: For Prototype 1, keep it tiny: one repeated action, clear scoring, fast play, and easy rules.

September 4

Prototype 1 Playtesting + Game Loop

Testing prototypes and drawing gameplay loops.

  • Playtesting means watching real people try your game and noticing what works or confuses them.
  • A gameplay loop shows what the player repeatedly does, what reward or result happens, and what they do next.
  • Loops help designers see how mechanics, rewards, outcomes, and player choices connect.
  • If one part of a loop changes, other parts of the game may change too.
Remember: For Cup Catch: drop paper ball -> try to catch -> score or miss -> switch roles -> repeat.

Important Terms

Mechanic

An action the player can do inside the rules of the game.

Core Mechanic

The main repeated action that defines the game.

Rule

What players can and cannot do.

Goal

What the player is trying to achieve.

Challenge

What makes the goal difficult or interesting.

Progression

How the game changes over time.

Game Loop

The repeated cycle of action, result, reward, and next action.

Playtesting

Letting people play so you can learn from their behavior and feedback.

Design Pillars

Short principles that guide design decisions.

Player Experience

What the player feels, understands, and does during play.

Game Team Roles

Systems Designer

Designs rules, mechanics, balance, and how the game works.

Experience Designer

Checks if the game feels good and is understandable for players.

Producer

Keeps the team organized, healthy, and on schedule.

Programmer

Builds the game systems and makes them work.

Tech Lead

Guides technical choices, code structure, and build process.

Artist

Creates visual style, assets, characters, environments, and UI.

Sound Designer

Creates sound effects, music, and audio mood.

Narrative Designer

Works on story, dialogue, choices, and text.

QA / Tester

Finds bugs and checks if the game behaves correctly.

Game Loop Graphics

A game loop is a simple drawing of what repeats. It helps you see how mechanics, results, rewards, and the next decision connect.

Pac-Man

Move through maze
Eat pellets
Avoid ghosts
Clear maze / chase score

Papers, Please

Inspect document
Compare rules
Approve or deny
Earn money / face consequence

Hay Day

Plant crops
Wait / harvest
Produce goods
Sell / upgrade farm

Animal Crossing

Explore town
Collect items
Decorate / talk
Return tomorrow

Cup Catch

Drop ball
Try to catch
Score or miss
Switch roles and repeat

Teacher Questions: Ready Answers

What is your core mechanic?

The core mechanic is catching a falling paper ball with a cup. The game repeats this action many times.

What are the rules?

Two players stand close. One drops the paper ball from shoulder height. The other catches with a cup. Catch gives 1 point. Miss gives 0. Players switch roles after each drop.

What is the goal?

The goal is to be the first player to reach 5 points.

Where is the challenge?

The challenge is timing the cup correctly, reacting quickly, and judging the paper ball's fall.

What is the game loop?

Prepare cup and paper ball, drop, try to catch, score or miss, switch roles, repeat.

Why is it a good Prototype 1 game?

It is analog, two-player, simple, fast to learn, easy to test, and funny when people almost catch the ball.

Prototype 1: Cup Catch

Copy-Ready Submission Text

Cup Catch is a very simple two-player physical game. One player drops a small paper ball, and the other player tries to catch it with a cup. The game uses no screen or digital tools, only one cup and one small paper ball.

Core mechanics: Drop, Catch, Switch, and Score. One player drops the paper ball from shoulder height. The other player tries to catch it with the cup. Players switch roles after each round. A successful catch gives 1 point.

Rules: exactly two players play. Players stand about one arm apart. One player is the Dropper and the other is the Catcher. The Dropper drops the paper ball from shoulder height. If the Catcher catches the ball in the cup, the Catcher scores 1 point. If the ball falls, no point is scored. Players switch roles after every drop. First player to 5 points wins.

Simple Gameplay Picture

Paper ball

Dropper releases the ball

Cup

Catcher tries to catch it

Materials

One cup and one small paper ball.

Players

Exactly two players: one Dropper and one Catcher.

Time

A round takes only a few seconds, so players get many attempts.

Feedback

The feedback is immediate: the ball is either inside the cup or not.

Fairness

Players switch roles after every drop so both players get the same chance.

Difficulty Tuning

Make it easier by standing closer. Make it harder by standing farther away.

Cup Catch Gameplay Loop

1Prepare cup and paper ball
2Dropper drops the ball
3Catcher tries to catch
4Score 1 point or 0 points
5Players switch roles
6Repeat until someone reaches 5 points
Why it fits Prototype 1

It is physical and analog, exactly two players, funny because failed catches are playful, and radically simple because the loop is only drop, catch, switch, score.