v1.1.15

• Fixes an issue where Posts with attachments of certain filetypes failed to send (#134)

Note

To receive updates for v1.1.x, you will need to manually upgrade the bot.

v1.2.4-patch

• Fixes upgrades failing due to missing upgrader.json file

v1.2.4

• Reply-to-Target (RTT) implementation
  • This feature is enabled by default. To turn it off, set enable_rtt to false in config.json.
• Added u!fullban to ban the worst of the worst
  • This will ban the user from interacting with the bot entirely. This includes bot commands.
• Reports will now create a thread for moderator discussion
• System Manager checks plugins/system.json instead of update.json to verify download
• Reactions now use on_raw_reaction_add/remove events to support uncached messages
• Deprecated allow_prs in favor of allow_posts
• Managing plugins is now blocked when a restart is required
• Components will always be empty for system messages
• Fixed incorrect user warning embed color

v1.2.3

• Added new content_processing and content_protection services to Plugins
• Embeds now use a default color, can be customized in config.json
• Moved invite and phishing filters to RaidGuard plugin
• u!badge can now be used on other users
• New u!trust command to "verify" users
• Optimized managing messages (edit/delete)
• Some QoL changes and bug fixes

v1.2.2-patch2

• Moved a prank command to a plugin instead

v1.2.2-patch

• Fixes incorrect standing calculation

v1.2.2

• Warnings and bans are now logged.
  • Users will be able to run u!standing to view their account standing. Recent sanctions will impact their standing more.
  • This does NOT affect any bans placed on users prior to this update.
• spy.pet and its newer domains have been blocked in RapidPhish.
• Filetypes can now be unrestricted by setting safe_filetypes to false in config.json.
• Cache backups can now be done periodically by setting periodic_backup to a positive value (seconds).
• Fixed a bug where hosts could not use u!system due to hard-coded IDs.

v1.2.1

• System Manager now uses tags corresponding to version rather than branch
• Cross server reactions
• Fix #95

Note

Some users may have received this update as part of v1.2.0-patch2, as System Manager and Upgrader will download changes from the main branch rather than the version's tag. This should not happen for future versions.

v1.1.14

• Fix #95
• Re-released because target branch was set to main and not v1.1.x

Note

To receive updates for v1.1.x, you will need to manually upgrade the bot.

v1.2.0-patch2

• System Manager will now install dependencies specified in plugin.json