A projectile rally transfers one encounter-owned shot between boss and player. Each valid return reverses its direction, records the new owner, and may shorten the next travel beat. The exchange ends on a clear miss, timeout, or invalid response; the boss's miss usually converts the shared timing test into a damage opening.
Kern charges one rune orb, fixes its lane, and releases it at 0.78 s. The rune on the single orb changes when Tavi returns it with the sword, distinguishing this serve from ordinary projectiles.
Autoplay is disabled by reduced motion. Scrub across 0.78, 1.48, 2.05, 2.48, 2.86, 3.15, 3.48, 3.90, 4.55, and 5.20 seconds to inspect serve, every ownership transfer, acceleration, miss, opening, punish, close, and reset.
Define the serve, eligible response verb, contact point, input window, ownership transfer, return aim, speed curve, maximum exchanges, audiovisual beat, miss rules, player damage, boss stagger, opening duration, co-op arbitration, latency tolerance, accessibility assists, reset, and tests that keep visible position, collision, and authority synchronized.
Give the projectile a stable encounter identity and server-authoritative owner. At the contact event, validate the response verb, input time, distance, facing if relevant, and whether the orb is still eligible. Then reverse or retarget its velocity from the visible contact point, increment the exchange counter once, and switch damage allegiance once. Do not destroy one shot and silently spawn another at a different position.
Author contact-to-contact beats rather than applying an uncapped multiplier. Shorten travel in measured steps, but preserve a readable launch, minimum reaction budget, stable lane, response anticipation, and distinct contact sound. If the boss can vary return angle, reveal that choice before speed makes correction impossible. Cap exchange count or speed so success remains reproducible.
Resolve one of four outcomes: player miss, boss miss, timeout, or cancellation by a documented rule. A player miss applies the orb's current damage and ends the rally. A boss miss consumes the orb, records boss stagger, opens a fixed punish window, and prevents another serve until recovery. Define co-op claimant rules and make all damage and rewards idempotent.
Respawning a new orb at every hit can hide position jumps, double collisions, stale ownership, or duplicate damage. Preserve one identity and derive its rendered position, collision, trail, owner, and exchange count from the same deterministic leg. Tests should seek backward and reproduce every contact exactly.
An exponential speed multiplier quickly reduces the last beat below input, display, network, or animation latency. Set a minimum readable interval, buffer slightly early inputs, expose a rhythm cue, and cap both speed and exchanges. Difficulty can tighten the window deliberately, but it should never be an accidental frame-rate contest.
Useful states are serve wind-up, outbound, player return window, inbound, boss return window, accelerated legs, player miss, boss miss, opening, and reset. Store projectile id, owner, leg index, departure time, arrival time, origin, destination, speed tier, accepted input, and outcome. One transition must own each contact.
A fixed lane asks for timing; a redirected return asks for aim; a boss-selected angle asks for reading. Combining all three at maximum speed obscures the failure. Teach one axis first, signal changes before contact, and decide whether assist settings widen timing, add aim magnetism, or both.
Give each accepted return a crisp transient, rising pitch or shorter interval, controller pulse, and visible ownership glyph. Reserve a distinct cadence for a miss and a sustained cue for the opening. The player should be able to follow the exchange when the orb crosses a visually busy boss silhouette.
Log serve id, leg, predicted and authoritative contact time, claimant, accepted input, ownership before and after, velocity, miss reason, boss stagger, punish damage, and reset. Simulate two players returning on the same frame, latency at the window edges, pause, rollback, low frame rate, projectile destruction, boss phase change, and repeated reward messages.
Kern compresses a rune into a humming stone spark. Tavi catches it on the sword's flat and sends it back; the elemental answers, then the blade answers again, each note closer to the next. On the final beat Kern's cracked hand closes too late, the spark drives into the core, and its runes separate into a brief opening.
Offer timing-window presets, early input buffering, optional aim assist, strong contact audio, controller vibration, non-color ownership glyphs, captions for serve and miss, and a capped slow-tempo mode that preserves exchange count. In online or co-op play, display the authoritative claimant and compensate latency without moving an accepted contact away from the visible blade.
Attack reflection changes one hostile shot into one return and may end immediately. A projectile rally explicitly supports another answer: ownership alternates, the same projectile persists across multiple legs, tempo or angle evolves, and a miss resolves the sequence. A counter stance can punish a melee trigger without any travelling object or continuing rhythm.
Phantom Ganon opens the Hyrule Castle fight by trading a colored energy ball with the Links until one side misses. The colored shot remains the eligible rally object while other blasts can break apart; repeated returns build a shared cadence and the boss's miss produces a clear stun for sword damage.
In the second phase, Link returns Phantom Ganon's electric orb with a sword swing. The boss may return it again, producing a faster back-and-forth test; when Phantom Ganon finally misses, the same orb knocks him down and converts timing success into a bounded melee opening.
At the Forsaken Fortress, Phantom Ganon serves a light ball that Link and the boss strike back and forth as it rapidly accelerates. A lost exchange damages Link; a successful final return drops Phantom Ganon, cleanly separating the rally's timing loop from the follow-up sword punish.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub