An Unofficial Update Bulletin for Mystery Booster Commander Edition

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

Sometime between the 19th of August 2026 and the 29th of August 2026, Wizards of the Coast updated the Gatherer card database. The update adds eighty cards from the Mystery Booster Commander Edition release, including all cards newly printed with that release.

In this article, I list all prerelease errata for the new cards, changes to existing Oracle text, and notable Gatherer rulings. For each item, I describe the change, its primary consequences, side effects, and anything else I find noteworthy. If I think that the update omits an erratum for a card, the omission gets its own entry.

See the Potential Rules Amendments companion article for suggested errata.

Disclaimer: I have no special insight into the inner workings of Wizards of the Coast or their rules team; any observations are based solely on official information and my own knowledge and understanding of Magic’s rules system. While I strive for completeness and correctness, I may miss some changes; in particular, my process for archiving and comparing Gatherer revisions is constantly evolving, just like Gatherer itself. (Then again, Wizards of the Coast purposefully omit minor changes in their own bulletins, so I think I’m still ahead.)

Table of contents

Changes to the Comprehensive Rules

Wizards of the Coast have not published a Comprehensive Rules update to go along with the Gatherer update.

The only necessary change would be the addition of new types and the rulebreaker ability word. I expect those additions to take place as part of a future Comprehensive Rules update, closer to the set’s release.

Prerelease errata

Note: Most of the time, I list only the changed parts of a card’s Oracle text, rather than the complete text of the card.

All subtypes removed (functional)

Wizards of the Coast have issued a large number of prerelease errata which change subtypes to (as yet undefined) card types. These errata affect all cards newly printed in the Mystery Booster Commander Edition release, as well as reprint versions added by this update.

The errata replace the em dash on the type line with a hyphen-minus. Since the Comprehensive Rules use a long dash to differentiate between card types and subtypes, removing the em dash automatically moves the former subtypes into the card-type part of the type line. See rule 205.3b.

As a result, each card printed with the creature card type and the Human and Wizard subtypes now has the creature card type, two undefined card types named “human” and “wizard,” and no subtypes. Other cards and reprint versions are affected accordingly.

Tolabow, Loch Rascal (functional)

Wizards of the Coast have issued a prerelease erratum for Tolabow, Loch Rascal’s rules text. The erratum changes the functionality of Tolabow’s rulebreaker ability in two ways:

First, the printed text allowed a player to include instant and sorcery cards of the chosen color, regardless of their color identity; for example, if the commander’s color identity is just blue and the chosen color is green, a deck with Tolabow could contain any green instant or sorcery card, such as Giant Growth, Wild Hunger, or even Conflux. Conversely, instant and sorcery cards that aren’t the chosen color had to match the color identity of the deck’s commander; in the example, the deck could contain Ponder but it couldn’t contain Memory’s Journey.

With the erratum, the chosen color instead expands the allowed color identity of all instant and sorcery cards in the deck. In the example with a commander whose color identity is just blue and with green as the chosen color, the deck can contain any instant and sorcery cards whose color identity fits into green/blue, such as Giant Growth, Ponder, or Memory’s Journey; it cannot contain Wild Hunger or Conflux.

Second, with the printed text, the rulebreaker ability’s effect applied to any deck that contains Tolabow, whether or not Tolabow was that deck’s commander. (The same still holds true for the other cards with a rulebreaker ability; see the next section.) The erratum makes the ability’s effect apply only if Tolabow is the deck’s commander.

Printed text

Rulebreaker — A deck with this commander can have instant and sorcery cards of one additional color not in this commander’s color identity and any basic land cards.

Oracle text

Rulebreaker – If Tolabow, Loch Rascal is your commander, the color identity of instant and sorcery cards in your deck can include one color of your choice not in your commander’s color identity, and your deck can have any basic land cards.

Omitted erratum for rulebreaker cards (functional)

As printed, the effect of Seluma, Light of Aysen’s rulebreaker ability applies to any deck that contains Seluma, even if Seluma is not that deck’s commander. The same holds true for the other rulebreaker cards.

Oracle text (example)

Rulebreaker – A deck with this commander can have Angel cards of any color identity and any basic land cards.

Per rule 700.7, a phrase like “this commander” really means “this object,” regardless of whether the object is a commander. Thus, a phrase like “A deck with this commander can have Angel cards of any color identity” is equivalent to “A deck with this card can have Angel cards of any color identity.”

