If this is a regression try and find which part of the stack that's regressed.
It could be the kernel, mesa, wine or Battle.net itself.  Once you've found
which component run a git bisect - there's plenty of instructions on how to do
so.

When you've found which commit that's caused the regression report back here.

Hopefully from there a solution can be found -obv is the issue is in wine
you'll need to report there and if it's in Battle.net itself - good luck...