At 0.55 seconds Kern's cracked rune reveals a marked exit and escape meter. From 1.15–2.85 seconds the elemental follows one committed route while Tavi takes a shorter intercept. A sword hit stops the escape before the gate, then creates a bounded opening instead of silently resetting the fight.
At 0.55 s Kern's health threshold cracks the retreat rune. The exit gate, fixed route, interrupt point, and empty escape meter appear together, so the player sees both destination and consequence before movement.
Autoplay is disabled by reduced motion. Scrub across 0.55, 1.15, 2.2, 2.85, 3.35, 4.45, and 5.15 seconds to inspect the escape contract.
Implement the escape trigger, destination, travel budget, allowed responses, success and failure outcomes, checkpoint policy, and return as one deterministic state machine.
Name the exact trigger: health threshold, broken part, expired objective, stolen resource, or scripted phase gate. Reveal the destination and consequence at the same moment. Reaching the exit may heal the boss, relocate the encounter, remove a reward, strengthen the next phase, or end the attempt, but the player must know which result is at stake before committing to pursuit.
Measure the boss route against ordinary player speed, full-body collision, camera lag, and the startup of every valid interrupt. Commit the boss to authored turns instead of continuously dodging the pursuer. If the intended response needs a stun, grapple, mount, ranged hit, or environmental switch, surface its eligibility and preserve at least one recoverable line after a small mistake.
Resolve interruption and escape as explicit states. Stop locomotion before opening vulnerability, or move the boss fully into the next arena before restoring combat. Define retained damage, healing, resources, checkpoints, multiplayer joins, and repeat limits. A failed catch should create a legible new condition, not an unexplained health reset.
A sudden sprint while the player is committed to a long attack turns knowledge of an unseen health value into the real test. Telegraph the threshold, protect a short reaction beat, and keep the exit direction readable before speed matters.
A full heal with no new rule can turn one missed intercept into pure repetition. Cap the number of retreats, preserve some progress, change the next phase, or make the recovery state tactically different enough to justify its time cost.
Compute time to exit, reaction delay, route length, acceleration, interrupt startup, hit-stop, and network latency separately. Test the last valid input rather than only a perfect early catch, and expose a margin that survives the animation and camera contracts.
Use a persistent gate marker, route line, compass edge cue, or progress meter when the boss can leave the camera. The player should not have to choose between watching incoming attacks and discovering where the retreat is going.
Specify which damage types, status effects, body parts, players, or arena devices can stop the escape. Give qualified hits distinct feedback and reject invalid hits clearly so teams can diagnose the outcome instead of blaming latency or damage totals.
Run the phase with slower movement assists, camera aids, solo and full parties, dead or distant teammates, and repeated failures. Decide whether the gate waits for all players, whether crowd control scales, and how many retreats remain before fatigue replaces tension.
When its core fractures, Kern turns toward an ancient gate that can rebuild the stone shell. The glowing route is a physical conduit, so Tavi can read both the destination and the moment the seal will accept the elemental.
Tavi does not gain a chase-only verb. Ordinary movement reaches a marked crossing, and one clearly timed sword hit breaks the retreat rune. The reward is a short opening; missing it lets the authored escape consequence resolve instead of teleporting either actor.
Chase herding progresses while the player maintains a relationship and steers a moving target. Forced scrolling advances space on a schedule. An escape phase begins from a state trigger and asks whether the boss reaches a specific exit whose success changes the encounter.
After enough damage, Yawie leaves the initial arena and the fight becomes a side-scrolling pursuit. The escape is a phase transition rather than a reset: the boss remains a target, new projectile patterns occupy the route, and sustained pressure carries progress into the following reversal.
At a health threshold the Patriarch cloaks, runs for cover, and tries to spend a limited healing syringe. Players can follow the shimmer, block routes, apply control, and continue damage; losing contact converts distance into a large heal and a more aggressive next phase.
A weakened Rathalos leaves the current combat space and returns toward its nest. Limping, map state, scoutflies, and a known destination turn the retreat into readable pursuit; reaching the nest can create sleep, capture, environmental, or wake-up decisions instead of erasing the hunt.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub