CR / RELEASE 2026-07-24

Rule 373.2

When applying Replacement Effects to events that occur simultaneously, each Replacement Effect may only be applied in one sequence, to any number of events that are qualified to be replaced. Example: Soraka, Wanderer reads “If another unit you control here would die, if it has less Might than me, instead heal it, exhaust it, and recall it.” Soraka dies simultaneously with two 1 [M] Recruit tokens at the same battlefield and two 1 [M] Recruit tokens in base. Soraka has a Guardian Angel attached to her when she dies, which appends “If I would die, kill Guardian Angel instead. Heal me, exhaust me, and recall me” to Soraka’s rules text. There are several possible ways to order the Replacement Effects being applied to the various events: If Soraka’s Replacement Effect is applied first, it saves the Recruits at the same battlefield as her but not the Recruits in base. If the Replacement Effect appended by Guardian Angel then saves Soraka, she cannot apply her Replacement Effect to the Recruits in base as her Replacement Effect has already been applied to an event simultaneous with it dying. If the Replacement Effect appended by Guardian Angel is applied first, it saves Soraka and recalls her - then when Soraka’s Replacement Effect is applied, it can only save the Recruits in base.

Rule hierarchy

Parent373If more than one event occurs simultaneously that Replacement Effects could apply to, each event is treated separately and individually for the purposes of Replacement Effects, and Replacement Effects with the same controller are applied in the order of their controller’s choosing. Example: Two units controlled by the same player die in the same cleanup. That player also controls Zhonya’s Hourglass. They must decide which event to apply Zhonya’s Hourglass to first.
Direct children

PROVENANCE

Pinned to Riot's source document

Effective date
2026-07-24
Release
2026-07-24
Source PDF SHA-256
9c5fb8b8638f2cd19ceda237929fa2c37aac23c797cc7410294993470ba5a30b
Rendered rules SHA-256
8cc6bea6992957818c584e1b02742c6d3be805417004b96567b2cf2367a6dae0