TLDR: A player loses after taking 21 or more combat damage from the same individual commander over the course of the game. Track each commander against each receiving player separately. My preferred Commander damage tracking method is a visible grid, but labeled dice or a capable app can work if everyone can identify every total without conducting an archaeological excavation.
Commander damage tracking becomes difficult when one die is parked beside a commander and expected to represent damage dealt to three different opponents. It cannot. That die has been assigned four jobs, no supervision, and access to sensitive information. The clean solution is to record a separate running total for every commander-player pairing and update it immediately after combat.
The commander damage rule, without smoke grenades
The official rule is specific: a player who has been dealt 21 or more combat damage by the same commander over the course of the game loses. Wizards states this on its official Commander format page.
Four parts of that sentence do the heavy lifting:
- It must be combat damage.
- It must total at least 21 damage.
- It must come from the same individual commander.
- The total accumulates over the entire game.
Commander damage is not a separate packet of damage floating above the battlefield. When a commander connects in combat, that combat damage has its normal game consequences and also increases the appropriate commander-damage record. Gaining life later can raise your life total, but it does not erase commander damage already received.
Damage from a commander’s triggered ability, activated ability, or spell does not count just because the commander caused it. If a commander says, in effect, “deal damage to an opponent,” that is noncombat damage and does not advance the 21-point commander total. A giant bird striking during combat counts. A giant bird operating artillery from the command zone does not.
Commander damage tracking needs a matrix, not one heroic die
Every individual commander needs a separate total against every player who might receive its combat damage. Do not combine all commander damage received by one player. Do not combine one commander’s damage to several opponents. Both approaches destroy the information the rule needs.
For a four-player game with one commander per player, use a grid with receiving players as rows and commanders as columns. When Commander A deals 6 combat damage to Player C, find Player C’s row and Commander A’s column, then write 6. If the same commander later hits Player D for 6, that is a different cell. Player C remains at 6 from Commander A; Player D is now at 6 from Commander A.
| Receiving player | Commander A | Commander B | Commander C | Commander D |
|---|---|---|---|---|
| Player A | — | 0 | 0 | 0 |
| Player B | 6 | — | 0 | 0 |
| Player C | 11 | 0 | — | 0 |
| Player D | 0 | 4 | 0 | — |
The diagonal cells are usually unused because players normally control their own commanders. Technically, they are not impossible. If an opponent gains control of your commander and hits you with it, your own commander can deal commander damage to you. The identity of the individual commander matters, not who currently controls it. You may therefore leave the diagonal available if your pod contains theft effects and people who enjoy procedural surprises.
Choose a tracking tool that exposes the whole situation
The best tool is not necessarily the one with the most features. It is the one your table can read quickly and update consistently. Here is the threat assessment.
Paper or dry-erase grid
A shared grid is my default recommendation for a regular four-player table. Put players down one side and commanders across the top. A sheet of paper works. A laminated sheet or small dry-erase board is easier to reuse. Use commander names, player names, initials, or clearly distinguishable colors.
The advantage is visibility: every relevant total is in one place. The disadvantage is that someone must maintain it, and the grid grows when players have multiple commanders. This is manageable. Bureaucracy becomes dangerous only when it begins wearing a tie.
Personal inbound-damage cards
Each player can instead keep a small card listing every opposing commander and the combat damage received from each. This distributes the work and keeps the totals near the affected player’s life counter. It is especially practical when players already manage their own poison, experience, energy, or other counters.
The weakness is public visibility. Keep the cards face up and large enough for opponents to read. A private note hidden beneath a deck box may be accurate, but nobody can verify it during combat. That is not tracking. That is a classified archive.
Dice
Dice are acceptable if each die has one unmistakable assignment. Place a labeled commander token, name slip, or portrait beside each total. A die sitting on a commander card is ambiguous because it might represent power modification, tax, damage dealt to one opponent, or the owner’s growing sense of destiny.
If using dice, each receiving player should maintain one die per commander that has damaged them. Never use one die to represent a commander’s combined damage across the table. Also avoid dice that can be confused with +1/+1 counters or other battlefield markers.
Life-tracking apps
An app can reduce physical clutter, but only if it exposes damage by individual commander and receiving player. A generic life counter or damage history is not automatically sufficient. Wizards describes Magic Companion as having a life counter and other play tools, but the supplied product information does not establish a commander-damage matrix.
As one feature example rather than a universal recommendation, Moxtopper’s App Store listing says it tracks commander damage by commander and can separate Partner commanders. App availability, interfaces, platform support, and pricing can change, so inspect the current listing before deploying one. The tactical test is simple: can every player reach the correct commander-player total in seconds?
Use the four-second combat announcement
Most disputes are not caused by obscure rules. They are caused by someone saying “take seven,” moving a die, passing the turn, and assuming three other people recorded the same event correctly.
Use this routine whenever a commander deals combat damage:
- Name the commander.
- Name the receiving player.
- State the amount of combat damage dealt.
- State the receiving player’s new total from that commander.
- Update the tracker immediately.
For example: “Rafiq deals 10 combat damage to Morgan. Morgan is now at 16 from Rafiq.” This distinguishes the commander-damage total from Morgan’s life total and gives the table a chance to catch an error while the combat step is still fresh.
This is also good general table communication. The same habit that prevents proxy misunderstandings in a new Commander playgroup prevents commander-damage disputes: announce relevant information before it becomes a surprise weapon.
Rules dojo: the edge cases that ambush trackers
The commander changes zones
Commander damage does not reset because the commander dies, returns to the command zone, gets exiled, enters a graveyard, or later returns to the battlefield. Commander status is attached to the designated card, and the running combat-damage record remains relevant across zone changes. Keep the same column on your grid.
Someone steals a commander
Changing control does not create a new commander-damage identity. If Player B steals Player A’s commander and attacks Player C with it, the damage still belongs to that same individual commander’s total against Player C. It does not become damage from Player B’s commander.
A commander copies something else
A card designated as a commander remains a commander even if an effect changes its characteristics, including making it a copy of another card. Its combat damage still counts as damage from that commander. By contrast, a separate creature that merely copies a commander does not become a commander just because it copied one. Track the actual designated commander, not the appearance it has borrowed for the operation.
A player has two commanders
If a player has two commanders through an applicable deckbuilding ability, track each one separately. Their combat damage does not combine toward 21. If one commander has dealt 12 to an opponent and the other has dealt 9, that opponent has not taken 21 from the same commander and does not lose for commander damage. Give each commander its own column, label, or app entry.
The anti-confusion checklist
- Track combat damage only, not damage from spells or abilities.
- Maintain a separate total for each commander against each receiving player.
- Do not erase totals when a commander changes zones or controllers.
- Give each commander a separate record when a player has two commanders.
- Label physical dice so their assignments cannot be mistaken.
- Announce the commander, recipient, damage, and revised commander total after combat.
- Use an app only if its per-commander view is fast and visible to the table.
Final extraction
Commander damage is simple; compressed recordkeeping is the enemy. Use a player-by-commander grid, clearly labeled personal counters, or an app that preserves the same structure. Then announce every update as it happens.
Retire the single mysterious die beside the commander. It has served bravely, but it knows too little and has already compromised the perimeter.