devtrackers.gg
Okay give me a “Tap All” button then that auto taps all lands that only produce one color.
That's coming in the next release, actually! #wotc_staff
Okay give me a “Tap All” button then that auto taps all lands that only produce one color.
That's coming in the next release, actually! #wotc_staff
These days, effects that animate a land usually give haste because they know you’re often picking from a stack of similar things. So you shouldn’t end up getting screwed unless Arena starts adding older cards.
Even in the current world, you could make the animated land lose all abilities, or become a copy of something that doesn't have haste, or probably other situations where you still wish you didn't click the one with summoning sickness. #wotc_staff
We want to prompt you for priority for mana abilities with a side effect, like The Great Henge's, and abilities with mana that can be spent for two different types of costs accidentally got caught up in the logic for that.
Does that also include Castle Garenbrig? (Which also holds priority even if you can't cast anything)
Yes, in fact that was the card that the bug was specifically made to address. Both say "Spend this mana only to cast [...] or activate", which resulted in the parser thinking that that mana did something special besides having a spending condition. #wotc_staff
Read moreWow, this was a lot of work putting this together. I love the passion you have for the game. It's always easier to start the conversation with images and possible solutions. Here are some answers to your questions:
- We try to reduce information in the UX when we can, but keep it accessible. Magic is a complicated game, and having tons of extra things to look on the screen isn't always helpful for decision making. This is one of those instances where hiding it until pulled up is trying to thread that needle between over and under sharing information.
- I'm not a rule dev: u/WotC_BenFinkel
- This is to minimize crossing lines during a complicated blocking situation, but I will say it annoys me too sometimes. +1
- Probably just to make this action clear (if it was land there is a different interaction, so players might get confused if they just drew a card)
- There is no 5.
- Cool...
Regarding Chandra's Embercat, if by "block the stack" you mean prompts you for priority for its mana ability, it is a bug that should be fixed when Historic Anthology 3 goes live. We want to prompt you for priority for mana abilities with a side effect, like The Great Henge's, and abilities with mana that can be spent for two different types of costs accidentally got caught up in the logic for that.
As for Risen Reef, you have to remember that 99% of our rules-text code is machine-generated from the text of rule, in English. Risen Reef reads "look at the top card of your library. If it’s a land card, you may put it onto the battlefield tapped. If you don’t put the card onto the battlefield, put it into your hand." That is literally broken into 25 steps, branches, and labels, which look a little like the following (I took some out for brevity):
Your opponent's Legion Warboss (or any card that has a time-based trigger that is in an active zone for that trigger) will only prompt you for priority on the turn that it enters the relevant zone. If the Warboss entered the battlefield earlier than that, the onus is on you to put a stop on their main phase: the existence of the Warboss is not a "surprise" any more. #wotc_staff
I think it was Ben who said that all the old sets work, but they wont relese it yet because they arent as polished as the new sets.
A few cards here and there regress. For Amonkhet block, around five cards got minor problems as a result of being untested for two-ish years of development. Not too bad for machine-generated code I think! #wotc_staff
Thanks for the report! I'm sad to announce that I've fixed this bug this morning. Also, I learned something new about mutate and layered effects that point at spells! The correct behavior is for the layered effect to end up pointing at the permanent it becomes. Not so useful for Domri, but maybe someday we'll get [[Hall of the Bandit Lord]]. #wotc_staff
[deleted]
What can I say, our release schedule is weird. The fix isn't live yet, but it will be pretty soon. #wotc_staff
I coded up a fix a little while back, but it's not live yet. It should be going up in our next update (as it just got promoted to trunk yesterday). #wotc_staff
Thanks for the report. I'll look into it. We've been having trouble with that dang Wildbonder... #wotc_staff
Do you have automatic trigger sorting enabled? It is on by default. You can disable it in gameplay options. That should allow you to sort which trigger you want to resolve first. #wotc_staff
Basic lands have an activated ability: for example, Plains have "{oT}: Add {oW}." #wotc_staff
Read moreOn a related note, I'm fairly certain [[Sunbird's Invocation]] is currently bugged with adventure creatures. Before the last update, the Sunbird's Invocation trigger from casting a 4cmc or greater spell would let me cast the [[Granted]] half of [[Fae of Wishes]] without paying its mana cost. Now, selecting the Fae from the revealed cards just casts the 1/4 creature. WOTC pls fix. I want to play my jank.
"Casting a card as an Adventure isn’t casting it for an alternative cost. Effects that allow you to cast a spell for an alternative cost or without paying its mana cost may allow you to apply those to the Adventure."
Deck 4 Wolfwillow Haven (THB) 205 4 Fae of Wishes (ELD) 44 2 Mirrormade (ELD) 55 4 Gift of Paradise (M19) 184 4 Setessan Champion (THB) 198 3 Leyline of Anticipation (M20) 64 4 Wilderness Reclamation (RNA) 149 3 Storm's Wrath (THB) 157 4 Sunbird's Invocation (XLN) 165 1 Nyxbloom Ancient (THB) 190 2 Genesis Ultimatum (IKO) 189 4 Steam Vents (GRN) ...
Thanks, looks like we regressed sub-card interactions with resolution-time casting permissions, I'll get it fixed. #wotc_staff
Is that so? My bad then, I was absolutely sure it was even, but admittedly the card was killed and then brought back from the graveyard and I might have been confused if the opponent made a different choice.
That being said, I remember distinctly checking the protection before choosing top or bottom, and deciding that odd was the right one...
For what it's worth, I also tried reproducing your example as described and the Venturer was a legal target. Please let me know if you encounter this again though, I'm happy to take another look. #wotc_staff
In your screenshot, the Lavabrink Venturer has a "badge" with 3 crystals on it. That badge means it that "odd" was chosen for its protection ability, otherwise it would be two crystals. Thanks for the report though! #wotc_staff
Hey Ben, there’s also another higher profile bug were mutating creatures on top of nissa lands do not keep their stats.
That is rules-correct. The power/toughness setting effect Nissa confers happens on a later layer than the modifications Mutate does. #wotc_staff
So does this affect other abilities as well now that ability counters are in the game? Flying comes to mind.
I believe Menace is the only one of the "Ikoria nine" keywords to be backed by a qualification. Admittedly Flying probably should be for consistency's sake, but it isn't. #wotc_staff
Natual Menace is always first, issue is/was with second and later not properly adding it's effect. So since non-conditional non-counter instance of Menace (or any other ability) cannot be removed from creature without also removing all other instances, it's not possible to reproduce this bug on creature with natural full-time Menace.
Precisely! #wotc_staff
Thanks, I have a fix for this. As /u/50_Shades_of_Graves alludes to here, the word "creature" is the culprit - once the Scorpion dies it's not a "creature" any more but a "creature card". Still, the damage from it is dealt by a creature - the last-known-information of the Scorpion. I adjusted our code for "prevent" to allow for checking last-known-information objects. #wotc_staff
WotC coding
creature.menaceCounter--; if (creature.menaceCounter == 0) creature.menace = false;
Check out my postmortem of the bug here to see what actually happened! #wotc_staff