You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a token Eternal Sword effect jumps onto another creature, it is turned into a regular Eternal Sword enchantment. After it is destroyed, it gets into a players deck as a token enchantment scroll To Reproduce
Create a custom match: difficulty(Easy); buffUnitCreated(P1, Eternal Sword);
Get 2 creatures in play
Destroy your creature
Observe that second Eternal Sword on other creature is displayed as Enchantment.
Destroy the second creature
Observe that the count of (library + graveyard) increased.
Cycle through the deck until you get the Token Enchantment in your hand.
Expected behavior
The library+graveyard count shouldn't increase, and Token Enchantment should not be showed in hand. Eternal Sword should be displayed as Effect after jumping, not Enchantment.
Screenshots Screenshot (note how i have 55 scrolls in play after starting with 50).
Server or Client?
Server
Additional context
This was discovered via a Daily Medium trial on 16.07.2018. Also might need to investigate Infectious Blight?
The text was updated successfully, but these errors were encountered:
Similacrest
changed the title
Token Eternal Sword gets in hand
Token Eternal Sword becomes a card in play after jumping onto another creature
Jul 16, 2018
Describe the bug
When a token Eternal Sword effect jumps onto another creature, it is turned into a regular Eternal Sword enchantment. After it is destroyed, it gets into a players deck as a token enchantment scroll
To Reproduce
difficulty(Easy); buffUnitCreated(P1, Eternal Sword);
Expected behavior
The library+graveyard count shouldn't increase, and Token Enchantment should not be showed in hand. Eternal Sword should be displayed as Effect after jumping, not Enchantment.
Screenshots
Screenshot (note how i have 55 scrolls in play after starting with 50).
Server or Client?
Server
Additional context
This was discovered via a Daily Medium trial on 16.07.2018. Also might need to investigate Infectious Blight?
The text was updated successfully, but these errors were encountered: