An external healing source moves recovery out of the boss and into the arena. The player must identify which object owns the heal, understand its route and deadline, and decide whether leaving the boss is worth preserving progress. Each source needs an explicit lifetime, intercept rule, delivery event, amount, and reset policy.
At 0.28 s, two diamond runes light up and connect to Kern while the boss health bar remains at 42. Their separate bodies and dashed routes show that the arena objects own the pending recovery.
Autoplay is disabled by reduced motion. Scrub across 0.28, 0.72, 1.20, 1.42, 1.78, 2.46, 2.90, 4.08, 4.50, 5.08, and 5.36 seconds to inspect both outcomes and the reset.
Define source identity, spawn and signal timing, source health, packet ownership, travel route, interception predicate, delivery frame, requested and applied healing, overheal, duplicate-event protection, cleanup, phase transitions, rollback, and telemetry that joins one source id to one result.
Represent the healer, pickup, projectile, or objective as a separate encounter entity with a stable id. Show its relationship to the boss before healing begins so the target-priority decision is readable.
Choose whether the source body, the travelling packet, or both can be attacked. Tune travel time, source durability, distance, and concurrent threats around the response verbs the player actually has.
On arrival, verify that the source is still active, apply one clamped heal, record the source and result ids, then consume or reset the source. Rejected and duplicated deliveries must change no health.
If the source has no readable body or route, players interpret the health gain as an unexplained self-heal. Maintain a visible connection and make source destruction visibly cancel the transfer.
Too much durability, frequency, or healing turns target priority into mandatory cleanup. Bound the restored amount and compare the time to intercept with expected damage, movement cost, and exposure.
Store sourceId, packetId, spawnedAt, interceptedAt, arrivedAt, healRequested, healApplied, and result. This prevents a destroyed source from completing through a stale callback and makes rollback deterministic.
Separate sources spatially, limit simultaneous clutter, and show which one is active. If several sources can heal, communicate ordering, shared deadlines, and whether partial interception still matters.
Track source spawns, time to first response, sources destroyed, packets intercepted, deliveries completed, health restored, damage forgone, travel distance, resource spend, and deaths after a delivery.
Two standing stones wake and draw pale threads toward the cracks in Kern’s chest. Tavi breaks the nearer rune before its light can leave; the farther stone survives and seals part of the elemental with one final pulse.
Combine silhouette, tether, packet motion, cadence, source count, and health-bar feedback. Offer weaker sources, slower packets, fewer simultaneous targets, aim assistance, or a dedicated intercept prompt without changing the rule.
The external entity owns the delivery and can be targeted independently. An interruptible self-heal belongs to the boss action itself, while on-hit healing requires qualifying contact with a target.
At 0:02, three Revival Prisms appear around the exposed core. The player must destroy them with elemental reactions; each surviving prism restores health and remains for the next recovery attempt, turning a damage check into persistent target priority.
At 0:31, the Moon Lord’s tongue connects to the player and produces Moon Leech Clots that travel toward his mouth. The clots can be destroyed in transit; every survivor that arrives heals the boss, so route readability directly supports interception.
At 0:30, Ultra Greed releases a wave of Heart Coins. Each coin is a separate destructible target that heals him if it survives, forcing the player to retarget quickly without losing awareness of the boss and the rest of the coin wave.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub