Ordered targets assign each player a unique place in a forthcoming attack sequence. The group can see who is next, move that strike away from unmarked bodies, and reclaim space after it resolves. The lesson is not simply a boss repeating attacks: the marks bind later attacks to specific recipients and the order remains stable after it is revealed.
At 0.70 seconds the boss places unique marks 1, 2, and 3 over three players. The order locks before anybody moves; a persistent next-target cue points to mark 1.
Reduced motion disables autoplay. Scrub to 0.70, 1.80, 2.08, 3.28, 4.48, and 5.60 seconds.
Define unique assignment, a single strike cursor, target geometry, isolation travel time, invalid or missing targets, damage, event deduplication, and reset.
Assign one unique number to each eligible player and show all marks before the first hit. Snapshot the roster and order at 0.70 seconds. Do not silently reshuffle on death, disconnect, proximity changes, or camera motion; define an explicit fallback for a missing numbered target.
For this variant, each hit uses a 72-unit circle centered on its assigned target at impact. Give ordinary movement enough time to isolate it, and compare all player bodies with the complete circle rather than checking anchor points only. The intended target takes 25 damage; another occupant would take 80.
Resolve exactly one event ID for the current number, then advance the cursor. Reject a repeated ID, a future number arriving early, or a hit from an old encounter. Test simultaneous callbacks, a missing target, late movement, and reset so seeking and retry never add phantom damage.
A mark is a promise. If the boss silently switches recipients after commitment, the group cannot plan its isolation route. Only an explicitly telegraphed cancellation may change the locked order.
Animation and collision events can fire twice. Advance only after a unique, valid strike ID, and keep the active number visible until that resolution is committed.
Measure the distance from assignment to the first receiving spot and between successive spots with ordinary walk speed. The next target should be able to enter after the previous hit without crossing its persistent danger.
Number glyphs, an active-number halo, and a completed-state change carry the sequence; color can reinforce but must not be the only code. Keep the next cue visible when the boss or effects cover a player.
Record encounter ID, strike ID, expected number, assigned player, impact center, complete radius, actual occupants, damage, and resulting cursor. A rewind must recompute the same ledger without side effects.
The boss carves three numbered runes over the party. Each one foretells whose stone pulse comes next, so the players can carry their own impact to separate parts of the floor.
Numbers can direct circles, cones, dashes, or beams. This demo uses small circles to make isolation measurable; changing geometry also changes receiving spots and safe travel. A 2D sequential attack-type pattern may teach ordering but does not itself assign numbered players.
The target order is visible and locked before the first hit. Personal spread can resolve all marks at once, while this sequence hands the next safe-space obligation to a different player after each strike.
Palladion in Anabaseios: The Twelfth Circle (Savage) assigns players numbers 1–8 and resolves the boss's dashes in that order. Its spatial follow-ups are much more complex than the demo's three small circles; the reusable rule is the committed numbered recipient queue.
Flood Ray in The Cloud Deck (Extreme) gives each player a number from 1 to 8 and fires conal cleaves consecutively. The two platforms, odd/even grouping, and vulnerability make the receiving-space problem sharper than the demonstration.
In a related 2D ordering variant, First Adversary charges three times with red, blue, then yellow attributes. It does not put numbered marks on three players: it demonstrates how a fixed, readable attack order can change each successive response. The player-assignment layer in this lesson is a separate design choice.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub