Potential Amendments to the Rules Update for Magic: The Gathering | The Hobbit

(Originally published on 2026-11-11; last reviewed on 2026-11-11; last updated on 2026-11-11)

With each new set release, Wizards of the Coast update the Comprehensive Rules (CR) and the Oracle text of any number of cards. These updates include support for new mechanics, error fixes, and improvements to the wording of rules and cards.

In my unofficial update bulletin, I list the changes made by the Magic: The Gathering | The Hobbit update and I point out issues I perceive as inelegant, unintuitive, or even faulty. Which gives the bulletin a rather negative outline, even when I factor in the things I point out as laudable.

This shouldn’t be seen as a slight against Wizards of the Coast or their rules team though; we just have different visions for Magic’s rules system. In my mind, the rules system should strive for intuitiveness, consistency, and completeness; and while the system has never truly met these lofty goals, Wizards of the Coast shared this vision for many years.

For a few years now, Wizards of the Coast’s design goal for the rules system is . . . something different. I don’t know what it is; I only know that it isn’t intuitiveness, consistency, or completeness anymore, as evidenced by their rules updates. While this may seem like a dangerous course of action for the game’s long-term success, I trust that Wizards of the Coast don’t undermine their game in this way and I remain content in the knowledge that I simply lack the intelligence and insight to recognize their grand vision.

Until they reveal their plans in an appropriately dramatic fashion, I continue to cling to my old-fashioned goal of an elegant rules system. But complaining is cheap and gets old very fast, so at some point, I started to wonder what the rules might look like had they been written with the three classic goals in mind.

The results of my musings are the Potential Rules Amendments, a counterpoint to the Unofficial Update Bulletins. What I criticize in my bulletins, I reenvision in the amendments. Where the bulletins ask questions, the amendments give an answer.

Each section briefly recounts issues presented in my bulletin, as well as older and somewhat related issues, and what the outcome for those issues should be; I then discuss what the Comprehensive Rules and Oracle would need to consider to achieve the desired outcomes; finally, I present a sample implementation based on that discussion.

Table of contents

Mana abilities

In my update bulletin, I discuss several issues with the new criterion for activated mana abilities.

First, the new criterion doesn’t prevent the movement of cards to or from a library during the activation and resolution of a mana ability; rather, it prevents abilities where such a movement is an intrinsic part of the ability from classifying as mana abilities. If the movement results from the application of a replacement effect to the activation or resolution of a mana ability, it still happens as before.

This behavior can remain as is. There are no rules issues arising from such scenarios and the Comprehensive Rules even address how to revert affected mana abilities, if necessary; as such, the current behavior enriches the rules system. Furthermore, a universal handling of library manipulation in the context of mana abilities comes with its own issues:

Outright preventing library manipulation during the activation and resolution of mana abilities would produce other unintuitive results, for example when discarding Darksteel Colossus to activate Overeager Apprentice’s mana ability. Delaying the library manipulation until the “larger” action has been completed (e.g. casting a spell or resolving a spell that asks for a mana payment) would require defining an order for cases where multiple manipulations happen (or are supposed to happen).

Finally, if Wizards of the Coast wanted to keep mana abilities entirely free from library manipulation, their rules team would have devised a corresponding rule that also addressed the above issues in an elegant manner. The fact that they didn’t is the best evidence that the current behavior is the intended one.

The other issue with the new criterion is with its wording. Rule 605.1a’s new text isn’t entirely clear on whether the library manipulation should be evaluated in a vacuum or in the context of activating the ability in question. Additionally, the new sentence about replacement effects may cause questions regarding rules and other kinds of effects that interact with the library manipulation.

For this issue, I think the best solution is to refer to the ability’s text. If the ability’s text contains an instruction to move a card to or from a library, it’s not a mana ability. This approach comes with the following benefits:

  • By looking at an ability’s text, that ability can be evaluated as a characteristic of an object. There is no need to consider a potential activation of the ability in the current game state or in a hypothetical alternative game state.
  • Many kinds of effects can add or remove abilities, but the text of an ability is almost immutable. While certain text-changing effects replace subtypes and color words with other subtypes and color words, none of them are so complex as to replace an instruction with another. (The cleave keyword comes close but restricts itself to a single spell’s text.) Thus, the kinds of instructions (i.e. the verbs) in an ability’s text remain the same.
  • While resolving an ability on the stack (or wherever mana abilities resolve), an instruction might not get carried out because a rule or effect states that the instruction can’t happen (e.g. Spirit of the Labyrinth), because the game state makes it impossible (e.g. an empty library), because a replacement effect causes a different instruction to be carried out instead (e.g. Words of Worship), or because it’s part of a self-replacement effect that isn’t applied. In all those cases, the instruction is still present in the ability’s text; it may get skipped or ignored in favor of another instruction, but it’s still there. This means that there’s no relevant difference between the instructions of an ability as a characteristic and that ability as an object that’s activated or resolving.
  • As a direct consequence, the current game state can be ignored entirely. In other words, a card’s Oracle text is sufficient to determine whether any of its abilities are mana abilities.
  • An ability’s text includes everything about that ability: its activation cost, its effect (including any self-replacement effects), and any activation instructions—in other words, all the things the new criterion cares about.
  • Conversely, an ability’s text doesn’t include replacement effects (other than self-replacement effects), other kinds of continuous effects, rules, and anything else external to the ability—in other words, everything the new criterion doesn’t care about.

By looking for a specific kind of instruction in the ability’s text, the entire sentence about replacement effects becomes redundant and the ambiguity about other continuous effects is removed.

This approach can also eliminate the vague conditional form of the “could add mana” criterion: if the text includes an instruction to add mana, the criterion is fulfilled. No need to consider actual or hypothetical game states to determine whether mana “could” be added; the ability’s text in the Oracle card reference is enough.

There would be two differences to the current criterion: first, if an ability’s activation cost included an instruction to add mana, that ability would count as a mana ability. Second, if an ability had an instruction to add mana but there were no possible game states where that instruction would actually produce mana, the ability would count as a mana ability. No such abilities exist and I don’t expect Wizards of the Coast to print either kind, so these differences are entirely theoretical.

Rules section 605 also has a couple of preexisting smaller issues that I will address here.

First up is rule 605.1b, which defines the criteria for triggered mana abilities. Like rule 605.1a, it talks about abilities that “could” add mana; this should be replaced with instructions to add mana.

A criterion unique to this rule is that a triggered ability has to trigger from the activation of an activated mana ability, from the resolution of such an ability, or from mana being added to a player’s mana pool. The third part applies exclusively to Caged Sun’s ability. Meanwhile, the first part doesn’t apply to any existing ability at all.

Before the Magic Origins update, phrases like “tap for mana” or “is tapped for mana” referred exclusively to the activation of a mana ability with {T} in its activation cost; as a result, triggered mana abilities such as that of Wild Growth triggered from the activation of an activated mana ability. If an ability such as that of Gaea’s Cradle didn’t produce any mana while resolving, the triggered ability would still trigger.

The Magic Origins update made this interaction more intuitive by redefining the trigger event to be the resolution of a mana ability that actually produces mana. As a result, if the ability of Gaea’s Cradle didn’t produce any mana, triggered mana abilities no longer triggered. The criterion in rule 605.1b changed from “triggers from activating a mana ability” to “triggers from the resolution of an activated mana ability.”

Later, the Ixalan update added the alternative criterion of “[triggers] from mana being added to a player’s mana pool” to account for scenarios involving Caged Sun.

Finally, the Strixhaven: School of Mages update (re)introduced “triggers from the activation […] of an activated mana ability” as a third alternative. However, no card in that release had a triggered ability that matched that criterion, nor did an existing card receive an erratum.

To this date, no ability exists that triggers from the activation of a mana ability and that meets the other criteria for a triggered mana ability, making this alternative criterion redundant. Given that the Magic Origins update’s intent was to make this rule more intuitive, this situation is unlikely to change, and the criterion should simply be removed.

Next is rule 605.4a, which describes how a triggered mana ability resolves. Specifically, it states that the ability resolves immediately after the activated mana ability that triggered it. This rule wasn’t updated by the Ixalan update and doesn’t account for Caged Sun’s ability, which triggers from mana being produced by any ability, not necessarily a mana ability.

Next is rule 605.5a, which effectively reiterates the criteria for mana abilities by stating that abilities that don’t meet those criteria aren’t mana abilities. Both the Magic Origins update and the Ixalan update left this rule unchanged, causing its text to conflict with rules 605.1a–b.

Like any other rule, rule 605.5a must be read in context. In this case, its parent rule 605.5 clearly defines it as a supplement to rules 605.1a–b, so the latter take precedence, solving the apparent contradiction. Only a malicious actor or a person lacking basic reading comprehension would ever conclude that rule 605.5a meant that Caged Sun’s ability weren’t a mana ability. (And if they did, they would also have to declare every other triggered mana ability to not be a mana ability.) Still, consistency alone dictates that rule 605.5a should be updated.

Finally, both rule 605.5a and rule 605.5b use the phrase “put mana into a player’s mana pool.” Elsewhere in the Comprehensive Rules, this phrase has long been replaced by “add mana to a player’s mana pool.”

Proposed amendments

Two of the criteria in rule 605.1a refer to instructions in the ability’s text. The sentence about replacement effects is removed.

605.1a An activated ability is a mana ability if it meets all of the following criteria: it doesn’t require a target (see rule 115.6), it could its text contains an instruction to add mana to a player’s mana pool when it resolves, it’s not a loyalty ability (see rule 606, “Loyalty Abilities”), and its cost and effect don’t its text doesn’t contain an instruction to move any card to or from a library. Do not take into account replacement effects that may apply, other than self-replacement effects, when evaluating these criteria.

One criterion in rule 605.1b refers to instructions in the ability’s text. The unused criterion is removed.

605.1b A triggered ability is a mana ability if it meets all of the following criteria: it doesn’t require a target (see rule 115.6), it triggers from the activation or resolution of an activated mana ability (see rule 605.1a) or from mana being added to a player’s mana pool, and it could its text contains an instruction to add mana to a player’s mana pool when it resolves.

The text of rule 605.4a is made more generic to account for both trigger events.

605.4a A triggered mana ability doesn’t go on the stack, so it can’t be targeted, countered, or otherwise responded to. Rather, it resolves immediately after the mana ability that triggered it, without waiting for priority.

Rule 605.5a is aligned with rules 605.1a–b and no longer uses “put mana into [a mana pool].”

605.5a An ability with a target is not a mana ability, even if it could put add mana into to a player’s mana pool when it resolves. The same is true for a triggered ability that could produce mana but triggers from an event other than activating resolving a mana ability or adding mana to a player’s mana pool, or a triggered ability that triggers from activating resolving a mana ability but couldn’t produce mana. These follow the normal rules for activated or triggered abilities, as appropriate.

Rule 605.5b no longer uses “put mana into [a mana pool].”

605.5b A spell can never be a mana ability, even if it could put add mana into to a player’s mana pool when it resolves. It’s cast and resolves just like any other spell. Some older cards were printed with the card type “mana source”; these cards have received errata in the Oracle card reference and are now instants.

Prepare for battle

The Magic: The Gathering | The Hobbit update expands the rules for battles in several places to handle non-Siege battles.

My first issue with the updated rules is that rule 122.1g has not been updated and does not account for the new state-based action.

Next are the rules for choosing a (new) protector for a battle. The update makes the language of rule 310.9a broader and its new text may apply both when a battle enters the battlefield and whenever a battle has an illegal protector or no protector at all. This provides a good basis for other rules to build upon.

Consequently, the update drops references to battle types from rules 310.11 and 704.5y; as a result, they don’t mention any criteria for protectors anymore and rely entirely on those found in rule 310.9a. Rule 704.5x, on the other hand, has retained such a reference and even gains an additional sentence for battles with no battle type.

I think that rule 310.9a should be made a bit clearer (and its typo should be corrected). Rule 704.5x should be shortened in the same manner as rules 310.11 and 704.5y, and not repeat the criteria defined in rule 310.9a.

Finally, there is an older issue with rule 310.10. Its first sentence states that a battle can’t be attached to a player or a permanent. Its next sentence mentions permanents again, but not players. Furthermore, the referenced state-based action applies to battles attached to players and objects. Rule 310.10 should be updated to match rule 704.5p.

Proposed amendments

Rule 122.1g mentions both of the state-based actions for battles with defense 0. The phrase “0 defense” is changed to “defense 0” to match the rest of the Comprehensive Rules.

122.1g The number of defense counters on a battle on the battlefield indicates how much defense it has. A battle with 0 defense 0 is put into its owner’s graveyard. If it’s a Siege battle, it is put into its owner’s graveyard only if it isn’t the source of an ability that has triggered but not yet left the stack. This These state-based actions doesn’t don’t use the stack. See rule 704.

Rule 310.9a is split into two separate rules; one contains the criteria for choosing a battle’s protector while the other just states that a battle’s controller chooses a protector as the battle enters the battlefield. Subsequent rules are renumbered accordingly. This separation makes it clear that the criteria apply in all situations where a protector must be chosen. The rewrite eliminates the typo found in the current text (“are determined”).

310.9a As a battle enters the battlefield, its controller chooses a player to be its protector. Which players may be chosen as its protector are determined by its battle type A battle’s battle type determines which players can be its protector (see rule 310.12). If it has no battle types, only its controller can be its protector.

310.9b As a battle enters the battlefield, its controller chooses an appropriate player to be its protector.

The references to battle types are removed from rule 704.5x.

704.5x If a battle has no player in the game designated as its protector and no attacking creatures are currently attacking that battle, that battle’s controller chooses an appropriate player to be its protector based on its battle type. If the battle has no battle type, its controller must be chosen. If no player can be chosen this way, the battle is put into its owner’s graveyard. See rule 310, “Battles.”

The text of rule 310.10 is changed to match rule 704.5p.

310.10. A battle can’t be attached to players or permanents objects, even if it is also an Aura, Equipment, or Fortification. If a battle is somehow attached to a permanent player or object, it becomes unattached. This is a state-based action (see rule 704).

Glossary entries for kinds of counters

While examining the new glossary entries, I noticed that the entries for kinds of counters are inconsistent in which rule they refer to. Some refer to top-level rule 122, while others refer to a specific subrule, such as the entry for finality counters which refers to rule 122.1h.

Among those entries that refer to rule 122, I think that Hone Counter and Keyword Counter should refer to their specific subrule instead.

Hone Counter

A counter on an Equipment that gives the equipped creature +1/+0. See rule 122, “Counters.” 122.1j.

Keyword Counter

A marker placed on an object that modifies its characteristics by granting it a keyword. See rule 122, “Counters.” 122.1b.

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

You will not be added to any email lists and we will not distribute your personal information.

This site uses Akismet to reduce spam. Learn how your comment data is processed.