[BUG] - RemoveBlockedUsers

[amiga-500]

Describe the bug
Despite successfully hiding blocked users posts, Discord STILL shows phantom notification alerts caused by blocked users posts. So when going to check a channel expecting to see somethign new and find there is nothing -- because it was the blocked user's posts.

To Reproduce
Occrs all the time. Just have a blocked user post a new message and have notifications enabled for a channel

Expected behavior
To NOT show notifications if the post was from a blocked user.

Discord Build (stable, ptb or canary):
Latest discord build (as of July 12, 2026). Using latest addon.

[8ug8ird]

Hi! I ran into similar issues while working on my own BetterDiscord plugin. I ended up implementing a different approach that solves this particular problem. If it helps as a reference, you can take a look at the implementation here:
https://github.com/8ug8ird/ByeBlocked
Hopefully it helps if this issue remains unresolved.

[choomcore-sketch]

thanksssssssssss @8ug8ird

[amiga-500]

Huge thank you @8ug8ird ! However, after trying your plugin, i notice it persistently shows the red dot badge at all times despite no unread messages. At least with RemoveBlockedUsers it will not show the red-dot unless there was something new, but has a bug where it shows the red dot randomly for no reason which i suspect is due to blocked users which i can make go away by simply restoring the discord app (i am using Windows desktop app).

So for now, i have disabled your plugin and gone back to RemoveBlockedUsers plugin instead.

[8ug8ird]

@amiga-500 Okay, no problem at all. Thanks for the report.

The "stuck permanently until restart" behavior you described was a real bug. The taskbar badge was only computed once, and nothing ever triggered a recomputation afterward. As a result, if it ended up in the wrong state during startup, it would stay that way until Discord was restarted, since a restart forced a fresh initialization and recomputation.

That's already fixed in the latest version. The badge now updates automatically once the plugin finishes determining which unread channels are blocked-only, instead of relying on a restart to correct itself.

One caveat: there's still a brief flash on cold startup in some cases. Discord's own native badge update can occur before BetterDiscord finishes loading plugins, and that's not something any plugin can fully prevent. The difference now is that the badge corrects itself within a second or so instead of remaining stuck. That's a separate, much smaller issue than the one you encountered.

[amiga-500]

@amiga-500 Okay, no problem at all. Thanks for the report.

The "stuck permanently until restart" behavior you described was a real bug. The taskbar badge was only computed once, and nothing ever triggered a recomputation afterward. As a result, if it ended up in the wrong state during startup, it would stay that way until Discord was restarted, since a restart forced a fresh initialization and recomputation.

That's already fixed in the latest version. The badge now updates automatically once the plugin finishes determining which unread channels are blocked-only, instead of relying on a restart to correct itself.

One caveat: there's still a brief flash on cold startup in some cases. Discord's own native badge update can occur before BetterDiscord finishes loading plugins, and that's not something any plugin can fully prevent. The difference now is that the badge corrects itself within a second or so instead of remaining stuck. That's a separate, much smaller issue than the one you encountered.

WOW thanks a bunch @8ug8ird ! Just updated and your plugin seems to be working well! You are super quick! Awesome work!