Added Functionality to Require Mod Reasons #6477
Open
+90
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
Category: Cogs - Mod
Flame442
added
the
Type: Enhancement
|
It would probably be faster to read the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the changes
This PR adds an option to classify reason in moderation actions as required. Users are able to use
!modset requirereason trueto specify if a reason is required for running any moderation action. It adds the requirement to all moderation commands includingban,kick,massban,tempban,softban,voicekick,voiceunban,voiceban, andunban. If a user runs a mod command when the reason setting is enabled but doesn't include a reason, the bot reasons by telling the user that a reason is required.Closes #6105
Have the changes in this PR been tested?
Yes, I manually tested my changes by running each moderation command with and without the requirement. The bot successfully executed the command when a reason is provided and rejects the command if a reason isn't provided when reasons are required.