Introducing the Enhanced ActionBar Statistics!

We are excited to announce the launch of an upgraded ActionBar statistics system, now providing detailed, real-time insights tailored to each specific attack type. Every notification includes key metrics such as:

• Bots last second — the number of bots detected in the last second;
• Pings last second — the number of pings detected in the last second;
• Connections — the total number of connections;
• Pings — the total number of pings.
  
• Firewalled — the number of blocked IP addresses;
• Packets blocked — the number of malformed packets blocked by BotShield;

Depending on the attack type, you will receive customized and informative notifications that enable prompt monitoring and well-informed decision-making. This unique, attack-specific notification system is exclusive to our anti-bot solution and is not available in any other product on the market.

A new notification feature has been added to inform you about the number of malformed packets detected and blocked by BotShield on your network. You can configure the threshold for the minimum number of blocked malformed packets per second required to trigger a notification via the console.

Fixed:

• Various bug fixes related to the iteration process.
• Resolved an issue where enabling ping protection while another attack type, such as connection protection, was active caused the previously enabled protection to be disabled instead of allowing a combined multi-attack protection mode. Now, both protections can operate simultaneously without interfering with each other.

We highly recommend installing this update as it includes valuable enhancements that, while not critical, significantly improve functionality.

Added:

• Introducing a new module for the Filter component, enabling manual addition of messages to be filtered by BotShield through the configuration settings.
• Minor code adjustments.

Added:

• Recorded an engaging trailer showcasing BotShield protection; please see it below.

Fixed:

• Minor issue related to the plugin's startup message — a missing space before the text.

Added & Improved:

• Listener Priorities: Changed priorities in the plugin’s listeners for more efficient event handling.
• Performance Optimization: Recoded check methods by changing return type from void to boolean, resulting in improved performance.
• Enhanced Logging: Added more detailed log messages when the Ratelimiter component detects anomalies in connections.
• Code Readability: Further improved code readability to facilitate easier development.
• Watcher Module Update: Added an "Advanced" module to the Watcher, allowing management of consistent verification and strict mode.
• Proxy Loading Optimization: Fully optimized the task that loads proxies from the Proxy component.
• Attack Detection Logic: Recoded parts of the logic responsible for detecting attack status to increase accuracy.
• Expanded Attack Section: Added new attack types: LISTENING, LOCKDOWN, STARTUP, CONNECTIONS, PINGS, and COMBINED types.
• Placeholder Update: Changed the {module} placeholder to {component} for better clarity and consistency.
• Bug Fixes: Fixed various bugs related to the Inspector and Watcher components.
• Bot Nicknames: Added more bot nicknames to the default configuration.
• Country Component Update: Added Bangladesh, Thailand, Pakistan, and the Philippines to the default Country component configuration.
• FirstJoin Module: Added a "reset" option that automatically clears players’ cache at regular intervals defined in the configuration.
• Message Redesign: Completely redesigned all messages to improve clarity for players.
• New Placeholders:

1. {0} — displays the current plugin version in statistics messages.
2. {5} — shows the size of the queued IP addresses.
3. {6} — shows the number of IP addresses currently under verification.
4. {7} — displays the network status from the attack section.

• Lockdown Enhancement: Lockdown mode is now more advanced. If lockdown ends earlier than other attack types, those other types continue protecting the network. No other anti-bot solution in the world has a lockdown like this — this is BotShield, baby!
• Inspector Trigger: Added a trigger in the Inspector: if the Watcher detects incorrect verification behavior multiple times (e.g., five times), the player is automatically placed in the firewall.
• Filter Component Updates: Added messages for IOException and SocketException exceptions, as these can cause network instability.
• Notification Actionbar: Added an amazing notification actionbar featuring a wealth of cool statistics. It can be toggled on or off using the command /botshield notifications [on/off] and requires the permission botshield.notifications.

WARNING:

• It is highly recommended to use this version of BotShield, as it maximizes plugin performance.
• All provided components and modules have been thoroughly tested in this update.
• The entire codebase has been recoded — everything now works perfectly.
• Install this update ASAP, as it includes critical enhancements.
• Reset your configuration after updating, since some settings have changed.

Hello there! Over the past few weeks, we have undertaken a significant and challenging task. We have completely recoded the plugin's codebase and structure. Our efforts have not only enhanced stability, security, components and modules, but we are also excited to announce VELOCITY SUPPORT! Now you can easily use BotShield on your Velocity network.

Developing for Velocity is no small feat, especially when coding complex plugins like BotShield, but we have successfully navigated these challenges.

Key Updates:

• NOW BOTSHIELD SUPPORTS VELOCITY PROXY!
• We are proud to announce that we have improved the stability, performance, protection, and codebase of BotShield by over 300%!

Performance Enhancements:

• BotShield no longer loads components "dynamically" in the previous manner. Instead, components will now load using a more efficient method in the current update and future updates, significantly improving performance. This change was a crucial step in our development process.

New Features:

• Expanded Filter Component: More than 20 additional messages have been added to the Filter component.
• Configuration Flexibility: You can now change the statuses of the under-attack mode in the configuration within the messages section.
• Inspector Improvements: The Inspector has been enhanced for better functionality.
• BungeeCord Compatibility: Fixed an issue where the Filter component did not work on BungeeCord.
• Rewritten Filter Component: The Filter component has been recoded from scratch, improving stability and performance.
• Alerts Module Update: The alerts module has been removed from the Filter component and is now a separate module.
• Bug Fixes: Resolved a bug where the "was blocked" message would double in certain situations.
• CraftBukkit Compatibility: BotShield is no longer compatible with CraftBukkit. To protect your gaming server, you must use Paper or its forks.
• Updated Alert Conditions: The conditions for the "attack-information" alert have been revised.
• Java Version Requirement: The minimum Java version required for BotShield is now 17.
• Command Argument Checks: Added conditions for deeper checks of arguments when using the main plugin's command.
• Verification Message Removal: The "has to pass the verification" message has been removed when an attack is detected.
• Consistent Verification Tasks: Bots must now pass verification tasks consistently! This new technology guarantees unparalleled protection—no other anti-bot solution on the market offers this level of security!

Fixed Issues:

• Resolved issues with the blacklisted nicknames module.
• Fixed the "attack-information" messages not being sent when lockdown was enabled.
• Corrected attempts displaying when strict mode is enabled.
• Fixed bugs related to FirstJoin and Inspector interactions.
• Resolved a bug with the queue system.

Thank you for your continued support, and we look forward to providing you with even more updates in the future!

Added:

• Streamlined performance by removing unnecessary checks.
• Introduced the /botshield check [IP] command, allowing players to verify their IPs against either the cloud or a manual database.
• Adjusted certain configuration values for improved functionality.

Fixed:

• Resolved the issue of the "no-permission" message not displaying correctly in the latest Minecraft versions.
• Corrected bugs related to the "api-version" in the plugin.yml file affecting recent updates.
• Addressed various errors encountered in version 1.20+.
• Color display issues in the console for the most recent Minecraft versions.
• Implemented several fixes related to the Proxy component.
• Corrected issues with the /botshield firewall command when no arguments were provided by the sender.

Added:

• Our log filter now excludes "read timed out..." and "ServerConnector..." messages on BungeeCord networks.
• The Cloud module has been relocated to the Proxy component to enhance performance.
• The proxy component has been completely rewritten, and log messages (including cloud logs) have been updated. Now, BotShield consumes 0% of CPU and RAM during database downloads.

Fixed:

• Several issues with the /botshield command have been resolved.

Added:

• We are thrilled to announce the successful development of the CHAT component, which already includes two additional modules: SPAM and REGISTER. This component is now capable of blocking advertising bots and bots that use identical passwords, significantly enhancing chat security and user experience.
• The latency component now autonomously calculates the player's ping using advanced algorithms, ensuring more accurate and dynamic measurements. Furthermore, the log messages generated by this component have been enhanced for clarity and improved monitoring.
• An "api-version" string has been included in the plugin.yml for better version tracking.
• Certain configuration values have been updated to enhance functionality.
• Several methods have been refined and recoded to boost overall performance.
• The class that manages the functionality of the plugin commands has undergone a complete rewrite.

Fixed:

• Addressed false positives associated with the IPLimit component by implementing a more effective detection method.
• Resolved issues within the Whitelist section of the Firewall component to ensure smoother operation.

Added:

• "Nicknames" component has been renamed to "Nickname".
• The configuration for the pattern module in the Nickname component now includes a Regex string.
• The Startup mode in the Inspector component has been modified due to incompatibility with other components.
• Lockdown mode has been updated to activate only when the specified number of connections in the configuration matches the current connections during attack mode. This approach enhances security by ensuring that the system is only locked down under specific conditions, making it more effective.
• We have added a new module to the Inspector component called FirstJoin. This module automatically detects if a player is joining for the first time and, if so, kicks them immediately. This helps to effectively identify and prevent slow bot attacks by monitoring new player connections.
• The enabling and disabling of the Startup mode in the configuration has been reworked for improved functionality.
• The nickname length module has been implemented, requiring nicknames to be between 4 and 16 characters long. This setting can be customized in the configuration for greater flexibility.

Fixed:

• Resolved the conflict between the Inspector and Lockdown components.
• Fixed the update availability check module.

Added:

• Some parts of the Watcher component code have been modified for easier verification.
• We have successfully integrated a new function for the Watcher component called Strict mode. This function is disabled in the default configuration, but you can enable it if necessary.
• A second behavioral analysis layout for Strict mode has been added to the configuration, which needs to be used when this mode is enabled.

Fixed:

• The issue of duplicate messages regarding IP address blocking when using IPTables has been resolved.

WE ARE BACK WITH A BANG! INTRODUCING THE HUGE UPDATE!

Enhancements:

• Comprehensive Watcher Update: The Watcher component now boasts two additional layers of protection, allowing for even more meticulous monitoring of player behavior.
• Improved Detection Systems: With the introduction of new Watcher functions, our non-signature VPN and PROXY detection systems have been significantly enhanced.
• Expanded Nickname Blacklist: The default configuration for bots now includes a broader array of nicknames for the blacklist.
• Nickname Pattern Check: A new pattern-checking feature has been implemented for the nickname component.
• Smart Log Filtering: Our intelligent log filter now excludes InitialHandler messages, which are associated with a specific type of exploit.
• Automated IP Blocking: We now utilize IPSet for blocking IP addresses, eliminating the need for manual configuration—this will be set up automatically.
• Enhanced Debugging Information: Additional details have been incorporated into debug messages for improved clarity.
• Whitelist Management: If a player on the whitelist is detected for issues such as IPLimit, they will be promptly removed from the whitelist.
• Revamped Watcher Component: The Watcher has been recoded for enhanced performance and intelligence, featuring new algorithms for superior bot identification.
• Updated Default Messages: The default messages in the configuration have been revised for better communication.
• Optimized IP Download Speed: The speed of downloading IP addresses from the Cloud has been adjusted to accommodate servers with lower capabilities (you can configure it in the configuration).
• Resource Protection: To safeguard your server's resources, BotShield will now only add non-existing IP addresses to the database.
• Verification Symbol Display: A symbol indicating successful verification has been added to the configuration.
• Startup Mode Update: Now, if you want to disable startup mode completely, you can set the value to false.
• Improved RateLimiter Component: RateLimiter now works better than later, ping attack protection was improved.
• Additionally, we recorded a new video showcasing the latest version of our anti-bot — check it out here:

Fixes:

• Resolved Interrupted Exception during server shutdown.
• Corrected the display count for MitigatedIPs.
• Fixed issues with the IPLimit whitelist.
• Addressed the /botshield firewall add command, which previously kicked the sender.
• Recoded various sections of the code that were causing bugs.
• Fixed IP addresses did not unblock properly.

Important Notice: We urge you to install this update as soon as possible, as it includes critical enhancements to your protection system. We strongly advise against using older versions. Our dedicated efforts have significantly bolstered the protection framework for your servers, enhancing non-signature protection, IPTables integration (now automatically configured using IPSet), and the Watcher component, which plays a vital role in the verification process.
As always, BotShield remains the premier choice for the anti-bot protection!

Fixed:

• Interrupted Exception on server disabling.

Added:

• Now, the IP address that pings the server will be automatically blocked if it is in the Cloud or Proxy list.
• Now, the IP address that pings the server belongs to the specific country that is in the blacklist, it will be automatically blocked.
• All messages in the configuration have been changed.

These changes improve the protection system a lot. Connections that are suspicious will be automatically blocked if they try to reach the server.

Added:

• New advanced algorithms. Now the Inspector has an advanced component called Watcher that will check player's behavior. It can also stop players with VPN or PROXY using non-signature protection preventing systems.
• Strange player component has been renamed to Proxy.
• Blocked component has been renamed to Firewall.
• Ratelimiter component now works differently, using new algorithms to check players' connections.
• Players who previously tried to join the server when it was under attack must pass the verification anyway, even when the server is not under attack now.
• Some messages in the logs have been changed.
• More comments to the configuration.

Fixed:

• IPLimit does not work properly.
• IPLimit does not detect players with alt accounts if they passed the verification.
• The display of the number of pings in the statistics.
• The display of the kick messages from the components.

WARNING:

• You have to reset your previous config.yml before using this version.
  

Added:

• Updated cloud system protection. Now it works better than later.
• About 13 millions malicious IP addresses are now in our database.

Removed:

• Strange IPs placeholder is no longer accessible.

Added:

• We are glad to announce you that we have added a new component to our protection system. It is country component. So, now you can deny login from specific countries if you want (for example, we have blocked countries with the largest amount of botnets).
  
• Performance IPtables integration improvements.
• A new advanced check on player join (it was added for additional protection if the bots can pass the main one).
• A new advanced cloud system (we will often add malicious IP addresses there or at your request).

WARNING:

• You have to reset config.yml before using this version. Just delete the plugin folder and it will load new configuration automatically.