Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A card that was transformed into Keli'dan by Transmogrifier will trigger his "drawn this turn" ability even though Keli'dan was not the card drawn #1349

Open
Jetz72 opened this issue Jun 9, 2020 · 0 comments

Comments

@Jetz72
Copy link

Jetz72 commented Jun 9, 2020

Keli'dan the Breaker - Battlecry: Destroy a minion. If drawn this turn, instead destroy all minions except this one.

https://us.forums.blizzard.com/en/hearthstone/t/kelidan-aura-bug/34686

I was playing a game where I had a Transmogrifier on the board and the card I had drawn transformed into Keli’dan due to Transmogrifier’s effect. The aura around was the card was green, when normally if it’s effect would be active it’s aura is yellow which would signify that his ability would trigger and destroy all other minions instead of just one. I figured since he was transformed from a card that it would explain why his aura was green and that I could play him to destroy a single minion.

When I played Keli’dan, he destroyed all other minions. His aura was green and thus had indicated to me that this would not be the case.

Also shown by HearthTech - https://www.bilibili.com/video/BV1Ut4y1C74c - 0:56.

Display bug as reported by the user. However, I'd say it seems more wrong that Keli'dan's "drawn this turn" property is either carried over through the transformation or was set afterwards regardless of the transformation. The former is reminiscent of #969, where among other issues, transforming a minion played last turn into an Elemental would count as an elemental played last turn. That was fixed, indicating that even properties such as a card's history of moving through zones is not meant to be kept through transformation. The latter would be another case of #1347 - a property reflecting an event updating so long after the event has happened while ignoring the possibility that the card involved is no longer the same.

@Jetz72 Jetz72 added this to the 17.2.2.48705 milestone Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant