Battlefield Abilities and Control

Control and Contested are separate states. When an opposing unit arrives, the battlefield becomes Contested, meaning a player is challenging its control, but its existing controller stays its controller during the Showdown or Combat until the procedure instructs a change.

Example - A controls a battlefield. B moves a unit there. During the resulting contest, A remains its controller. An ability referring to the battlefield’s controller still refers to A. Even if A’s last unit leaves during the contest, do not transfer control early; finish the relevant contest steps.

Normally, the battlefield’s controller handles its abilities: placing triggered abilities, which happen when a specified event occurs, on the Chain and making their choices. The Chain tracks spells and abilities waiting to resolve, meaning to carry out their instructions. Read the text before applying that default. An ability naming the player who makes a choice gives that player control of the ability, even if someone else controls the battlefield.

Abandoned Hall is a useful example. When a player plays a spell, that player may give a unit they control there +1 Might for the turn. If A controls the battlefield and B plays the spell, B controls this triggered ability and chooses B’s eligible unit. A cannot choose a unit instead.

If the battlefield is uncontrolled and its ability does not name a controller, the turn player handles adding it to the Chain and making its choices. Treat that player as its controller if a rule needs one. An explicitly named player still takes precedence.

That responsibility does not make the turn player the battlefield’s controller. In battlefield text, “you”, including an implied “you” in an instruction such as drawing a card, means the battlefield’s controller. At an uncontrolled battlefield it refers to no one, so those instructions are ignored. An instruction explicitly naming a player can still work.

After the contest and intervening effects, the appropriate control step may establish a new controller. From then on, the normal default uses that player. An ability already created on the Chain is a separate object: changing the battlefield’s controller does not by itself transfer that existing ability.

Example - A’s battlefield ability is already on the Chain. The battlefield later comes under B’s control. A still handles the existing ability unless another effect changes that ability’s controller. Future abilities use B as the default. In a team game, the teammate’s control is still separate; shared points do not mean shared battlefield control.