Can you dodge Hidden Blade with a Tideturner at a different battlefield?

Yes, you can dodge a Hidden Blade with a Tideturner played from hidden at a different battlefield.

According to the RiftJudge FAQ entries (specifically FAQ #7179, #210, and #7907), Tideturner is a special case that is permitted to target units outside of its own battlefield when played from hidden. Because of this, it is an effective way to remove your unit from the battlefield that Hidden Blade is targeting.

How the Interaction Works:

  1. Hidden Blade is played/activated targeting your unit at Battlefield A.
  2. You play your Hidden Tideturner at Battlefield B in response.
  3. Tideturner enters play and its triggered ability ("When you play me...") goes on the chain.
  4. You resolve the Tideturner ability, swapping your unit from Battlefield A with the Tideturner at Battlefield B.

The Result:

  • If Hidden Blade was played from your hand: Per FAQ #7179, Hidden Blade simply requires that the target be a unit at any battlefield. If you move your unit to a different battlefield, Hidden Blade still tracks it and will successfully kill it at the new location. In this scenario, you do not dodge the effect.
  • If Hidden Blade was played from "Hidden": Per FAQ #210 and the core rules (811.1.d.2), when played from hidden, Hidden Blade is restricted to targeting a unit at the specific battlefield where it was hidden. If you move the target away with Tideturner, the target becomes illegal for the Hidden Blade. The Hidden Blade will resolve, but because its target is no longer at the specified battlefield, it will "mistarget" and have no effect (no unit dies, no cards are drawn). In this scenario, you successfully dodge the effect.

Note: This interpretation is based on the specific interaction rules for "Hidden" cards and the unique targeting capabilities of Tideturner as documented in our FAQ. Official rulings confirm that Tideturner's ability to target outside its location when hidden overrides the standard restriction for hidden cards.

FAQ #10852June 5, 2026