RIFTCOMBO

Combo · ENGINE

373.2: a Replacement Effect is applied ONCE per sequence, to any number of qualifying events - so stacking Guardian Angel on Soraka is a choice of which half of the board to save

6 cards · order + calm · verified

Pieces

Payoff

Repeatable bodies

Deck

Prerequisites

Steps

  1. Play SFD-173 Soraka, Wanderer (4 Energy + 1 Power) and attach SFD-051 Guardian Angel (2 Energy, [Equip] one Calm rune) to her. Her Might is now 5 (137.3, 477.3.d), so her save covers friendly units there under 5 rather than under 4.
  2. The opponent wipes the board. Soraka, the garrison at her battlefield and any bodies at your base die simultaneously.
  3. 373 gives you the order, because both replacements are yours. Count the qualifying bodies at her battlefield against those at your base.
  4. Guardian-Angel-first: it kills the Angel instead, and heals, exhausts and recalls SORAKA. Her own replacement then applies once (373.2) and can only reach the bodies at your base.
  5. Soraka-first: her replacement applies once and saves the qualifying bodies at her battlefield; the Angel then saves her, but her effect is spent and the base bodies die.
  6. Either way 373.1.a performs the saves before the unsaved bodies finish dying, and 455 puts every saved body at your base, exhausted, with 315.1.b readying them at your next Awakening.
  7. Three copies of each (103.2.b): the Angel is consumed on each use, and Soraka survives only on the Angel-first line.

Per iteration

one wipe answered on one of two halves of the board, with the choice of which half, and Soraka kept on the line that takes the base

How it ends

engine only - nothing here scores. Each Guardian Angel is consumed when it fires, three copies of each card (103.2.b), and the battlefield is lost under 323.6 whichever order you pick

Sources

Published elsewhere

Walked here, in this project

How this entry was audited

REFUTE = a refutation pass, with its date and verdict · WOUNDED = the pass found a flaw and the entry was rewritten · BUDGETED = the pass checked the recycle-and-draw ledger · lens = the hunt that proposed it.

HAND-WALKED 2026-09-07 (issue #187, sub-rule lane 100-499). 373, 373.1, 373.1.a, 373.2 and 373.2.a are cited by no entry and no synergy rule in this project, and 373.2's worked example names SFD-173 Soraka, Wanderer and SFD-051 Guardian Angel together. Card text verbatim from data/corpus_flat.txt. Citations opened: 103.1.b.2, 103.2.b, 103.2.d.2, 136.2.d, 137.3, 315.1.b, 323.6, 370.4, 373, 373.1, 373.1.a, 373.2, 455, 477.3.d. THIS IS THE LIMIT THAT 370.4 ALONE DOES NOT STATE, and it refines my own soraka-wanderer-vanguard-armory-simultaneous-save from the same night: 370.4 says the replacement reaches simultaneous deaths, 373.2 says it reaches them ONCE PER SEQUENCE - so a second replacement on the same body is a fork between two halves of the board, not a doubling. That entry was patched with a notable citing 373.2 before it was merged. Distinct from soraka-fiora-loop-shield and from tianna-guardian-angel-forge-god-lock, neither of which cites 373. Trap check: the ordering choice is yours only because both replacements share a controller (373); across controllers 373.1 uses turn order; the Angel is consumed on use; the battlefield is lost either way; no unruled reading.

Walked against Core Rules 2026-07-16

Match a deck list against the whole catalogue