Phyrexian Toxin Tokens count as a cast, when really they should count as a summon (merely ‘coming into play’) like all other tokens.
I feel like this needs to be fixed sooner rather than later. Currently the only serious interaction I’m aware of which is being used by players is with Painful Quandary, but I expect that there are more options for combos in the existing cardpool and there will be more in the future too. Also, Inexorable Tide will now be owned by a number of players since it became available in the Elite packs today.
It can affect you negatively as well, such as playing against Hallowed Haunting, Blightcaster, and Willbreaker
Manaform hellkite will trigger from these tokens as well, leaving your opponent a nice stack to hit you with on their turn
Somehow, in your play testing and development, you, the devs, didn’t realize phyrexian toxin tokens count as casting a card, for your opponent. Which triggers a number of effects that shouldn’t happen, but nonetheless do. Log in, play a match on a test server, or live one, and you’ll see what players figured out within an hour of the set releasing. Is that the strategy here, hope for the best and let the players find your mistakes and complain until you correct them? Not the best plan I would say
Tokens are broken, count as your opponent casting a card when comes into play. See post in general discussion for full thoughts
Tokens count as your opponent casting a card
This bug seems to affect other tokens as well. E.g. AjaniPMA loyalty abilities spawn four tokens, and they count as casting, too.
And now that it’s a requirement not to cast more than 3 supports in order to get full points in this week’s white node of Revolving Planeswalk, it’s going to be even more of an issue.
@Oktagon_Support : this bug causes us to play more matches than needed to get to full progression, which means lost time. Please fix this asap.
Hello everyone,
I already asked the team to investigate this issue.
Thanks for letting me know!
Rebeca.
Hello @Specter ,
I already asked the team to investigate this issue.
Thanks for letting me know!
Rebeca.