Spartan AntiCheat & AntiExploit v4.0.8.8

Unlike the previous hot-fix update, this one is not required to download, but it provides many incremental improvements in the internals of Spartan's processes, so it's definitely recommended.

Adjusted some code in the Combat Processing handler to prevent dealing with null parameters.

1. The plugin will now max out its time division to 30 instead of 90 days.
2. Completely rewritten a big part of KillAura check with new utilities and design, with the remaining awaiting completion.
3. Introduced a new messages.yml configuration option named “console_name”.
4. The Maximum Checked Players feature will now be more synchronized with its interactions.
5. Major Incompatible plugins/features can now be toggled via compatibility.yml if you don’t want to account for them.
6. Certain compatibilities were updated to work better on more recent versions of Minecraft.
7. Completely rewritten the way the plugin understands yaw & pitch difference for more accurate calculations.
8. Discordapp.com will now also work as a webhooks domain compared to only discord.com previously.
9. Adjusted certain potion effect methods of the Player Data utilities to help improve detection stability.
10. Adjusted the accuracy of the identification of jump movement down to 6 decimal places for less false positives.
11. Did a general maintenance of many classes and replaced a lot of outdated & inefficient code.
12. The previously secret option that allowed to toggle console logs has returned in settings.yml.
13. Implemented new checks.yml options and removed old ones to adjust to the changes of the KillAura check.

Plugin maintenance & Preparation for the upcoming big changes

Replaced the entity-height method with the entity-eye-height method for 1.8, 1.9 & 1.10 Minecraft servers, since the original method is missing.

1. Implemented additional bounding boxes to consider in the Ground utilities.
2. Partly rewritten the HitReach check to be more accurate and faster.
3. Completely rewritten the Teleport protection to be more consistent.
4. Partly rewritten the Combat Processing handler to use recent systems of cache.
5. Partly rewritten the Movement Processing handler to be more compact & reliable.
6. Prepared the Combat utilities for the upcoming KillAura check rewrite.
7. Removed the Item Teleporter & Enderpearl handler as it no longer had a significant purpose.
8. Improved the False Fall Damage handler with checking for canceled & silent causes.
9. The certain {detection} placeholders will now fallback to {detections} when no longer supported due to plural grammar.
10. Stopped using the required-resource-pack method since it caused errors in some recent versions.
11. False Positives & Hacker-Free players will now be calculated asynchronously in par with the remaining Research Engine cache types.
12. Repositioned the way certain Configuration & Discord notifications are being sent to staff players.
13. Rewrote some of the detection information of the Speed sprint detection to help organize the handlers around it.
14. Detection Notifications will no longer forcefully add the detection information in the lowest frequency.
15. Made the False Positive Detection less lenient to prevent it from overly detecting violations.
16. The Hack Prevention object will now pass a lot of its information to the Moderation handler to prevent unecessary memory calls.
17. Detection Notifications will now also replace Suspicion Notification when the Research Engine doesn’t have data or is caching.
18. The Exploits undetected-movement detection will no longer function when major incompatible plugins are detected.
19. Spartan Location objects will now clear their data every 3 ticks instead of 2 and will have more accurate comparisons.
20. Removed the Automated Configuration functionality as it’s barely used and probably not desirable.
21. Decreased the amount of threads Spartan is using, although this did not negatively impact performance.
22. The Maximum Checked Players feature will now disable if configured with a zero or negative number.
23. Decreased the violation cooldown of the XRay check for more frequent notifications.
24. The evidence of a player will no longer be cleared when being updated but refreshed until the update takes place.
25. Implemented a new feature named Skip Detection Ticks to help optimize performance when the Maximum Checked Players feature is inactive or ineffective.
26. Updated the Spartan Player object to be able to limit the amount of nearby entities calculated to save crucial performance.
27. The Spartan Player object will now cache its Player Profile object to prevent unnecessary memory calls.
28. The KillAura check will no longer attempt to understand the legitimacy of a fight to allow detections to run more frequently.
29. The Spartan inventory menu will now have one row for suspected & hackers, one for legitimate players and one for reports.
30. The IrregularMovements check will now search for liquid blocks below the player when the player is falling.
31. The Player Fight system will now be able to calculate the max hit combo of a player.

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.