
identify mechanics such as scoring, resource management and movement, explain how they combine into systems with positive and negative feedback loops, and critique a draft rule set for balance.
Instruction
A single mechanic is a word; a system is a sentence. Designers spend most of their time not inventing mechanics but deciding how mechanics affect each other.
Common mechanics. Scoring measures progress and defines what players value: if collecting gems scores and defeating enemies does not, players will avoid fights. Resource management gives players something scarce to spend (health, money, time, cards, ammunition) and forces trade-offs. Movement determines how players move through space: speed, jumping, turning, momentum. Others include turn order, chance (dice, shuffled decks, random drops), trading, building and capture.
Systems. A system is a set of mechanics that feed each other. In many strategy games, gathering wood (resource) lets you build a farm (building), which produces food (resource) that trains soldiers (units) that protect the gatherers. Change the cost of one link and the whole chain shifts. Systems thinking means asking “if I change this, what else changes?” before you change it.
Feedback loops. Two kinds of loop decide whether a game stays close or runs away. A positive feedback loop rewards success with more power: in Monopoly, owning more property brings more rent, which buys more property. Positive loops end games decisively, but can make the last hour a foregone conclusion. A negative feedback loop pushes back against the leader or helps whoever is behind. Many kart-racing games give better random items to players further back, which keeps races close. Negative loops create comebacks, but overdone they make skill feel pointless. Good designs usually combine both: a positive loop to let skilled play pay off and a negative loop to keep losing players engaged.
Chance and balance on paper. Dice are the paper designer’s random number generator, and their odds are easy to compute. With two six-sided dice there are 36 equally likely outcomes. A sum of 7 happens 6 ways (1+6, 2+5, 3+4, 4+3, 5+2, 6+1), so 6/36 = 1/6, about 17% of the time. A sum of 12 happens only one way: 1/36, under 3%. If a powerful card triggers on a 12, players will almost never see it; if it triggers on 10 or more (6 outcomes, also 1/6), they will see it about once every six rolls. Doing this arithmetic before a playtest lets you test the feel rather than rediscover the math.
Warning signs in a rule set. A dominant strategy is one choice that is always best, which removes real decisions. A runaway leader signals an unchecked positive loop. A dead turn is a turn when a player can do nothing meaningful. Unclear rules produce arguments rather than play. When you critique, name the sign, point to the rule that causes it and suggest a test.
Critique norms for today. Critique the rules, not the person, including when the designer is you. Read your own draft as if a stranger wrote it, ideally after a day away, and end every critique with one “I wonder what would happen if…” suggestion. On a studio team the designer listens first and asks questions second rather than defending; do the same when a family playtester comments on your game. Accepting feedback is a professional skill: write it down, thank the person and decide later what to act on.
📖 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, whoever has the most cards draws two extra cards each turn. What kind of loop is this, and what risk does it create?
Rolling two six-sided dice gives 36 equally likely outcomes. A sum of 11 happens ways, so its probability is /36.
Read the Orchard Race draft in the reading, then your own draft rule set after at least a day away. For each, name one mechanic, one system (two or more mechanics that feed each other) and one feedback loop. Identify one warning sign (dominant strategy, runaway leader, dead turn or unclear rule), point to the rule that causes it and write one “I wonder what would happen if…” suggestion. Then write which point in your own draft you will test first.
How confident are you that you can explain how mechanics combine into systems and feedback loops, and critique a rule set for balance?
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.
- Define a positive feedback loop and a negative feedback loop, and give the lesson’s example of each.
Check your answer
Answer: Positive: success brings more power, so leaders pull ahead (Monopoly: more property, more rent, more property). Negative: the system pushes back against the leader or helps whoever is behind (kart racers giving better random items to players further back).Positive loops end games decisively; negative loops create comebacks. Good designs usually combine both. - Name the warning sign: (a) one choice is always best; (b) on some turns a player can do nothing meaningful; (c) the player in front keeps getting stronger until the end is a foregone conclusion; (d) players argue about what a rule means.
Check your answer
Answer: (a) dominant strategy; (b) dead turn; (c) runaway leader (an unchecked positive loop); (d) unclear rules.When you critique, name the sign, point to the rule that causes it and suggest a test. - If collecting gems scores points and defeating enemies does not, what will players tend to do, and what does that show about scoring?
Check your answer
Answer: They will avoid fights and go for gems. Scoring defines what players value.Scoring is a mechanic that steers behavior, so choose what you score on purpose.
Application
Use the skill in context. Show your reasoning.
- With two six-sided dice, how many ways can you roll a sum of 9, and what is the probability (as a fraction and a percent to the nearest whole number)?
Check your answer
Answer: 4 ways; 4/36 = 1/9, about 11%.3+6, 4+5, 5+4, 6+3 = 4 ways out of 36. 4 ÷ 36 ≈ 0.111. - A rule triggers a bonus on a roll of 2 or 12 with two dice. What is the probability? About how many times would players see it in 72 rolls?
Check your answer
Answer: 2/36 = 1/18, about 5.6%; about 4 times in 72 rolls.A sum of 2 (1+1) and a sum of 12 (6+6) each happen one way: 2 outcomes out of 36. 72 × 2/36 = 4. - In a racing board game, the player in last place moves one extra space each turn. What kind of loop is this, what does it create, and what happens if it is overdone?
Check your answer
Answer: A negative feedback loop. It creates comebacks and keeps the race close, but overdone it makes skill feel pointless.The lesson recommends pairing a negative loop with a positive one so skilled play still pays off. - Critique this draft rule: “On your turn, you may spend 1 coin to Attack. An Attack always wins 3 coins.” Name the warning sign, point to the rule and write one “I wonder what would happen if…” suggestion.
Check your answer
Answer: Dominant strategy: spending 1 to always gain 3 means attacking is always best. Model suggestion: “I wonder what would happen if an Attack succeeded only on a die roll of 4 or higher?”Must name the sign, tie it to the exact rule and suggest a test, not a verdict. (A roll of 4 or more on one die succeeds 3/6 = half the time, which would make the Attack a real choice.) - A family playtester says your game drags. Following the lesson’s critique norms for designers, write what you do in the moment and afterward.
Check your answer
Answer: In the moment: listen first, ask questions second, do not defend; write the comment down and thank them. Afterward: decide what to act on, ideally after a day away, and test one change.Accepting feedback is a professional skill.
Review
Keep earlier skills sharp.
- Review (Lesson 2.1): what is the difference between alpha and beta?
Check your answer
Answer: Alpha: every feature is in, even if rough. Beta: all content is in and the team is mainly fixing bugs.Both are production milestones that mark progress.
Orchard Race: A Rule Set to Critique, and Feedback Loops Worked Turn by Turn
SLS original; tables computed by simulation of the stated rules · SLS original
Why this reading. The lab asks you to name a mechanic, a system and a feedback loop in a rule set (the draft below, then your own), spot a warning sign and suggest a test. This reading gives you a complete two-player rule set with a flaw in it, a turn-by-turn table showing a positive loop and then a negative loop, the full dice table, and a model critique. The game, table and critique are SLS original.
Orchard Race, draft 0.1 (a rule set to critique)
- Each player starts with trees and 0 apples. Player 1 starts with 2 trees, player 2 with 1 tree.
- Each round, both players harvest: 1 apple for every tree they own.
- Then each player may trade 3 apples for a new tree, as many times as they can afford.
- After 8 rounds, the player with more trees wins.
Turn-by-turn table (draft 0.1, positive loop only)
| Round | P1 trees | P1 apples left | P2 trees | P2 apples left |
|---|---|---|---|---|
| 1 | 2 | 2 | 1 | 1 |
| 2 | 3 | 1 | 1 | 2 |
| 3 | 4 | 1 | 2 | 0 |
| 4 | 5 | 2 | 2 | 2 |
| 5 | 7 | 1 | 3 | 1 |
| 6 | 9 | 2 | 4 | 1 |
| 7 | 12 | 2 | 5 | 2 |
| 8 | 16 | 2 | 7 | 1 |
Check round 2 by hand: P1 has 2 trees and 2 apples; harvests 2 more to reach 4, spends 3 for a tree, keeps 1: 3 trees, 1 apple. P2 has 1 tree and 1 apple; harvests 1 to reach 2; cannot buy. Extend the table to round 10 and check: P1 22 trees and 0 apples after round 9, then 29 and 1; P2 9 trees and 2 apples after round 9, then 12 and 2.
Adding a negative loop
Draft 0.2 adds: the player with fewer trees harvests 1 bonus apple. Same start, same trade rule:
| Round | P1 trees | P1 apples left | P2 trees | P2 apples left |
|---|---|---|---|---|
| 1 | 2 | 2 | 1 | 2 |
| 2 | 3 | 1 | 2 | 1 |
| 3 | 4 | 1 | 3 | 1 |
| 4 | 5 | 2 | 4 | 2 |
| 5 | 7 | 1 | 6 | 1 |
| 6 | 9 | 2 | 8 | 2 |
| 7 | 12 | 2 | 11 | 2 |
| 8 | 16 | 2 | 15 | 2 |
After 8 rounds, draft 0.1 has 16 trees against 7 (a gap of 9); draft 0.2 has 16 against 15 (a gap of 1). The bonus is a negative loop: the trailing player grows faster. Notice that both drafts still grow explosively: the positive loop (trees make apples make trees) is still there, and the negative loop only limits how far the leader gets ahead.
Dice odds for chance-based rules
| Sum | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Ways (of 36) | 1 | 2 | 3 | 4 | 5 | 6 | 5 | 4 | 3 | 2 | 1 |
A card that triggers on a sum of 10 or more happens 3 + 2 + 1 = 6 ways, 6/36 = 1/6, about 17 percent. A sum of 11 happens 2 ways, 2/36, about 5.6 percent.
Model critique of draft 0.1
Mechanic: harvest one apple per tree (rule 2). System: harvest plus trade (rules 2 and 3) feed each other. Feedback loop: positive, since trees make apples make trees. Warning sign: runaway leader, caused by rule 1, which lets Player 1 start ahead and rule 2, which pays more to whoever owns more. Also a possible dead turn: in round 1 Player 2 has 1 apple and nothing to decide. I wonder what would happen if the trailing player harvested a bonus apple? Test it on paper first, as above.