v2.7.6

Optimization

• Reduced redundant DOM scanning on large servers: some checks that previously scanned the entire page now scan only known member-list containers instead. This should lower background CPU usage on large servers.

• Merged two internal observers into one to reduce duplicate work on DOM changes. The improvement is small on its own but helps reduce unnecessary processing.

• Added missing on/off checks so several background functions stop running when their related setting is disabled. Previously, some of them continued running regardless of the setting.

Fixed

• Fixed minor edge cases in the component-matching logic for blocked users to ensure better reliability after recent Discord updates.

• Fixed an internal bug where the message-filtering patch could occasionally fail to fully activate, causing unnecessary background retries. Blocked users' messages were still being hidden correctly; this only affected internal plugin health tracking.

• Fixed a bug that could cause the blocked-message-group patch to loop indefinitely and never finish after reloading the plugin with a channel already open.

• Fixed a bug where reactions from non-blocked users could sometimes disappear from the reactions popup, especially with custom server emojis.

SHA256: 1E0A25DC0BC9334E03EAF66C6EA62B4112B615A51C3AD768906A5437BCF9F47B

v2.7.5

Fixed

• Fixed an issue where the “Invite to Voice” button could disappear after joining a voice channel.

• Fixed an issue where reactions from non-blocked users could incorrectly disappear from messages

SHA256: 19F36F3D59EDC2C817FB321BCA5F25694884598A58C9FFEF88B240C834C2B9BA

v2.7.4

Fixed

• Fixed a mismatch between hasUnread, hasUnreadOrMentions, and hasTrackedUnread: the latter two used a simpler filtering logic that could let an unfiltered value through, causing the badge or unread indicator to show even when the only activity was from a blocked user.

• Fixed a case where, with Discord running in the background, a new message from a non-blocked user could fail to trigger the unread badge, because the plugin was comparing the latest message using a local cache that hadn't updated yet.

• Fixed a case where, after receiving a message from a blocked user followed by a message from a non-blocked user in the same channel, the unread badge wasn't updated right away. It would only show up once an additional message came in later.

• Fixed a case where a guild's unread state could be reported as visible before the plugin had finished scanning all of its blocked-only channels, which could show the badge even when the only unread activity in that guild was from blocked users.

• Hardened DM recipient resolution to fall back to recipients[] when recipient/recipientId aren't populated, so blocked-user checks on a DM channel don't silently fail to false in that case.

• Fixed a case where the taskbar/system badge could get stuck showing a stale count after blocking or unblocking a user, since the badge wasn't being recalculated at that moment.

Note

If you're still seeing a stuck unread badge after updating, it may not be related to blocked users at all.
Discord's own read state can occasionally get out of sync between the desktop app and browser,
try opening the conversation directly in the desktop app once. If the badge stays stuck for a
conversation with someone you've actually blocked, please open an issue with the console output
from window.__byeBlocked._debugBadge = true.

SHA256: 8763EA9EB416FD407EACB2F4E30315DEA7FC1508518FA2DCC31ADDA637F47C58

v2.7.3

Fixed

• Fixed a case where unread badges were suppressed when the plugin was inside the plugins folder but disabled.

• Fixed an issue where the unread notification would get stuck next to the server icon when enabling the plugin, when the last message was from a blocked user. It would only disappear after reloading Discord.

SHA256: BAC1ABABC1C8D9FEEF1CA525C3482C86FB3E5082345EBCEE6EB614866D4118FD

v2.7.2

Fixed

• Fixed the Stage voice-channel filter getting stuck retrying indefinitely after a Discord update, which caused repeated warnings in the console.

• Fixed a case where blocking a Stage user wasn't reliably detected, which could let a blocked user still appear.

• Fixed blocked users' messages sometimes staying visible on slower-loading servers.

• Fixed notifications (sound, taskbar badge, and server unread indicator) firing when a non-blocked user replied to a blocked user's message.

SHA256: BE723295CF9C6E0D5893EB540F5988FD3B6889A71F79562D0A0E27356812EBFB

v2.7.1

Improvements

• Improved performance by reducing redundant cache and module processing.

• Improved Discord compatibility by making module recovery more efficient.

• Improved voice state handling by standardizing internal state tracking.

• Reduced the risk of Discord rate limits when loading blocked users across many unread channels by limiting concurrent message requests.

• Added better logging for Discord changes that may affect guild icon detection.

• Added a one-time startup check that warns if core hooks fail to initialize, making it easier to notice when Discord has changed something that affects the plugin.

• Replaced hardcoded numeric channel type checks (forum, thread, stage, voice, DM, group DM) with a single named CHANNEL_TYPES constant, so a future Discord enum change only needs to be fixed in one place instead of hunting down scattered magic numbers. No behavior change.

• Added a health check for the voice channel join/leave sound suppression, so the plugin can detect and automatically recover if a future Discord change silently breaks it, matching the coverage already in place for the other voice features.

• Improved voice sound state tracking to reset cleanly on plugin restart instead of carrying over stale channel data.

Fixes

• Fixed redundant processing during module refreshes.

• Fixed inconsistent internal state handling for voice users.

• Fixed a rare case where the taskbar/system tray badge could stay stuck at zero if Discord's relationship data never resolved.

• Fixed settings not saving if Discord was closed immediately after toggling an option.

• Fixed the blocked-message-group patch failing silently instead of logging when it ran out of retry attempts.

• Fixed the blocked-banner text detector not recognizing singular or gendered phrasing in German, Italian, Dutch, Russian, and French, or count-less phrasing in Japanese, Chinese (Simplified/Traditional), and Korean.

• Fixed the "user left call" sound still playing when a blocked user moved to a different voice channel instead of disconnecting entirely.

SHA256: 90132C9C3EBD6261C0ACD54DA58FB8543C09D0BD4CF2A91D3B170315BE9B994C

v2.7.0

Security

• Improved update verification with stricter download validation and trusted redirect handling.

Improvements

• Improved overall stability and reliability across internal systems.

• Reduced background resource usage when Discord is minimized or running in the background.

• Improved compatibility with recent Discord updates.

• Improved voice channel detection and synchronization.

• Improved reaction detection in edge cases.

• Improved consistency between automatic and manual update checks.

• Improved invite suggestion filtering reliability.

Fixes

• Fixed rare issues with voice channel joins failing unexpectedly.

• Fixed the fake voice timer remaining visible after disabling the plugin.

• Fixed blocked-user call muting using outdated settings after plugin restarts.

• Fixed various edge cases involving voice counters and blocked-user activity detection.

• Fixed reactors not being hidden correctly when display names matched other users.

• Fixed automatic reaction-tab switching relying on unreliable simulated clicks.

• Fixed settings toggles incorrectly prompting for a plugin reload when changes applied immediately.

• Fixed unsafe settings label handling in the settings panel.

• Fixed leftover call-ringing state after disabling ringing suppression.

• Fixed the guild events sidebar briefly displaying unfiltered event counts.

• Fixed scroll anchoring being disabled unnecessarily across all channels.

• Fixed screen readers announcing incorrect event counts and duplicated reaction counts.

• Fixed unnecessary update checks when automatic startup checks were disabled.

• Fixed group DM hiding in the unread sidebar using fragile internal styling selectors.

New

• Added an option to disable automatic tab switching and popup closing when all reactions belong to blocked users.

SHA256: 4892AA923D01EFA149A31524391CECD72526A1DCD47DBFD4002F6FA9A019C03E

v2.6.4

Fixes

• Fixed a rare case where ByeBlocked could incorrectly assume a message had no reactions and hide it when it shouldn't.

• Improved how ByeBlocked removes custom voice channel statuses from blocked users. If the primary method fails, the plugin now automatically falls back to an alternative approach.

• Improved how ByeBlocked identifies voice call interface components, reducing the chance of visual issues after Discord updates.

• Improved the internal handling of voice channel activity updates (games, apps, and other activities), helping prevent edge-case conflicts.

• Removed compatibility with the Probe plugin, which is no longer maintained.

• Removed an unused legacy function and reduced unnecessary processing while navigating forums and threads, resulting in a small performance improvement.

Recommendation

If you notice anything unusual after updating, simply reload Discord (Ctrl + R) to refresh the client.

SHA256: 44934924CE52BB07938BD9C33E3DD40486BA4AAF40AB18B6F6A92BDF805343F0

v2.6.3

Fixed

Notification Badges and Audio: Resolved a regression from version 2.6.2 where a temporary boot-time patch remained active permanently. This was causing notification badges and audio alerts to be incorrectly suppressed for non-blocked servers and DMs. Both badges and audio now respect native Discord behavior and function properly again.

sha256: d7c5730bc21cffb887f2c6c3ec2c4fef13334c06b7be6cf67af980151dd80212

v2.6.2

Fixed

• Persistent blocked-user notification badges on startup: Resolved an issue where unread messages sent by blocked users while Discord was closed caused red notification badges to remain visible on both the Windows taskbar and inside Discord upon launching. These badges would stay visible until the server was manually marked as read. Now, they automatically disappear right after Discord finishes loading.

Warning

Brief badge flash on cold start: You may still notice a brief flash of the red notification badge when opening the app. This happens >because Discord's native badge call can fire before BetterDiscord finishes loading plugins. However, the badge will now automatically >clear itself within a second once the plugin resolves the blocked channels, instead of remaining visible.

sha256: 4606a8428781cb464ee7e3bae818e28a2c5c0ee050b5a1ebd50793687231185a