Combo · ENGINE
Stalking Wolf eats a Bird — six Might at Reaction speed where you have nothing left
Pieces
- Stalking Wolf ×3
UNL-166 · payoff · order
[Ambush] (You may play me as a [Reaction] to a battlefield where you have units.) As an additional cost to play me, kill a Bird, Cat, Dog, or Poro you control. You may [Ambush] me to its battlefield, even if you don't have other units there.
- Ultrasoft Poro ×1
UNL-160 · engine · order
Exhaust: Play two 1 Energy Might Bird unit tokens with [Deflect]. Use this ability only while I'm at a battlefield. (Opponents must pay 1 Power of any domain to choose a [Deflect] unit with a spell or ability.)
Payoff
Deck
- Mono-Order.
- A battlefield you control with one of your Birds standing on it - which is also the Bird you are about to kill.
Prerequisites
- The pair is a real dependency, not a preference: 356.2.a.1 makes "as an additional cost to play me, kill a Bird, Cat, Dog, or Poro you control" mandatory, because it carries no "may". Without one of those four tags on the board Stalking Wolf is a dead card.
- The fuel is exactly the tag, checked card by card in the corpus. UNL-T02 Bird is [Tags: Bird] and qualifies; UNL-160 Ultrasoft Poro qualifies as himself, [Tags: Poro, Freljord]; UNL-153 Carrion Dredger does NOT - it is [Tags: Mech, Zaun] - although the Bird token it dies into does.
- What the final clause actually widens, and what it does not. 822.1.b is "I may be played to a battlefield where you control Units" and 822.1.c calls Ambush a passive that "adds options to locations that are valid"; the Wolf's own sentence waives Ambush's own requirement for one battlefield, so he can arrive at a battlefield you control where your last body there is the token you just killed. It does not hand out a battlefield you do not control: 813.3.a keeps the inherent restriction that a unit played with Reaction "can only be played to the controlling player's base or a battlefield they control". This entry is written so it never has to settle whether the clause overrides 813.3.a for a token that walked onto an enemy battlefield - that question is real but no line here stands on it.
- He arrives exhausted (143.4), so he never attacks or moves the turn he lands. His whole value is being present before the Cleanup: 464.2.c.3.a gives a unit that becomes present after the fact the Attacker or Defender designation during the Cleanup following the action, so 6 Might joins the combat after the opponent has already committed their turn.
- Ultrasoft Poro readies once a turn (415.3.a) and makes two Birds, so he sustains one Wolf per turn. 103.2.b caps the Wolves at 3, and each is a one-shot: 4 Energy + 1 Order Power + one token, three times.
Steps
- Have Ultrasoft Poro at a battlefield you control and exhaust him on your turn for two 1-Might Bird tokens.
- Pass. The opponent commits their turn against a board that looks like two 1-Might tokens.
- At Reaction speed, play Stalking Wolf: the mandatory additional cost kills one of the Birds (356.2.a.1) and the final clause lets him [Ambush] to that Bird's battlefield even if it was your only body there.
- 464.2.c.3.a gives him the Defender designation in the Cleanup that follows, so a 6-Might body is in the combat the opponent had already sized up. He is exhausted (143.4) and does nothing else this turn.
How it ends
one 6-Might Reaction body per turn out of a free token, up to three across the game
Sources
Walked here, in this project
- Reaction/Deflect lens hunt, issue #44 candidate 6 (rc-huntF) 2026-09-05
- Hand walk 2026-09-06 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-reaction-deflect-candidates.md), issue #44 candidate 6. The verdict is the hunt's, the argument is not. #44 closed the door on an enemy battlefield with 355.2.a - "tokens can only have been played to your base or a battlefield you control, so there is never a token of yours where you have no presence" - and 355.2.a governs where a token is PLAYED, not where it can stand: a token moves, and moving to an enemy battlefield is how attacking works. The rule that actually closes it is 813.3.a, with 822.1.c explaining that what the Wolf's clause lifts is Ambush's own "where you control Units" requirement. Written so that the residual question (822.1.c against 813.3.a) is not load-bearing, so no reading was filed, the same discipline #44 used for 809.2.
Walked against Core Rules 2026-07-16