Skip to content

v2.7.4

Choose a tag to compare

View all tags
@8ug8ird 8ug8ird released this 31 Aug 08:39
· 2 commits to main since this release
V2.7.4
ed75e42
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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
Assets 3
Loading