Banishment and Linked Destinations

If an effect banishes a card and later refers to that card, keep the association clear. Another copy of the card that created the effect does not gain access to the first copy’s banished card. Following similar instructions again also does not let you retrieve every card previously banished that way.

Example - One effect banishes card A and creates a triggered ability that draws it when you Conquer this turn. A second effect banishes card B with the same instructions. Each trigger retrieves only its own card. If the first effect’s duration expires unused, a later copy cannot retrieve A merely because A is still in Banishment.

An instruction may name one destination while a replacement effect makes the card go somewhere else. Carry out the replacement and use the resulting event when evaluating later instructions; do not pretend the original journey also happened. Banish is distinct from Kill and Discard.

A spell played for Flow illustrates the destination check once it is finalized: its choices, costs and legality checks are complete, and it is waiting on the Chain. If Abandon counters it and tries to return it to hand, Flow replaces that departure with banishment. The spell goes to Banishment, even though Abandon would ordinarily return a countered spell to its owner’s hand. The costs already paid stay paid.

Replace creates a token in the original object’s place and stores the original in Banishment. This is not a Banish action, and creating that token is not playing it. Units and facedown cards at a replaced battlefield stay in place. The token inherits control, scoring history, effects and statuses.

Existing effects that target or refer to the battlefield follow the replacement token as the same game object. Its own printed abilities now apply, but an ability already on the Chain can still use that location. Replacing a battlefield you scored earlier this turn does not create another scoring opportunity there.

When an effect instructs a swap-back, the token disappears and an eligible original returns from Banishment to that space. The original inherits the token’s current effects and statuses, not the state it had before replacement. An original replaced earlier in a chain of replacements can remain eligible. If no eligible original is left in Banishment, the swap-back cannot happen.

Worked sequence - Player A controls and scores a battlefield → it is Replaced → Player B later takes control of the token → an effect swaps the original back. Player B keeps control of the returning battlefield. Its location and current scoring history persist; returning the original does not rewind the intervening game.