Final v2.13.x release - ability to disable sent and blocked emoji

What's new?

Added the ability to disable the sent_emoji and blocked_emoji when a user messages modmail.

You can do this via ?config set sent_emoji disable

Fixed

The bot now handles having too many roles to show in the thread created embed.

Style Update

What's new?

Added image link in title in case discord fails to embed an image.

Implement account age

What's new?

• Introduced a new configuration variable account_age for setting a minimum account creation age.
  • Users blocked by this reason will be stored in blocked along with other reasons for being blocked.
  • account_age needs to be an ISO-8601 Duration Format (examples: P12DT3H 12 days and 3 hours, P3Y5M 3 years and 5 months PT4H14M999S 4 hours 14 minutes and 999 seconds). https://en.wikipedia.org/wiki/ISO_8601#Durations.
  • You can set account_age using config set account_age time where "time" can be a simple human readable time string or an ISO-8601 Duration Format string.

Changed

• block reason cannot start with System Message: as it is now reserved for internal user blocking.
• block, like close, now supports a block duration (temp blocking).

Bug Fix

Fixed

• Fixed an issue where status and activity do not work if they were modified wrongly in the database.
  • This was especially an issue for older Modmail users, as the old status configuration variable clashes with the new status variable.

Bug Fix

Fixed

• Fixed a bug where an error was raised when a message with received during a scheduled closure.

Bug Fix

Fixed

• A bug where a thread was blocked from sending messages when multiple images were uploaded, due to a typo.

changed

• Uses https://hasteb.in instead of https://hastebin.com for ?debug hastebin.

Stable Release

Added

• The ability to enable typing interactions.
  • If you want the bot to type in the thread channel if the user is also typing, add the config variable user_typing, the value doesn't matter, just it's the presence. use config del to disable the functionality. The same thing in reverse is also possible if you want the user to see the bot type when someone is typing in the thread channel add the mod_typing config variable.
• New status command, change the bot's status to online, idle, dnd, invisible, or offline.
  • To remove the status (change it back to default), use status clear.
  • This also introduces a new internal configuration variable: status. Possible values are online, idle, dnd, invisible, and offline.

Changed

• The internals for activity has drastically changed to accommodate the new status command.

Bug Fix

Fixed

• Fixed a bug in the contact command where the response message did not send.

Stable Release

Added

• You will no longer need to view your bot debug logs from Heroku. debug will show you the recent logs within 24h through a series of embeds.
  • If you don't mind your data (may or may not be limited to: user ID, guild ID, bot name) be on the internet, debug hastebin will upload a formatted logs file to https://hasteb.in.
  • debug clear will clear the locally cached logs.
  • Local logs are automatically cleared at least once every 27h for bots hosted on Heroku.

Fixed

• Will no longer show Unclosed client session and Task was destroyed but it is pending! when the bot terminates.
• thread.create is now synchronous so that the first message sent can be queued to be sent as soon as a thread is created.
  • This fixes a problem where if multiple messages are sent in quick succession, the first message sent (which triggers the thread creation) is not sent in order.
• Trying to reply to someone who has DMs disabled or has blocked the bot is now handled and the bot will send a message saying so.

Changed

• print is replaced by logging.
  • New environment variable introduced: LOG_LEVEL.
  • This influences the number of messages received in Heroku logs.
  • Possible options, from least to most severe, are: INFO, DEBUG, WARNING, ERROR, CRITICAL.
  • In most cases, you can ignore this change.
• on_error and CommandNotFound are now logged.

Stable Release

Changed

• ?contact no longer raise a silent error in Heroku logs when the recipient is a bot. Now Modmail responds with an error message.