A returning projectile stays dangerous after its first pass because it travels back toward its owner. It works when the turnaround and return route are visible before the player commits, the projectile does not secretly retarget, both passes use consistent collision geometry, and recovery begins only after the object is caught or removed.

Open boss builder
Preview both legsKern shows a straight outbound leg, a fixed turnaround, and a curved route back to the same owner.
Test the returning projectile A looping diagram of a returning projectile. One shot travels from the boss to a marked turnaround, then follows a distinct curved route back while the player moves outside both collision paths. Boss Player

Kern shows a straight outbound leg, a fixed turnaround, and a curved route back to the same owner.

Implementation checklist

Design the outbound route, turnaround, return route, two-pass response, and catch as one complete spatial rule.

Core checks

Three questions for the mechanic

  • Can both passes be planned from the first signal?

    Show the outward line, turnaround cue, and broad return route together. The player should understand that the first dodge is not the end of the attack before leaving a safe position.

  • Does the return preserve its committed geometry?

    Lock the turnaround point and return curve at release. Sample the complete player body against the projectile on both legs, including the crossing region where a move that clears the throw may enter the return.

  • Is the catch visibly complete?

    Keep the projectile, trail, collision, and owner animation synchronized until the catch. Recovery should begin only when the returning body is no longer active, confirming the end of the two-pass rule.

Design mistakes

  • Only the outbound route is telegraphed

    A surprise return punishes the correct first response. Even when the exact curve emerges in motion, signal which side or corridor the projectile will revisit.

  • The return homes onto the player

    Unannounced steering turns a boomerang rule into tracking. If the owner recalls toward a new position, show that destination and lock it before the turn.

  • The catch animation ends before collision

    An invisible late hit near the owner makes recovery unreliable. Use one catch event to end visuals, collision, audio, and ownership state together.

Tuning

Tune the attack

  • Store one round-trip plan

    Capture owner, outbound segment, turnaround, return curve, speed profile, radius, and catch time in one plan. Rendering and safety checks should derive both legs from it.

  • Give the turnaround a readable beat

    A brief slowdown, flash, sound, or rotation marks the change of direction. Keep it short enough to preserve flow but long enough to separate the two decisions.

  • Test the crossing, not only endpoints

    The dangerous moment is often between the legs. Sweep the player’s full route across time so a dodge around the outward path does not collide with the returning curve.

  • Escalate by changing ownership carefully

    Later variants can move the owner or let the player reflect the object. Make the new owner and catch point explicit; otherwise the learned return route stops being reusable.

Arena

  • What the mechanic communicates

    A returning projectile makes Kern’s attack feel controlled rather than disposable: the same rune-charged object leaves and answers its owner’s call. The round trip gives Tavi a visible consequence to anticipate after the first success.

Player upgrades

  • Adapt it to the player verbs

    Movement may cross between the two legs or stay outside their combined envelope. Blocking can stop only one pass, reflection can change ownership, and destruction can cancel the return; define which verb affects the round trip and show the result.

Do not confuse this with

  • Keep the mechanic distinct

    A returning projectile reverses or curves back to an owner after an outbound pass. A ricochet changes direction at a surface, a homing projectile continually steers toward a target, and crossfire uses multiple sources. Preserve the round trip and ownership.

Bosses that use this mechanic

Learn more

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