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
Break was solely built as voluntarily picked role so there is no need to worry about potential abuse by people who are timed out. This issue only talks about Break, not Time Out for that reason.
More and more people are taking up on the offer of getting the Break role assigned, removing access to most channels. They later contact moderators to get it removed.
Idea
Implement a !break command that works everywhere. It prompts the user whether they are sure they want the Break role and when confirmed assigns the tag. When the user wants it removed, they can send YesBot a DM and an additional option is included in the DM menu that, when clicked, removes the Break role.
Usage
!break
!menu # in DMs with YesBot, then click the respective icon
Thoughts
Is there any reason to save these things in a database? The only thing that comes to mind is the 24 hour limit which was set to prevent people from asking for a Break for 20 minutes. If we can expect sensible use of the command, we can get away with not saving the time. If we can't, we have to to prevent API restrictions because of the flood of channel permission changes the role causes.
If we do need a database, it might be worth thinking about adding mod only variants of the command !break @user and !break remove @user to properly modify the database when handing out the role.
The text was updated successfully, but these errors were encountered:
Break was solely built as voluntarily picked role so there is no need to worry about potential abuse by people who are timed out. This issue only talks about Break, not Time Out for that reason.
More and more people are taking up on the offer of getting the Break role assigned, removing access to most channels. They later contact moderators to get it removed.
Idea
Implement a
!break
command that works everywhere. It prompts the user whether they are sure they want the Break role and when confirmed assigns the tag. When the user wants it removed, they can send YesBot a DM and an additional option is included in the DM menu that, when clicked, removes the Break role.Usage
Thoughts
!break @user
and!break remove @user
to properly modify the database when handing out the role.The text was updated successfully, but these errors were encountered: