ВЕРСИИ (8)

This version fixes a critical cache logic issue on Velocity. The bug occurred in a specific scenario involving plugin event ordering. When a subsequent plugin denied the login event, our plugin incorrectly maintained a player/event reference due to improper disconnect reason validation. Note: This issue is only presented in our Velocity plugin, Bungeecord is not affected. Users are advised to upgrade to avoid Out of Memory crashes / issues on their proxies. This version requires at least Java 17 to run. We recommend using Java 21 or newer. Please avoid running on obsolete Java versions. Deprecation Notice: Support for versions 2.5.0 and older will be discontinued on October 31st. Please update to the latest version. If you encounter any issues during the upgrade, feel free to contact us.

This version fixes a critical cache logic issue on Velocity. The bug occurred in a specific scenario involving plugin event ordering. When a subsequent plugin denied the login event, our plugin incorrectly maintained a player/event reference due to improper disconnect reason validation. Note: This issue is only presented in our Velocity plugin, Bungeecord is not affected. Users are advised to upgrade to avoid Out of Memory crashes / issues on their proxies. This version requires at least Java 17 to run. We recommend using Java 21 or newer. Please avoid running on obsolete Java versions. Deprecation Notice: Support for versions 2.5.0 and older will be discontinued on October 31st. Please update to the latest version. If you encounter any issues during the upgrade, feel free to contact us.

This version fixes a few specific scenarios that might be caused on edge cases. We have fixed the following issues: - **Enforce case sensitive usernames.** This avoid a edge case with our protection stack that was detected and reported by a customer. - **Proper invalidation of expired checks.** This specific scenario can cause a memory leak if the backend was dropping your checks (for example, stability issues). And also, can be triggered by specific plugins that emulate logins. This was reported by a customer after their proxy crashed (while we were dropping his checks). - **Fallback timeout of pending kicks.** This can be triggered if the user had set an invalid connect-timeout on their config. For example, less than 3 seconds, meaning that our async logic would be non operational.

This version fixes a few specific scenarios that might be caused on edge cases. We have fixed the following issues: - **Enforce case sensitive usernames.** This avoid a edge case with our protection stack that was detected and reported by a customer. - **Proper invalidation of expired checks.** This specific scenario can cause a memory leak if the backend was dropping your checks (for example, stability issues). And also, can be triggered by specific plugins that emulate logins. This was reported by a customer after their proxy crashed (while we were dropping his checks). - **Fallback timeout of pending kicks.** This can be triggered if the user had set an invalid connect-timeout on their config. For example, less than 3 seconds, meaning that our async logic would be non operational.