Combo · ENGINE
Blast Cone and Moonfall — the opponent attacks into your garrison, stunned, on your turn
Pieces
- Blast Cone ×1
UNL-133 · payoff · chaos
When you play this, you may move an enemy unit. When you move an enemy unit, you may exhaust this to [Stun] it. (It doesn't deal combat damage this turn.)
- Moonfall ×3
UNL-198 · engine · mind/chaos
[Action] (Play on your turn or in showdowns.) Choose a battlefield where you have units. You may move up to one enemy unit to that battlefield. Then give enemy units there -2 Might this turn.
Payoff
Deck
- UNL-198 Moonfall is a SIGNATURE card tagged Diana, so 103.2.d.2 forces a Diana legend that also covers chaos + mind: UNL-197 Scorn of the Moon — the only one. Domain-legal legends without the Diana tag cannot run the list. (Rebuilt from the census by test/legend-lines.test.ts, 2026-09-07; an earlier line named legends that cannot hold a Diana Signature card.)
- A garrison of your own at the destination battlefield — Moonfall's own condition, and what makes the combat one-sided.
Prerequisites
- The mechanism is CLAUDE.md's #58 and #141 finding used offensively, and every link was opened. 190.3.a.1 applies Contested to a battlefield when a unit whose controller does not control it moves there — it keys on the MOVED unit's controller, not on who caused the move. 464.2.c.1: 'The Attacker is the player whose unit(s) applied the Contested status to the Battlefield.' So dragging an enemy body onto a battlefield you control makes THEM the Attacker, on YOUR turn.
- The stun then blanks their whole side of the damage step: 423.1.b — 'A Stunned Unit does not contribute its might to damage in the combat damage step.' 465.2.c has each player assign damage equal to their summed Might; theirs is nothing, yours is the whole garrison.
- It still has to DIE, and that is where Moonfall's second clause earns its place: 423.1.c with 710 keeps the stunned body's full CURRENT Might as the damage needed to kill it (the #89 correction to #61), and -2 Might this turn lowers exactly that number. 143.2.b caps the downside: a Might driven below zero is TREATED as 0 for the damage step, so the -2 can never hand the attacker anything back — though 143.2.b.1 warns it 'is not 0', which matters only if something later tries to add Might back.
- One stun per turn. The Cone's second ability costs its own exhaust and 315.1.b readies it at Awaken, so three Moonfalls across three turns is three stuns; three in one turn is one stun and two ordinary drags. 423.1.a.1 ('A Stunned Unit can not be Stunned again') closes the other door.
- This does not reach an EMPTY board. If the dragged unit is the opponent's last body at its origin, 323.6 strips their Control there as a bonus — but the combat this entry wins is at YOUR battlefield, and 466.5's Conquer is not available to you there because 464.2.c.2 and 323.11.a make you the Defender who already controls it (the #118 finding). This is removal, not a point.
- Four drags a game at most: the Cone's play effect once, plus three Moonfalls (103.2.b).
Steps
- Have a garrison at a battlefield you control, and the Blast Cone on the board and ready.
- In your Main Phase, cast Moonfall for E3 + 1 Power choosing that battlefield. Move one enemy unit there, then give enemy units there -2 Might this turn.
- The Cone's second trigger sees the enemy move: exhaust it to [Stun] the unit you just dragged.
- The Cleanup applies Contested (190.3.a.1). 323.9 stages the Combat and 323.13 opens it; 464.2.c.1 makes the OPPONENT the Attacker on your own turn, and 464.2.c.3 hands the designations out.
- 465.2.c: the stunned attacker assigns nothing (423.1.b); your garrison assigns its summed Might against a body that 423.1.c / 710 price at its current Might, already 2 lower. It dies and you take nothing.
- 466.1.a.2's recall of surviving Attackers has nothing to send home. Repeat next turn with the second Moonfall, after 315.1.b readies the Cone.
How it ends
engine only — up to four enemy bodies dragged and up to one killed per turn with no damage taken, bounded by three Moonfalls (103.2.b) and by one Cone exhaust a turn. Nothing here scores: you are the Defender at your own battlefield, so 466.5 gives no Conquer.
Sources
Published elsewhere
- Riftbound Core Rules, Last Updated 2026-07-16 (data/Riftbound-Core-Rules-2026-07-16.txt) 2026-07-16
- Issue #153 (GitHub) 2026-09-06
Walked here, in this project
- Hand walk 2026-09-06, issue #153 — the 55 synergy rules no catalogued entry stands on 2026-09-06 record
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-orphan-synergy-rules.md §14), issue #153, from the orphan rule blast-cone-enemy-move. Card text verbatim from data/corpus_flat.txt. Citations opened: 103.1.b.2, 103.1.b.3, 103.2.b, 143.2.b, 143.2.b.1, 190.3.a.1, 315.1.b, 323.6, 323.9, 323.11.a, 323.13, 423.1.a.1, 423.1.a.2, 423.1.b, 423.1.c, 464.2.c.1, 464.2.c.2, 464.2.c.3, 465.2.c, 466.1.a.2, 466.5, 710. CLAUDE.md recorded that 'no entry of the catalogue moves an ENEMY unit' as of #58; this is the first that does it to make them the Attacker, and it names the reason the line does NOT score (#118's 464.2.c.2 / 323.11.a). Trap check: the combat has units of both players, so the empty-battlefield trap does not arise; no [Repeat] is used, and Moonfall carries none; no [Temporary]; no token; the drag is a move by effect, not a Recall, so 455 does not carve it out; 167 is not touched. Depends on no unruled reading.
Walked against Core Rules 2026-07-16