Combo · ENGINE
One card moves both bodies, and its own parenthetical settles which player the Contested rules make the attacker
Pieces
- Void Assault ×3
UNL-202 · payoff · body/chaos
Move a friendly unit, then move an enemy unit. (If they both move to a battlefield you don't control, you're the attacker.)
- Towering Combatant ×3
UNL-099 · engine · body
[Shield 2] (+2 Might while I'm a defender.) [Tank] (I must be assigned combat damage first.)
Payoff
Deck
- UNL-202 Void Assault is a SIGNATURE card tagged Kha'Zix, so 103.2.d.2 forces a Kha'Zix legend whose two domains cover body + chaos - and the census prints exactly one such name: UNL-201 / UNL-236 Voidreaver. No other legend can hold this list.
- Neither card is banned or restricted in either format. The spell spends one of the three Signature slots 103.2.d.1 allows; UNL-099 is not a Signature card.
- Two bodies to move, one of them theirs. Both halves are effect moves under 449, so 420.3.a's exhaust and 144.4's destination limits do not apply.
Run play
Prerequisites
- THE PARENTHETICAL IS A PRINTED ANSWER TO A RULES QUESTION, AND IT IS WORTH READING TWICE. 190.3.a.1 applies Contested to a battlefield when a unit moves there whose CONTROLLER does not already control it, and 450 says the same from the destination's side; 464.2.c.1 then makes the Attacker 'the player whose unit(s) applied the Contested status'. If BOTH players' units move to a battlefield neither controls, both applied it - and the card resolves the tie itself: '(If they both move to a battlefield you don't control, you're the attacker.)' No reading was needed and none is filed.
- AND THE OTHER DIRECTION IS THE ONE THE CARD DOES NOT SPELL OUT. Move the enemy unit to a battlefield YOU control and the same paragraphs run the other way: THEIR unit applied Contested to a battlefield they do not control, so THEY are the Attacker and you are the Defender (464.2.c.2) - on your own turn. That is the trick this catalogue records on OGN-067 Blitzcrank, Impassive, and Void Assault is a second, cheaper way to set it up, with the added half that your own body can be moved into the same fight in the same card.
- SO ONE SPELL CHOOSES WHICH SIDE OF THE COMBAT YOU ARE ON, WHICH NOTHING ELSE IN THE POOL DOES. Attacking matters for every 'when I attack' trigger and for [Assault] (807.1.c, 807.1.d); defending matters for [Shield] (814.1.c) and for every 'when I defend' trigger. Two Energy and a Power buys the designation you want, and the parenthetical is how you know which you are getting.
- BOTH HALVES ARE EFFECT MOVES, WHICH IS WHY EXHAUSTED BODIES ARE FINE. 449: 'Spells, Abilities, or other effects may cause a Move to occur', with 449.1 leaving the restrictions to the source; 420.3.a puts the exhaust cost on the STANDARD Move alone, so a body that has already acted this turn can still be moved, and 144.4's base-to-battlefield restriction never comes up - this goes battlefield to battlefield with no [Ganking]. 449.2 is the one limit: 'Units cannot Move to a Battlefield that already has units from 2 other players present by any means', which in a Duel (485.1) never applies.
- AND THE ARRIVING BODIES ARE IN THAT COMBAT. 319.6 runs after Game Objects enter or leave the Board, and 323.2.a: 'If there are Units present at the Battlefield the Combat is taking place at, but do not have a designation, they gain the same designation as their Controller now.' 143.4's entering exhausted is irrelevant on defence, because neither 464.2.c.3 nor 465.2.b filters by state.
- THE PARTNER IS A [TANK] BECAUSE THE DEFENSIVE DIRECTION IS THE STRONGER ONE. Dragging one enemy body onto a battlefield you hold makes them the Attacker with a garrison of exactly one, and 815.1.c.2 then makes every other body of yours an invalid assignment until the Towering Combatant - a 3 that reads 5 on defence by 814.1.c - has lethal. 466.1.a.2 recalls the dragged body to their base if it survives, so price this as forced damage and a tempo tax rather than as removal.
- WHAT IT IS NOT. Nothing here scores; 469 defines Scoring as Conquer or Hold. And it moves ONE body of each - it sets up a fight, it does not win one.
Steps
- Decide which designation you want before casting - the card gives you either.
- TO ATTACK: move your unit and their unit to a battlefield NEITHER of you controls. Both applied Contested, and the card's own parenthetical makes YOU the attacker.
- TO DEFEND ON YOUR OWN TURN: move their unit to a battlefield YOU control. 190.3.a.1 with 450 keys Contested on the MOVED unit's controller, so 464.2.c.1 makes them the Attacker and 464.2.c.2 makes you the Defender.
- Move your own Towering Combatant in alongside if it is not already there - 449 allows it and 420.3.a means an exhausted body is fine.
- 319.6 with 323.2.a give both arrivals their designations before 465.2 resolves; 815.1.c.2 then forces the whole assignment onto the [Tank].
- Expect the dragged body to go home if it lives: 466.1.a.2 recalls Attackers when Defenders remain.
Per iteration
one combat created on the side of your choosing, for 2 Energy and 1 Power, moving one body of each
How it ends
engine only - three copies by 103.2.b, one fight each, and a dragged body that survives is recalled to their base (466.1.a.2); nothing here scores
Sources
Published elsewhere
- Riftbound Core Rules, Last Updated 2026-07-16 (data/Riftbound-Core-Rules-2026-07-16.txt) 2026-07-16
- Card text verbatim from data/corpus_flat.txt (built from Riot's gallery content API) 2026-09-07
Walked here, in this project
- Hand walk 2026-09-07 (docs/phase0/walks/2026-09-07-orphan-remainder.md, part 1) 2026-09-07 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-07 (issue #193, part 1). The first entry to use UNL-202 Void Assault. Card text verbatim from data/corpus_flat.txt. Citations opened and quoted: 103.2.b, 103.2.d.1, 103.2.d.2, 143.4, 144.4, 190.3.a.1, 319.6, 323.2.a, 420.3.a, 449, 449.1, 449.2, 450, 464.2.c.1, 464.2.c.2, 464.2.c.3, 465.2, 465.2.b, 466.1.a.2, 469, 485.1, 807.1.c, 807.1.d, 814.1.c, 815.1.c.2. Its parenthetical is a printed resolution of the both-players-applied-Contested case, so no reading is filed. Ban check: neither card is banned or restricted. No unruled reading.
Walked against Core Rules 2026-07-16