WotC_BenFinkel

To clarify, you have to Mutate a menace creature on top? Having menace naturally doesn't seem to result in this bug, I'll try again with mutating. #wotc_staff

EDIT: Yes, mutating seems to do the trick. Let's figure out what's going wrong.

EDIT 2: Alright, got it! Here's what's going on. Whenever we detect that you've gained a new ability, we usually kick off that new ability's continuous effects. However, multiple different places in the code can attempt to start those continuous effects (creating attachment relationships and redestining zone transfers are some somewhat esoteric examples), and we don't want to double-dip starting those continuous effects, so we see if there are any already from this ability.

Menace makes a BlockedByMinCountQualification, which is a continuous effect. When you add menace (say, Menace2, the one from Cavern Whisperer) to something that already has it (say, Menace1, from the Menace counter) we were erroneously thinking we'd be d...

The rule for predicting cost adjustments accidentally removed all checks for zone constraints (instead of just the ones about "this spell" - it's not a spell until it's on the stack!). So basically Mystical Dispute is predicting it cost 2 less if there was a blue card anywhere in the game. Oops! I have a fix, but it probably won't be live for a while, especially as it doesn't affect gameplay much (just gives you stops if you can afford U and your opponent controls a spell...) #wotc_staff

I'll be investigating this tomorrow. #wotc_staff

According to my chat with MTG rules manager Eli Shiffrin, "another" on Cavalier of Thorns means "other than any card that constituted this permanent". I suppose a Melded creature that became a copy of Cavalier of Thorns would have had the same issue - y'know, if Eldritch Moon were in Arena. #wotc_staff

That would probably need some new semantics in the prompting-time version of the noun to mean "or has X in its cost", as that could POTENTIALLY become a 3+ cmc spell. And we'd need to ensure the X-bound logic enforced a MINIMUM X choice. Let alone the autotap concerns... #wotc_staff

Consider that Lurrus is the first card on MTG:Arena that both allows you cast a spell constrained by its CMC and doesn't provide an alternative cost for doing so (unlike cards like [[Electodominance]]). So right off the bat we're talking about something new, but that looked really familiar - I'm not surprised that our testing strategy missed this case.

In order to even begin proposing casting the spell, some rule or ability needs to grant you permission to do so. Lurrus' code sees a card in your graveyard with CMC <= 2, and so it proposes it, thus you can start casting it. We need an entirely different step in the process, and thus entirely different code, to then step in at the choose-X step to enforce that the resulting CMC is STILL <=2. That doesn't come "free" from just "implement the comprehensive rules 1:1" - Lurrus' "you have permission to cast a CMC <= 2 spell" code needs to check in again there. Fortunately, the fix makes it so all CMC-capped casting permissions w...

Nailed it. Release bugs are the worst from the stress perspective - we have such limited time to fix in time for adequate testing before the "fast follow" release! The puzzle-solving aspect is one of my favorite components of this job. #wotc_staff

Thank you! Fixing these things is fun (of course, not as fun as getting them right in the first place!). #wotc_staff

We have a fix for this coming this week. #wotc_staff

Cards you see in your opponent's hand aren't "real" cards - internally, we call the object a RevealedCard. They get created when a known card goes to a hidden zone, and are removed when a card with the same appearance leaves (or the contents of that zone become unknown in some other way, like a Brainstorm effect). RevealedCards should have no impact on actual gameplay, such as effects that count the number of cards in a hand, or selecting a card to discard.

We didn't properly handle making RevealedCards for tokens that have been mutated; they make RevealedCards because the object-on-the-battlefield was a "real card". Clearly, that should be examined on a component-by-component basis. We should fix it this week, I hope, but know that it's only a visual problem. #wotc_staff

Thanks for the report. I have some ideas about what's happening here, I'll look into then soon. #wotc_staff

This is fixed in the upcoming release hopefully coming this week. The parse tree got flipped around, and now it basically thinks it means "search your library for a black creature card in your graveyard with cmc less than the number of creature cards (anywhere in the game)." A card can't be in your library and graveyard! #wotc_staff

This is fixed for the next release, hopefully coming this week. In the meantime I recommend manually placing stops when you want to cast it - the game will allow you to do so, it just mistakenly thinks you can't afford it. #wotc_staff

This is fixed in the next release, which I'm hoping is later this week.

Funnily enough, it is not more expensive to target the older Skybonder, just the newer one. #wotc_staff

Kale is my hero! #wotc_staff

Thanks for the report, this was an interaction I hadn't thought of. I checked with our paper-MTG rules folks and they confirmed that indeed, a mutated creature only earns you one land with Settle the Wreckage, so I'm fixing it! We hope to have an engine update sometime next week, so I hope the fix will be live then. #wotc_staff

It seems to have been an issue with how the client understands the messaging about how cards are attached to other ones. I didn't work on this bug, so take this with a grain of salt, but I think Journey to Eternity transforming and thus stopping being attached to something caused the next time we made a new attachment to be handled incorrectly. #wotc_staff

Looking at our issue tracker, it seems this bug has been fixed for the Ikoria release. #wotc_staff

The event should be live again now! #wotc_staff

Fortunately, it should be fixed with the Ikoria release. #wotc_staff