Planeswalkers & Battles

Loyalty, the uniqueness rule, and the newest permanent type almost nobody has read the rules for.

Planeswalkers and battles are built from the same three pieces, so learning one teaches you most of the other. Both are cast at sorcery speed. Both enter carrying counters. Both are attacked rather than blocked. And for both, the number in the lower right corner is only their starting value — once on the battlefield, the counters are the characteristic.

Loyalty is counters, not a life total

A planeswalker's loyalty off the battlefield is the printed number. On the way in, its own intrinsic ability — a replacement effect, not a trigger — puts that many loyalty counters on it. From then on its loyalty simply is the number of counters. There is no separate tracker, and nothing is "marked" on it.

That single fact answers most planeswalker questions. Damage removes that many loyalty counters, immediately and permanently; there's no damage-wears-off-at-end-of-turn step, because no damage was ever marked. Proliferate and counter-doubling effects work on planeswalkers because loyalty is counters like any other. And when loyalty hits 0, a state-based action puts the planeswalker in the graveyard — no trigger, no stack, nothing to respond to.

Loyalty abilities: once per turn, per permanent

You may activate a loyalty ability any time you have priority during a main phase of your turn with an empty stack — sorcery timing. The restriction that catches people is the other half: only if no player has previously activated a loyalty ability of that permanent this turn. It belongs to the permanent, not to you, so gaining control of a planeswalker whose ability an opponent already used gets you nothing this turn.

Two more details worth having. A negative loyalty ability can't be activated at all unless the permanent has at least that many counters — you can't overpay into death. And when several add-or-remove-loyalty costs combine, they become a single cost first: with an extra [+1] applied, a [−4] is a cost of removing three counters, which a planeswalker with only 3 loyalty can therefore pay.

Two rules that were deleted

Both of these are still quoted confidently at tables, and both are gone:

• The planeswalker uniqueness rule. Two planeswalkers sharing a type are no longer forbidden by that rule. Old planeswalkers were given the legendary supertype in Oracle instead, so it's the ordinary legend rule — which cares about names — that stops you keeping two Jaces.
• Damage redirection. You can no longer choose to send noncombat damage aimed at a player to their planeswalker. Aim at what you want to hit; "any target" already includes planeswalkers and battles.

Battles, and the protector

Battles copy the planeswalker template — defense instead of loyalty, defense counters instead of loyalty counters — and add one genuinely new idea: every battle has a protector, chosen as it enters.

The protector, not the controller, is the axis everything turns on. A battle's protector can never attack it, and it can be attacked by any player for whom the protector is a defending player. Every battle printed so far is a Siege, and a Siege's protector must be one of its controller's opponents — which produces the rule that reads like a misprint the first time: you attack your own Siege. The protector is also the only player who may block those attackers, and while the battle is under attack, every effect that says "defending player" means the protector.

Crack it and the Siege's own trigger exiles it and lets its controller — not the player who dealt the damage — cast the transformed back face for free. Note the careful wiring: a battle at 0 defense goes to the graveyard as a state-based action unless it's the source of an ability that has triggered but not yet left the stack, which is precisely what keeps the Siege around long enough to flip.

20 questions in this track, checked against the 2026-06-19 Comprehensive Rules.

Rules covered: 306.1, 306.3, 306.4, 306.5a, 306.5b, 306.5c, 306.5d, 306.6, 306.8, 306.9, 310.1, 310.4a, 310.4b, 310.4c, 310.6, 310.7, 310.8a, 310.8b, 310.8c, 310.8d, 310.8f, 310.9, 310.10, 310.11a, 310.11b, 508, 508.5, 606.2, 606.3, 606.5, 606.6, 614.1c, 704, 704.5j.