{"id":1479,"date":"2026-08-07T06:50:16","date_gmt":"2026-08-07T06:50:16","guid":{"rendered":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/"},"modified":"2026-08-08T07:01:17","modified_gmt":"2026-08-08T07:01:17","slug":"mtg-commander-damage","status":"publish","type":"post","link":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/","title":{"rendered":"MTG Commander Damage Explained: The 21 Rule, Every Edge Case, and the Commanders That Get There (2026)"},"content":{"rendered":"
\n\"A\n<\/figure>\n\n

Every page you have ever read about commander damage tells you the same sentence: deal 21 combat damage with the same commander and that player loses. That sentence is correct, and it is where every one of those pages stops. It is also almost never the thing you needed to know, because the arguments that actually break out at a table are never about the number 21. They are about whether the token copy counts, whether the infect swing counts, whether gaining forty life bought you anything, and whether the counter went back to zero when you finally killed the thing.<\/p>\n\n

This guide answers those. Every rule below is quoted from the official Magic: The Gathering Comprehensive Rules<\/strong> text file effective 7 August 2026<\/strong> \u2014 the version Wizards published alongside The Hobbit<\/em> \u2014 and every card is verified against the live Scryfall database at the time of writing, including its current Commander legality and price. Where a widely repeated piece of advice is wrong, it is named.<\/p>\n\n

The rule, in the exact words that matter<\/h2>\n\n

Commander damage is written into the Comprehensive Rules in three separate places<\/strong>, and all three say the same thing. That redundancy is worth knowing about, because it means there is no obscure fourth clause hiding somewhere that changes the answer.<\/p>\n\n\n\n
Rule<\/th>What it says<\/th>Why it matters<\/th><\/tr><\/thead>\n
903.10a<\/strong><\/td>“A player who’s been dealt 21 or more combat damage by the same commander over the course of the game loses the game. (This is a state-based action. See rule 704.)”<\/td>The primary statement. Note “over the course of the game” \u2014 this is the phrase that makes the counter permanent.<\/td><\/tr>\n
104.3j<\/strong><\/td>“In a Commander game, a player who’s been dealt 21 or more combat damage by the same commander over the course of the game loses the game.”<\/td>Listed among the ways to lose the game, alongside 0 life and ten poison counters.<\/td><\/tr>\n
704.6c<\/strong><\/td>“In a Commander game, a player who’s been dealt 21 or more combat damage by the same commander over the course of the game loses the game.”<\/td>Listed as a state-based action, which is what makes it automatic and untargeted.<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n

Being a state-based action<\/em> is not trivia. It means nobody has to notice, nobody has to do anything, and it cannot be responded to. The game checks the condition every time a player would receive priority, and the moment the 21st point has been dealt, that player has lost. You cannot hold up an instant to save yourself after the damage resolves, for the same reason you cannot respond to dying at 0 life \u2014 and that is the same timing rule that governs everything in flash, priority and the stack<\/a>.<\/p>\n\n

Four words decide every argument: “combat damage by the same commander”<\/h2>\n\n

Nearly every real dispute over commander damage comes down to one of those four words. Here is what each one excludes.<\/p>\n\n\n\n
Source of the damage<\/th>Counts toward 21?<\/th>The reason<\/th><\/tr><\/thead>\n
Your commander attacks and connects with a player<\/td>Yes<\/strong><\/td>Combat damage, dealt by the commander, dealt to a player. All three conditions met.<\/td><\/tr>\n
Your commander is blocked and assigns damage to the blocker<\/td>No<\/strong><\/td>The damage was dealt to a creature, not a player. 903.10a is explicit that the recipient is a player.<\/td><\/tr>\n
Your commander deals damage via an activated or triggered ability<\/td>No<\/strong><\/td>Not combat damage. A commander that pings for 2 on tap will never close a game on the 21 clock.<\/td><\/tr>\n
Your commander fights another creature<\/td>No<\/strong><\/td>Fight damage is not combat damage, and it is not dealt to a player.<\/td><\/tr>\n
A spell you cast deals damage while your commander is out<\/td>No<\/strong><\/td>The commander is not the source.<\/td><\/tr>\n
Your commander deals combat damage to a planeswalker<\/td>No<\/strong><\/td>Rule 120.3c: that damage removes loyalty counters. The player was not dealt anything.<\/td><\/tr>\n
Your commander deals combat damage to a battle<\/td>No<\/strong><\/td>Rule 120.3h: that damage removes defense counters.<\/td><\/tr>\n
Your commander connects while it has infect<\/td>Yes<\/strong><\/td>Combat damage is still dealt; infect only changes the result<\/em>. See the infect section below.<\/td><\/tr>\n
An opponent<\/em> attacks you with your own commander they have stolen<\/td>Yes<\/strong><\/td>903.10a never says whose commander. It says “the same commander.” Detailed below.<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n

The second row is the one that costs games. A commander with high power that keeps getting chump-blocked is making no progress at all on the 21 clock, no matter how much damage it “deals” each turn \u2014 which is why evasion, not power, is the real currency of this strategy.<\/p>\n\n

Nothing resets the counter. Nothing.<\/h2>\n\n

“Over the course of the game” is doing enormous work in 903.10a. The count is a permanent property of a pairing \u2014 this commander, that player \u2014 and there is no card, effect, or sequence of events in Magic that sets it back to zero. Players get this wrong constantly, usually in a way that gets them killed.<\/p>\n\n\n\n
Myth<\/th>Reality<\/th><\/tr><\/thead>\n
“I gained 40 life, so I’m fine.”<\/td>Life total is a completely separate loss condition. A player at 200 life who has taken 21 from one commander is dead.<\/td><\/tr>\n
“I killed their commander, so the count resets.”<\/td>It does not. The commander returning to the command zone under 903.9a changes nothing about damage already dealt.<\/td><\/tr>\n
“They recast it, so it’s a new object \u2014 new count.”<\/td>Rule 903.3: the commander designation “is an attribute of the card itself. The card retains this designation even when it changes zones.” Same card, same count.<\/td><\/tr>\n
“They exiled it permanently, so those points are gone.”<\/td>The points were dealt. Exile is not a rewind.<\/td><\/tr>\n
“It stopped being a creature, so the count went away.”<\/td>No. Damage already dealt stays dealt.<\/td><\/tr>\n
“I have 20 damage from two different commanders, so I’m at 20.”<\/td>You are at 10 and 10, and neither is close. Damage never pools across commanders.<\/td><\/tr>\n
“It’s 21 total, so 21 is lethal.”<\/td>21 is lethal. 20 is not. A 20\/20 commander connecting once has done twenty \u2014 see the Spacecraft section for the most literal example of this in the game.<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n

The practical consequence: partial commander damage is an unremovable liability<\/strong>. If you have taken 14 from one commander, that number will still be 14 in an hour, and every removal spell you hold for that commander is worth more than it looks. This is exactly the situation where a cheap exile effect earns its slot over a cheap destroy effect \u2014 not because exile removes the damage, but because it removes the recursion.<\/p>\n\n

Partners, Backgrounds and the Doctor’s companion: two counters, not one<\/h2>\n\n

If a player has two commanders, this is the rule that decides the game, and it is quoted almost nowhere. Rule 702.124d<\/strong> is unambiguous:<\/p>\n\n

“When determining whether a player has been dealt 21 or more combat damage by the same commander, consider damage from each of your two commanders separately (see rule 903.10a).”<\/p><\/blockquote>\n\n

Rule 702.124a lists the abilities that let you do this: partner<\/em>, partner\u2014[text]<\/em>, partner with [name]<\/em>, choose a Background<\/em>, and Doctor’s companion<\/em>. So a partner pair that has hit you for 12 and 11 has dealt you 23 total combat damage and has killed nobody. You are on two separate clocks, both of them unreset, and neither has fired.<\/p>\n\n

This cuts both ways for the attacker. Two commanders means two ways to be blocked, two removal targets, and two counters that each have to reach 21 independently \u2014 which is why partner pairs are usually built as value engines rather than as commander-damage kills, and why a single-commander build like a dedicated voltron deck<\/a> closes faster on this axis despite having half the cards in the command zone.<\/p>\n\n

The trap that ends more games than any other: copies are not your commander<\/h2>\n\n

This is the single most expensive misunderstanding in the format, and the rule that settles it is one sentence in 903.3<\/strong>:<\/p>\n\n

“This designation is not a characteristic of the object represented by the card; rather, it is an attribute of the card itself<\/em>.”<\/p><\/blockquote>\n\n

A token is not a card. It has no card underneath it. It therefore cannot carry the commander designation, no matter how perfect a copy it is \u2014 and a token copy of your commander deals zero commander damage<\/strong>. Three very popular cards run straight into this.<\/p>\n\n\n\n
Card<\/th>What it does<\/th>Commander damage?<\/th>Price<\/th><\/tr><\/thead>\n
Blade of Selves<\/strong><\/td>Grants myriad: “for each opponent other than defending player, you may create a token copy that’s tapped and attacking that player.” Exiled at end of combat.<\/td>None from the tokens.<\/strong> Only the original commander’s damage counts. The tokens hit life totals only.<\/td>$2.95<\/td><\/tr>\n
Helm of the Host<\/strong><\/td>“At the beginning of combat on your turn, create a token that’s a copy of equipped creature, except the token isn’t legendary.”<\/td>None from the tokens.<\/strong> The copies are enormous value, but they make no progress on any 21 clock.<\/td>$4.64<\/td><\/tr>\n
Kiki-Jiki, Mirror Breaker<\/strong><\/td>Creates a token copy of another target nonlegendary creature you control.<\/td>None<\/strong>, and it cannot legally copy a legendary commander anyway.<\/td>$16.10<\/td><\/tr>\n
Sakashima the Impostor<\/strong><\/td>Enters as a copy of any creature, “except its name is Sakashima the Impostor, it’s legendary in addition to its other types.”<\/td>Yes<\/strong> \u2014 if Sakashima is your commander<\/em>. It is the physical card, so all of its combat damage counts, whatever it is currently copying.<\/td>$18.50<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n

Sakashima is the exception that proves the rule and the reason the rule is worth learning properly. It is not a copy of<\/em> your commander; it is<\/em> your commander, wearing something else’s face. Meanwhile Blade of Selves \u2014 a card that appears in a great many “voltron” primers \u2014 turns your commander into a value engine and quietly stalls the kill you were building toward. Note the further wrinkle: myriad tokens are legendary copies, so on a legendary creature they also collide with the legend rule<\/a> the instant they arrive.<\/p>\n\n

Your commander can now be a Vehicle or a Spacecraft \u2014 and it changes the math<\/h2>\n\n

Almost every article on this subject was written when 903.3 read differently. As of the current rules, the card you designate as your commander must be:<\/p>\n\n

“either (a) a creature card, (b) a Vehicle card, or (c) a Spacecraft card with one or more power\/toughness boxes.” \u2014 903.3<\/strong><\/p><\/blockquote>\n\n

A live Scryfall query confirms the scale of this: 40 Vehicles and 5 Spacecraft can legally be designated as a commander<\/strong> right now. Both deal combat damage to players when they are creatures, so both accumulate commander damage normally.<\/p>\n\n

There is also a genuine internal wrinkle worth flagging, because it will confuse anyone who reads the rules top to bottom: 903.1 still describes Commander as a format where “each deck is led by a legendary creature.”<\/strong> That summary sentence is narrower than the actual requirement two rules later. 903.3 is the operative text.<\/p>\n\n\n\n
Commander<\/th>Type and stats<\/th>Swings to 21<\/th>Price<\/th><\/tr><\/thead>\n
Dawnsire, Sunstar Dreadnought<\/strong><\/td>Legendary Artifact \u2014 Spacecraft, {5}, 20\/20<\/strong>, becomes an artifact creature at 20+ charge counters<\/td>2<\/strong> \u2014 and this is the point: one connection deals 20, which is one damage short<\/em> of lethal.<\/td>$8.35<\/td><\/tr>\n
Shorikai, Genesis Engine<\/strong><\/td>Legendary Artifact \u2014 Vehicle, {2}{W}{U}, 8\/8, crew 8<\/td>3<\/strong> (24 damage). Its Pilot tokens crew as though their power were 2 greater, which is how it crews itself.<\/td>$2.57<\/td><\/tr>\n
Slicer, Hired Muscle<\/strong><\/td>Legendary Artifact Creature \u2014 Robot, {4}{R}, 3\/4 double strike haste; converts to a 3\/2 Legendary Artifact \u2014 Vehicle with living metal and first strike<\/td>4<\/strong> as the Robot (6 per attack)<\/td>$8.95<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n
\n\"Dawnsire,\n
Dawnsire, Sunstar Dreadnought \u2014 art by Jaime Jones. A 20\/20 commander whose single connection lands exactly one damage short of the 21 threshold. Card images and data courtesy of Scryfall; Magic: The Gathering is \u00a9 Wizards of the Coast.<\/figcaption>\n<\/figure>\n\n

Dawnsire deserves the emphasis. A 20\/20 commander that connects with an untouched opponent has dealt twenty<\/em> commander damage, and 903.10a requires twenty-one. Every single-point pump effect in your deck is, in that specific board state, a lethal spell. It is the cleanest demonstration in the game that the threshold is 21 and not 20.<\/p>\n\n

Infect and toxic: two clocks running at once, and one of them is faster<\/h2>\n\n

The most common rules question about commander damage that page one of Google does not answer: does infect damage count? Yes.<\/strong> The derivation is short and comes straight from the rules on how damage is processed.<\/p>\n\n

Rule 120.4b<\/strong> deals the damage. Rule 120.4c<\/strong> then processes “damage that’s been dealt” into its results. Rule 120.3b<\/strong> defines that result: “Damage dealt to a player by a source with infect causes that source’s controller to give the player that many poison counters.” Infect changes the result<\/em> of the damage. The damage was still dealt, by your commander, in combat, to a player \u2014 which is the entire test in 903.10a.<\/p>\n\n

So a commander with infect is running two independent loss conditions against the same opponent simultaneously: the 21-damage clock, and the ten-poison-counter clock in 104.3d. The poison clock is less than half as long.<\/p>\n\n\n\n
Card<\/th>What it grants<\/th>Swings to 21 commander damage<\/th>Swings to 10 poison<\/th>Price<\/th><\/tr><\/thead>\n
Skithiryx, the Blight Dragon<\/strong><\/td>4\/4 flying, infect, {B}: haste, {B}{B}: regenerate<\/td>6<\/td>3<\/strong><\/td>$12.87<\/td><\/tr>\n
Grafted Exoskeleton<\/strong><\/td>+2\/+2 and infect; sacrifice the creature if it becomes unattached<\/td>Depends on power<\/td>Halves almost any clock<\/td>$5.40<\/td><\/tr>\n
Phyresis<\/strong><\/td>Aura: enchanted creature has infect<\/td>Depends on power<\/td>Same<\/td>$3.98<\/td><\/tr>\n
Vishgraz, the Doomhive<\/strong><\/td>3\/3 menace, toxic 1; grows +1\/+1 for each poison counter your opponents have<\/td>7 and shrinking as it grows<\/td>10 from the commander alone<\/td>$1.59<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n

Note the distinction in that last row. Toxic is not infect.<\/strong> Rule 120.3g: combat damage from a creature with toxic deals its damage normally and<\/em> gives poison counters “in addition to the damage’s other results.” A toxic commander therefore drains life, builds commander damage, and stacks poison from the same connection \u2014 three clocks, not two. An infect commander trades the life-total clock away for the poison one.<\/p>\n\n

One warning on Grafted Exoskeleton: “Whenever this Equipment becomes unattached from a permanent, sacrifice that permanent.” Any effect that moves it \u2014 including a well-meaning one of your own \u2014 kills your commander. It goes back to the command zone under 903.9a, but the damage clock does not care and neither does your board.<\/p>\n\n

Damage doublers count. Life-loss doublers do not.<\/h2>\n\n

This is the most valuable single distinction in this article and it is almost never stated. Both categories of card kill an opponent faster. Only one of them moves the commander damage counter.<\/p>\n\n

A damage<\/em> replacement effect changes how much damage is dealt, so 903.10a sees the larger number. A life-loss<\/em> replacement effect leaves the damage alone and doubles the life the player loses afterwards \u2014 so the opponent’s life total falls twice as fast while the commander damage counter creeps up at its original rate. Compare the two oracle texts directly:<\/p>\n\n\n\n
Card<\/th>Oracle text<\/th>Increases commander damage?<\/th>Price<\/th><\/tr><\/thead>\n
Fiery Emancipation<\/strong><\/td>“If a source you control would deal damage to a permanent or player, it deals triple that damage<\/em> instead.”<\/td>Yes<\/strong> \u2014 a 7-power commander deals exactly 21 in one connection<\/td>$13.76<\/td><\/tr>\n
Gratuitous Violence<\/strong><\/td>“If a creature you control would deal damage to a permanent or player, it deals double that damage<\/em> instead.”<\/td>Yes<\/strong> \u2014 an 11-power commander one-shots<\/td>$0.37<\/td><\/tr>\n
Dictate of the Twin Gods<\/strong><\/td>Doubles damage from any<\/em> source, including your opponents’<\/td>Yes<\/strong>, symmetrically \u2014 it also halves your own clock to live<\/td>$2.48<\/td><\/tr>\n
Angrath’s Marauders<\/strong><\/td>Doubles damage from sources you control<\/td>Yes<\/strong><\/td>$0.41<\/td><\/tr>\n
Bloodletter of Aclazotz<\/strong><\/td>“If an opponent would lose life<\/em> during your turn, they lose twice that much life instead.”<\/td>No.<\/strong> The damage dealt is unchanged; only the life loss doubles<\/td>$37.35<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n

Bloodletter of Aclazotz is a $37 card that appears in a great many aggressive black lists, and against an opponent you are trying to kill with commander damage specifically, it does nothing for that plan. It is an excellent card doing a different job. Fireshrieker, at 22 cents, does more for the 21 clock than Bloodletter does \u2014 because double strike deals combat damage twice<\/em>, and both instances are combat damage from your commander.<\/p>\n\n

The arithmetic: how many connections you actually need<\/h2>\n\n

Twenty-one is an awkward number by design. It is one more than a starting life total in most other formats and one more than the largest common power value, and it repeatedly lands a swing short of where players expect.<\/p>\n\n\n\n
Power of your commander<\/th>Connections needed<\/th>With double strike<\/th>With a damage doubler<\/th><\/tr><\/thead>\n
3<\/td>7<\/td>4<\/td>4<\/td><\/tr>\n
4<\/td>6<\/td>3<\/td>3<\/td><\/tr>\n
5<\/td>5<\/td>3<\/td>3<\/td><\/tr>\n
7<\/td>3<\/strong> (exactly 21)<\/td>2<\/td>2<\/strong>, or 1 with a tripler<\/td><\/tr>\n
8<\/td>3<\/td>2<\/td>2<\/td><\/tr>\n
10<\/td>3<\/strong> \u2014 10 and 10 is twenty, one short<\/td>2<\/td>2<\/td><\/tr>\n
11<\/td>2<\/td>1<\/strong><\/td>1<\/strong><\/td><\/tr>\n
20<\/td>2<\/strong> \u2014 one connection is one damage short<\/td>1<\/td>1<\/td><\/tr>\n
21+<\/td>1<\/td>1<\/td>1<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n

Two rows repay study. At power 10<\/strong>, two connections deal twenty and you need a third whole combat to finish a job that looks done \u2014 which is why “+1\/+1” effects are disproportionately valuable in these decks and why power 11 is the real breakpoint for a two-swing kill. And double strike is mathematically identical to a damage doubler<\/strong> on this clock while costing far less, because both instances of combat damage are dealt by the commander.<\/p>\n\n

The cards that get you there<\/h2>\n\n
\n\"A\n<\/figure>\n\n

Commander damage is not a power problem. It is a connection<\/em> problem: your commander has to survive removal, get past blockers, and land damage on a player rather than a creature, repeatedly. These are the pieces that solve those three problems, all Commander-legal and all verified today.<\/p>\n\n\n\n
Equipment or land<\/th>What it solves<\/th>Effect<\/th>Price<\/th><\/tr><\/thead>\n
Rogue’s Passage<\/strong><\/td>Blockers<\/td>“{4}, {T}: Target creature can’t be blocked this turn.” A land slot that guarantees a connection.<\/td>$0.39<\/td><\/tr>\n
Whispersilk Cloak<\/strong><\/td>Blockers and removal<\/td>Equipped creature has shroud and can’t be blocked. The single most efficient answer to both problems on one card.<\/td>$1.51<\/td><\/tr>\n
Trailblazer’s Boots<\/strong><\/td>Blockers<\/td>Can’t be blocked by creatures with nonbasic lands \u2014 in a format built on nonbasic lands, that is close to unblockable<\/td>$3.32<\/td><\/tr>\n
Lightning Greaves<\/strong><\/td>Removal and speed<\/td>Shroud and haste, equip {0}. Lets a freshly recast commander attack the turn it lands<\/td>$4.55<\/td><\/tr>\n
Swiftfoot Boots<\/strong><\/td>Removal and speed<\/td>Hexproof and haste \u2014 worse protection than Greaves, but you can still target your own commander to equip auras<\/td>$1.95<\/td><\/tr>\n
Fireshrieker<\/strong><\/td>Speed<\/td>Double strike. Halves your clock for three mana and 22 cents<\/td>$0.22<\/td><\/tr>\n
Embercleave<\/strong><\/td>Speed and blockers<\/td>+1\/+1, double strike and trample, with flash and a cost reduction per attacker<\/td>$9.01<\/td><\/tr>\n
Colossus Hammer<\/strong><\/td>Power<\/td>+10\/+10 for one mana. Equip {8} is the real cost \u2014 pair it with an effect that attaches for free<\/td>$1.92<\/td><\/tr>\n
Blackblade Reforged<\/strong><\/td>Power<\/td>+1\/+1 for each land you control; equip {3} on a legendary creature<\/td>$2.07<\/td><\/tr>\n
Shadowspear<\/strong><\/td>Blockers and defence<\/td>Trample and lifelink, plus the activated ability that strips hexproof and indestructible from all opposing creatures<\/td>$31.50<\/td><\/tr>\n
Darksteel Plate<\/strong><\/td>Removal<\/td>Indestructible. The counter does not reset when your commander dies, but a dead commander deals no more damage<\/td>$6.97<\/td><\/tr>\n
Sword of Feast and Famine<\/strong><\/td>Removal and blockers<\/td>Protection from black and green, untaps your lands on connection<\/td>$40.11<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n

Trample deserves a specific note here because it is routinely overrated for this plan. Trample damage assigned to a player is<\/em> combat damage from your commander and does count \u2014 but you only get the excess, so a 12\/12 trampler into a 5\/5 blocker moves your counter by seven, not twelve. Deep-dive on how trample, double strike and the rest interact in the combat damage keywords guide<\/a>, and see the full equipment rankings<\/a> for the pieces that pull double duty in other archetypes.<\/p>\n\n

Commanders that realistically close on 21<\/h2>\n\n

A commander that gets there needs some combination of high power, built-in evasion, a damage multiplier stapled to its own text, or protection from removal. These are verified Commander-legal, with current prices, and none of them are Game Changers under the bracket system \u2014 which means every one of them is legal in a Bracket 2 deck.<\/p>\n\n\n\n
Commander<\/th>Cost and stats<\/th>Why it closes<\/th>Price<\/th><\/tr><\/thead>\n
Rafiq of the Many<\/strong><\/td>{1}{G}{W}{U}, 3\/3<\/td>Attacking alone grants exalted +1\/+1 and<\/em> double strike \u2014 a 4\/4 dealing 8 per swing, three connections for the kill, off a 30-cent card<\/td>$0.30<\/td><\/tr>\n
Zurgo Helmsmasher<\/strong><\/td>{2}{R}{W}{B}, 7\/2<\/td>Power exactly 7, so three clean connections is exactly 21. Indestructible during your turn, and grows with +1\/+1 counters when creatures it damaged die<\/td>$0.56<\/td><\/tr>\n
Uril, the Miststalker<\/strong><\/td>{2}{R}{G}{W}, 5\/5<\/td>Hexproof, so it dodges targeted removal entirely, and gets +2\/+2 for each Aura \u2014 three Auras makes it an 11\/11 two-swing kill<\/td>$1.11<\/td><\/tr>\n
Skithiryx, the Blight Dragon<\/strong><\/td>{3}{B}{B}, 4\/4<\/td>Flying, infect, self-haste and regeneration. Three connections for a poison kill, and the regeneration makes it very hard to answer with damage<\/td>$12.87<\/td><\/tr>\n
Wilson, Refined Grizzly<\/strong><\/td>{1}{G}, 2\/2<\/td>Vigilance, reach, trample, ward {2}, uncounterable, and takes a Background as a second commander. A two-mana body that resists removal for 23 cents<\/td>$0.23<\/td><\/tr>\n
Rograkh, Son of Rohgahh<\/strong><\/td>{0}, 0\/1<\/td>Free. First strike, menace and trample on a body that costs nothing to recast, however many times it dies<\/td>$2.27<\/td><\/tr>\n
Syr Gwyn, Hero of Ashvale<\/strong><\/td>{3}{R}{W}{B}, 5\/5<\/td>Equipment costs nothing to attach to Knights and they draw on connection \u2014 the archetypal equipment commander<\/td>$2.97<\/td><\/tr>\n
Halvar, God of Battle<\/strong><\/td>{2}{W}{W}, 4\/4<\/td>Gives equipped and enchanted creatures double strike, and moves auras and equipment each combat. Its back face is an Equipment, which deals no combat damage at all<\/td>$24.93<\/td><\/tr>\n
Godo, Bandit Warlord<\/strong><\/td>{5}{R}, 3\/3<\/td>Tutors an Equipment on arrival and grants an additional combat phase<\/em> the first time it attacks each turn \u2014 two connections per turn cycle<\/td>$1.24<\/td><\/tr>\n
Skullbriar, the Walking Grave<\/strong><\/td>{B}{G}, 1\/1<\/td>Counters stay on it when it changes zones, including to the command zone. Removal costs the opponent nothing but tempo<\/td>$2.15<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n

Zurgo is the honest budget pick on this list. A 7\/2 for four mana that must attack every turn, is indestructible on your own turn, and needs precisely three connections \u2014 with a 56-cent price tag. The fragility is real: 2 toughness dies to almost anything on an opponent’s turn, which is exactly what Darksteel Plate and Whispersilk Cloak are for.<\/p>\n\n

Defending against it<\/h2>\n\n

Because the counter never resets, the defensive game is entirely about preventing connections \u2014 and about answering the commander before the count gets uncomfortable rather than after.<\/p>\n\n\n\n
Card<\/th>Cost<\/th>What it does about a voltron commander<\/th>Price<\/th><\/tr><\/thead>\n
Swords to Plowshares<\/strong><\/td>{W}<\/td>Exiles it. One mana, no regeneration, no death triggers, no recursion from the graveyard. The best answer in the format<\/td>$1.41<\/td><\/tr>\n
Path to Exile<\/strong><\/td>{W}<\/td>Same effect for a basic land. Note that the land helps a ramp deck more than the life gain helps you<\/td>$1.24<\/td><\/tr>\n
Beast Within<\/strong><\/td>{2}{G}<\/td>Destroys any permanent at instant speed. The 3\/3 token it leaves is a real cost against a deck that wanted a blocker<\/td>$0.51<\/td><\/tr>\n
Generous Gift<\/strong><\/td>{2}{W}<\/td>The white equivalent, and it answers hexproof commanders that Swords cannot target<\/td>$0.74<\/td><\/tr>\n
Teferi’s Protection<\/strong><\/td>{2}{W}<\/td>Phases out everything you control and makes you gain no damage this turn. A single card that blanks an entire lethal alpha strike<\/td>$49.57<\/td><\/tr>\n
Blustersquall<\/strong><\/td>{U}<\/td>Taps target creatures before attackers are declared. Forty-six cents to skip a turn of the clock<\/td>$0.46<\/td><\/tr>\n
Fog<\/strong><\/td>{G}<\/td>Prevents all combat damage this turn \u2014 the cleanest possible answer, since it prevents the damage from ever being dealt<\/td>$2.88<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n

Note why Fog is categorically different from life gain. Rule 120.4b deals damage “as modified by replacement and prevention effects.” Prevented damage is never dealt, so it never enters the commander damage count in the first place. Life gain happens strictly after the damage was dealt and counted. The two are not remotely equivalent, and against a commander-damage deck only one of them is doing anything.<\/p>\n\n

Teferi’s Protection is the only Game Changer on this list, which matters if you are building to a specific bracket \u2014 the same framework covered in detail in the Commander brackets and Game Changers guide<\/a>.<\/p>\n\n

You can lose the game to your own commander<\/h2>\n\n

Read 903.10a once more with this in mind: “A player who’s been dealt 21 or more combat damage by the same commander.”<\/em> There is no clause about whose commander it is, and no clause about who controls it.<\/p>\n\n

If an opponent takes control of your commander \u2014 Mind Control<\/strong> ($0.25), Agent of Treachery<\/strong> ($4.63), or any of the format’s many theft effects \u2014 and swings it back at you, that damage is dealt by “the same commander” and accumulates against you exactly as it would against anyone else. Combine that with the fact that the count never resets, and a commander you have already used to hit an opponent for 14 becomes a two-turn clock on you<\/em> the moment it changes hands.<\/p>\n\n

This is a real and underrated argument for keeping a way to sacrifice or bounce your own commander in decks built around a very large one. It is also the reason a stolen commander is worth answering immediately rather than racing.<\/p>\n\n

A starting package<\/h2>\n\n

The following is a functional commander-damage core rather than a complete list \u2014 the protection, evasion and multiplier pieces that any build of this archetype wants, priced today. Slot it around whichever commander you have chosen from the table above, then fill out lands and ramp to taste.<\/p>\n\n

Commander Damage Core Package<\/h4>

16 cards \u2014 one click loads the full list into a TCGplayer cart so you can check real prices and grab the whole deck at once.<\/p>Buy this deck on TCGplayer<\/a>Affiliate link \u2014 buying through it supports KrakenTheMeta at no extra cost to you.<\/span><\/div>\n\n

Every card in that package is Commander-legal as of today and none of them are Game Changers, so the package itself does not push a deck out of Bracket 2. If you would rather start from a finished list, there are thousands of public builds on the community deck browser<\/a>, and you can check any of these prices yourself with the card price tool<\/a>.<\/p>\n\n

The mistakes that decide games<\/h2>\n\n\n\n
Mistake<\/th>What it costs<\/th><\/tr><\/thead>\n
Tracking one combined commander damage total in a game with partner commanders<\/td>You will think you are at 19 and dead when you are at 10 and 9 and safe \u2014 or the reverse<\/td><\/tr>\n
Counting damage your commander dealt to blockers<\/td>Only damage dealt to a player<\/em> counts. This is the most common overcount<\/td><\/tr>\n
Assuming a token copy of your commander is closing the game<\/td>Blade of Selves and Helm of the Host generate enormous board damage and zero commander damage<\/td><\/tr>\n
Playing a life-loss doubler in a deck built to kill with commander damage<\/td>It never moves the counter. Fireshrieker at 22 cents does more for that plan than Bloodletter at $37<\/td><\/tr>\n
Gaining life against a voltron deck<\/td>Life is the wrong resource. Prevention, exile and blockers are the right ones<\/td><\/tr>\n
Stopping at 20<\/td>The rule says 21. A 20\/20 connecting once has not killed anybody<\/td><\/tr>\n
Racing a stolen commander instead of answering it<\/td>Your own commander’s damage counts against you and does not reset when you get it back<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n

Frequently asked questions<\/h2>\n\n

How much commander damage kills a player?<\/h3>\n

Twenty-one or more combat damage from the same commander over the whole game, per rule 903.10a. Twenty does not do it.<\/p>\n\n

Does commander damage from two commanders add together?<\/h3>\n

No. Rule 702.124d requires you to “consider damage from each of your two commanders separately.” Twelve from one and eleven from the other is 23 total damage and zero progress toward the rule.<\/p>\n\n

Does noncombat damage from my commander count?<\/h3>\n

No. Activated abilities, triggered abilities, fight damage and spell damage never count, even when your commander is unambiguously the source. The rule says combat<\/em> damage.<\/p>\n\n

Does gaining life reset commander damage?<\/h3>\n

No. The two loss conditions are completely independent. A player at 200 life who has taken 21 from one commander loses.<\/p>\n\n

Does killing the commander reset the count?<\/h3>\n

No, and neither does exiling it, recasting it, or its returning to the command zone. Rule 903.3 states that the commander designation is an attribute of the card, which it retains across every zone change.<\/p>\n\n

Do token copies of my commander deal commander damage?<\/h3>\n

No. A token is not a card, so it cannot be a commander. This applies to Blade of Selves myriad tokens, Helm of the Host copies, and every other token copy effect.<\/p>\n\n

Does infect damage from my commander count toward 21?<\/h3>\n

Yes. The combat damage is still dealt (rule 120.4b); infect only changes the result into poison counters (120.3b). You are running the 21-damage clock and the ten-poison clock at once.<\/p>\n\n

Do damage doublers increase commander damage?<\/h3>\n

Yes, if they replace the damage<\/em> \u2014 Fiery Emancipation, Gratuitous Violence, Dictate of the Twin Gods. No, if they replace the life loss<\/em>, like Bloodletter of Aclazotz.<\/p>\n\n

Does commander damage apply in a two-player Commander game?<\/h3>\n

Yes. Rule 903.2 explicitly allows a Commander game to be a two-player game, and nothing in 903.10a is restricted to multiplayer.<\/p>\n\n

Can I lose the game to my own commander?<\/h3>\n

Yes. Rule 903.10a says “the same commander,” not “an opponent’s commander.” If somebody steals yours and attacks you with it, that damage counts against you.<\/p>\n\n

The short version<\/h2>\n\n

Twenty-one, combat only, to a player only, per commander, never reset. Tokens do not count, infect does, damage doublers do, life-loss doublers do not, and your own commander can kill you if somebody borrows it. Everything else is arithmetic \u2014 and the arithmetic is unforgiving in a way that is easy to miss, because 21 keeps landing exactly one point past where a clean number would put you.<\/p>\n\n

If you want to see how a commander-damage plan looks in a finished ninety-nine, the fastest route is to describe the commander you want to build around and let the deck builder do the first draft \u2014 then test your commander recognition against the format in Guess That Commander<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"21 combat damage from one commander kills. But token copies do not count, infect does, and nothing ever resets it. Every edge case, cited from the 2026 rules.","protected":false},"author":0,"featured_media":1476,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-1479","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mtg-guides"],"yoast_head":"\nMTG Commander Damage Explained: The 21 Rule & Every Edge Case<\/title>\n<meta name=\"description\" content=\"21 combat damage from one commander kills. But token copies do not count, infect does, and nothing ever resets it. Every edge case, cited from the 2026 rules.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MTG Commander Damage Explained: The 21 Rule & Every Edge Case\" \/>\n<meta property=\"og:description\" content=\"21 combat damage from one commander kills. But token copies do not count, infect does, and nothing ever resets it. Every edge case, cited from the 2026 rules.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/\" \/>\n<meta property=\"og:site_name\" content=\"KrakenTheMeta\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-07T06:50:16+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-08T07:01:17+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2026\/08\/kraken-img-1786085096-mtg-commander-damage-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1376\" \/>\n\t<meta property=\"og:image:height\" content=\"768\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2026\/08\/kraken-img-1786085096-mtg-commander-damage-1.jpg\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"23 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/\"},\"author\":{\"name\":\"\",\"@id\":\"\"},\"headline\":\"MTG Commander Damage Explained: The 21 Rule, Every Edge Case, and the Commanders That Get There (2026)\",\"datePublished\":\"2026-08-07T06:50:16+00:00\",\"dateModified\":\"2026-08-08T07:01:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/\"},\"wordCount\":4745,\"publisher\":{\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/kraken-img-1786085096-mtg-commander-damage-1.jpg\",\"articleSection\":[\"MTG Guides\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/\",\"url\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/\",\"name\":\"MTG Commander Damage Explained: The 21 Rule & Every Edge Case\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/kraken-img-1786085096-mtg-commander-damage-1.jpg\",\"datePublished\":\"2026-08-07T06:50:16+00:00\",\"dateModified\":\"2026-08-08T07:01:17+00:00\",\"description\":\"21 combat damage from one commander kills. But token copies do not count, infect does, and nothing ever resets it. Every edge case, cited from the 2026 rules.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/#primaryimage\",\"url\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/kraken-img-1786085096-mtg-commander-damage-1.jpg\",\"contentUrl\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/kraken-img-1786085096-mtg-commander-damage-1.jpg\",\"width\":1376,\"height\":768},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/mtg-commander-damage\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"MTG Commander Damage Explained: The 21 Rule, Every Edge Case, and the Commanders That Get There (2026)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/\",\"name\":\"Kraken The Meta\",\"description\":\"MTG Strategy & Deck Guides\",\"publisher\":{\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/#organization\",\"name\":\"Kraken The Meta\",\"url\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/wp-content\\\/uploads\\\/2024\\\/05\\\/krakenlogo.png\",\"contentUrl\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/wp-content\\\/uploads\\\/2024\\\/05\\\/krakenlogo.png\",\"width\":865,\"height\":816,\"caption\":\"Kraken The Meta\"},\"image\":{\"@id\":\"https:\\\/\\\/krakenthemeta.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"MTG Commander Damage Explained: The 21 Rule & Every Edge Case","description":"21 combat damage from one commander kills. But token copies do not count, infect does, and nothing ever resets it. Every edge case, cited from the 2026 rules.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/","og_locale":"en_US","og_type":"article","og_title":"MTG Commander Damage Explained: The 21 Rule & Every Edge Case","og_description":"21 combat damage from one commander kills. But token copies do not count, infect does, and nothing ever resets it. Every edge case, cited from the 2026 rules.","og_url":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/","og_site_name":"KrakenTheMeta","article_published_time":"2026-08-07T06:50:16+00:00","article_modified_time":"2026-08-08T07:01:17+00:00","og_image":[{"width":1376,"height":768,"url":"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2026\/08\/kraken-img-1786085096-mtg-commander-damage-1.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_image":"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2026\/08\/kraken-img-1786085096-mtg-commander-damage-1.jpg","twitter_misc":{"Est. reading time":"23 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/#article","isPartOf":{"@id":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/"},"author":{"name":"","@id":""},"headline":"MTG Commander Damage Explained: The 21 Rule, Every Edge Case, and the Commanders That Get There (2026)","datePublished":"2026-08-07T06:50:16+00:00","dateModified":"2026-08-08T07:01:17+00:00","mainEntityOfPage":{"@id":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/"},"wordCount":4745,"publisher":{"@id":"https:\/\/krakenthemeta.com\/blog\/#organization"},"image":{"@id":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/#primaryimage"},"thumbnailUrl":"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2026\/08\/kraken-img-1786085096-mtg-commander-damage-1.jpg","articleSection":["MTG Guides"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/","url":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/","name":"MTG Commander Damage Explained: The 21 Rule & Every Edge Case","isPartOf":{"@id":"https:\/\/krakenthemeta.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/#primaryimage"},"image":{"@id":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/#primaryimage"},"thumbnailUrl":"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2026\/08\/kraken-img-1786085096-mtg-commander-damage-1.jpg","datePublished":"2026-08-07T06:50:16+00:00","dateModified":"2026-08-08T07:01:17+00:00","description":"21 combat damage from one commander kills. But token copies do not count, infect does, and nothing ever resets it. Every edge case, cited from the 2026 rules.","breadcrumb":{"@id":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/#primaryimage","url":"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2026\/08\/kraken-img-1786085096-mtg-commander-damage-1.jpg","contentUrl":"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2026\/08\/kraken-img-1786085096-mtg-commander-damage-1.jpg","width":1376,"height":768},{"@type":"BreadcrumbList","@id":"https:\/\/krakenthemeta.com\/blog\/mtg-commander-damage\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/krakenthemeta.com\/blog\/"},{"@type":"ListItem","position":2,"name":"MTG Commander Damage Explained: The 21 Rule, Every Edge Case, and the Commanders That Get There (2026)"}]},{"@type":"WebSite","@id":"https:\/\/krakenthemeta.com\/blog\/#website","url":"https:\/\/krakenthemeta.com\/blog\/","name":"Kraken The Meta","description":"MTG Strategy & Deck Guides","publisher":{"@id":"https:\/\/krakenthemeta.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/krakenthemeta.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/krakenthemeta.com\/blog\/#organization","name":"Kraken The Meta","url":"https:\/\/krakenthemeta.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/krakenthemeta.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2024\/05\/krakenlogo.png","contentUrl":"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2024\/05\/krakenlogo.png","width":865,"height":816,"caption":"Kraken The Meta"},"image":{"@id":"https:\/\/krakenthemeta.com\/blog\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/krakenthemeta.com\/blog\/wp-json\/wp\/v2\/posts\/1479","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/krakenthemeta.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/krakenthemeta.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/krakenthemeta.com\/blog\/wp-json\/wp\/v2\/comments?post=1479"}],"version-history":[{"count":1,"href":"https:\/\/krakenthemeta.com\/blog\/wp-json\/wp\/v2\/posts\/1479\/revisions"}],"predecessor-version":[{"id":1496,"href":"https:\/\/krakenthemeta.com\/blog\/wp-json\/wp\/v2\/posts\/1479\/revisions\/1496"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/krakenthemeta.com\/blog\/wp-json\/wp\/v2\/media\/1476"}],"wp:attachment":[{"href":"https:\/\/krakenthemeta.com\/blog\/wp-json\/wp\/v2\/media?parent=1479"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/krakenthemeta.com\/blog\/wp-json\/wp\/v2\/categories?post=1479"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/krakenthemeta.com\/blog\/wp-json\/wp\/v2\/tags?post=1479"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}