v4Guard Connector v3.1.1

What's Changed

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.

v4Guard Connector v3.1.0

What's Changed

This version fixes a few specific scenarios that might be caused by 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 requires at least Java 17 to run (We recommend a minimum of Java 21). Please avoid using obsolete Java versions!

The support from the old versions (2.5.0 and older) will be dropped on 31 of October. So please, update accordingly. And if you have issues, please contact us.

Full Changelog: v3.0.0...v3.1.0

v4Guard Plugin Connector v3.0.0

What's Changed

This version features a lot of requested features from from our feedback forum over at Discord.

We have mainly:

• Exposed part of our plugin methods via an API. This was necessary for the long term, for a better maintainability for our (future) sister addons. Including parts of the settings, the communication, and custom events.

1. This can be asked upon request if needed for your custom plugins! We will evaluate our request and see if it feasible.

• Added the ability to override the hostname and the folder name. This is necessary for elastic instances (k3s or docker environments). Allowing a better identification on the panel. You can take advantage of this via the corresponding system properties:

-Dio.v4guard.connector.name
-Dio.v4guard.connector.hostname

• Implemented in-game commands for whitelist and blacklist. Only for our @Enterprise Customers.
  This allows for staffs members (suggested high staff members), to directly benefit from the local blacklist and whitelist of users.

v4guard.command.whitelist - /v4guard whitelist <add/remove> <username>
v4guard.command.blacklist - /v4guard blacklist <add> <username> [-p (propagate) -s (silent) -i (ban the ip of the user)]
                                               <remove> <code> 

1. This uses the underlying API, so it is the same as using the API on your own implementation. And at this time, we are not consuming the executor field (that was requested on the forum). This will be done later on the following days, so you can update your implementations. Thank you for your patience.

2. We have dropped the support on our main Connector to detect if the user's game profile comes from a online (Mojang) session, as we were having circular dependencies between our main connector and Account Shield.

3. The support for the old versions with be dropped at October 30, 2025. So please, update!

Full Changelog: v2.5.0...v3.0.0

v4Guard Plugin Connector v2.5.0

In this release, we have resolved several issues previously affecting our Connector.

Our efforts were primarily focused on the following areas:

• Major code refactor: Achieved a more modular and scalable system, including replacing the previous implementation with Jackson.
• 1.20.2+ compatibility: As the need to validate the protocol state becauses of the config phase in our async state.
• Removed Account Shield logic: In favour of handling all the logic over our sister addon.

Please note: This update introduces significant breaking changes. The packaging structure has been updated, meaning older versions of Account Shield are not compatible. Additionally, if your system depends on one of our events, ensure your codebase is updated accordingly.

Full Changelog

For a detailed list of changes, please refer to: v2.0.0...v2.5.0

v4Guard Plugin Connector v2.0.0

What's Changed

• Complete codebase rewrite: Thanks to the dedicated efforts of @f4n74z14, the entire codebase has received an important rewrite. This major revision has significantly improved the overall quality of the code.
• Some additional checks have been added: New checks have been incorporated to enhance the plugin's capabilities.
• Added bedrock support: A notable addition to this release is the introduction of support for bedrock players. Now, the plugin can effectively detect and mitigate malicious players accessing from bedrock clients, some known issues with bedrock clients were known.
• Improved cache system: The cache system has been refined and improved, contributing to better performance and efficiency.
• General bug-fixes: Several bugs have been addressed and resolved, leading to a more stable version.

Contributors

• @f4n74z14 has made its first contribution in #25. We really appreciate your work!
• @zHackeed has also contributed to fine-tuning the final details of this release. Appreciated!

Full Changelog

For a detailed list of changes, please refer to: v1.1.4c...v2.0.0

v4Guard Plugin Connector v1.1.4c

What's Changed

• Cleanup: Code reorganization
• Fix: Changes in event priorities + missing line from last commit
• Fix: Reject check if the player is already logged in

Full Changelog: v1.1.4b...v1.1.4c

v4Guard Plugin Connector v1.1.4b

What's Changed

• fix: incorrect imports by @samfces in #22
• perf: cache player after sending client brand to backend && fixes by @zHackeed in #23
• Fix CME when listening to Minecraft client branding by @eugeniodevv in #24

New Contributors

• @zHackeed made their first contribution in #23
• @eugeniodevv made their first contribution in #24

Full Changelog: v1.1.4...v1.1.4b

v4Guard Plugin Connector v1.1.4

This release adds new privacy options and new ways of detecting fraudulent clients. In addition to this, support for Spigot has been definitely removed.

Changes

• Added a new privacy option to anonymize subdomains.
• Spigot support has been dropped.
• Client brands can now be collected from the client (with option to disable it).
• Added a permission to activate/deactivate account shield detection.
• Small optimizations and tweaks have been made in the code. Thanks to @xism4 and @f4n74z14
• [HOTFIX] Incorrect imports solved.
• [HOTFIX 03/01/2023] Fixed a bug where players who are already logged in were kicked.
• [HOTFIX 21/01/2023] Several MC Brand fixes and cleanups had been made.

What's Changed

• Reduce redundancy & improve verification in #18
• v4Guard Plugin v1.1.4 in #21

Full Changelog: v1.1.3c...v1.1.4

v4Guard Plugin Connector v1.1.3c

In this release small bugs have been eliminated and, in addition, support for a new feature has been included.

Additions

• Added support for v4Guard Account Shield.

Changes

• Fixed an issue related to the JSON document parsing.
• Removed innecesary data from location packet.

What's Changed

• v4Guard Plugin v1.1.3c in #17

Full Changelog: v1.1.3b...v1.1.3c

v4Guard Plugin Connector v1.1.3b

his minor release adds support for the new protection feature: v4Guard Account Shield.

Additions

• Added support for v4Guard Accound Shield

What's Changed

• v4Guard Plugin v1.1.3b in #14 and #15

Full Changelog: v1.1.3...v1.1.3b