A personal spread marks several players for simultaneous area hits. Each normally takes their own hit; standing inside another player's zone adds one more. Show markers early enough for ordinary movement, then resolve each hit once. The circles may intersect without extra damage if no other player stands inside them.
At 0.65 seconds Kern marks all three players with radius-110 circles. The two allies move from the center to reachable side positions. Their circles still intersect, but no body touches a foreign circle: center distances are 135 and full-body clearance requires more than 134.
Reduced motion disables autoplay. Scrub through 0.65, 1.20, 2.10, 2.30, 3.05, 3.65, 4.20, 4.35, and 5.45 seconds.
Specify marked IDs, follow-versus-lock behavior, radius and body collision, simultaneous resolution, duplicate prevention, cumulative damage, reachable spacing, retry reset, and multiplayer telemetry.
Give every mark a stable owner and one circle. At contact, test each living player's full collision shape against each marked zone. The owner's own hit is expected; a body inside another owner's zone receives that extra source. Two circles may share pixels while both owners stand clear.
Define whether zones follow owners until contact or lock beforehand, and communicate that choice. Snapshot all marked positions on the same resolution frame, derive one hit list per player, and apply each source once by encounter and hit ID. Do not let network callbacks turn one impact into several.
Measure the arena's usable width, mark radius plus full body radius, movement speed, warning duration, and obstacles. Here a 135-unit separation clears a 110-unit zone plus 24-unit body, while a 70-unit separation does not. Compare hit counts and health, then reset the entire roster on retry.
Painted circles can overlap in empty space. Calling that a failure needlessly demands impossible spacing in a compact arena. Check whether a foreign body intersects a zone, with the same collision radius used by damage.
If a player stands in three marked areas, one capped hit erases the coordination consequence. Retain separate source IDs in the hit ledger, apply each only once, and show the total and surviving health.
Test worst-case initial grouping, ordinary travel distance, a player's full body, blocked corridors, and latency. The clear distance in this example is greater than 134 units; leave a small tolerance beyond that mathematical edge.
A shared-damage stack rewards entering one marker; a personal spread rewards leaving foreign markers. Give the two signals different silhouettes and a transition interval before asking a group to reverse direction.
Record encounter ID, hit ID, marked IDs, final positions, body radius, source-to-target intersections, per-player damage, health before and after, and duplicate callbacks. Test an exact boundary, downed or absent targets, crossing motion, and retry.
Kern puts a rune over Tavi and two companions. The first pulse finds them spread enough to carry only their own sparks. The second pulse catches them crowded together, and their separate sparks stack on Tavi.
Use distinct marker tips, persistent outlines, visible hit counts and health values. Keep labels readable without color or audio, preserve the result on a paused timeline, and provide reachable spacing on a narrow screen without changing the encounter rule.
A stack has one total damage budget split among bodies in a marked area. A personal spread creates a separate hit from every marked owner; crowding adds damage rather than dividing it. A fixed tower instead asks for occupancy of a world-anchored zone.
Kaling's phase-two guide shows one marked player taking a periodic attack every four seconds for fifteen seconds. This 2D, one-carrier variant makes the marked player's position relevant to nearby allies; it is not the demo's simultaneous three-mark pattern.
Conceptual Octaflare resolves as separate AoEs on every player after its earlier signal. The group must preserve distinct body positions while other arena constraints resolve; the timing and crowded floor make the spacing budget part of the design.
Explosive Corruption marks players who need space before detonation. On Mythic, many may be marked together; the debuff also leaves persistent danger, so spread planning has to consider both immediate neighbors and later arena use. This differs from the demo's three clean, simultaneous circles.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub