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.

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.