Can't select attacking creature token collectlly.
I had two beast tokens, and one of them had one +1/+1 counter. Then, I activated The Wondering Emperor's [+1] to the beast, so now I had two 4/4 tokens and one of them had firststrike. In combat phase, I preferred to attack with only firststrike one because opponent controlled Glissa Sunslayer, but two beast were piled and I could't that. When I selected just one of them, it was always without firststrike one.
In short; in Declare Attackers Step, different tokens are piled up and it can cause troubles.
I'm not English user. I apologize for my bad text.
P.S. I played on Windows 11. And I forgot to screenshot.
-
TMLTurby#98334 commented
1. Create two identical tokens (for example, with Sokenzan, Crucible of Defiance).
2. Use The Wandering Emperor to give one of the tokens (Token A) a +1/+1 counter.
3. The tokens no longer stack on the battlefield because of their different stats (correct behavior).
4. Use The Wandering Emperor again on Token B. It now has a +1/+1 counter, but also first strike until the end of turn.
5. The tokens stack due to their same name/power/toughness (incorrect behavior, as one has first strike and the other does not).
6. Try to attack with only Token B (this one currently has first strike).
7. Cannot select Token B to attack. The game always selects Token A (no first strike). No matter in what order I select and deselect the tokens, there is no way to get the first striker to attack alone.This has been a reproduceable bug for me. I've added a screenshot for what it's worth.