Game Feel — the difference between landing and happening
The action RPG's stage 06 is the almanac's first pass at feel — "the juice," one sitting, on one sword. This shelf is the general treatment: the same instincts (the hit lands, the push reads, the screen answers) pulled out of that one stage and made into a system you can apply to any game, in any order, at any count.
The definition the shelf works from: feel is the time between the event and the perception
of it, filled with intent. A damage event is a frame — the hitbox's active tick, the
damage_received signal, the float text's spawn. A felt damage event is that frame plus
the flash, the stop, the thock, the shove — a handful of frames of consequence the player's
eye and ear read as "that connected." Without the consequence, the event happens (a number
changes, a health bar moves); with it, the event lands. The shelf builds the consequence,
one sense at a time, and part 04 is where it learns to stop.
What this shelf teaches#
| Part | You build | Right when |
|---|---|---|
| 01 | The hit-flash and the hit-stop, on the damage frame, in the right order | A hit changes a number and the player has to check it |
| 02 | The impulse + damping, and the composition of the forces that share a frame | A hit does damage and the target stays where it was |
| 03 | The camera shake, the float text, the tween timing, and the sound's ride | The event has a frame and a force and no answer |
| 04 | The tuning loop, the A/B, the feel checklist, and the stop — no code | You have effects and can't say which ones are earning their frames |
The rule the shelf keeps returning to#
The consequence rides the event, not the presentation — the audio shelf's rule (part 04
there), made visual. The flash, the stop, the shove, the thock all leave the damage frame
(the damage_received signal, the hitbox's active tick), the same frame the float text
leaves. The swing's whoosh and the windup's tell are the presentation — the promise, the
eye's job — and they may ride the animation. The split is the boss fights shelf's
tell/active anatomy on the player's side: the
presentation sells the intent, the event confirms it, and a consequence on the wrong frame
is a confirmation that arrives before or after the fact — which is a lie the player's ear
files under "this doesn't feel right" without being able to name the frame.
What feel actually buys you#
- Confirmation — the hit is known without a check. The flash and the thock are the damage number's witnesses; a hit that only moves a health bar is a hit the player has to verify, and verification is the feel's absence.
- Readability — the shove is the damage. A golem that flies back three metres took more than one that hops; the enemy AI shelf's fair-and-readable part is the design version (the player must be able to read the game's state from its motion), and the knockback is the state made visible. A hit that does damage and moves nothing withholds the reading.
- Weight — the stop and the shake are the game's mass. A world that doesn't flinch at
a hit is a world made of numbers; the two frames of
time_scaledip is the difference between "the sword connected" and "the sword landed."
What it doesn't buy you#
Feel is the last layer, and it's the layer that hides the layers under it. A hit-flash on a hit that's on the wrong frame (the audio shelf's part 04 bug) makes the wrong frame feel good — the consequence confirms the lie, and the player feels a game that's both juicy and off, which is the worst of both. The order is the point: the event first (the damage path, the survivors stage 04), the force second (the knockback, stage 04's shove), the consequence third (this shelf). Juice over a broken event is makeup over a hangover; the shelf assumes the event is right and builds the answer.
And feel has a budget, the performance shelf's row of the table: every effect is a frame of work, a listener, and (for the sound) a bus. A per-enemy hit-flash tween at 300 enemies is the performance part 02's frame-skip applied in reverse — the presentation line that can't skip, because the flash is the confirmation, and the answer is the wallpaper rule (part 04): the effect that plays thirty times a minute stops being information after the tenth, and the budget is where the thirty becomes the three that land.
Prerequisites#
- The damage path — a
damage_receivedsignal (or equivalent) that's the event's home. The survivors stage 04 is the reference; without an event the consequence has no frame to ride, and the shelf's first rule is unbuildable. - Tweens — the flash, the shake's decay, and the float text are all
create_tween()s, and the curve vocabulary (TRANS_BACKthe pop,TRANS_QUADthe natural,TRANS_CUBICthe confident) is part 03's working material. - The Monitor — part 04's taste is measured, and the effect's frame cost is the performance shelf's row. A feel pass you can't measure is a feel pass you can't stop.
Where this shows up in the projects#
The action RPG is the shelf's origin — stage 06's hit- flash, shake, and float text are parts 01 and 03 worked on one sword, and the stage's "violent in the good way" is the overview's "lands" in the author's words.
The survivors game is the shelf at count — stage 04's knockback and float text are part 02 and 03's machinery, stage 05's hit frame (the phase-timeline) is part 01's event, and stage 08's pool is part 03's float text at the count where the effect has a budget. The survivors game is where feel meets performance, and part 04's stop is the line between them.
The boss fights shelf is the shelf's other side — the tell and the active are the boss's feel, the windup the player reads and the hit the player survives. This shelf is the player's consequence; that shelf is the enemy's. A game where both sides land is a game where every hit is a conversation, and the conversation is the feel.