Releases: bdashore3/RoyalGuard
RoyalGuard v2.4.1
Hotfix release:
- I left a println!() statement when debugging reaction roles previously. This has been fixed and the debug logs should no longer have emoji spam.
RoyalGuard v2.4
Update dependencies:
- Serenity -> 0.10
- Tokio -> 1.0
The bot has been tested and verified to work. In addition, clippy has been ran to fix any code semantic issues.
RoyalGuard v2.3.1
Hotfix for TLS error (Issue #20).
Rustls does not play nice with typed IP addresses due to a webpki issue, so use native-tls for the time being.
RoyalGuard v2.3
Release v2.3:
- Updated serenity and all dependencies to their latest compatible versions
(Note: tokio 0.3 doesn't work with serenity due to higher-up dependencies also not being compatible) - Changed the
welcome roles
subcommand toautoroles
. This makes it more intuitive for users to actually work
with this command.
Please let me know in regards to any bugs in the issues tab!
RoyalGuard v2.2.1
Reaction role hotfix:
Some unicode emojis have > 1 character, so instead of checking if the emoji exists, we check if the reaction goes through. This brought some errors in terms of handling with the wizard. Therefore, the error handling was changed as well.
Help documentation has been updated to reflect the new command format
- rr new/remove: emoji and role id parameters have been switched
RoyalGuard v2.2
Feature release!
- Reaction roles can now add more than one role to a message's reaction!
- A leftover guild cleaner removes any inconsistencies between the database and the bot if the bot's offline and it's kicked from the guild
RoyalGuard v2.1.3
This release patches some errors that occurred within RoyalGuard's production instance.
- Don't error out when spawning the mute timer deletion task
- Add a filter on the reaction role wizard to check for the author and the channel
RoyalGuard v2.1.2
Update serenity to the latest git head and fix all breaking changes associated with that.
RoyalGuard v2.1.1 Hotfix
Fix a glaring issue where users can't ban/kick with an ID due to invalid permissions.
Also update serenity to the latest commit on github.
RoyalGuard v2.1
RoyalGuard has undergone some changes that patch security and permissions
- Update resetprefix and other administrator commands to use the dispatch error variant
- Update serenity to the github version due to dispatch error fixes
- The bot is also updated to the MPL license. This means that any forks HAVE to have a source and the MPL license within the bot!
Enjoy!