Course Mindset
The course teaches process: make small games, test them, learn from players, and improve.
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.
The course teaches process: make small games, test them, learn from players, and improve.
Use clear words: mechanic, rule, goal, challenge, progression, player experience, and loop.
Games are made by roles working together: designers, producers, programmers, artists, sound, writing, QA.
A loop shows what the player repeatedly does and how actions connect to outcomes and rewards.
August 24
August 28
August 31
September 4
August 24 section
https://learnit.itu.dk/course/section.php?id=170413
Intro lecture, Rego intro slides, course structure, expectations, prototypes, and design vocabulary.
August 28 section
https://learnit.itu.dk/course/section.php?id=170414
Design terminology, mechanics, goals, challenge, progression, readings, and videos.
August 31 section
https://learnit.itu.dk/course/section.php?id=170415
Roles in game development, Fullerton team structures, and Prototype 1 intro.
September 4 section
https://learnit.itu.dk/course/section.php?id=170416
Prototype 1 playtesting, showcase, and game loop lecture.
The LearnIT links may require your ITU login. The explanations on this page are written from the local PDFs and course text you provided.
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
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.
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.
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.
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 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.
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
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.
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 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.
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 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 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.
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
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.
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.
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.
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.
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.
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.
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 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
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.
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.
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.
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.
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.
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.
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.
This is the easiest order for understanding almost every lecture.
Player
The person taking action
Mechanic
The action they can do
Rule
The limit around the action
Goal
The reason to act
Challenge
The difficulty or obstacle
Feedback
The result the player sees or feels
Loop
The repeated cycle of action and result
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?
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.
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.
The goal is to reach 5 points. The challenge is timing, hand-eye coordination, and the uncertainty of the falling paper ball.
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.
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
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
August 24
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.
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?
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.
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
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.
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.
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 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
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.
Systems designers care about rules, balance, numbers, and mechanics. Experience designers care about how the player feels, understands, learns, and moves through the game.
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 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 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.
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.
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 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.
August 24
Course mindset, prototypes, players, teamwork, and what a game wants to be.
August 28
Game design language: mechanics, goals, rules, challenge, progression, and gates.
August 31
Game development roles and the physical two-player prototype assignment.
September 4
Testing prototypes and drawing gameplay loops.
An action the player can do inside the rules of the game.
The main repeated action that defines the game.
What players can and cannot do.
What the player is trying to achieve.
What makes the goal difficult or interesting.
How the game changes over time.
The repeated cycle of action, result, reward, and next action.
Letting people play so you can learn from their behavior and feedback.
Short principles that guide design decisions.
What the player feels, understands, and does during play.
Designs rules, mechanics, balance, and how the game works.
Checks if the game feels good and is understandable for players.
Keeps the team organized, healthy, and on schedule.
Builds the game systems and makes them work.
Guides technical choices, code structure, and build process.
Creates visual style, assets, characters, environments, and UI.
Creates sound effects, music, and audio mood.
Works on story, dialogue, choices, and text.
Finds bugs and checks if the game behaves correctly.
A game loop is a simple drawing of what repeats. It helps you see how mechanics, results, rewards, and the next decision connect.
The core mechanic is catching a falling paper ball with a cup. The game repeats this action many times.
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.
The goal is to be the first player to reach 5 points.
The challenge is timing the cup correctly, reacting quickly, and judging the paper ball's fall.
Prepare cup and paper ball, drop, try to catch, score or miss, switch roles, repeat.
It is analog, two-player, simple, fast to learn, easy to test, and funny when people almost catch the ball.
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.
Dropper releases the ball
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.
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.