RIFTCOMBO

Combo · ENGINE

One card moves both bodies, and its own parenthetical settles which player the Contested rules make the attacker

6 cards · body + chaos · verified

Pieces

Payoff

Unit delivery

Deck

Run play

Prerequisites

Steps

  1. Decide which designation you want before casting - the card gives you either.
  2. 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.
  3. 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.
  4. 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.
  5. 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].
  6. 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

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 #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

Match a deck list against the whole catalogue