Releases: CyaOnDaNet/plex_discord_role_management
Releases · CyaOnDaNet/plex_discord_role_management
v2.0.2
v2.0.1
Minor Bug Fixes
- Fixed an error caused by attempting to manipulate a discord user that left the server
- Fixed an error caused from processing a deleted role in list embed
v2.0.0
New Features:
- Added Recently Added Notifications. Use command
!bot recentlyadded off
to disable it - Added tvdb link to notifications show react role pages
- The
!notifications preview
list now expires after 5 minutes to make it more clear that it is a temporary command - Bot now deletes old
!notifications list
messages on new call - The
!notifications list
command now preserves people's settings from the old list until they become active on the new list - The
!users
command now states the number of users in the embed message - Created a version changelog notifier
- Database is backed up on shutdown and startup to allow for version saving between bot upgrades
- Database is automatically backed up every 8 hours and kept for up to 7 days
- Custom React Role Page can now be edited without recalling
!notifications list
Changes:
- Discord.js v12 refactor
- Reworked react role events to work better with Discord.js v12 (Because of occasional emoji error)
- Split up notifications command, index.js, and database setup into multiple files for easier editing later
- Changed setActivity to toggle between help command, number of people watching plex, and the bot version. Changes every 10 seconds
- Improved Tautulli error handling
- Notifier re-work. All channel related settings were moved to the
!notifiy
command
Fixes:
- Fixed double watching log notifications (Update - Might Not Be Completely Fixed)
- Fixed show notifications resulting in null role if networks not enabled
- Fixed alphabetical order being inaccurate with grouped shows
- (Untested) Implemented a theoretical fix for discord outages crashing the bot
- Fixed unintended bug causing errors during unenroll from react list
- Fixed a role react bug where an emoji click during list creation would break the new list from generating
Support for up to 3 Sonarr Instances
- Up to 3 Sonarr instances can be included now
- Added Tautulli re-connection attempt on startup (for example, if bot starts before Tautulli is ready during a system reboot)
- Improved Tautulli error logging
- Added debugging as config value
- Bug Fix: Handles a person in the database that has left the server instead of throwing an error and misbehaving
Bug Fixes
- Accounted for Discord Embed Filed Count Limitations in
!linklist
command - Accounted for Discord Embed Description Character Count Limitations in
!users
and!showlist
commands
Added !notification preview
- Fixed bug where previousNotifierList could cause errors after
!delete
so it was changed to clear the previousNotifierList database on!delete
as well. - Added
!notification preview
which is nearly the same as!notification list
except the embeds are not stored in the database as to not unintentionally un-track the primary list.
New Delete Command. Improvements and Bug Fixes.
- Created
!delete
command to delete all Roles created by the bot - Added error handling in the even that Discord Role Limit is hit
- Fixed database calls to account for multiple discord servers
- Implemented React-Role check of last
!notification list
command - generateNotificationSettings() only fires once now to improve efficiency.
Webroot Changes
- Accounted for Sonarr or Tautulli webroot changes by allowing full root path to be specified in ip field and port field being left blank
Tautulli API Changes
- Discovered xml responses may be used instead of json, forced Tautulli to always return json.
- Created some sql tables to be used for the future.
Added version to bot info, bug fixes and improvements.
- Fixed sonarr connection bug introduced in v1.1.3
- Fixed proper tracking of watching role in database
- Changed the way unlink handles non tracked users
- Made it so client ID changes would not cause duplicate messages
- Made some link command quality of life changes
- Changed it so only valid Plex usernames can be linked
- Fixed cron job issue firing more than intended