Skip to content

Conversation

@iamshoXy
Copy link
Contributor

This pull request adds two new commands:

  • enable
  • disable [reason]

When the bot is disabled, no more tickets can be created and the following message appears: "ModMail is currently disabled in {guild.name}. Reason: {reason}".
The reason for disabling is optional and the default reason is "No reason specified.".

When disabling the status column is set from None to the reason. If no reason is specified, it remains an empty string. As soon as the bot is enabled again, the field is set to None again.

@chamburr chamburr linked an issue Feb 18, 2023 that may be closed by this pull request
@chamburr
Copy link
Owner

Thanks for your interest in contributing. A few major things regarding this pull request:

  • For consistency, prefer a single command that toggles between on and off.
  • Format of the bot response message when ModMail is disabled should match the ticket closed message.
  • Database migration is missing.
  • Command documentation on the web is also missing.

@iamshoXy
Copy link
Contributor Author

Thank you for the feedback. Is a reason necessary or can I remove it?

@chamburr
Copy link
Owner

I think reason is rather useful for admins to provide the users with relevant information, for example, regarding why ModMail is disabled and how they could contact staff in the meantime.

@iamshoXy
Copy link
Contributor Author

  1. The command is now toggle and accepts a reason as before.
  2. The embed formatting is now similar to the others.
  3. Database migration added
  4. Documentation added

@chamburr chamburr merged commit b983fc3 into chamburr:master Mar 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Disable ModMail in a server

2 participants