44. Lesson identity
This lesson names how the player receives one mapped loop. It does not teach animation, sound design, VFX, or a juice checklist. It does not teach Lesson 2 of this module.
45. Learning objective
After this lesson, you can distinguish a system result from a player-perceived result, name response, follow-through, and confirmation on a short action, and judge whether that action is CLEAR, UNCLEAR, or OVERSTATED for the next decision.
46. Why this matters
Module 1.1 asked you to recognize, map, and protect one game loop. Mapping is not yet receiving.
A mechanic can be correct and still feel unclear, weak, delayed, unresponsive, noisy, or disconnected. Game feel is not “make it pretty.” It is how the game communicates ACT, RESPOND, CHANGE, and consequence so the player can take the next step.
The new question: Can the player perceive RESPOND and CHANGE strongly enough to make the next decision?
47. Prior knowledge
Module 1.1: you can map one small repeating behavior as ACT → RESPOND → CHANGE → AGAIN, and decide which additions support that bounded loop. This lesson does not repeat those drills. It asks how the player receives a response or change you can already point at.
48. Core concept — system result vs player-perceived result
System result — what the simulation actually did. The enemy lost 10 health. A passage stopped blocking. The collectible count incremented.
Player-perceived result — whether the player can perceive that the action connected and mattered. That may use visibility, sound, motion, timing, a state display, or a consequence. Those are possible channels, not a mandatory effects list.
A change that exists internally but is not legible can make a functioning mechanic feel broken or weak.
You are still using the analytical model from Module 1.1. You are not yet using a later implementation model for building a playable micro-loop.
49. Mental model — response, follow-through, confirmation
Use this as a practical Stage 1 working model for inspecting how a short action is received by the player. It is not a universal taxonomy of all game feel.
“Contract with the player’s body” is a memorable metaphor. The teaching here is perception, timing, interpretation, cause and effect, and the next decision — not that every feel must be a literal physical sensation.
response — immediate acknowledgement that the game received or responded to the player’s action. It can be subtle. It is not “equals animation.”
follow-through — the response continues, persists, or develops long enough for the player to follow its effect rather than losing it immediately. It can be very short. It is not “equals a long animation.”
confirmation — the player can understand what result occurred, what changed, and why that result matters for the next ACT. It can come from the resulting world state itself. It is not “equals HUD.”
One visual event may serve more than one of these functions. The criterion is readability and meaning, not effect quantity. A quiet latch that finishes moving can honor the contract. A giant explosion for a tiny press can break it.
50. Concrete examples
Attack. Case A: health drops internally; nothing visible or audible. Same damage logic as Case B: the enemy reacts, a small state change is visible, timing ties it to the swing. Case A is a system result. Case B is a player-perceived result.
Door. A blocking passage is removed in the simulation versus the player can see that the way through is now open. The player needs to know the path changed.
Collect. The count increments versus evidence the item was taken — enough to decide whether to search again.
Three short cases. None of them require an engine. None of them say “add more effects.”
51. Boundary
This is not animation theory, sound design, VFX, camera shake, UI polish, or accessibility as a course. Some feedback can be polished later. The ability to perceive cause and effect is part of whether the behavior works as an experience.
Game feel is not equivalent to more effects. A huge explosion for a tiny action can be poor feedback. A subtle, immediate state change can be excellent feedback.
Ask whether the player understands: what happened, whether their action mattered, what changed, what they can do next.
An AI agent can implement effects rapidly. You still decide what the player must perceive and why. This lesson does not ask you to prompt an agent or edit a project.
52. Common mistakes
The state changed in code, so the player knows. Code is not perception. Name what the player can actually read.
More effects automatically means better game feel. Spectacle can hide CHANGE or delay AGAIN.
Game feel comes after gameplay. Cosmetic extras can wait. Unreadable cause and effect is not a finished loop.
Clarity is spectacle. Confirmation can be small. Overstated feedback is not stronger feel.
53. Practice
These labels are judgments for this lesson, not universal scores.
CLEAR — the player can perceive and interpret enough of the result to make the next decision.
UNCLEAR — the system changed, but the player lacks or may miss information needed to interpret the result.
OVERSTATED — the feedback overwhelms, delays, or distorts the result instead of making the next decision clearer.
Worked example
Situation: you pull a lever. The system removes the blocking state of the passage — crossing is now possible. The lever and the gate look exactly as they did. You have no evidence that walking through will work.
System result: the passage is traversable; that change is relevant to the next action. Player-perceived result: none. UNCLEAR. The next decision (cross) has no readable evidence that the relevant state changed.
Classify perception
Each situation below already works as a mechanic. Classify how the player receives it: CLEAR, UNCLEAR, or OVERSTATED. Write one sentence saying whether the player can perceive what happened, understand what changed, and what decision follows. Do not ask an AI to classify them.
Item 4 is thin on purpose. More than one label can be defensible if you name what is missing.
Try first. Compare with the notes only after you have written your own labels and sentences.
1. You swing. The enemy loses 10 health internally. Nothing moves, flashes, or sounds. The next swing looks identical.
2. You swing. The enemy flinches on the hit and settles through a brief recovery that is long enough to register. A small health or state mark changes. The timing clearly ties the reaction to that swing. You can decide whether to swing again or move.
3. You press a tiny floor switch. A four-second explosion fills the screen, the camera slams, and play freezes before the door actually opens.
4. (ambiguous — reasoning required) You pick a herb. The herb vanishes. A small number in the corner of the screen increases by one. Nothing else happens in the world.
Notes after you try
1. UNCLEAR. UNCLEAR. There is a system result (health dropped) and almost no player-perceived result. Both immediate response and readable confirmation are absent here. Follow-through cannot be judged because no perceptible event continues or develops. The player cannot recognize that the attack connected or what to do next.
2. CLEAR. CLEAR. Response (the flinch begins on impact), follow-through (the brief recovery persists long enough to register), and confirmation (a visible state change) help the player interpret RESPOND and CHANGE. Not a particle checklist — a readable connection.
3. OVERSTATED. OVERSTATED. Spectacle is not confirmation. The explosion delays and drowns the actual CHANGE (the door). More effects made the next decision harder, not clearer.
4. Reasoning. Ambiguous on purpose. The herb disappearing MAY itself confirm that the object was collected. The corner counter MAY additionally confirm that quantity increased. CLEAR is defensible if disappearance clearly acknowledges collection, the counter visibly confirms quantity, and that information is enough for the next decision. UNCLEAR is defensible if the quantity or state the player needs for the next decision is easy to miss — disappearance may communicate removal without communicating the state information they need. OVERSTATED does not fit: there is too little signal, not too much. Feedback quality depends on the information the current behavior requires.
Practical check
Select one repeated player input and write its feedback contract: what the player sees, hears, and feels; how quickly each response occurs; and what consistent outcome the player should learn to expect.
Ten-second action
Imagine one 10-second action — a press, a pickup, a swing, an open. Label response, follow-through, and confirmation in one line each, or name which one is missing. Thought experiment only. No engine.
Your own idea
Return to one loop you mapped in Module 1.1. Choose one RESPOND or CHANGE inside it. Answer in a few words: How would the player know this happened? Do not build or polish. Do not list multiple feedback channels.
54. Validation / self-check
Point at the short action:
What is the system result?
What can the player actually perceive?
Where are response, follow-through, and confirmation — or which is missing?
Is this CLEAR, UNCLEAR, or OVERSTATED for the next decision?
If you only named effects, you have not yet named the contract.
55. Key takeaways
A system result is not automatically a player-perceived result.
Game feel is how the player receives RESPOND and CHANGE, not decoration.
Name response, follow-through, and confirmation — a Stage 1 working model for perception, not a universal law or an effects checklist.
More effects are not automatically better feel.
Some polish can wait; unreadable cause and effect cannot pretend the loop already works as an experience.
56. Knowledge check
Answer these five items for yourself before reading the answers. This check covers system vs perceived results, more effects, polish-later, OVERSTATED vs CLEAR, and practical labeling of response, follow-through, and confirmation.
The enemy loses 10 health in the simulation. Nothing the player can see or hear changes. This is closest to:
Answer: A system result without a player-perceived result
Why: The mechanic can be correct internally and still fail as an experience if the player cannot perceive the response or the change.
Adding more screen shake, particles, and sound automatically improves game feel.
Answer: False
Why: Feedback quality depends on whether the player can perceive what happened, recognize that the action mattered, understand what changed, and know what to do next. Spectacle can hide that.
Game feel is only polish added after the real game already works.
Answer: False
Why: Some cosmetic work can wait. The player’s ability to perceive cause and effect is part of whether the behavior works as an experience. Not every extra effect is foundational.
A coin pickup is correct in the count. It also triggers a long explosion and freeze before the player can move again. Best label:
Answer: OVERSTATED
Why: The collect registered, but the spectacle delays the next decision and overpowers a tiny CHANGE. Clarity is not the same as spectacle.
You press a wall button. Its lamp lights immediately and stays lit for half a second. A nearby door opens and remains visibly open, so you can decide to cross. Which labeling best fits this action?
Answer: Response: the lamp lights immediately; follow-through: it remains lit briefly; confirmation: the door remains visibly open
Why: The immediate timing of the lamp provides response; its brief persistence provides follow-through; and the readable resulting state of the open door confirms the change and supports the next decision. Score the functions by timing, persistence, readable state change, and support for what the player does next—not by the number of effects.
57. Connection to the next lesson
The next lesson in module 1.2 will ask you to describe a moment that can be correct in the system and still dead in play. Do not do that work yet. Leave this lesson when you can tell a silent internal change from a result the player can actually read.
58. Knowledge check
Answer these items for yourself before reading the answers.
The enemy loses 10 health in the simulation. Nothing the player can see or hear changes. This is closest to:
Show answer and feedback
Answer: A system result without a player-perceived result
Why: The mechanic can be correct internally and still fail as an experience if the player cannot perceive the response or the change.
Adding more screen shake, particles, and sound automatically improves game feel.
Show answer and feedback
Answer: False
Why: Feedback quality depends on whether the player can perceive what happened, recognize that the action mattered, understand what changed, and know what to do next. Spectacle can hide that.
Game feel is only polish added after the real game already works.
Show answer and feedback
Answer: False
Why: Some cosmetic work can wait. The player’s ability to perceive cause and effect is part of whether the behavior works as an experience. Not every extra effect is foundational.
A coin pickup is correct in the count. It also triggers a long explosion and freeze before the player can move again. Best label:
Show answer and feedback
Answer: OVERSTATED
Why: The collect registered, but the spectacle delays the next decision and overpowers a tiny CHANGE. Clarity is not the same as spectacle.
You press a wall button. Its lamp lights immediately and stays lit for half a second. A nearby door opens and remains visibly open, so you can decide to cross. Which labeling best fits this action?
Show answer and feedback
Answer: Response: the lamp lights immediately; follow-through: it remains lit briefly; confirmation: the door remains visibly open
Why: The immediate timing of the lamp provides response; its brief persistence provides follow-through; and the readable resulting state of the open door confirms the change and supports the next decision. Score the functions by timing, persistence, readable state change, and support for what the player does next—not by the number of effects.