RIFTCOMBO

Combo · ENGINE

385.2's worked example is Super Mega Death Rocket! — every copy in your trash answers the same conquer

7 cards · fury + chaos · verified

Pieces

Payoff

Repeatable removal

Deck

Prerequisites

Steps

  1. Cast Super Mega Death Rocket! for 4 Energy + 1 Power: deal 5 to a unit. 157 places the spell in your trash when it has finished.
  2. Do the same with the other two copies over the following turns. 108.2.d makes them Public Information there, which is what 385.1 needs for a trigger in that zone to work.
  3. Conquer a battlefield. 385.2 gives EACH copy in the trash its own trigger; 383.3.d lets you order the three.
  4. Each trigger asks its own 'you may discard 1'. Pay it with a Flame Chompers: 422.1.a chooses it, 422.1.b runs its trigger after the discard, 1 Fury Power buys a 3 Might body (355.2.a, exhausted by 143.4).
  5. All three Rockets are back in your hand. Recasting is the real bill - 4 Energy + 1 Power apiece, so two a turn on the free floor of 2 Power.

Per iteration

one Rocket back in hand per copy sitting in the trash, per conquer, at one aimed discard each

How it ends

engine only - the returns are free but each recast costs 4 Energy + 1 Power, so the free floor of 2 Power a turn pays for two; no scoring anywhere in the line

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-06 (docs/phase0/walks/2026-09-06-discard-trash-lens.md), issue #95 candidate 3. HOLDS. THE FINDING IS THE MULTIPLICITY AND IT IS SETTLED BY THE RULES' OWN WORKED EXAMPLE: 385.2 quotes OGN-252's printed sentence verbatim, so no reading is filed. 385 was cited by NO entry in the catalogue before this walk (grep: 0 hits), and 108.2.d is what makes a trash trigger executable at all. The extra task the issue asked for - correcting the misleading 'why' on the OGN-252 exclusion of the red-brambleback-conquer synergy - was ALREADY APPLIED in data/synergies.json by commit 6eaa1aa (#99, 2026-09-06); this walk read the current text and confirms it, and nothing in data/synergies.json was touched. Card text verbatim from data/corpus_flat.txt. Citations opened: 002, 051, 103.2.b, 108.2.d, 143.4, 157, 161.2.b, 164.2.b, 315.3.b, 355.2.a, 356.1.a, 383.3.d, 385.1, 385.2, 422.1.a, 422.1.b, 430.4.a. Ban check: none of the three carries a [BANNED marker. Trap check: no Attacker designation; no [Repeat]; no [Temporary]; no token, so 185/186.1 never arise; no recall; no Gold; no battlefield of its own; all costs are Main Phase costs, so 167 does not bite. Depends on no unruled reading.

Walked against Core Rules 2026-07-16

Match a deck list against the whole catalogue