You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within #get-help, it'd be useful if the bot could apply ✅ to a thread if that reaction has already been added by a user. In the thread list view, Discord only shows the most used reaction for a thread and in a tiebreaker, it seems to go with the first applied reaction. When the thread is created, the bot applies a track reaction if detected so if the user adds the checkmark reaction, the track reaction is shown first because both have been applied once. So if the bot seconds a checkmark, that should break the tie and show the checkmark, not the track reaction. Of course if someone seconds the track reaction, it'd still be a tie if the bot seconds the checkmark, but that doesn't appear very common in recent threads.
The simpler option might be to have the bot prefix "[SOLVED]: " to the thread title if the checkmark is detected. That'd be less fragile.
The text was updated successfully, but these errors were encountered:
Within #get-help, it'd be useful if the bot could apply ✅ to a thread if that reaction has already been added by a user. In the thread list view, Discord only shows the most used reaction for a thread and in a tiebreaker, it seems to go with the first applied reaction. When the thread is created, the bot applies a track reaction if detected so if the user adds the checkmark reaction, the track reaction is shown first because both have been applied once. So if the bot seconds a checkmark, that should break the tie and show the checkmark, not the track reaction. Of course if someone seconds the track reaction, it'd still be a tie if the bot seconds the checkmark, but that doesn't appear very common in recent threads.
The simpler option might be to have the bot prefix "[SOLVED]: " to the thread title if the checkmark is detected. That'd be less fragile.
The text was updated successfully, but these errors were encountered: