TLDR
To investigate an accidental infinite combo MTG deck, scan the list by function rather than card name. Look for interactions among resource producers, sacrifice outlets, untappers, recursion effects, token makers, cost reducers, and triggered payoffs. When something looks suspicious, write out every action, cost, target, zone change, and resource gained. A real loop must return to a repeatable state; a winning combo must also produce a useful net result or reach a separate payoff.
Finding an accidental infinite combo MTG deck interaction does not automatically mean you should remove it. First prove that it works. Then decide whether the loop supports the deck’s intended power level, deserves pregame disclosure, or depends on a bridge card the deck can comfortably replace.
First identify what kind of interaction you found
Powerful cards working together do not necessarily form an infinite combo. Before auditing the rules, classify the interaction. This prevents an ordinary value engine from setting off the combo alarm just because it had a particularly good turn.
| Interaction | What it does | What to check |
|---|---|---|
| Synergy | Two or more cards improve one another without creating a repeatable sequence. | Whether the interaction merely increases efficiency or card quality. |
| Value engine | Repeated investment generates cards, mana, tokens, or another advantage. | Whether each repetition consumes a limited resource. |
| Loop | A sequence can return to a substantially repeatable game state. | Whether it can continue and whether anything changes each cycle. |
| Lock | An interaction prevents or severely restricts normal game actions. | Whether it wins, stalls the game, or can be broken. |
| Deterministic win | A reproducible sequence leads to a defined winning result. | Whether the line has all required resources, legal choices, and a payoff. |
A loop can be real without being profitable. For example, a permanent might leave the battlefield, return, and reset another object, but the sequence accomplishes nothing unless it creates extra mana, tokens, damage, life, cards, counters, or another meaningful result. Conversely, a loop that creates unlimited mana still needs a legal way to spend that mana if mana alone does not end the game.
Magic’s rules handle loops as repeatable sequences rather than requiring anyone to perform literally unlimited actions. A player using a shortcut specifies a finite number of repetitions and describes the resulting game state. The current official Magic rules hub is the appropriate starting point when exact wording or an unusual corner case matters.
Why normal deckbuilding cards accidentally form loops
Accidental combos usually appear because individually reasonable deck roles overlap. A Commander deck might add a sacrifice outlet for resilience, recursion for value, a token maker for board presence, and a triggered payoff for reach. None was included as a dedicated combo piece, but together they may restore every resource consumed by the sequence.
Pay particular attention when a list contains several of these functions:
- Resource production: cards that create mana, tokens, life, cards, counters, or untapped permanents.
- Recursion and reset effects: cards that return objects from a graveyard, exile, hand, or battlefield.
- Sacrifice or conversion outlets: repeatable abilities that turn creatures, artifacts, life, or other resources into value.
- Untapping and blinking: effects that allow another permanent to be used again or re-enter with fresh status.
- Cost reduction: effects that make an action free or cheaper than the resource it produces.
- Replacement and persistence effects: cards that prevent an object from staying gone after it is sacrificed or destroyed.
- Triggered payoffs: effects that care about entering, leaving, dying, casting, drawing, discarding, or creating tokens.
The dangerous card is often not the obvious payoff. It is the bridge that connects two otherwise fair packages. A recursion effect may connect the sacrifice package to the token package, or an untapper may connect mana production to repeated activations. That bridge is also often the cleanest card to replace if you decide the loop does not belong.
Scan the decklist by role, not by card name
Start with a complete, clean list. If your deck is scattered across notes and screenshots, move it into the MTG Deck Builder or use the guide to import a plain-text decklist. A missing card, duplicate entry, or misplaced commander can make a combo audit misleading before it begins.
Tag cards by everything they do, not merely their primary purpose. A creature listed as ramp might also create a death trigger. A removal spell might sacrifice one of your permanents as a cost. A protection card might blink something and therefore reset it. Role compression is good deckbuilding, but it is also how innocent-looking cards acquire suspicious friends.
- Mark every repeatable source of mana, tokens, cards, counters, life, untaps, and damage.
- Mark every free or inexpensive sacrifice, discard, bounce, blink, and activation outlet.
- Mark recursion that returns the type of object consumed by an outlet.
- Mark effects that reduce, refund, copy, or avoid costs.
- Mark cards that trigger whenever one of those actions occurs.
- Draw connections between cards whose outputs pay another card’s costs.
- Investigate any path that appears capable of returning all required objects to their starting zones.
You can use the MTG Combo Database to search likely pieces and generate hypotheses. Combo search is useful for discovering that a harmless-looking support card participates in known lines, but a result should begin your verification rather than end it. The actual deck, available mana, zones, targets, timing, and current card text still determine whether your version works. MTG App’s combo workflow similarly separates synergies, engines, loops, locks, and deterministic wins.
Verify the exact loop one action at a time
Do not settle for “these three cards go infinite.” Build a miniature game-state audit. Write down the objects needed on the battlefield, in the graveyard, in hand, in the command zone, or under an opponent’s control. Include required counters, tokens, lands, targets, life totals, and available mana.
Next, check the current Oracle text for every card. Small phrases such as “another,” “nontoken,” “only as a sorcery,” “once each turn,” and “you control” routinely break alleged combos. Confirm whether an effect is a cost, a target, a triggered ability, or part of a resolution. Those distinctions affect whether the next action is available and where opponents can respond.
Then write one complete cycle as a numbered sequence. For every step, record what is paid and what is produced. After the cycle, compare the state with the starting position.
| Audit category | Starting state | End of one cycle |
|---|---|---|
| Required objects | Which cards, tokens, counters, and targets are available? | Have all necessary objects returned or been replaced? |
| Mana | How much and what colors are available? | Is there a net gain, loss, or no change? |
| Cards and zones | What is in hand, library, graveyard, exile, and play? | Did a finite zone lose a required object? |
| Life and counters | What totals are required to begin? | Does the sequence gain, lose, or eventually exhaust them? |
| Payoff | What result is supposed to matter? | Did the cycle advance toward a win or merely reset itself? |
A valid repeatable loop normally restores access to every component needed for the next cycle. If each cycle consumes a card from the library, needs a new target, loses one life, or exiles a component permanently, the sequence is bounded. It may still be powerful, but it is not unlimited under that game state.
Check choice points and stopping conditions
Determine whether each action is optional. A loop controlled through activated abilities or “may” triggers can usually be stopped by declining the next action. A sequence made entirely from mandatory triggers may behave differently. If mandatory actions keep recreating the same state without a way to advance the game, consult the current Comprehensive Rules rather than improvising a table ruling.
Also mark every response window and vulnerable component. Can an opponent remove the sacrifice outlet, exile the graveyard target, counter a trigger, stop an activated ability, or prevent the payoff? “Can be disrupted” does not mean “is not a combo.” It tells you how resilient the line is and what information opponents need to interact intelligently.
Prove the payoff separately
Do not blur the repeating engine and the winning outlet into one claim. An engine might create arbitrary mana but require another card to convert it into damage, cards, or a game-ending activation. A token loop may need those tokens to survive long enough to attack. A repeated draw effect can become dangerous if the player cannot stop before exhausting the library.
Write the conclusion precisely: “These pieces repeat but produce no net resource,” “the loop creates mana and requires an outlet,” or “each cycle triggers the payoff and can be repeated a chosen number of times.” Precise language makes both rules verification and pregame communication much easier.
Test how the combo changes the deck
Once the interaction is proven, test its practical role. MTG App presents deck construction, analysis, combo research, and goldfishing as connected parts of an iterative workflow. Use opening-hand tests or goldfishing to ask how often the pieces appear naturally, how many tutors locate them, and whether assembling the line competes with the deck’s normal plan.
Do not evaluate the combo in isolation. Cutting a bridge piece might alter the mana curve, interaction count, or redundancy of an important package. Run the revised list through the appropriate analysis again; the comparison between a deck builder and mana curve analyzer explains what each tool can reveal.
- How many distinct cards are required?
- Are any pieces available from the command zone?
- Does each piece perform a useful job outside the combo?
- How much mana and setup does the complete line require?
- How easily can opponents disrupt it?
- Does the deck actively tutor for the pieces or merely encounter them occasionally?
- Does the line create the kind of game the deck is supposed to create?
Keep, disclose, or remove the accidental combo
Keep it when it fits the deck
Embrace the loop if it supports the deck’s intended plan and power. You may decide that the accidental discovery gives a value engine a clean ending or rewards assembling several independently useful pieces. If you keep it intentionally, document the sequence so you can explain it without making the table reconstruct it while everyone waits.
Disclose it when it could surprise the group
An incidental combo may deserve pregame disclosure even if the deck does not aggressively tutor for it. Explain the number of pieces, whether any start in the command zone, whether the deck searches for them, and what the loop produces. “There is a three-card mana loop, but I do not tutor for it” communicates more than simply labeling the deck casual or upgraded.
Remove the least essential bridge
If the combo conflicts with the intended experience, avoid cutting several good cards at random. Identify the bridge, outlet, recursion piece, or payoff with the least independent value. Replace that card with another option that performs its main job without reconnecting the loop. Then scan again: combo surgery occasionally creates a sequel.
Retest ordinary hands after the change. Removing a free sacrifice outlet might eliminate the loop but also weaken your protection against exile or theft. Removing an untapper might damage the deck’s mana development. The best replacement breaks the unwanted sequence while preserving the deck’s legitimate structure.
Check legality separately from functionality
A combo functioning under the rules does not establish that every component is legal in your format. Consult Wizards’ live Banned & Restricted list for current format-specific information. Commander house rules and pregame expectations are separate questions again: legality answers whether a card is permitted, while communication addresses whether the resulting experience fits the group.
Turn suspicion into an intentional deckbuilding choice
The reliable workflow is simple: categorize card functions, locate possible bridges, write the exact sequence, calculate the net change, identify response windows, and prove the payoff. Then test how frequently the line matters in the actual deck.
If the interaction works, choose deliberately. Keep it because it belongs, disclose it because it may surprise the table, or remove the least essential connector and retest. That is much better than discovering the combo halfway through a Commander game and beginning the traditional group activity known as reading every card six times.