The erratum for Tolabow, Loch Rascal (see above) changes its text to use the standard “if this card is your commander” template. As a result, the effect of Tolabow’s rulebreaker ability applies only if Tolabow is actually the deck’s commander.

Wizards of the Coast have not issued prerelease errata for the other seven rulebreaker cards, so their abilities’ effects apply to any deck they are a part of.

For potential errata, see the Potential Rules Amendments.

Omitted errata for Yume, Chronicler of Valor (functional)

Rule 113.2c establishes the default of how to divide rules text into abilities: each paragraph in a card’s text represents one ability. It also establishes an exception in the form of keyword abilities. Rules 603.11 and 607.2h establish another exception in the form of a static ability and one or more triggered abilities that are linked to that static ability.

Yume, Chronicler of Valor has one paragraph of rules text, so by default it would have a single ability of an undefined nature: half static ability and half triggered ability.

Oracle text

The first spell you cast during each of your turns has assist. When you cast that spell, if another player spent mana to cast it, you and that player each draw a card. (As you cast a spell with assist, you may choose another player. They may pay some or all of the generic mana in the spell’s cost.)

If the paragraph was instead treated as two linked abilities, one would clearly be a static ability and one would clearly be a triggered ability. Rule 607.2h would apply to those abilities such that the triggered ability would trigger only from actions taken as a result of the static ability. However, the static ability doesn’t instruct a player to take any actions (or allow them to take an action); rather, it grants an ability to specific spells. Thus, there would be no actions that could cause the triggered ability to ever trigger.

Wizards of the Coast have not issued an erratum that clarifies the nature of Yume’s ability, nor have they issued an erratum that splits the paragraph into two distinct and unlinked abilities.

For a potential erratum, see the Potential Rules Amendments.

Changes to Oracle text

Version-specific Oracle text for Oracle of the Alpha (functional)

The Magic: The Gathering—FINAL FANTASY update removed the types and rules text of all Mystery Booster 2: Convention Edition Alchemy cards, including Oracle of the Alpha.

The Mystery Booster Commander Edition update adds an entry for Oracle of the Alpha’s reprint, but doesn’t change the Mystery Booster 2: Convention Edition entry. As a result, Oracle of the Alpha has two different official Oracle texts.

Mystery Booster 2: Convention Edition

Oracle of the Alpha

{2}{U}



2/3

Mystery Booster Commander Edition

Oracle of the Alpha

{2}{U}

Creature – Bird Wizard


Flying

When this creature enters, conjure the Power Nine into your library, then shuffle.

Whenever this creature attacks, scry 1.


2/3

Gatherer rulings (nonfunctional)

Rulebreaker

One of the standard rulings for the rulebreaker ability word claims that the effect of a rulebreaker ability applies only if the card with that ability is the deck’s commander. As discussed above, this is incorrect for seven of the eight cards with a rulebreaker ability.

The effect of a card’s rulebreaker ability applies only if that card is designated as your deck’s commander and functions only before the game begins.

Sahir, Visitor in Darkness

A ruling on Sahir, Visitor in Darkness’s Gatherer page claims that a source dealing exactly 1 damage to Sahir’s controller will cause its second ability to trigger only once. That is not always correct.

A source dealing exactly 1 damage to you will cause Sahir’s last ability to trigger only once, even though you also lose exactly 1 life. This is because the source dealing you damage isn’t what’s causing you to lose life. (That’s a job for the rules!)

Suppose Alex resolves Psychotic Haze while she controls Sahir, Visitor in Darkness. To carry out the damage event, Alex determines the amount of damage dealt to her, which is 1 damage [CR 120.4b]. Then she determines the result of that damage, which is that she loses 1 life [CR 120.4c][CR 120.3a]. Once those two things have been determined, the damage event occurs: Psychotic Haze deals 1 damage to Alex and Alex simultaneously loses 1 life [CR 120.4d].

In this scenario, Psychotic Haze makes itself deal damage to Alex, so Psychotic Haze is the cause of that damage. The damage in turn makes Alex lose 1 life, so Psychotic Haze is also the cause of the life loss. Thus, two events occur that each meet one of the trigger conditions of Sahir’s second ability. Those two events occur simultaneously and are highly related, but they are ultimately two distinct events, and Sahir’s second ability recognizes them as two instances of its desired trigger event(s) and triggers twice [CR 700.1].

