May have found the reason for Playful Sprites error: HS Deck Tracker?

Technical Support
1

I think I might have found the culprit for playful sprites error that’s ongoing at my PC gaming setup for approx. 2-3 weeks by now. And never had it before.

So, I have created a ticket for this and tried numerous support articles and solution methods, none of them worked permanently except for the support article (https://eu.battle.net/support/en/article/000018238) where you clean the Hearthstone options cache folder. I figured, every time I deleted the folder, the game would launch properly, but only allowed me to play a few games until it required me to quit the game one way or another. And last time I deleted the folder, and not start my HS Deck tracker, I just tried relaunching the game again and again and for the first time in weeks, game would launch without issues repeatedly. THEN, I saw that Deck tracker wasn’t working because that log.config file was updated after deletion naturally, and it asked me to restart HS in order to start tracking again… Anyway, I did as it said, and guess what, playful sprites came back just as annoyingly, almost in alliance with HS Deck tracker???

I think this may be caused by a certain update of the game or the tracker itself that has taken places in last 2-3 weeks.

What do you think guys?

I am planning to quit HS deck tracker until another update comes out. Games seems to launch and run properly without it so far. I’ll update if I see any sign on the contrary of this finding.

UPDATE, 07.07.2020, 12:43
I am testing this on my side again, and it really does work as I said. Once you clear (delete) HS folder as stated in support article, game starts to work perfectly fine. But it’s only because HS Deck tracker stops working. It asks you to restart the game because that config.log is changed. But as soon as you get the tracker back online, game starts giving playful sprites error. As long as you avoid using deck tracker, game runs perfectly after deleting the hs folder for once. Now, until this bug is solved, I guess I’ll have to memorize my decks better :slight_smile: …
Please let me know if anyone has similar experience.