When you have three creatures on the battle field and then cast a token creature, it will freeze the game if you try to replace a token with another token.
I know that’s not specifically a card, so I’ll delete from the post if you’d like.
I just dug through my screen shots and I have one from a month ago that was using Saheeli’s (old) first ability and trying to replace a moon token with her thopter.
Regarding Seasons Past, we have a bit of an issue - we are unable to reproduce it, sadly.
What would really help in fixing it is if someone could come up with exact steps that make the game freeze 100% (even if it freezes 80% of the time, it would help put us on the right path).
This is true of any card that freezes the game (or does something unintended) - reporting “This card freezes the game” is good because we become aware of the problem, but not having specifics on what happens when it freezes or a sequence of events that make the game freeze it can sometimes be very difficult to pinpoint.
Very specific - cast a card with transform. Transform the card. Destroy the transform card while in the transformed state. Then use Seasons Past or Liliana to return the card from the graveyard. Freeze. Every time.
What he said with the transform cards. For me, it’s when I play Startled Awake in the same deck as Seasons Past. The condition in which it freezes seem random, but I know every event I play I have to exile Seasons Past so I don’t cast it.
I highly suggest a deck with Seasons Past, Reclaim, and Kessig Prowler.
Cast two of the same card with transform ability (I suggest Kessig Prowler, as the transform mechanism is Activate and won’t the card won’t flip back).
Transform that card.
Kill that creature. (This is why I suggest Reclaim)
Cast Seasons Past.
Cast Seasons Past again. This is where you’ll find your freeze.
Speculation: It’s freezing when it attempts to bring back the second copy of flipped card, but the card is flipped and it can’t handle this edge case.
This is exactly the type of info we’re looking for.
Thanks to this, we have identified the exact source of the problem are we are in the process of fixing it! Unfortunately I do not have an ETA as to exactly when this will be pushed live (it requires a full client change and it very most likely won’t be in the next version since it’s already been sent out) but you can rest assured that it will be fixed!
As an aside, if you have bugs that you want us to look at, this is by far the best way to do so. If we have clear, precise steps to reproduce the issue, we can very easily identify the problem and work towards a resolution.
Awesome. Happy to help; I’m glad you guys got the root cause!
Question: do you guys have a sandbox environment where you can set which interactions to test, or do you have to do it like we do (by just playing the game) ?
I ask because there are some other interesting bugs that can be difficult to test (1 [I think you guys already know about this one], 2 [this one I cannot replicate because it’s SO specific], 3) without a sandbox.