1. Completely rewritten the EntityMove check with the use of vehicle attributes but also new calculations.
2. Simplified the way cross-server notifications are distributed to avoid confusions between users.
3. The Maximum Checked Players feature will now iterate properly though some of its information.
4. Compatibilities will attempt to send Awareness Notifications when failing to load.
5. The Cloud feature will no longer impact the “server_name” option in settings.yml.
6. Potentially corrected a NoFall water bucket false positive. (MinecraftSGP message me if not fixed)
7. Optimized the Cloud feature with less specific error handling.
8. Implemented a new Cloud sub-feature to command the plugin to send customer-support information.
9. The Cloud feature will now refresh for the first time after the Research Engine handler has completed its caching.
10. Cache stored by the movement event will now be specific to the vehicle the player is riding.
11. Improved the effectiveness of the False Positive Detection by making it run on violations not containing a prevention which will allow for premature learning.
12. The False Positive Detection will now have a 2MB limit in the data it can retain in its memory, although there have been no reported issues.
13. The False Positive Detection will now round integers to the nearest of 5 to improve stability.
14. Improved the compatibility of Ultimate Statistics with more useful calls and less code checks.
15. The Vehicles compatibility will now provide more accurate and less lenient results.
16. Pistons will now be accounted for in the water detection of the Speed check.
17. The evidence algorithm of the Player Profile object will now search for false positives instead of just problematic detections.
18. The evidence algorithm of the Player Profile object will now calculate the days based on your first significant violation till now instead of days you had violations recorded.
19. The evidence algorithm of the Player Profile object will now decide whether a player is suspected or a hacker based on the amount of suspicions instead of level of individual suspicions.
20. Evidence of hacking or suspicion will now be held longer in the memory for offline players to save performance.
21. Brought performance & accuracy improvements in the way the Speed check caches its limits.
22. Inventory menus and certain calculations will now use more accurate results of a player’s violation history.
23. The overall history of a player will now be based on the amount of unique dates instead of the total collected amount of dates.
24. The main inventory menu will no longer process multiple versions of itself for a single players, which could potentially happen in a time of server lag or spam while already loading.
25. Rewrote a part of the punishment algorithm to run faster, be more reliable with its results and have no limit to how many checks a player can be punished for.
26. Combat-based calculations of the Research Engine handler will now be returned to their original values if not enough data is available.
27. Implemented a new checks.yml configuration option for the GhostHand check: check_fully_solid_blocks_only

This update is for those of you whom encounter this rare string replacement error. It's effectively harmless, but here you go.

Click to expand...

Resource packs will now be identified when the Bukkit method is available.

Click to expand...

Made extra functionalities available to everyone natively via the plugin's code, older versions will continue to receive them via a web-server connection. Additionally, online documentation has returned the options of the extra functionalities.

Click to expand...

1. The Exploits undetected-movement detection will no longer check players in vehicles as it doesn’t need to.
2. The Exploits undetected-movement detection will now check the configuration before running.
3. The IrregularMovements check will now be more lenient when the scenario changes.
4. The plugin will now convert text to decimals faster which will help when analyzing violation information data.
5. The Inventory utilities will now use different methods to set the owning head of a player depending on the server version.
6. Decreased the amount of threads the plugin uses for asynchronous tasks.
7. The Information Analysis object will now remove numbers from detections and will try to correlate them to configuration options for more unique outcomes.
8. The Cancel Violation handler will now be updated more frequently for more consistent and accurate calculations.
9. The Cache system will no longer clear certain important types of data.
10. The False Positive Detection feature will now create more simplified keys for higher chance of catching false positives.
11. The False Positive Detection feature will now consider hackers & suspected players in its calculations in more strict terms.
12. Corrected a few outdated messages related to the Research Engine handler.
13. Completely rewritten the way Problematic Detections are calculated.

489.2​

489.1​

Corrected a SQL table creation issue and a major check cancellation issue. Updating is more than recommended, sorry for the inconvenience, Phase 488 was a massive update.

Click to expand...

Fixed an issue where the class of the Performance Optimizer feature wouldn't initiate.

Click to expand...

1. Many static class methods have been made part of new/existing objects to improve performance.
2. Completely rewrote the Performance Optimizer feature to be more universal, more organized & better.
3. The Speed ground detection will now account for a player’s building process.
4. The unban command will now properly clear the cache of the ban feature.
5. The SQL Config and SQL Logs are now combined as the SQL Feature.
6. Potion Effects will now have their own organized cache to prevent false positives.
7. The “Logs.log_file” option will now reappear in the settings.yml configuration.
8. Decreased the amount of threads Spartan uses and replaced it with existing ones.
9. Many checks.yml & config.yml options will now be generated when first used.
10. Removed forgotten configuration options & functionalities from several checks.
11. Removed Configuration Recommendations and replaced them with proper listing of problematic detections.
12. The checks.yml configuration will no longer be existent when the config.yml configuration is used.
13. Check with no ability to punish will now show punishments as disable in the inventory menus.
14. All players will be treated as testers when the server is identified as a testing environment.
15. Awareness notifications will now be delivered to all staff players.
16. The XRay check will now notify staff players when it has insufficient data to work with.
17. The plugin will now look for surrounding blocks when trying to identify if the player is in a water bubble elevator.
18. The plugin will now detect decimals in detection information more accurately.
19. Mining notifications will now be logged in the plugin’s files regardless of the check’s or player’s state.
20. Added more information to be sent with the use of the customer-support command.
21. Check objects will now handle more or less memory depending on their needs.
22. Violations will no longer reset every minute for all players but individually.
23. Removed the messages.yml option “violations_reset” as it’s no longer needed.
24. Rewrote a big part of the Punished Players algorithm, mainly to improve consistency & security.
25. Checks can no longer be named with the name of another check.
26. The Research Engine will no longer cache for longer than a minute.
27. The IrregularMovements check will now require the player to move slightly to be checked for a specific cobweb movement.
28. The False Positive Detection will now adjust its decimal points for the MorePackets check also.