(Bug) Hidden channels plugin causes servers to be marked as not read even though all channels are marked as read

[Adamillo]

trafficstars

The workaround for this bug is by muting the hidden channels, but that's not very ideal

[JustOptimize]

It's a known bug. I already plan to fix it (see readme)

[Serega007RU]

Please take this issue as a priority, it is impossible to use discord when you have phantom notifications. Adding functions and settings to this plugin does not look so useful compared to fixing this problem

[JustOptimize]

Please take this issue as a priority, it is impossible to use discord when you have phantom notifications. Adding functions and settings to this plugin does not look so useful compared to fixing this problem

It's a slow and painful process, I've been working on it for weeks but the only problem is that it's probably just wasted time not actually knowing what I'm doing

[GoldenChrysus]

It looks like there might be two stores that control unread statuses: one for the guild (server) and one for each channel.

The line const UnreadStore = WebpackModules.getByProps("isForumPostUnread"); seems to return the store controlling each channel's unread state (e.g. if you just set the hasUnread patch to always return true, all your channels will light up as unread, but the servers won't necessarily be marked unread).

If I do const SomeStore = WebpackModules.getByProps("hasUnread"); I get a different store than the one above, and this one seems to control server unread statuses (e.g. add a patch for hasUnread that returns true and all your servers will be marked as unread).

I'm unsure if there's some mechanism (e.g. other module) that coordinates/controls both of these states, but otherwise these stores might need to be used in tandem to determine if the server as a whole is unread based on the presence of non-hidden unread channels.

---

Unrelated to the above as it's potentially a different approach. Of course, removing/commenting the existing has...Unread patches (specifically hasUnread itself) seems to resolve the issue, but potentially creates other issues like the hidden channels being marked as unread. However, I noticed in the hasUnread patch that res was true for a non-hidden, muted channel. Perhaps there is some check that needs to be done to see if a channel is muted, though I'm unsure why the previous hasUnread logic (pre-patch) would be returning true for a muted channel. However, that muted channel is currently in a server that is permanently flagged as unread in my Discord due to this issue.

[JustOptimize]

It seems like i can't read, I'm checking rn, thanks for the suggestion

[JustOptimize]

In the latest version i added this setting so you people can mark as read manually

I will still work on a fix, don't worry guys

[JustOptimize]

This was fixed with v0.0.7