4.2.0 // Show context in admin notifications, bug fixes, dev API, new Chat Executor features, & more
ChatSentry
Update 4.2.0
Improvements
- Admin Notifier messages can now display the context in which the notification is related to with {CONTEXT}. All the notification messages use this starting format: "&7(&b{VIOLATION_TYPE}&8 - &b{CONTEXT}&7)" - ex. "(Link or Ad Block - Sign)". In order to make use of this placeholder you will need to manually add it to your notification messages in lang.yml, or delete the file and let the plugin regenerate a fresh one
- The plugin now has a developer api! See more here: https://wiki.chatsentry.xyz/api/about
- Updated the top level domain list utilized by the Link & Ad Blocker, now version 2021031101 (Updated Fri Mar 12)
- You can now use "{dont_notify}" in Chat Executor set-as nodes to not send any admin notifier message when matched (if admin notifications are enabled for the Chat Executor)
- You can now use "{dont_log}" in Chat Executor set-as nodes to not log anything the when the entry is triggered (if logging is enabled for the Chat Executor)
- Various code improvements and optimizations across the plugin
Fixes
- Fixed the plugin taking an increasingly longer amount of time to reload when reloading within similar timeframes. This issue was due to a part of the cache failing to dispose of its previous instance before recache thus continued to eat a growing amount of memory. Was only noticeable when reloading over and over as GC took care of it eventually
- Fixed the Link & Ad Blocker failing to block links with directories with only filter TLDS enabled
Updating Steps
- Delete ChatSentry-x.x.x.jar from your plugins folder.
- Place the new ChatSentry-4.2.0.jar in your plugins folder.
- Restart your server.
Join the Discord
You can gain access to the plugins discussion channel to chat with fellow ChatSentry users, get support, make suggestions, give feedback, and more related to the plugin!
Join the Discord server here:
https://discord.gg/m5Su7Af