Back to patterns
Intermediate Impact Feedback Combat

Hit Confirm Stack

Use this when an attack, projectile, or collision technically works, but the player cannot feel the impact.

Problem

Is this your problem?

The player hits an enemy or object but the action feels weak, unclear, or lacks physical weight.

When to use it

  • A hit connects, but the player is not sure it registered.
  • Enemies lose health without feeling physically affected.
  • Combat reads as mathematically correct but emotionally flat.
  • Different hit strengths need to feel meaningfully different.

When not to use it

  • Every frame of control matters and hit stop would break the rhythm.
  • The screen already has dense combat readability problems.
  • Camera shake or flashes would create accessibility issues without a reduction option.

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. 1. Freeze

    Pause motion for 0.03s to 0.1s on the exact impact frame. Small hits stay short. Big hits earn more time.

  2. 2. Flash

    Flash the target for one or two frames so the contact point reads immediately.

  3. 3. Recoil

    Move the enemy, attacker, or hit object a few pixels away from the impact to show transferred force.

  4. 4. Sound

    Layer a low thud with a sharper crack. The low layer sells weight, the high layer sells contact.

  5. 5. Particles

    Spawn directional sparks, debris, or impact sprites from the contact point, not from the center of the target.

  6. 6. Camera

    Use a small punch or shake only for hits that deserve it. Keep ordinary hits readable and restrained.

Why it works

The pattern is about confirmation, not decoration.

Multiple feedback channels fire simultaneously, confirming the action across visual, audio, and kinesthetic senses. The freeze frame creates a moment of punctuation -- the brain registers consequence before motion resumes.

A good hit confirm works because it removes ambiguity. The player does not need to check a health bar or wait for an animation to finish. The hit announces itself at the moment of contact.

The stack also creates hierarchy. A light tap, heavy strike, and critical hit can share the same recipe while using different intensity. That consistency helps players learn the game language quickly.

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.

Hit-stop duration

Start around 0.03s for light hits, 0.06s for heavy hits, and 0.1s for rare critical hits.

Flash length

Keep hit flash short. One readable frame is often enough for small sprites.

Recoil distance

Use a few pixels for normal hits. Larger recoil should change spacing or communicate stagger.

Sound weight

Raise low-frequency weight for heavy hits and add sharper transient detail for clean contact.

Particle count

Use direction and timing before quantity. Too many particles can hide the actual hit.

Camera movement

Reserve camera punch for heavy hits, finishers, and critical moments.

Mistakes

What usually goes wrong.

Most failed applications of this pattern come from adding more feedback before the core timing and readability are working.

  • Applying the full stack to every hit, which makes strong hits feel ordinary.
  • Triggering feedback after the damage frame instead of on the contact frame.
  • Using camera shake so often that combat becomes harder to read.
  • Relying on particles alone while the target itself does not react.
  • Ignoring reduced motion and flash settings for intense effects.

Before / After

What changes for the player.

Before

The enemy loses health, but the action feels soft and the player has to trust that the hit landed.

After

The impact pauses, flashes, sounds, recoils, and resolves with a readable consequence.