domains / families / software-engineering / game-feel

game-feel

separate

Add "juice" and game feel that makes actions satisfying — screen shake, hit-stop/freeze frames, tweened/eased motion, squash & stretch, knockback, and layered audio-visual feedback — as engine-neutral techniques that pair with the detected engine's tween, particle, and camera APIs. Use when the user mentions game feel, juice, "make it feel good/punchy", screen shake, hit stop, screen freeze, easing, squash and stretch, impact frames, or feedback/polish on hits, jumps, pickups, and deaths.

When to use

• Use when an action (hit, jump, dash, pickup, death, button press) is mechanically correct
• Use to add screen shake, hit-stop/freeze frames, eased motion, squash & stretch, knockback,
• Use to decide *how much* juice is enough and where it crosses into noise.

When not to use

• implementing raw controller math or movement mechanics
• camera follow, deadzone, or orbit framing
• mixing, ducking, or adaptive music
• shader-based dissolves or flashes
• concrete engine tween or particle node APIs

Skill page

Source