Problem
Is this your problem?
Jumps feel floaty, static, and lack a sense of power or gravity. The character just moves up and down.
When to use it
- The player action is important but easy to miss.
- The game state changes, but the player does not immediately understand why.
- A mechanic works correctly but feels dry, flat, or unresponsive.
When not to use it
- The action happens constantly and strong feedback would become noise.
- The feedback would hide information the player needs to react to.
- The player cannot reduce intense motion, flash, or sound when needed.
Recipe
Apply the stack in order.
Each layer should support the same moment. If a layer arrives late, lasts too long, or fights the player for attention, reduce it before adding more.
-
1. Squash and stretch
Squash the sprite vertically before launch (anticipation frame)
-
2. Anticipation
Stretch the sprite horizontally mid-air to emphasise upward velocity
-
3. Particle burst
Spawn a small dust cloud at the launch point
-
4. Asymmetric gravity
Apply asymmetric gravity: fall faster than you rise (feels more natural)
-
5. Coyote time
Add coyote time -- allow jumping briefly after walking off a ledge (10-15 frames)
-
6. Step 6
Spawn landing particles + screen micro-shake on touchdown
Why it works
The pattern is about confirmation, not decoration.
Squash/stretch communicates mass and elasticity. Asymmetric gravity matches player expectation from real-world physics. Coyote time reduces frustration without breaking immersion -- it feels fair.
The useful part is not the amount of polish. It is the timing. Feedback needs to arrive on the frame where the player expects confirmation, then get out of the way.
Tuning
Adjust the knobs, not the whole pattern.
Start with the smallest readable version, then increase only the parts that help the player understand the moment.
Intensity
Scale the response to the importance of the action.
Timing
Fire the stack on the confirmation frame, not after the moment has passed.
Duration
Keep repeated actions short and reserve longer pauses for rare events.
Accessibility
Offer reduced motion, reduced flash, or separate audio controls where intensity can spike.
Mistakes
What usually goes wrong.
Most failed applications of this pattern come from adding more feedback before the core timing and readability are working.
- Using the same feedback strength for every action.
- Adding effects that obscure the thing the player needs to read.
- Treating juice as decoration instead of confirmation.
Before / After
What changes for the player.
Before
The action happens, but the player has to infer the result from health, score, or delayed state changes.
After
The game confirms the action immediately through synchronized feedback that matches the importance of the moment.