RIFTCOMBO

Combo · ENGINE

Vilemaw's Lair works while nobody controls it, and Bounty Hunter is the only legend that unsticks a unit from it every turn for free

2 cards · body + chaos · verified

Pieces

Payoff

Tempo denial

Deck

Prerequisites

Steps

  1. Bring Vilemaw's Lair as one of your three battlefields (485.4.a). It needs no Control and no set-up: the sentence has no 'you' for 190.6.d to blank.
  2. Play normally. Any unit that walks to the Lair — yours or theirs — loses 144.4.b, its only other Standard Move destination.
  3. When the opponent commits a garrison there and keeps it, those bodies are stranded: they cannot reach their base and they cannot reach the other battlefield of the Duel without [Ganking].
  4. On each of your turns, exhaust Bounty Hunter to give one of your own units [Ganking] this turn and move it from the Lair to the other battlefield with its Standard Move (144.4.c.1, paying 144.2's exhaust).
  5. 315.1.b readies the legend every Awaken, so the grant is available again next turn. 810.2 makes a second grant on the same unit worth nothing.

How it ends

engine only — a permanent one-way movement lock on everything the opponent leaves at this battlefield, with one of your own bodies bought out of it per turn; nothing here scores and nothing about it is unbounded

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 #171 — the first entry to use either card, and the first of the ten uncatalogued legend names to be walked. Card text verbatim from data/corpus_flat.txt. The obvious first reading of Vilemaw's Lair is that it strands a failed attack; 456.3 refutes that in one sentence and it was checked before the entry was written, which is why the notable leads with it. Trap check: no attack is claimed, so 807.1.d / 383.4.e / 461 never come up; 190.6.d is cited for what it does NOT do here, which is the #161 Ripper's Bay reading applied a second time; 810.1.c.3 is cited so [Ganking] is not mistaken for an extra move; exactly one battlefield is named, so 485.4.a is respected; produces is deliberately empty, as it is on the twenty-six other lock and shield entries the vocabulary does not yet cover (issue #157).

Walked against Core Rules 2026-07-16

Match a deck list against the whole catalogue