A hit displaces the player, so its real danger depends on nearby walls, ledges, hazards, and the loss of a chosen position.

Open boss builder
SignalCommunicate push direction and strength through the boss pose, impact line, and arena context before the force resolves.
Test the knockback A looping diagram of knockback. The boss signals and commits the rule, the player uses the intended response, and the scene holds a readable recovery before resetting. Boss Player

Communicate push direction and strength through the boss pose, impact line, and arena context before the force resolves.

Implementation checklist

Tune the signal, commitment, geometry, response, and recovery of a knockback as one rule.

Core checks

Three questions for the mechanic

  • Can the player read the complete rule?

    Communicate push direction and strength through the boss pose, impact line, and arena context before the force resolves.

  • Is the intended response reachable?

    Players brace, move away from dangerous boundaries, steer during displacement, use immunity, or deliberately take a safe push for repositioning.

  • Does recovery create a useful outcome?

    The player regains control before the next unavoidable threat while the boss completes its follow-through, preserving recovery from a safe landing.

Design mistakes

  • A small-looking hit that launches the player farther than the arena reads makes environmental deaths feel arbitrary

    A small-looking hit that launches the player farther than the arena reads makes environmental deaths feel arbitrary.

  • The cue and active geometry disagree

    If the visible knockback cue promises a different area or timing, the player cannot carry the learned rule into the next cycle.

Tuning

Tune the attack

  • Tune the complete rule

    Evaluate force, stun time, air control, collision behavior, and every possible landing zone rather than balancing damage alone.

  • Escalate one variable at a time

    Combine moderate push with changing boundary hazards or directional choices instead of scaling force until recovery is impossible.

  • Prove the recovery

    The player regains control before the next unavoidable threat while the boss completes its follow-through, preserving recovery from a safe landing.

Arena

  • What the mechanic communicates

    A hit displaces the player, so its real danger depends on nearby walls, ledges, hazards, and the loss of a chosen position. The encounter uses that rule as a short promise: a visible signal, a committed action, and a result the player can verify.

Player upgrades

  • Adapt it to the player verbs

    Players brace, move away from dangerous boundaries, steer during displacement, use immunity, or deliberately take a safe push for repositioning. Evaluate force, stun time, air control, collision behavior, and every possible landing zone rather than balancing damage alone.

Do not confuse this with

  • Keep the mechanic distinct

    A small-looking hit that launches the player farther than the arena reads makes environmental deaths feel arbitrary. Do not hide that distinction behind extra effects or tracking that the announced rule does not contain.

Bosses that use this mechanic

Learn more

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