
analyze a game with the MDA framework and its core loop, and write specific, evidence-based feedback on a draft design and on my own analysis.
Instruction
When people talk about games they usually talk about feelings: “it’s addictive”, “it’s boring”, “it’s stressful in a good way”. A designer has to trace those feelings back to decisions. The most widely taught tool for doing that is the MDA framework, published in 2004 by Robin Hunicke, Marc LeBlanc and Robert Zubek.
Mechanics, Dynamics, Aesthetics. Mechanics are the rules and actions the designer writes: jump height, how many cards you draw, how much a sword costs. Dynamics are the behavior that emerges when players use those mechanics over time: rushing, hoarding, bluffing, camping in a safe spot. Aesthetics are the emotional responses the player has: challenge, discovery, fellowship, fantasy, expression, tension. The key insight is direction. The designer builds from mechanics toward aesthetics, but the player experiences the game from aesthetics inward: they feel tension before they notice the timer that causes it. Your job in a critique is to work backward from a feeling to the mechanic that produced it.
A worked example: Tag. Mechanics: one player is “it”; touching another player passes “it” on; there is a play area. Dynamics: players cluster near the edges, taunt, and form temporary alliances against whoever is “it”. Aesthetics: chase excitement, near-miss relief, fellowship. Now change one mechanic: add a “safe” base where you cannot be tagged. The dynamic changes (players hover near base, and play slows) and so does the aesthetic (less tension, more waiting). One rule, a different game. That is why designers test small changes.
The core loop. Most games have a short cycle of actions that players repeat hundreds of times. In a platformer it might be see a gap → jump → land → move on. In a farming game, plant → wait → harvest → sell → buy seeds. Draw it as a circle of three to five verbs. The four building blocks of play sit inside it: a goal (what the player wants), an action (what they can do), a challenge (what makes it hard) and a reward (what they get). A loop that is satisfying in thirty seconds can hold players for thirty hours; a loop that is tedious in thirty seconds will not be rescued by a good story.
Immersion is the sense of being absorbed in a game so that the outside world fades. It can come from sensory richness, from challenge that matches skill, or from caring about characters and a world. Ask what each game you analyze does to create it, and what breaks it (a confusing menu, an unfair death, a loading screen at the worst moment).
Player-centric and designer-centric. A player-centric design starts from what its audience wants and tests constantly to deliver it. A designer-centric game starts from what the designer wants to say or explore, and may deliberately frustrate, slow or unsettle players. Papers, Please (Lucas Pope, 2013) makes paperwork tense in order to make players feel the moral weight of a border inspector’s job. Neither approach is wrong, but you should know which one you are judging.
Critique norms. Feedback in this course is specific, tied to evidence and kind. Say what you observed, what effect it had and what you would try. “Your core loop leaves out the reward: what does the player get for landing the jump?” helps. “It’s good” does not. When the work is your own, set it aside for at least a day first, then read it as if a stranger wrote it: the gap of time is what lets you see what is missing.
📖 Read for this lesson
The reading opens over the lesson; close it to come back to exactly where you were. The checks below draw on it.
Formative check
Work through these before moving on. They are not graded — they tell you whether the standard below has landed yet.
In a card game, players start saving their best cards for the final round. In MDA terms, what is “saving cards”?
A designer-centric game is a badly designed game, because it ignores what players want.
For one game you know well, draw its core loop as three to five verbs in a circle and label the goal, action, challenge and reward. Then write one sentence naming an aesthetic the game produces and the mechanic you think causes it. Write one feedback note on the Lunch Dash draft in the reading, and, after at least a day away, a second note on your own loop: what you observed, its effect and one thing to try.
How confident are you that you can analyze a game with MDA and its core loop and give specific, evidence-based feedback?
Practice
Work these on paper or in your notebook, then open Check your answer. Aim for all of Fluency and Application; try at least one Challenge.
Printable version: this unit’s practice workbook (PDF)
Fluency
Build speed and accuracy with the core skill.
- Label each as a mechanic, a dynamic or an aesthetic: (a) how high a character jumps; (b) players camping in a safe spot; (c) tension; (d) the price of a sword; (e) bluffing; (f) fellowship.
Check your answer
Answer: (a) mechanic; (b) dynamic; (c) aesthetic; (d) mechanic; (e) dynamic; (f) aesthetic.Mechanics are written rules and actions; dynamics are behavior that emerges as players use them; aesthetics are the player’s emotional responses. - Name the four building blocks of play that sit inside a core loop, and give each one for the farming loop plant → wait → harvest → sell → buy seeds.
Check your answer
Answer: Goal: grow and sell crops (a bigger farm). Action: plant, harvest, sell. Challenge: waiting and limited money or seeds. Reward: money from selling, which buys more seeds.Any answer that names goal, action, challenge and reward and fits the farming loop is correct. - In one sentence each, define player-centric and designer-centric design, and say which describes Papers, Please.
Check your answer
Answer: Player-centric design starts from what the audience wants and tests constantly to deliver it; designer-centric design starts from what the designer wants to say or explore. Papers, Please is designer-centric.It makes paperwork tense on purpose, to make players feel the moral weight of a border inspector’s job.
Application
Use the skill in context. Show your reasoning.
- Change one mechanic of Tag: “it” must hop on one foot. Predict one new dynamic and one change in aesthetic.
Check your answer
Answer: Model answer: Dynamic: runners stay closer and taunt more, because “it” is slow, and “it” passes on less often. Aesthetic: less chase excitement, more silliness.Strong answers follow the chain mechanic → dynamic → aesthetic, as in the lesson’s safe-base example. Other reasonable predictions are fine. - Rewrite this feedback so it follows the course’s critique norms: “Your game is boring.”
Check your answer
Answer: Model answer: “In my test I waited about a minute between turns with nothing to do (observed). I lost interest and checked the clock (effect). Could each player take a small action during others’ turns (try)?”Must include what was observed, the effect it had and one thing to try, and must be specific and kind. - A draft platformer loop reads see a gap → jump → see the next gap. Which of the four building blocks is missing, and how could you add it?
Check your answer
Answer: The reward. Add something gained for landing, such as a coin, a checkpoint, a sound and sparkle, or progress toward the exit.The goal, action (jump) and challenge (the gap) are there; nothing tells the player the jump paid off. - Name two things the lesson says can break immersion, and for each say what the player suddenly notices instead of the game.
Check your answer
Answer: Any two: a confusing menu (they notice the interface), an unfair death (they notice the rules feel broken), a loading screen at the worst moment (they notice the machine and the wait).Immersion is absorption in the game so the outside world fades; a breaker pulls attention back to the outside world.
Review
Keep earlier skills sharp.
- Review (Lesson 1.2): what is delta, and what goes wrong if you leave it out of a movement line?
Check your answer
Answer: delta is the time in seconds since the last frame. Without it, movement is per frame, so the game runs faster on fast computers and slower on slow ones.At 60 fps delta ≈ 0.0167 s; at 30 fps it is ≈ 0.0333 s, and multiplying by it keeps pixels per second the same.
MDA and the Core Loop: Two Worked Analyses, a Draft to Critique and a Model Feedback Note
SLS original analyses; MDA framework paraphrased from Hunicke, LeBlanc and Zubek, ‘MDA: A Formal Approach to Game Design and Game Research’ (2004), not hosted · SLS original
Why this reading. The critique lab asks you to draw a core loop, name an aesthetic and its cause, and write a feedback note on a draft and on your own work. This reading models all three on games you can check: a worked MDA table and core loop for mancala and Spacewar!, a draft with a flaw in it to critique, and a model feedback note. The MDA framework is from Hunicke, LeBlanc and Zubek (2004), which is freely available but not openly licensed, so I paraphrase it and do not reproduce it.
The eight aesthetics in the MDA paper
The authors name eight kinds of player response and describe each in a phrase: sensation (game as sense-pleasure), fantasy (make-believe), narrative (drama), challenge (an obstacle course), fellowship (a social framework), discovery (uncharted territory), expression (self-discovery) and submission (a pastime). Most games pursue several in different amounts.
Worked MDA analyses (SLS original)
| Mancala (rules in Reading 1.1) | Spacewar! | |
|---|---|---|
| Mechanics | Sow seeds one per pit; last seed in your store earns an extra turn; last seed in your empty pit captures the seeds opposite | Rotate, thrust, torpedoes, star gravity, screen wraparound |
| Dynamics | Players count ahead to time an extra-turn chain; they hoard seeds in one pit to set up a big capture; they leave a weak pit exposed as bait | Players circle the star to build speed, then fire on the way out; they hide behind the pull of the star; they waste torpedoes early and regret it |
| Aesthetics | Challenge (planning), fellowship (talk across the board) | Challenge (aim and orbit), sensation (the swoop of a slingshot) |
| One-rule change | Remove the extra turn: chains vanish, planning shrinks to one move, the game feels flatter | Turn off the star: orbits vanish, and the game becomes a duel in empty space |
Core loops, labeled
Mancala: look at the board → choose a pit → sow → capture or take an extra turn. Goal: more seeds in your store. Action: choose a pit. Challenge: the opponent’s counter-captures. Reward: seeds banked, and the small win of a chain.
Spacewar!: read the other ship → rotate and thrust → fire → recover from the star. Goal: destroy the opponent. Action: steer. Challenge: gravity and limited fuel. Reward: a hit, or a clean escape.
A draft to critique (invented for practice)
Lunch Dash (draft). Two players race a coin across a 10-space track. On your turn roll one die and move that many spaces. If you land on a space with a star, take another turn. First to space 10 wins. Core loop: roll, move, land, repeat. Aesthetic: excitement.
A model feedback note
What I observed: the loop “roll, move, land” has no decision in it. The only choice is which die face comes up, and that is chance. Effect: a player can finish the game without ever choosing anything, so the aesthetic will be luck, not excitement. Try: let players choose between moving the coin and moving the opponent’s coin back one space, and see whether the game creates the excitement you named.
Notice the parts: an observation you can point to, the effect on the player, and one thing to test. “It’s boring” has none of them.
Sources: Hunicke, LeBlanc and Zubek, MDA: A Formal Approach to Game Design and Game Research (2004) (users.cs.northwestern.edu)