Hello, i would like to report a bug, had hapenned several times that, at the time i play the Springpaw, or the lynx it show me the green ring (means that i´ts able to attack) but i can´t click the minion to command, i´ts like the minion wasn´t in the board.
Springpaw
There is a known issue which can sometimes cause minions to be unactivatable if you interact with them too quickly after playing them (before the enter play animation is done). This is most obvious with charge and rush minions but can happen with others too (if you somehow can interact with the minion on the turn it is played). Some have reported having laggy connections, there could be a link there.
The main way to avoid that is to wait until the animation is completely done before attacking. If you encounter the issue, you can disconnect and reconnect quickly (on Windows, I use Alt+F4 to kill Hearthstone; in Mac OS, maybe command+Q will work), this will refresh the client and make the minion work normally again. Hopefully you catch it early enough in your turn that it reconnects before the rope times out.
1 Like
thanks man, would it be great to Blizzard to repair this bug, i´ve lost a few match for it, and it isn´t cool, the reload thing could be an option if the client dont take so long to log in!
1 Like
They included in the release notes for yesterday’s patch that the reconnection experience should be better.
Reconnect Improvements – Players attempting to reconnect to matches should now have a smoother overall experience.
I am not sure if that will help in this case at all. My recommendation is to avoid the bug as much as possible by waiting a second or two after the minion is on the field to try to attack with it.
As for fixing the bug, this has been known since 2015:
https://github.com/HearthSim/hs-bugs/issues/160
It must be a very difficult bug to isolate for it to be there for so long.
They mentioned in the recent Reddit AMA that they think they’ve got it pinned down:
https://www.reddit.com/r/hearthstone/comments/ay645h/hearthstone_developer_ama_year_of_the_dragon/ei0v1ht/?context=3
It’s been one of the more elusive bugs for us. We’ve finally been able to reproduce this bug more consistently and think we have a fix for it.
Evidently it didn’t make 13.4 but hopefully this one will finally be fixed soon.
2 Likes
Excellent! Tarzanboy, can you confirm that the bug has happened to you since yesterday’s patch, or did you just now posted, but the bug was happening before? There was no mention of the charge bug in the patch notes, but it could still have been fixed and the mention left out of the notes.
If it has not been fixed yet, we know the new expansion comes out April 9th, so there should be a patch for that, that is only 3 weeks away. Fingers crossed that it makes it for that patch!
1 Like
the bug was happened befor the patch, one or two times, but not always of course, but after the last patch it happened againg, i´ll take your advice and hope for you to fix it in the next one, thanks you very much for the help!