Commander Damage Rules: How the 21-Damage Rule Works

In Commander, a player loses if they have been dealt 21 or more combat damage by the same commander over the course of the game. The important words are combat damage and the same commander. Damage from attacks counts. Damage from an activated ability, triggered ability, or spell-like effect on that commander does not count toward the special 21 total unless it was combat damage.

That is why players often get confused when a commander has multiple ways to hurt people. A creature like that can still lower life with any kind of damage, but only combat damage adds to the commander damage record. If a commander attacks for 5 and later pings for 3 with an ability, the player has taken 8 total damage to life but only 5 commander damage.

The 21 rule is an extra way to lose the game. It does not replace life totals. Commander damage still reduces life, and a player can also die the ordinary way by reaching 0 or less life.

Commander damage is tracked by source, not by player and not by team. If one opponent attacks you with a commander for 9 early, then deals another 8 later, that specific source has you at 17 commander damage. If another opponent hits you for 12 with a different commander, those totals do not combine. You are under pressure from two different sources, but neither one has reached 21 yet.

This becomes even more important with partner commanders. If partner A deals 10 combat damage and partner B deals 11, that is not lethal commander damage. Each partner is its own commander for rules purposes, so both totals are tracked separately. The same logic applies when commanders change controllers. The source is the commander itself, not whoever currently owns the card or attacked with it last.

If your table is also tracking poison as a second alternate loss condition, this poison counters guide helps keep the two systems separate.

Yes. A commander with infect deals its combat damage to players as poison counters instead of life loss, but that damage is still combat damage dealt by that commander, so it also adds to the 21 total. In practice the poison race usually ends first, because ten poison counters lose the game long before 21 commander damage does. That double clock is exactly why infect commanders draw so much removal.

Toxic works the other way around. A toxic commander deals normal combat damage that lowers life and grows its commander damage total, and then also hands out poison counters on top. Both clocks advance from a single hit. If your pod plays either mechanic, keep life, poison, and commander damage as three separate numbers, because each one can end the game on its own.

Being a commander is a property of the physical card, not something a copy effect picks up. Rule 903.3 spells this out. A clone copying your commander, or a token copy of it, is not a commander, so its combat damage never adds to any commander damage total. It can still deal plenty of ordinary damage, it just cannot win through the 21 rule.

Control changes work the other way. If an opponent steals your commander and attacks you with it, that damage absolutely counts, because the card is still a commander no matter who controls it. Damage is tracked by the commander as a source, so the same total keeps growing across the whole game even if the creature changes sides several times.

The first common mistake is counting noncombat damage as commander damage. A commander can absolutely burn, drain, fling, or trigger damage, but if the damage was not dealt in combat, it is not part of the 21 total. The second common mistake is combining damage from two different commanders because they belong to the same player or deck. That is never how the rule works.

The third mistake is forgetting that commander damage still changes life totals. Imagine a player at 18 life who takes 7 combat damage from a commander. That player drops to 11 life and also records 7 commander damage from that source. If later they gain life back up to 20, the 7 commander damage does not disappear. Life gain fixes the life total, but it does not erase the commander damage history.

This persistence is why commander damage changes politics in long games. A player sitting at 26 life can still be in immediate danger if one commander has already connected for 16 or 18 across previous turns. In that sense, commander damage works more like a pressure meter than a replacement life bar.

The easiest method is to track each player against each commander source separately. In a four-player pod that means a lot of small numbers, which is exactly why players forget them when using paper scraps or relying on memory. Partner decks double the bookkeeping. The cleanest answer is to use a tracker that stores damage per source instead of one shared commander damage number.

For example, suppose Player 2 takes 6 from Commander 1, later 5 more from that same commander, and then 8 from Commander 2. The correct record is 11 from Commander 1 and 8 from Commander 2. That is not lethal, even though the combined total is 19. One more hit for 10 from Commander 2 would still not matter if Commander 1 remains at 11, because the loss condition only checks whether any single commander has reached 21.

If you are also teaching newer players why Commander starts differently from other formats, the starting life totals guide explains where 40 life fits into the broader game. Then you can return to the main MTG Commander tracker for live play.

Commander damage matters because it changes what counts as safe. A player can be at 30 life and still be one clean combat step from losing if a Voltron commander has already connected twice. That changes blocks, politics, threat assessment, and even how lifegain is valued. A deck that stabilizes well against regular damage can still be vulnerable to one tall attacker.

That is also why players talk about commander damage as a second clock. Life total tells one story. Poison or combo pressure may tell another. Commander damage tells a third story focused on a single recurring threat. Good tables respect all three without mixing them together, because the wrong shortcut often leads to a wrong concession or a missed lethal attack.

No. Commander damage is remembered by source across the whole game, not by the creature's current board state. If a commander hits you for 12, gets removed, returns later, and hits again for 9, that is still 21 from the same commander. Life gain in between does not matter to that record. Neither does the commander being recast from the command zone.

This is one of the biggest reasons players should not rely on memory after a long game. Zone changes make the battlefield look fresh, but the commander damage history is still there. If your table only watches current life totals, it is easy to miss lethal pressure that has been building over several combat steps.

The 21 rule belongs to Commander and its close variants. Casual multiplayer Commander uses it, and one on one Duel Commander keeps the same 21 threshold even though the starting life total is lower there. In every case the tracking works the same way, per commander and per player.

Brawl is the notable exception. The Brawl rules specifically switch off the commander damage loss condition, so a Brawl commander can never win through the 21 rule, on Arena or at a kitchen table. If your group drifts between Brawl and Commander, remember that both the starting life total and this rule change between the two formats.

The fastest clean explanation is this: each commander has its own separate damage track, and a player loses if any one of those tracks reaches 21 combat damage. That framing helps newer players immediately understand why partner commanders do not combine, why abilities do not count unless they are combat damage, and why life gain does not erase the threat.

A practical example helps even more. If a player takes 7 from one commander three different times, they lose even if their life total never reached 0. If they take 10 from one commander and 11 from a different commander, they do not lose to commander damage yet. Once a table hears those two examples, most of the confusion disappears.