Repeated messages only pinned once
Closed this issue · 3 comments
Describe the bug
If a pinned message has the same [time], [username] and [message] as one of the previous messages, it won't be pinned again. For example, sending "1" at 03:01:30 will be pinned as
03:01 [Username] 1
Sending "1" again at 03:01:45 won't be pinned because the [time] (only hours and minutes matter), [username] and [message] are the same.
However, sending "1" at 03:02:15 will be pinned as
03:02 [Username] 1
since the [time] is different.
Steps to reproduce
- Go to 'BetterTTV Settings' > 'Chat Settings'.
- Configure the following settings:
- Highlight Keywords:
- Type: Username
- Keyword: [Your username]
- Pinned Highlights:
- Pin your highlighted messages above chat: Enable
- Highlight Feedback (Optional):
- Play a sound for messages directed at you: Enable
- Send a message (e.g., "1") at a specific time (e.g., 03:01:30). The message pins as expected.
- Send the same message again within the same minute (e.g., 03:01:45). It does not pin.
- Send the same message in the next minute (e.g., 03:02:15). The message pins.
Expected behavior
Every message should be pinned.
Screenshots
2.mp4
Device information
- OS: Windows 10 Pro x64 (21H2, build 19044)
- Browser: Chrome, Version 126.0.6478.62 (Official Build) (64-bit)
BetterTTV Version
7.6.5
Additional information
1.This bug was also present in version 7.6.4.
2. This issue likely also affects keywords of types "Message" and "Badge," but I can't check this due to bug #6895.
3. This occurs not only with your messages but also with messages from other users.
Version Check
- I have checked that I'm using the newest version of BetterTTV available.
This is working as intended to prevent spammy pinned messages. The goal of pinning messages is to retain a message when you step away. Multiple messages in an ongoing conversation would still be highlighted, but not pinned.
Thank you for the clarification. I understand the intended functionality now.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related issues or feature requests.