RIFTCOMBO

Combo · ENGINE

The fourth route to making the opponent attack on your turn — and the only one that pumps your garrison with the same card

2 cards · calm + order · verified

Pieces

Payoff

Repeatable removal

Deck

Prerequisites

Bodies no card supplies

Have exactly two friendly units at a battlefield you control

Steps

  1. Have exactly two friendly units at a battlefield you control.
  2. Play Shadow Dash (2 Energy + 1 Power): move an enemy unit to that battlefield. Your two units each get +1 Might this turn.
  3. 450 and 190.3.a.1 apply Contested through THEIR unit, so 464.2.c.1 makes them the Attacker; the next Cleanup stages and opens the Combat (323.9, 323.13).
  4. Inside the combat, exhaust Eye of Twilight at [Action] speed: give the bigger of your two units [Tank] this turn.
  5. 815.1.c.2 makes your other body an invalid assignment until the Tank has lethal, so all of the dragged unit's damage lands where you chose.
  6. 465.2.c: your summed Might is the two bodies plus 2. If it reaches the dragged unit's Might it dies; if not, 466.1.a.2 recalls it to their base and 466.1.a.1 heals everything.

Per iteration

one enemy unit dragged off its battlefield and into a fight you chose, with +2 summed Might and all of its damage funnelled into one body of yours

How it ends

engine — one enemy body pulled out of position and fought on your own terms per Shadow Dash, six a game with the [Flow] replays; no point is scored, because 466.5 gives Control only to a player who did not already have it

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.

VEN-148 Shadow Dash was in ZERO entries; VEN-147 Eye of Twilight appears in two others (`eye-of-twilight-zephyr-sage-tank-redirect`, `royal-entourage-eye-of-twilight-double-tank`), both of which grant [Tank] against an attack the OPPONENT chose to make — this entry schedules the attack itself, which is the different number. Card text verbatim from data/corpus_flat.txt; 103.2.b, 103.2.d.1, 103.2.d.2, 108.6.c, 190.3.a.1, 323.9, 323.13, 450, 455, 464.2.c.1, 465.2.c, 466.1.a.1, 466.1.a.2, 466.5, 806.1.b, 809.1.c, 815.1.c.2, 829.1.b opened in the Core Rules file. The comparison with the three existing routes to the same mechanism is stated in the first notable, as the catalogue requires of a fourth member of a family.

Walked against Core Rules 2026-07-16

Match a deck list against the whole catalogue