This MTG life counter tracks life, poison, and commander damage for each player with clear elimination status and a running action log. It is designed for real table flow, not just single-value tapping.
An MTG life counter is a game-state tracker that records life totals and additional loss conditions throughout a match. In modern Magic formats, especially commander, a single number is never enough. Players track life, infect pressure, commander damage, and combat math across several turns while multiple triggered abilities resolve in sequence. Manual dice and paper notes can work, but they often fail when the table needs to reconstruct an exact action chain after a dispute. This page solves that problem by centralizing every update into a readable board and a chronological log.
The core value is not just convenience. It is dispute reduction. Most table conflicts happen because one player remembers a sequence differently than another player. When each life or damage change is appended as an event with player context, the table can confirm the last valid state quickly and continue the game. That means less social friction and fewer stalled turns. The tool is therefore useful in friendly pods, competitive commander practice, webcam matches, and content recording sessions where state clarity matters.
Another practical advantage is elimination visibility. In commander, players can lose through more than one path. A life counter that watches life only can miss lethal commander damage or poison threshold events. This tool checks all three conditions for every player and marks elimination automatically so the table does not need to re-evaluate thresholds manually after each combat step. That behavior is simple, but it removes repeated mental overhead over long games.
Finally, this counter keeps setup flexible. You can run two to six players, pick duel or commander baseline, rename each seat, and restart cleanly for the next pod. That setup speed matters for repeated game nights and testing sessions where you need reliable rounds without spending extra time rebuilding table state from scratch.
The state model is straightforward. Each player has three tracked values: life total, poison counters, and commander damage taken. Life starts at either twenty or forty depending on selected format. Poison starts at zero. Commander damage starts at zero. Every button action mutates one value by a fixed amount, then the new snapshot is written into the event log.
After each mutation, elimination is computed using a three-condition rule. Condition one: life less than or equal to zero. Condition two: poison greater than or equal to ten. Condition three: commander damage greater than or equal to twenty-one. If any condition is true, the player status is set to eliminated. Otherwise, the player remains active. This logic mirrors common gameplay interpretation while staying visible enough that every player can verify it instantly.
Undo logic uses a history stack. Before each counter mutation, the tool stores a full table snapshot. If someone taps the wrong button, one undo operation restores the previous snapshot and appends a correction event. That approach is safer than trying to infer reverse operations from the last button click because it handles complex sequences and renamed players without ambiguity.
The start-player helper is intentionally light. It reads current active players and chooses one at random, then posts the result into the log. You can optionally add a seed text in the UI for your own reference, but the picker remains random per call. In short, the calculation cycle is consistent: read state -> apply change -> recompute elimination -> render cards -> append log entry. That repeatable cycle is what keeps multiplayer bookkeeping stable through long commander turns.
You start at 40 life, then one player takes 8 combat damage and 2 poison over two turns. The board shows both values immediately, and the event log confirms action order if the table needs to review combat math.
A player still has positive life but reaches 21 commander damage. The status flips to eliminated even before life reaches zero, so the table does not miss commander-specific lethal conditions.
Someone subtracts five life instead of one. Press Undo Last Action and the prior state returns instantly. The correction is logged, so everyone understands why the board changed.
It tracks life total, poison counters, and commander damage taken for each player, with an event log you can review during disputes.
Yes. You can set player count from two to six and start in commander mode with 40 life by default.
A player is flagged eliminated when life reaches zero, poison reaches ten, or commander damage reaches twenty-one.
Yes. Every action is appended to the event log and you can press undo to roll back the most recent state update.
Yes. It works well for in-person pods, webcam games, and stream overlays where you need a clean shared board.
No. Counter updates run in your browser session and are not uploaded unless you manually copy text out.