MC Plugin Spartan Anti-Cheat | Advanced Cheat & Hack Detection | 1.7 - 1.20.4 Phase 534

Advanced & reliable cheat prevention made simple, trusted by over 100,000 servers.

1. Improved the documentation of the inventory menus.
2. Introduced new methods to handle different connections in the Cloud feature.
3. Implemented a new punishment webhook which lists the commands executed.
4. The Spartan inventory menu’s max pages were limited to 999 instead of practically unlimited.
5. The messages.yml configuration now has the configuration syntax {prefix} for mass plugin name replacement.
6. Files will no longer be synchronized when just created to avoid manipulating important options to their defaults.
7. The way responsible for calculating the min height of the world has been made a mass used method.
8. The IrregularMovements will now treat bedrock players more properly in terms of accuracy.
9. The Cloud feature customer-support command will now be more precise with the information it sends.

1. Completely rewritten the FastClicks check as the previous one was great but did not meat certain expectations.
2. Completely rewritten the Cps Counter handler as an object and renamed it to Click Data.
3. The identification of jump movement has been adjusted for bedrock players.
4. The Explosion protection will now properly calculate the time it needs to function.
5. Reworked the Trident handler to be more universal and cross compatible.
6. Certain parts of the FastPlace & MorePackets will disable when the server has competitive CPS.
7. The Research Engine will now be able to cache for much longer so more data can be accounted for.
8. The Suspicion-based algorithms such as punishments will now work even when the Research Engine is caching.
9. Renamed the description of the Compatibilities item to not be so confusing.
10. The KillAura time detection will no longer check in specific hit time delays.
11. The KillAura raytrace detection will no longer check bedrock players due to their abstract line of sight.
12. The HitReach check will no longer run its longer detection on bedrock players.
13. The Customer Support command will now include configuration values when executed.
14. Violation category will now appear as “unlikely” when a false positive has taken place.
15. The configuration system will now accept text as logic, integers & decimals if typed correctly.
16. Completely rewritten the way Spartan calculates CPS for more accuracy and new detections.
17. Increased the near max falling motion of the IrregularMovements step detection as a way to improve stability.
18. Added more information to the KillAura raytrace detection for more knowledge for the development.
19. Optimized the punishment algorithm by forcing it to recalculate less information and in more needed circumstances.
20. Adjusted the positioning of the Information Analysis object so the detection of a check is found successfully.
21. The Research Engine will now longer attempt to calculate evidence for players who have been offline for long.
22. Improved the accuracy of the IrregularMovements ground-up detection to match the possible expectations of some.
23. Greatly optimized the way Spartan handles its violations in its cache for faster performance and less memory usage.

1. Made the Player Info inventory menu look into the player’s online state in more situations.
2. Adjusted the Minigame Maker compatibility after the project was transferred to another developer.
3. The IrregularMovements step detection will now resort to greater limits in certain situations.
4. Big entities will no longer be checked by the KillAura raytrace detection as it’s too risky stability-wise.
5. Implemented more new KillAura detections and replaced their old ones.
6. Made a few corrections to the Combat Processing handler related to how it handles cache.
7. Adjusted how the plugin uses its threads for more appropriate processing times and queues.
8. Adjusted the ImpossibleInventory check to be more accurate and functional.
9. Adjusted the False Positive Detection feature and mostly removed the Problematic Detections feature due to problems.
10. The Research Engine will now recalculate the False Positives by removing redundant violations.
11. Added the X Y Z coordinates in the plugin’s logs since they were already added in the SQL feature.
12. The IrregularMovements will no longer run when in liquid blocks as it doesn’t need to.
13. Improved the protection of the NoSlowdown check of using a bow in combination with specific movements.
14. Optimized & improved the process the Velocity check uses to understand if it can check a player.
15. The IrregularMovements will now treat its cache more appropriately with several improvements.
16. The Punishment algorithm will now be more accurate due more frequent cache refreshes.
17. Partly rewritten the Violation History object to handle violations & false positives more appropriately.
18. The XRay check will no longer wait a minute for the next violation but will notify when the violation cycle resets.
19. Added more information to the Player Info inventory menu about the evidence of the player.
20. Removed the Performance.disable_problematic_detections settings.yml option as it no longer plays an important role.
21. Improved the bedrock compatibility by better identifying offline players without necessarily accessing heavy offline player data.
22. Rewritten how the Research Engine handlers cache works to optimize asynchronous performance but offer more main-thread updates at the same time.
23. The No Hit Delay compatibility will now only account when a player recently received damage.
24. Deleting a player’s stored data will instantly remove them from the inventory menus.

The Spartan inventory menu will now be able to again access the. data of offline players.

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.

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. 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.