Combo · ENGINE

The pool's one answer to a [Tank] wall is one-way by rule - 767 says only the player the ability names ignores it, and only while assigning combat damage

6 cards · fury · verified

Pieces

• Dune Surfer ×3 VEN-004 · enabler · fury

  You ignore [Tank] while assigning combat damage here.

• Cleave ×3 OGN-004 · engine · fury

  [Action] (Play on your turn or in showdowns.) Give a unit [Assault 3] this turn. (+3 Might while it's an attacker.)

Payoff

Deck

• Both cards are mono-Fury, so 103.1.b.3 admits them under any legend with Fury among its two domains - measured over data/cards.json those include OGN-249 / OGN-300 Relentless Storm (fury/body), OGN-251 / OGN-301 Loose Cannon (fury/chaos), OGN-253 / OGN-302 Hand of Noxus (fury/order), SFD-183 / SFD-241 Purifier (fury/body), SFD-185 / SFD-242 Glorious Executioner (fury/chaos), SFD-187 / SFD-243 Void Burrower (fury/order), UNL-183 / UNL-227 Pridestalker (fury/body), UNL-185 / UNL-228 Bloodharbor Ripper (fury/chaos), UNL-187 / UNL-229 Piltover Enforcer (fury/order), VEN-141 / VEN-190 Butcher of the Sands (fury/body) and VEN-143 / VEN-191 Master of Shadows (fury/chaos).
• Neither card is a Signature card (checked against data/cards.json), so 103.2.d.2 imposes no legend, and neither is banned or restricted in either format.
• Dune Surfer's clause says 'here', so he must be present at the battlefield whose combat you are assigning damage in - i.e. he attacks alongside, or he stands there when you defend.

Prerequisites

• WHAT A [TANK] WALL ACTUALLY DOES, AND WHY IT IS WORTH A CARD TO ANSWER. 815.1.c.2: 'Units without Tank are invalid assignments until all units with Tank have lethal damage assigned to them.' It is an ORDERING constraint, not absorption - but ordering is fatal when your summed Might is smaller than the wall. OGN-158 Volibear, Imposing defends at 13 (M10 plus [Shield 3], 814.1.c), so an attack of 12 assigns everything to him, kills nothing, and never legally reaches the Might 2 support behind him. Dune Surfer deletes that constraint for you and the same 12 kills six small bodies instead.
• 764-767 IS THE BLOCK AND ITS TWO WORKED EXAMPLES ARE THIS SENTENCE. 766: 'Any abilities ignored in this way are treated as inactive for the purposes of the game action or procedure', with the example 'A unit reads "You ignore Backline while assigning combat damage here." ... The unit's controller can assign damage to any units with Backline as if they didn't have it.' Dune Surfer prints the same sentence with [Tank]. Neither 764, 765, 766 nor 767 is cited by any entry or synergy rule in this project.
• AND 767 MAKES IT ONE-WAY, WHICH IS THE HALF THAT IS EASY TO MISS. 'Ignored abilities are only treated as inactive for the specific game action or procedure described, and only by the players directed by the ability', with the example 'Any other player assigning combat damage at the same location as that unit will not be able to ignore Backline.' So Dune Surfer standing at a battlefield does NOT switch off YOUR OWN Tank bodies for the opponent - the same board keeps walling them while it stops walling you. The card is a key, not a dispel.
• AND ONLY DURING THE DAMAGE STEP. 767's 'the specific game action or procedure described' scopes it to assigning combat damage, so [Tank] is fully in force for everything else - it never was a targeting restriction anyway (809.1.c prices [Deflect], SFD-105's 'can't be chosen' is the prohibition; [Tank] is neither), so the practical content is exactly the 465.2.c.6 ordering and nothing more.
• IT ANSWERS THE CATALOGUE'S OWN TANK-WALL FAMILY. lillia-flurry-of-feathers-tank-wall, lillia-vanguard-armory-renewing-tank-wall and kinkou-temple-lillia-bird-tank-wall all build a garrison of 1-Might [Tank] tokens whose whole value is 815.1.c.2. One Dune Surfer at that battlefield and the tokens are ordinary bodies again - and because he is Fury and Lillia is Calm, 103.1.b keeps them on opposite sides of the table, which is the honest reason this is a matchup card rather than a mirror-breaker.
• 465.2.c.4 IS STILL IN FORCE AND CAPS WHAT IGNORING BUYS. 'A player may not assign more damage to a unit than the minimum needed to kill it', so ignoring Tank changes WHICH bodies receive lethal, never how much total damage you have. Cleave is in uses[] because the constraint the wall really imposes is on total summed Might: 807.2 sums the granted [Assault 3] onto whatever the body prints, and 807.1.d.1 keeps it for as long as the Attacker designation lasts.
• 465.2.c.10 IS THE OTHER WAY THROUGH, AND IT IS NOT THIS CARD. 'If a unit cannot be dealt damage, then no amount of damage can be considered lethal. Such a unit is exempt from any considerations of mandatory assignment.' A Tank whose damage is entirely prevented (437.4) stops being a mandatory assignment at all - so a full Prevent switches a wall off from the other side. Recorded here because the two mechanisms read alike and are different: Dune Surfer removes the keyword's effect for you, a Prevent removes the body from the ordering for everyone.

Steps

1. Play VEN-004 Dune Surfer (3 Energy) and your attackers; 143.4 has them enter exhausted, so they attack from the following turn.
2. Standard-move Dune Surfer and the attackers to the enemy battlefield together (144.3 makes simultaneous Standard Moves one action to a shared destination). His clause says 'here', so he must be among them.
3. Contested applies (190.3.a.1), the Combat stages (323.9) and opens (323.13), and 464.2.c.3 designates the attackers. In the opened Combat Showdown play OGN-004 Cleave (1 Energy, [Action], 806.1.b) on your largest body: 807.2 sums the granted [Assault 3] with anything printed.
4. In the damage step, 766 treats every instance of [Tank] in the enemy garrison as inactive for YOUR assignment. 815.1.c.2 no longer makes their other bodies invalid, so you assign minimum lethal (465.2.c.4) to whichever units you actually want dead.
5. 767 keeps the asymmetry: any Tank of your own at that battlefield still walls the opponent's assignment normally, because the ability names you and not them.
6. The Surfer stays, so every later combat at that battlefield is assigned the same way. Three copies (103.2.b) cover both Duel battlefields and survive removal.

Per iteration

the enemy garrison's assignment order stops being theirs to set, for as long as the Surfer stands there, and your own Tanks keep working against them

How it ends

engine only - nothing here scores. It is bounded by the Surfer's presence at that battlefield and by 465.2.c.4, which never lets ignoring Tank produce more total damage than your summed Might

Sources

Published elsewhere

• Riftbound Core Rules, Last Updated 2026-07-16 (data/Riftbound-Core-Rules-2026-07-16.txt), 766 worked example 2026-07-16
• Riftbound Core Rules, Last Updated 2026-07-16 (data/Riftbound-Core-Rules-2026-07-16.txt), 767 2026-07-16
• Riftbound Core Rules, Last Updated 2026-07-16 (data/Riftbound-Core-Rules-2026-07-16.txt), 465.2.c.10 2026-07-16

Walked here, in this project

• Hand walk 2026-09-07 2026-09-07 record

Walked against Core Rules 2026-07-16

Match a deck list against the whole catalogue