Spartan AntiCheat & AntiExploit 4.0.6.6

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.

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

1. Bedrock players will now be treated more leniently in certain parts of the IrregularMovements check.
2. Removed the Awareness Discord Webhooks as they were undesired by many users including myself.
3. The Customer Support command will now complete being sent without the requirement for detection information.
4. The FastBreak check will now be more lenient towards bedrock players.
5. While the new EntityMove check is still being rewritten, the old one will stop checking bedrock players for stability.
6. The ItemsAdder compatibility will no longer work if the DisguiseAPI class is not found to prevent console errors.
7. Silent checks will now appear enchanted in the Manage Checks inventory menu.
8. Implemented a new feature and settings.yml option for it: Important.maximum_checked_players_at_once
9. The Discord Webhooks feature will now appear more frequently as many of you suggested it needed this.
10. The Spartan inventory menu has been optimized to refresh itself again.
11. Potentially corrected an IrregularMovements climbing jump false positive.
12. Compatible plugins of mine will appear in the Spartan inventory menu.
13. Decreased the amount of configuration calls & search algorithms in the settings.yml configuration.
14. Modified an outdated value reply in one of the Developer API’s methods.
15. The plugin will now exempt players from detections for a bit when the server has a resource pack.
16. The False Positive Detection will now focus more on integers than just decimals to correct more issues.
17. The Research Engine feature will now recalculate its cache much faster due to methods being combined in async mode.
18. The SQL port configuration option will now modify a decimal format to an integer one.
19. The Speed water detection will no longer check boats, this will be the job of the future rewritten EntityMove check.
20. The Cloud feature will not attempt new connections if a recent one failed to complete for any reason.
21. Hardcoded compatibilities will now show as functional if found to be loaded in the server.
22. Balanced dozens of methods in the Research Engine handler with native methods and less unnecessary checks.
23. When loading huge amounts of data, the Spartan Menu will no longer be performance intensive.

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.

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.

Implemented some corrections to the punishments system.

Did some critical optimisations to the Player Profiling objects to restore good performance for some users.

The SQL feature will no longer notify when it's not configured.

1. Rewritten the Exploits undetected-movement detection.
2. Removed unused methods from some objects.
3. Made the chunk cache more thread safe by decreasing recurrency.
4. Updated the Move utilities with more universal variables.
5. Listed more dependent plugins in the plugin.yml file.
6. Made some changes to the API’s events to adapt to the rewritten systems.
7. Improved the management of the Cloud feature’s exceptions.
8. The plugin will now update profile permission knowledge when permissions are checked.
9. The Research Engine will now need both profile and log requirements to start functioning.
10. Rebalanced the permissions that would identify staff players.
11. Optimized the permissions feature by decreasing memory calls.
12. Checks will not be silent by default, which was a mistake of the past update.
13. Checks who do not support silent mode will not have the option, just like past the previous update.
14. Removed the spartan.punishment permission as it was malfunctioning and wasn’t being used in general.
15. Living entities will now need to have their AI enabled to be supported by Spartan’s checks.
16. Removed the Low Violation handler as this is no longer considered a proper way to deal with violations.
17. The API will now support giving bypass permissions to players via the addPermission method.
18. The Player Info inventory menu will no longer update when there is no change in violations.
19. The Check object’s silent method will no longer try to check world data twice.
20. The entity AI method will no longer be used in versions that don’t offer it.
21. Improved the SQL feature with better errors, less variables/memory used, and more protections against mistakes.
22. Adjusted an invalid SQL query when deleting player information from the database.
23. Implemented a new checks.yml option for the Exploits check to manage the building detection.
24. Mining notifications will no longer be logged in the console.
25. Improved how the plugin identifies player swimming.
26. An API event will no longer be triggered asynchronously.
27. The Speed & IrregularMovements will now be more lenient towards bouncing blocks in certain scenarios.
28. Implemented a new type of utilities to manage characters in Java.
29. Drastically improved & optimized the way the plugin handles its check data.
30. Implemented a new awareness notification about the Discord Webhooks feature.
31. Adjusted the colors of the Spartan command’s content depending on certain scenarios.
32. Adjusted a Player Data utilities method that caused the Speed potion effect to not always be accounted.

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.

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

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.

1. Bedrock & Java player information will now be analyzed and structured separately.
2. The Velocity check’s detection will now detect things more accurately by accounting for online hackers in the data flow.
3. The Product Offer feature will no longer be so forceful with notifying staff users.
4. The Cross Server Information feature will now work better.
5. Improved the stability of the IrregularMovements check when it comes to bedrock players.
6. The Bedrock Detections notification will now appear less frequently and when needed.
7. Problematic Detections will no longer be included in hacker/suspected player calculations.
8. Made the variables and functionalities of the compatibility configuration more universal.
9. Players will no longer be able to pickup items when using Spartan’s spectator mode.
10. The Player Info inventory menu will no longer use magic color codes when the user has opted out of the ecosystem options.
11. Some information from the AntiCheat Updates item will now appear on other inventory menus.
12. The File GUI will now appear as a recommendation in the Manage Configuration menu.
13. Implemented a new settings.yml option to toggle bedrock detections for those that own it.
14. The Suspicious Fights feature will now return more relevant results based on a pre-existing more organized algorithm.
15. The HitReach check will now consider the average hit reach of the server’s players for better stability & detectability.
16. Improved the tab completion by detecting what to recommend based on the command’s arguments.
17. The Wave & Ban features will no longer do transfers from their old configurations due to them having been removed for a long time.
18. Rewritten how the raw command feature works with an awareness notification to always support command options.
19. Implemented a new awareness notification option to accompany the spectate command.
20. The Wave feature’s API method is now a boolean and not a void.
21. The Ban feature will now support SQL and also offer a creation date.
22. Slightly optimized the item search of all inventory menus with a direct equals method.
23. You can now dismiss reports via the inventory menu by clicking on the reported player item.