7.1.2-driverfix

Fixed java.sql.SQLException: No suitable driver error on Waterfall (SQLite) and Velocity (SQLite and MySQL) are now fixed.
This time i actually tested all possible combinations and no more hotfixes should be needed.

No need to update if you don't have this error.

7.1.2 (Hotfix release)

📜 Changelog

• Fixed errors with the database connection.
• EpicGuard is built with JDK 17, but because some hosts are still on Java 16, i added the compatibility to run the plugin on Java 16. This is a temporary fix, because with the release of Minecraft 1.18, all hosts will have to update their Java.

7.1.1

📜 Changelog

• Changed the required Java version from 16 to 17.
• Added support for MariaDB (storage system was rewritten again...).
• Debug mode will now log requests to the proxy services and their responses.
• Dropped support for Paper 1.16 (unsupported by Paper anyway)
• Removed metrics.

7.1.0

📜 Changelog

• Proxy check was not functional before this version. Many issues have been fixed, and the check is now working correctly. (#116)
• Added configurable priority for every check. You can now specify in which order the checks will be run.
• When debug is enabled, more information will be logged to the console.
• When an error occurs during plugin startup, it will no longer show that logger is null, and log the actual exception.
• Fixed exception during command tab-completion on Velocity. (#119)
• Fixed issues with MySQL. (#122, #110, #120)
• On Waterfall, SQLite driver will be downloaded automatically, this reduces the file size for this platform.
• Small optimizations.
• Improved command aliases (see README).
• Updated adventure (and other libraries)

⚠ Configuration changes

Your configuration will be updated automatically, but some options will need to be configured again

• In the proxy-check section, services will be reset to the new default value. The name changes below were made so the plugin won't use the incorrect default configuration from previous versions.
  • services section has been renamed to registered-services
  • response-regex has been renamed to matcher
• reconnect-check-mode and server-list-check-mode have been removed from the other section and moved to their sections - reconnect-check and server-list-check, now with the option to set their priority.

By the way - Java 17 is out! EpicGuard doesn't require it for now, but it is still recommended to update, as it is the current LTS release

7.0.1

📜 Changelog

• The plugin jar is now split for every platform to decrease the size (caused by including the SQL drivers).
• Many fixes for SQL database issues (invalid syntax, driver not found).
• Improved error logging with additional information.
• Fixed ConcurrentModificationException in name similiarity check.
• Config keys for credentials are now enclosed in quotes by default to prevent error when user forgets to quote them.
• API has been published on JitPack (see README).

⚠ If you are using MySQL: use-my-s-q-l option has been renamed to use-mysql. You should rename it before updating or enable mysql again after updating. Your settings.conf file will be automatically updated/fixed anyway. If you don't use MySQL you don't need to do anything

🔧 If you want to use EpicGuard's JitPack artifact (API), use version 7.0.1-jitpack

7.0.1-jitpack

JitPack broke again

7.0.0

Note

I have decided to release this as a new major release, because of the amount of breaking changes made after releasing 6.0.
Configuration didn't change in this release, but all other data (whitelist, blacklist, alt accounts) will be lost.

I encourage you to use the latest builds instead of the rarely released "stable" versions here, as the latest builds will always contain new features, fixes and improvements while being relatively stable.

Changes compared to v6.0

• Dropped support for Spigot and all legacy versions on this platform. Paper 1.16.5+ is required.
• Dropped support for BungeeCord. Now supporting only its fork - Waterfall.
• Dropped support for all java versions below 16.
• Data is now stored in an SQLite or MySQL database instead of a json file.
• RGB color support.

[6.0.0] Huge changes and new features.

🎉 It's been a long time but it's finally here! 🎉

🛑 This is a major update and it's not compatible with EpicGuard v5's configuration. 🛑

It is recommended to configure and test this version on your test or local server.
The storage system is the same as in v5, so you don't need to delete your /data directory or storage.json file. Your blacklist/whitelist will be safe.
Configuration is now stored in different files, so you need to configure it once again.

❗ Important changes

New configuration system

Completely new configuration system. The format has been changed from YAML to HOCON because of better compatibility.
Your old config and messages file will still be there, so you can move some values from the old config to the new one.

Outdated software deprecation

Support for Spigot 1.8 has been dropped. See the wiki for more details.
Support for Java 8 is deprecated and can be removed at any time in the future. See the wiki for more details

New wiki

EpicGuard finally has a wiki! There's not much there yet, but it will be further expanded in the future.
https://neox.gitbook.io/epicguard-wiki/

Rewritten proxy checking

Rewritten proxy checking, allowing multiple proxy detection services of your choice.
Cache duration is now measured in seconds rather than minutes.

New project, removal of the module system.

Spigot-exclusive features, also known as "command modules" or "operator protection" have been moved to a different project.
See https://neox.gitbook.io/epicguard-wiki/faq#what-happened-to-the-spigot-yml-command-op-protection for more details

One jar for every platform

The new build system now allows us to distribute a single jar for every platform, just as it was before the v5 version.

⭐ Improvements in checks

• NEW! SettingsCheck - it will check if the player has sent the settings packet after joining.
• NEW! NameSimilarityCheck - it will compare the connecting user's nickname with other nicknames in the recent connection history. This check is currently experimental.
• Removed RateLimitCheck - it is already implemented in all server platforms.
• More AutoWhitelist options - you can now whitelist only address, only nickname, or both.

⭐ Other, small improvements.

• Changes in the LogFilter configuration will now apply correctly after /epicguard reload.
• Fixed tab completion for commands.
• All messages are now configurable (including the main help command and analysis).
• Configurable attack reset task interval.
• More meaningful error and warning messages.
• Fixed some ConcurrentModificationExceptions.
• Huge refactor of the code, API, and build system.

[5.3.0] New features

Changelog

• Added new check: NicknameCheck - it uses regular expressions (regex) to validate nicknames.
• Added new command: /guard analyze - you can provide an IP address or nickname, and it will show you details about the user, such as country, city, blacklist/whitelist status, and alt accounts.
• Added nickname whitelist and blacklist. Commands /guard whitelist add/remove and /guard blacklist add/remove now also accepts nicknames. Check your message.yml file if you translated these commands before.
• Fixed many issues with AccountLimitCheck, such as not being able to login with any account after reaching the limit (may still be unstable).
• Added metrics for Velocity version.
• Many minor improvements in the code.

Example of /guard analyze
City and country are unknown because this is a localhost address

[5.2.2] Blacklisting & logging

Changelog

• Completely removed blacklisting from checks.
• Added config setting to adjust ProxyCheck cache duration (set to 30 minutes by default).
• New logging system, no longer logging everything as errors on Velocity and Waterfall.
• Invalid IP addresses are no longer throwing exceptions.
• Added connection/read timeout for URL requests.
• More meaningful error/warning messages.
• Added debug.