In general, whenever a spell or ability controlled by Sahir’s controller deals 1 damage to them (or has another source controlled by that player deal that damage) and they lose 1 life as a result, then Sahir’s second ability triggers twice. This includes Sahir’s eminence ability.

Notably, the claim that causing the life loss is “a job for the rules” is not true, at least not in any meaningful way.

A shared cause

The Comprehensive Rules don’t define “cause” as a term, so the word has its standard English definition [CR 701.1]. This leaves room for different interpretations, and crediting the rules as the cause of the life loss may seem reasonable at first: Psychotic Haze, by itself, doesn’t cause any life loss, it only causes damage to be dealt; the life loss enters the picture with rule 120.3a.

Taking this a step further though, is Psychotic Haze actually the cause of the damage? By itself, the spell can’t cause a damage event; it does so only thanks to rule 120.4. And without rule 608, Alex couldn’t carry out the damage-dealing instruction while Psychotic Haze resolves. And without rule 117, nobody could have passed priority so that the spell gets to resolve. And so on.

Ultimately, the Comprehensive Rules are the very basis for a game of Magic, so one can say that they cause everything happening in a game. But as the saying goes, “if everything is caused by the rules, nothing is.”

Consider Rage into the Valley. Without all the rules for casting spells, resolving spells, and passing priority in between, Rage into the Valley would never resolve and no life loss would ever happen. But saying that Rage into the Valley doesn’t cause the life loss seems ridiculous.

One might argue that Rage into the Valley causes the life loss because it’s the most immediate cause: while there are plenty of rules that cause Rage into the Valley to be a resolving spell on the stack, once that point is reached and the “lose 1 life” instruction comes up, no further rule comes between that instruction and the life loss event. In the long, long chain of things leading from the game’s start to this moment, Rage into the Valley’s instruction is the very last link.

Contrary to that, the damage-dealing instruction of Psychotic Haze would not be the ultimate step that leads to the life loss. Between the instruction and the life loss event would be rule 120.4 for processing the damage event and rule 120.3 for the results of the damage.

I see an issue with this argument when the payment of life is involved. Consider Voracious Tome-Skimmer’s triggered ability. If the ability’s controller pays 1 life, does that ability cause them to lose 1 life? Or wouldn’t rule 119.4 be the most direct cause, because paying 1 life needs to first be converted into losing 1 life? But saying that Voracious Tome-Skimmer’s ability doesn’t cause the life loss seems pretty unintuitive.

It looks like the direct-cause approach is not the final solution. The rules surrounding damage, life, and life loss are too numerous and too informal for this to work. (And my intuition tells me that trying to formalize the cause of something won’t be feasible.) I’m not even sure I didn’t overlook some rule in the Rage into the Valley scenario that could claim to be the direct cause of that life loss.

What I’m sure about is that the idea of a single cause for something is flawed: in almost all cases, multiple things are involved in causing an event. In the original example, a rule states that the life loss happens, but according to that rule’s text, the damage causes that life loss, and that damage is caused by Psychotic Haze. I find it reasonable to say that all three things—the rules, the damage, and Psychotic Haze—played a part in causing the life loss, so they all count as its cause.

Once I allow multiple causes for an event, the question of whether the rules cause an event becomes practically irrelevant. This is because no card actually cares whether a rule was involved: no ability triggers when a rule causes a player to gain or lose life, no replacement effect applies if a rule causes a player to discard a card, and so on. They all check spells, abilities, effects, or damage. But not rules. (Cards like Panharmonicon are their own thing.)

The Comprehensive Rules are basically the same. The only thing that is close to asking whether a rule caused something is the section on face-down spells and permanents with regards to what caused an object to be face down. Determining how an object came to be face down isn’t complicated though and I don’t think there’s any confusion over that.

So, in the Psychotic Haze scenario, asking whether the rules cause the life loss is the wrong question. The correct question is whether Psychotic Haze also causes the life loss. The answer to the first question is practically always yes, so it’s useless. For the second question, I repeat my above answer: Psychotic Haze is undisputably the cause of the damage, and according to rule 120.3a, that damage is the cause of the life loss. (If damage didn’t cause life loss, Archon of Coronation’s last ability would be pointless.) Thus, it seems reasonable to say that Psychotic Haze is one of the causes of the life loss.

Taking “[t]hat’s a job for the rules” to its logical conclusion

The two direct links, between Psychotic Haze and the damage and between the damage and the life loss, are pretty solid; the first is just that intuitive and the second is explicitly defined by rule 120.3a. The weakest part of my argument is introducing the transitivity: if Psychotic Haze causes the damage, it also counts as causing the results of that damage. I imagine if someone wanted to argue in favor of the Gatherer ruling, they’d dispute that transitivity and point to the “[t]hat’s a job for the rules” part.

I’d also expect that someone to apply “[t]hat’s a job for the rules” consistently, meaning to all results of damage, not just to life loss. After all, the various subrules of rule 120.3 describe all the results of damage in the same way: damage dealt to a player or a permanent with specific qualities by a source with specific qualities causes a specific result. Neither the Comprehensive Rules nor the Gatherer ruling indicate that one result in particular is treated differently from the rest. So, let’s examine some scenarios where damage is dealt and compare the outcomes of the shared-cause approach and the “a job for the rules” approach.

Suppose Alex controls Colossal Dreadmaw and Doubling Season. Nona casts Puncture Blast, targeting Colossal Dreadmaw. As Puncture Blast resolves, how many -1/-1 counters are put on Colossal Dreadmaw?

Using the shared-cause approach, the resolving Puncture Blast causes the damage and its results, so the -1/-1 counters are put on Colossal Dreadmaw by an effect. The replacement effect of Doubling Season’s ability applies to that event, so a total of six -1/-1 counters are put on Colossal Dreadmaw.

Using the “a job for the rules” approach, the resolving Puncture Blast causes only the damage while rule 120.3d causes the -1/-1 counters to be put on Colossal Dreadmaw. This rule doesn’t generate an effect, so the replacement effect of Doubling Season’s ability doesn’t apply. A total of three -1/-1 counters are put on Colossal Dreadmaw.

I assume most people’s intuition would say six -1/-1 counters should be put on Colossal Dreadmaw.

Another interesting result of damage is life gain:

Suppose Alex controls Firesong and Sunspeaker while Nona controls Rain of Gore. Alex casts Boros Charm, targeting Nona. As Boros Charm resolves, it deals 4 damage to Nona. Does Alex gain 4 life or lose 4 life? Does Firesong and Sunspeaker’s last ability trigger?

Using the shared-cause approach, the resolving Boros Charm causes the damage and its results, so the potential life gain is caused by a spell Alex controls. The replacement effect of Rain of Gore’s ability applies to that event, so the actual outcome is that Alex loses 4 life. She doesn’t gain life, so Firesong and Sunspeaker’s last ability doesn’t trigger.

Using the “a job for the rules” approach, the resolving Boros Charm causes only the damage while rule 120.3f potentially causes Alex to gain life. A rule isn’t a spell or ability, so the replacement effect of Rain of Gore’s ability doesn’t apply. Alex actually gains 4 life. However, the trigger condition of Firesong and Sunspeaker’s last ability isn’t met (similar to Rain of Gore), so that ability doesn’t trigger.

I assume most people’s intuition would say that Alex should lose 4 life.

Speaking of lifelink:

Suppose Alex casts Wave of Reckoning while she controls Archangel of Thune and Daybreak Chaplain. As Wave of Reckoning resolves, how often does Archangel of Thune’s last ability trigger?

So far, I focused on scenarios where a spell makes itself deal damage; here, a spell makes other objects deal damage. Inserting another object between the spell and the damage shouldn’t change anything for either approach though: on the one hand, if spell, damage, and rules can jointly cause the damage’s results, why not a quartet of instructing spell, instructed object, damage, and rules? And on the other hand, if only the rules cause the results, any number of additional objects don’t matter.

Meanwhile, Archangel of Thune’s last ability triggers whenever a source causes Alex to gain life, as per rule 119.9. The Comprehensive Rules define the term “source” for mana, abilities, and damage, but not for (gained) life, so the usage in rule 119.9 (and its sibling rule 119.10) is a bit vague.

Using the shared-cause approach, Wave of Reckoning, Archangel of Thune, and Daybreak Chaplain all count as causing the damage and its results. Arguably, Archangel of Thune’s last ability triggers three times: once for Archangel of Thune, once for Daybreak Chaplain, and once for Wave of Reckoning.

Intuitively, this is one time too many: the ability should trigger only for Archangel of Thune and Daybreak Chaplain. But saying that Wave of Reckoning doesn’t cause life gain in this scenario clashes with Rain of Gore and with Firesong and Sunspeaker.

I don’t think this is an issue with the shared-cause approach itself, though. Rather, the issue lies with rule 119.9’s vague use of the word “source.” Replacing that phrase with a detailed explanation that covers scenarios like the current one seems the way to go here. For the moment, I will have to live with Archangel of Thune triggering one more time than desired.

Meanwhile, the “a job for the rules” approach doesn’t recognize Wave of Reckoning as the cause of the life gain. In the same vein, it shouldn’t recognize Archangel of Thune or Daybreak Chaplain. Only rule 120.3f causes the life gain, and since that rule is always the same, Archangel of Thune’s last ability triggers exactly once.

And that should be all the results of damage relevant to this discussion. Applying the “[t]hat’s a job for the rules” approach consistently leads to surprising and unintuitive outcomes. The alternatives are an inconsistent application of this approach, or the consistent application of the shared-cause approach. Depending on how much one values intuitiveness and consistency, the choice should be clear.

For a proposal on how to make Sahir, Visitor in Darkness more intuitive and also have it match the ruling’s intended outcome, see the Potential Rules Amendments.

Chira, All In

A ruling on Chira, All In’s Gatherer page claims that Chira’s ability triggers only if the listed things happen as part of an effect. That is incorrect.

The ability’s trigger condition doesn’t mention effects, so Chira’s ability triggers whenever any of the listed things happen, regardless of the circumstances. It could be as part of an effect, but it could also happen while a spell is cast, an activated ability is activated, or a triggered ability is put onto the stack, or as part of a special action, a state-based action, or a turn-based action.

Chira’s ability will trigger only when an effect instructs you to flip one or more coins, roll one or more dice, or take one of the other listed actions at random. You can’t decide to discard a card at random when you’re simply instructed to discard a card in order to get Chira’s ability to trigger.

Ashaya’s Enduring Bond

The Gatherer page of Ashaya’s Enduring Bond features the standard rulings for the discover keyword action. One of those rulings concerns split cards.

Since a split card outside the stack has the combined mana cost of both halves, it can only be discovered if the sum of both halves’ mana values is less than or equal to the discover value. Consequently, either half’s mana value will be less than or equal to the discover value. The ruling’s parenthesis seems to have forgotten about this fact; alternatively, it implies the existence of split card halves with a negative mana value.

By mentioning the fuse keyword ability, the ruling also implies that split cards with fuse could be cast fused, which would be incorrect.

The mana value of a split card is determined by the combined mana cost of its two halves. If discover allows you to cast a split card that doesn’t have fuse, you may cast either half (as long as its mana value is less than or equal to the effect’s discover value) but not both halves.

Elda, Conjurer of Spectacle

Elda, Conjurer of Spectacle’s Gatherer page features the standard rulings for the demonstrate keyword ability.

The language of one of those rulings implies that the chosen opponent is forced to copy the spell with demonstrate, which would be incorrect. The opponent can choose not to copy the spell [CR 702.144].

If you choose to copy a spell with demonstrate, you then immediately choose an opponent. They copy the spell, and that copy goes on top of the stack.

Flitwing, Lyev Detective

One ruling on Flitwing, Lyev Detective’s Gatherer page features a typo: the period after the parenthesis is missing.

If an effect would put a noncreature permanent onto the battlefield attacking or blocking, it enters but it’s never considered to be an attacking or blocking permanent. For example, suppose you control Flitwing and Hero of Bladehold (a creature with battle cry and “Whenever this creature attacks, create two 1/1 white Soldier creature tokens that are tapped and attacking.”) [sic] As Hero of Bladehold’s last ability resolves, if you choose to apply Flitwing’s replacement effect to that ability, you’ll create two Clue tokens that are tapped, but not attacking.

Kuroki, Thief of Talents

One ruling on Kuroki, Thief of Talents’s Gatherer page features a typo in the form of a duplicate space.

If the target opponent has three or fewer cards in their library, they can still choose to draw four cards.  [sic] If they do, you’ll still be able to cast a spell from their hand without paying its mana cost, but once Kuroki’s ability finishes resolving, state-based actions will be checked and that opponent will (in most cases) lose the game since they attempted to draw a card from an empty library. At that point, they’ll leave the game along with the spell you cast from their hand. (They probably shouldn’t have chosen to draw four cards, but that’s not your problem anymore.)

Glava, Five-Advents Mage

One ruling on Glava, Five-Advents Mage’s Gatherer page features a typo: “permanent” should be “permanent spell.”

If a permanent has an ability that triggers when it’s cast that references the value of X, you choose whether to have the value of X become 5 before or after that ability resolves (based on the order in which you choose to put the triggered abilities on the stack).

Another ruling first mentions both spells and abilities; later in the same sentence, spells and abilities are mentioned again. In the second sentence, only spells are mentioned.

If the number of targets a spell or activated ability has is dependent on the value of X, those targets are chosen during the casting of that spell or activation of that ability. Changing the value of X later with Glava’s ability won’t affect the number of targets that spell has.

A third ruling is missing a period.

Regardless of choices made for Glava’s ability, X is 0 for the purpose of determining the mana value of a permanent with {X} in its mana cost once it’s on the battlefield [sic]

Feroz, Ulgrotha’s Warden

One ruling on the Gatherer page of Feroz, Ulgrotha’s Warden features a typo: it should refer to Feroz’s last loyalty ability.

Feroz’s last ability creates a token that’s a copy of the card Feroz’s Ban in the Oracle card reference. Official text for Feroz’s Ban can be found using the Gatherer card database at Gatherer.Wizards.com.

Selenia, the Cursed Heart

One ruling on Selenia, the Cursed Heart’s Gatherer page features a typo: “means” should be spelled “mean.”

In the rare case where you control two Selenias, life you gain is multiplied by four. Three Selenias means [sic] life you gain is multiplied by eight, and so on.

Oracle of the Alpha

The rulings published on the Gatherer page of the Mystery Booster Commander Edition version of Oracle of the Alpha differ from the rulings published in the Mystery Booster Commander Edition Release Notes.

The Gatherer rulings are identical to the rulings originally published for the Mystery Booster 2: Convention Edition version. The Edge of Eternities update removed those rulings from the Mystery Booster 2: Convention Edition page, and the Mystery Booster Commander Edition update has not restored them to that page. As a result, the two Gatherer pages for Oracle of the Alpha feature different sets of rulings.

One ruling in the Release Notes lists the Power Nine in lexicographical order; the Gatherer page lists them in alphabetical order instead.

Release Notes text

The “Power Nine” are Ancestral Recall, Black Lotus, Mox Emerald, Mox Jet, Mox Pearl, Mox Ruby, Mox Sapphire, Time Walk, and Timetwister.

Gatherer text

The “Power Nine” are Ancestral Recall, Black Lotus, Mox Emerald, Mox Jet, Mox Pearl, Mox Ruby, Mox Sapphire, Timetwister, and Time Walk.

Another ruling in the Release Notes uses Mystery Booster Commander Edition Limited and cards; the Gatherer page uses Mystery Booster 2 Limited and cards instead.

Release Notes text

You do not need to own an actual copy of a card in order to conjure it, and a conjured card does not need to obey format legality or deckbuilding restrictions. For example, in a game of Mystery Booster Commander Edition Limited, Overcooked can conjure Food Fight onto the battlefield, even though the card Food Fight isn’t found in Mystery Booster Commander Edition and isn’t normally legal in the Limited format.

Gatherer text

You do not need to own an actual copy of a card in order to conjure it, and a conjured card does not need to obey format legality or deckbuilding restrictions. For example, in a game of Mystery Booster 2 Limited, Toralf’s Disciple can conjure Lightning Bolts into your deck, even though the card Lightning Bolt isn’t found in Mystery Booster 2 and isn’t normally legal in the Limited format.

A third ruling in the Release Notes uses the phrase “a card” in its last sentence; the Gatherer page uses “an object” instead.

Release Notes text

You can represent conjured cards using objects from outside the game so long as the game state remains clear and understandable to all players. You might need to get creative. For example, while a conjured card is in a public zone, you can represent it by writing on a piece of paper or using some kind of token. But if a conjured card is put into a hidden zone, you must add a card to that zone which, while face down, is indistinguishable from other cards in your deck.

Gatherer text

You can represent conjured cards using objects from outside the game so long as the game state remains clear and understandable to all players. You might need to get creative. For example, while a conjured card is in a public zone, you can represent it by writing on a piece of paper or using some kind of token. But if a conjured card is put into a hidden zone, you must add an object to that zone which, while face down, is indistinguishable from other cards in your deck.

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.