Game feel is often treated as polish.
Several times, people have told me, “Your prototypes are super polished,” even when there was almost nothing there except responsiveness, signs, and feedback. But animation, sound, effects, camera shake, timing, and so-called juice are not only decoration. They are the manifestation of a phenomenon. They are how the prototype makes its idea felt.
I will leave my prototyping process for another post, but one point matters here: not every prototype is trying to answer the same question. A technical prototype tests feasibility. A proof of concept tests whether an idea can exist. A mechanic prototype tests whether a rule produces interesting behavior. A toy prototype tests whether the player wants to keep touching, moving, pressing, throwing, bouncing, repeating.
Depending on what you want to show, you cannot ignore the signs, feedback, and sensory elements that make the intention legible. If they are too vague, testers may not understand what the prototype means to convey. The idea may be judged as failed when the real failure was communication.
In games, emotional response matters early. A player can relate to a placeholder box as if it were a character, if the response is clear enough. But it is hard to judge an idea when the level of abstraction is so high that nothing clicks.
Feel is not decoration, polish, or juice. Feel is the first proof that the mechanic is speaking back to the player. You need to use everything available: input response, animation, sound, timing, effects, resistance, and rhythm, to convey the sensation you want the player to experience. In a toy prototype, for instance, if the player does not want to keep playing with the toy, the problem may not be the rule itself. The problem may be that the toy does not yet answer the player in a way that invites continued touch.
A mechanic can be logically correct and still feel dead. The input can work. The collision can work. The animation can play. The sound can trigger. The numbers can be balanced. But if the player does not feel contact, resistance, intention, and response, the system remains abstract.
This is where tegotae enters.
Tegotae is the sensation of response. The feeling that something answered your action. In games, it is the difference between pressing a button and touching another world.
The idea may be judged as failed when the real failure was communication.
The Player Feels the System Before Reading It
A player does not experience code directly. They experience mechanics as a chain of intention, action, reaction, and feedback.
Before the player fully understands the rule, they feel the response. They notice whether the system feels alive, fake, or dead. They may not yet understand every part of the mechanic, but they can already sense whether the game is answering them.
This means that every playable object has three layers:
The functional layer: what the system actually does. Its rules, states, transitions, and conditions.
The contact layer: how the player feels the system answering. Its timing, feedback, signs, resistance, animation, sound, and responsiveness.
The relational layer: how the object affects, modifies, or gives meaning to other entities in the world.
For example, the functional layer says: When I press this button, the character becomes hot. The contact layer says: The heat rises progressively, so I feel that I need to keep the button pressed. The relational layer says: This heat changes the surrounding world. Nearby objects receive a progressive red gradient within a certain range, showing that the character’s state is affecting the environment.
When the contact layer is weak, the player may understand the mechanic but not desire it.
When the contact layer is strong, even a simple action can become something the player repeats for pleasure.
Before the player fully understands the rule, they feel the response.
A toy begins to live when the player wants to repeat the interaction before being asked to score, win, or optimize anything, he keeps playing with, trying things without you've asked to do anything.
Tegotae Begins with Responsiveness
The first ingredient of tegotae is responsiveness.
An input does not always need to produce its final result instantly, but it must always be acknowledged intentionally. Latency is deadly because it separates the player’s action from the game’s answer. The moment the player presses a button and nothing seems to happen, the connection begins to break.
This does not mean every action must be immediate. Some actions need delay. A heavy hammer may need a wind-up. A spell may need to charge. A machine may need to click, lock, and release. A body may crouch before jumping. These delays can feel powerful, elastic, magical, or physical, but only if the player feels that the action has already begun.
That is the important distinction.
A delayed result can work. An ignored input cannot.
A punch that triggers late feels broken. A heavy hammer that begins with a clear wind-up can feel powerful. A jump that ignores input feels unfair. A jump with a tiny crouch before launch can feel alive.
The question is not simply:
Is the response immediate?
The better question is:
Does the system acknowledge the input immediately, and does the timing of the response match the fantasy of the action?
Responsiveness is not only speed. It is the agreement between input timing, player intention, and action meaning.
A delayed result can work. An ignored input cannot.
Physicality makes the object believable
The second ingredient is physicality.
Physicality does not mean realism. A cartoon character, a cube, a die, a slime, a robot, or a magic object can all feel physical without being realistic.
Physicality means the player can sense that the object belongs to its world.
It has mass. It has material. It has friction. It has elasticity. It has a way of starting, stopping, bending, bouncing, absorbing, or resisting force.
A good game object gives the player enough physical clues to predict what might happen next. It does not need to obey real physics perfectly. It needs to obey its own physical promise consistently.
A rubber object should not answer like stone. A heavy object should not stop like paper. A fragile object should not absorb impact without consequence. A living object should not react like a dead mesh.
The player is constantly asking, often unconsciously:
Does this thing behave like what it appears to be?
When the answer is yes, trust grows. When trust grows, the player starts playing with intention instead of fighting interpretation.
Animation is not cosmetic
Animation is one of the strongest bridges between function and feel.
The classic principles of animation are not only for cutscenes or character acting. They are design tools for player comprehension.
Squash and stretch can reveal force, elasticity, and impact.
Anticipation can prepare the player for an action before it happens.
Follow-through can make motion feel continuous instead of mechanical.
Slow in and slow out can communicate acceleration, weight, and control.
Arcs can make motion feel organic instead of artificial.
Exaggeration can clarify what would otherwise be too subtle to read during play.
Tuning the combination of these elements with immediate input feedback can make tegotae happen.
Feedback Teaches Pacing
A common mistake is to treat feedback as simple confirmation: the button was pressed, the state changed, the effect played. But good feedback does more than report that something happened. It teaches the player how the action should be felt, repeated, charged, released, or interrupted.
Feedback carries rhythm. It can express success or failure, intensity, direction, intention, and timing.
That is why tegotae requires feedback hierarchy.
The most important player-facing event must speak the loudest. Secondary information must support it. Decorative information must stay quiet enough not to compete.
When every effect screams, the player hears nothing.
Feedback does not only confirm state change. It teaches rhythm, timing, intensity, and priority.
Intuitive controls
Controls are not separate from game feel.
Controls are the player’s body inside the system.
A mechanic can have beautiful animation and still feel wrong if the input mapping does not match the expected action. The player does not only ask whether the object reacts. The player asks whether the object reacts as an extension of their intention.
This is why familiar models are powerful.
If the player pushes forward, they expect movement away from them, or movement relative to the camera direction, depending on the genre and camera convention. If the player holds a button, they expect continuation, charge, aim, grip, pressure, or commitment. If the player releases a button, they expect launch, cancel, drop, confirm, or relief. If a button toggles a state, the player needs to understand the state clearly: when it is active, when it is inactive, when it can be used again, and what resets it.
Every input carries a cultural and bodily expectation.
Good controls respect that expectation, or deliberately reshape it with care. They sit on top of common human perception, and conventions already taught by other systems.
Good controls do not begin from the button. They begin from what the player already believes the button means.
Bad controls accidentally violate it.
How to Test for Tegotae?
The first question is simple:
How does it feel? No theory. No justification. No second thought. Just the first perception.
That first perception matters. If the answer is, “I felt nothing, it just responded,” then the interaction is not yet speaking clearly enough.
The next question is:
What do I want the player to feel? The player should sense weight, material, force, friction, elasticity, pressure, resistance, or life. Even abstract objects need some form of body. Without body, there is no contact. Without contact, there is no tegotae.
Then ask:
Did the feedback explain the result of my intention? The player should understand whether the action succeeded, failed, transformed, charged, buffered, hit, missed, or produced a partial result.
Feedback must reduce ambiguity without killing discovery.
Finally, ask the brutal question:
Did I honestly want to do it again?
Before score, before progression, before reward, before mastery, does the interaction invite repetition?
That desire to repeat is often the first sign that a toy is alive.
Closing thought
Designing Tegotae means designing the moment where player intention meets world response.
It is not only animation. Not only physics. Not only controls. Not only sound. Not only feedback.
It is the agreement between all of them.
The input says: Do it!
The mechanic says: this is what I do.
Tegotae says: this is what it feels like to do it.