Hearthstone
Bug or intended?
Hello, everyone. Yesterday I was playing in wild and a particular Loatheb interaction caught my attention.
(I'm playing in German. Anduin says "I can't do that" and the error message states, that I need to target sth first.)
The reason why I am bringing this up is because the interaction between Forbidden Words and Loatheb worked differently in the past. Previously, if the opponent had played Loatheb and increased the cost of that spell, I would have still had the possibility to kill him, because I would have still used 5 mana to cast the spell. I am not sure when this interaction got changed - probably with the recent patch - but I think right now the forbidden spell wants us to use 5 extra mana, in order to compensate the temporary mana increase from Loatheb.
I would like to ask the following question - is the new interaction considered a bug or a fix to the previous one?
Leave a Comment
You must be signed in to leave a comment. Sign in here.
Hello, everyone. Yesterday I was playing in wild and a particular Loatheb interaction caught my attention.
(I'm playing in German. Anduin says "I can't do that" and the error message states, that I need to target sth first.)
The reason why I am bringing this up is because the interaction between Forbidden Words and Loatheb worked differently in the past. Previously, if the opponent had played Loatheb and increased the cost of that spell, I would have still had the possibility to kill him, because I would have still used 5 mana to cast the spell. I am not sure when this interaction got changed - probably with the recent patch - but I think right now the forbidden spell wants us to use 5 extra mana, in order to compensate the temporary mana increase from Loatheb.
I would like to ask the following question - is the new interaction considered a bug or a fix to the previous one?
in this situation, FW now costs 5 mana. Using FW would leave you with 0 mana left, and since there are no minions with 0 attack on the battlefield the spell cannot target anything. This is not a bug, this is an example of the card working as intended. In the past when the card didn't follow this logic, it was bugged and not working as intended as it didn't line up with the logic of the other forbidden spells in that situation.
Yes, I explained the logic of this interaction in the OP. Like I've said, it used to work differently in the past. I guess the old interaction wasn't intended, so it got fixed.