Hornet Protector
Hollow KnightHornet’s thrown needle remains attached by thread and returns after crossing the side-view arena. The visible tether and stable height make the second pass part of the same readable attack rather than a surprise shot.
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.
Kern shows a straight outbound leg, a fixed turnaround, and a curved route back to the same owner.
Autoplay is disabled by the reduced-motion setting. Use the timeline slider to inspect both legs.
Design the outbound route, turnaround, return route, two-pass response, and catch as one complete spatial rule.
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.
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.
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.
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.
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.
An invisible late hit near the owner makes recovery unreliable. Use one catch event to end visuals, collision, audio, and ownership state together.
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.
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.
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.
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.
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.
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.
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.
Hornet’s thrown needle remains attached by thread and returns after crossing the side-view arena. The visible tether and stable height make the second pass part of the same readable attack rather than a surprise shot.
Theseus marks Zagreus, throws his spear, and recalls it so the same weapon can hit on the way back. Arena pillars reveal how cover and owner position can shape both legs without changing the projectile’s identity.
Thor’s Mjölnir throw preserves a strong weapon silhouette and a clear relationship to its owner in a close 3D camera. The example shows why return audio and owner pose matter when depth can hide the inbound leg.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub