Couldn't block mutated menace creature
Hi guys,
Just encountered an issue where I couldn't block a menace creature with two creatures that had mutated. Each time I selected two creatures and clicked on the Glowstone Recluse with a menace counter a message would show up for a spit second saying "Illegal blocks. Try again.". I tried this numerous times over subsequent turns however it would never let me block the creature. I've attached a screen recording of what was happening, and given that the message only appears for a split second and the number of checks I did, I believe this to be a bug.
I checked the battlefield for the following:
- Another creature that said it must be blocked if able, preventing me from blocking the menace creature
- An effect on my creatures saying they couldn't block
- An effect on that creature saying it can't be blocked
- The new rare in this set that says menace creatures must be blocked by three or more creatures
- An effect that says it can't be blocked by MORE than one creature, which would combine with menace to make it unblockable
- Any other abilities on any other permanents that would prevent me from blocking
- Any global "until end of turn" effects to the side of the screen that would prevent me from making the blocks
- Any ! indicators saying I had to make certain blocks
After using 4 timeouts trying to find the reason I couldn't block it over multiple turns I eventually lost the game due to being unable to block this creature.
Please let me know if I am missing something. If this does turn out to be a bug, is it possible to get another entry/gems/something else as this draft event cost 10,000 gold to enter, and any extra wins after the first two in this format rewards quite a few gems.
-
WotC Ben Finkel#84357 commented
Hi there, I'm sorry you had this experience.
Currently, if there are any blocking restrictions or requirements, you are not allowed to make multiple blocks at once. In your video, you click on both of your blockers before clicking the attacker, which is a "batched" block. Next time you're in this situation, try clicking on one blocker, then the attacker, then the next blocker, then the attacker. It should work.
Now, this isn't great, I'll agree! We're working on supporting batched blocking for "must be blocked by N or more" restrictions, and ideally the client would be more communicative about what was going wrong in other cases, too. Thanks for your report! #wotc_staff