First off, I’m not sure whether this is a problem on the game’s side or on Battle.net’s side, so I apologize if this is posted in the wrong place.
Ever since World of Warcraft’s 12.0.7 update, I’ve been receiving an annoying number of notifications of friends logging in and out of Battle.net, both when they log out of the game and seemingly at random besides. Prior to 12.0.7, notifications were only received when the user actually logged into or out of Battle.net, not merely when logging out of a game. Additionally, the random notifications—and I’m only guessing here—seem to stem from the user’s status changing (such as from ‘online’ to ‘away’). As I said, this uptick in unwarranted notifications is already annoying, but it also often sends two (or even three) notifications at once! I’m really hoping that this can be looked at and potentially resolved.
This is actually a perfect place to post it. This forum is for the Battlenet team who handles the Desktop Battlenet launcher and services. What you are talking about are the Battlenet notifications - and how they are displayed. Is this about the display in WoW only, or do the notifications also persist on the Launcher when you only have that open?
You are not the only person I have seen reporting unwanted notifications that don’t match their settings.
Hopefully the Bnet team can investigate and fix it for everyone. In the mean time, I would uncheck then recheck the Bnet settings for notifications - which you may have done already. Not sure if that would help, but it won’t hurt.
Bugs that don’t impact everyone are honestly the hardest to fix.
Hey, thanks for the reply and reassurance that I found the right place to post!
Oh, it’s only for in-game notifications! I’m sorry I didn’t make that clear in my post. I’ve actually got most notifications turned off for the app/launcher itself, but I like seeing them in-game. Or did, until the 12.0.7 WoW update started inundating me with so many of them…I don’t really want to turn them off since I like seeing when my friends log in, but I may have to if this issue persists much longer and I can’t figure out a way to solve it on my end. 