A ground slam turns one impact into an expanding area threat. It works when the center and growth rate are visible, a valid route exists, and the impact timing tests a skill already taught.

Open boss builder
LiftThe boss raises its weight and marks the future impact point.
Test the pattern A looping diagram of ground slam. The boss signals the pattern, the player responds, and both return smoothly to their starting positions. Boss Player

Threat appears

Implementation checklist

Tune the signal, the impact center and wave edge, response time, and recovery.

Core checks

Three questions for the mechanic

  • Is the signal specific?

    Make the lift, impact point, and exact contact frame distinct from ordinary movement.

  • Is the response reachable?

    Compare wave speed with running, jumping, dodging, and the arena boundary.

  • Is the opening useful?

    Give the slam enough recovery for the successful response to change the fight.

Design mistakes

  • Hidden rule

    If the signal does not reveal the impact center and wave edge, the hit feels arbitrary.

  • Wrong scale

    If timing is tested only at one upgrade level, the pattern can become trivial or unavoidable.

Tuning

Tune the attack

  • Match visuals and collision

    The visible threat must match the active hitbox in space and time.

  • Start with ordinary abilities

    Keep one response available with abilities the player already has.

  • Retest upgrades

    Check movement, range, damage, and invulnerability against every phase.

Arena

  • Make the arena support the rule

    Keep the floor and wave edge visible; slopes and decoration must not mask timing.

Player upgrades

  • Respect player upgrades

    Test the strongest available build. If an attack is blocked, make the immunity clear and preserve another useful response.

Do not confuse this with

  • Name the exact pattern

    A slam is the impact; the shockwave is the expanding threat it may create.

Bosses that use this mechanic

Learn more

Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub