Provided the following additional optimisations to the player evidence algorithm:
1. The calculation will now have a 1 second cooldown.
2. The calculation objects will have their contents pre-calculated.
3. The calculation will be made using pre-calculated lists instead of calculated maps.
4. The calculation will only include checks that there is no evidence for.
5. The calculation will use a single thread if available to run or revert to run synchronously.

Provided the following additional optimisations to the player evidence algorithm:
1. The calculation will now have a 1 second cooldown.
2. The calculation objects will have their contents pre-calculated.
3. The calculation will be made using pre-calculated lists instead of calculated maps.
4. The calculation will only include checks that there is no evidence for.
5. The calculation will use a single thread if available to run or revert to run synchronously.

Did some deep optimisations to the hacker identification system for those of you who have servers with a lot of players/data. The rest of you should continue to be fine, but I recommend updating as always.

Click to expand...

Corrected an issue in the Player Velocity object that prevented some data collection, updating is more than recommended to help enrich the functionality of the Velocity check.

Click to expand...

• When a check runs, multiple detections execute per player, which can sometimes have consequences in performance. From this update and on, Spartan will allocate a single reusable thread to run detections asynchronously. This thread will run only when it’s not busy with another detection and when the circumstances allow for it, otherwise the detection will revert to run synchronously. For example, when we run a detection asynchronously and the check has preventions enabled, we risk moving the prevention to the next server tick, which will allow the hack module to work for a bit and cause potential damages to one’s server, so Spartan will first make sure there’s enough time in the current server tick to ensure the prevention also runs before the server updates itself. Additionally, Spartan will respect the time left in the server tick by running asynchronously only what’s necessary such as mathematical calculations instead of trivial code such as checking the configuration or cache to see if a detection is enabled or buffered enough, of which code has already run previously as this algorithm has been placed methodically in the code for the possible maximum potential. Lastly, this algorithm will only target heavy and frequent detections such as the ones implemented in movement checks.

1. Optimized the Spartan Player object in regards to its calculations related to the world border.
2. Optimized the ImpossibleInventory & NoSlowdown checks and rebalanced their detections and performance.
3. Improved the Spartan inventory menu with a more accurate statistics description.
4. Detections will now be toggleable in certain versions of Spartan.
5. The Velocity check will now support checking damage from entities but also more situations with players.
6. Did some maintenance in the Player utilities as it caused some checks to misperform.
7. The NoFall ratio detection will now start checking from the 3 fallen blocks instead of 4 but still be more lenient.
8. Slightly improved the speed of the punishment algorithm by using regex instead of ordinary strings.
9. Compatibilities will now refresh in memory when any plugin is loaded or unloaded, thus not having a problem when a plugin loads later.
10. The IrregularMovements step detection will now apply more lenient downwards limits when a player was not recently falling.
11. Completely rewritten the Speed sprint detection with the same but improved design.
12. The KillAura raytrace detection will now start raytracing from the entity’s width and after.
13. The punishment algorithm will no longer blame the first-party plugins when canceled as that’s not a plausible scenario.
14. The punishment algorithm will now offer possible dependent plugins when canceled as a way to ease search.
15. The Spartan’s inventory menu AntiCheat Updates item will no longer be considered clickable as it isn’t.
16. The KillAura sensitivity abstract detection is far too sensitive and will only occur with suspected players and identified hackers.
17. The KillAura sensitivity minimum detection has had its buffer separated but also increased in hopes of providing better stability.
18. The ban system will now insert the actual name of the punisher and not its object name, causing varchar issues to the database as a result.
19. The ban system will now distribute its keys using a list so less inconsistencies are created over time when modifying the code.
20. Restored the functionality of the unban command as it seemed to not perform as expected for some users.
21. The XRay detection has been rebalanced with faster and better calculations, and earlier signs in the inventory menus in the form of items.
22. The KillAura pattern detection will now require more observations to make correlation assumptions, and the required correlation has increased for all its sub-detections.
23. The KillAura pattern detection will now require the entity to be a player or monster and to not be blocked by a blocked behind.
24. The Cloud feature Customer Support will now send less logs when used as a way to help prevent time waste when studying such information.
25. The IrregularMovements climb detection will now apply different limits when climbing scaffolding blocks.
26. Decreased the amount of threads the plugin uses by bringing processes to the main thread in an optimized manner.
27. Suspicion Notifications will now run regardless of the Spartan inventory menu’s refresh rate.
28. The Spartan inventory menu will now refresh only when it needs to instead periodically.
29. The Explosion handler will now combine multiple events to calculate the players surrounding the location, which will dramatically decrease the amount of iterations and calculations needed.
30. The KillAura and HitReach checks will no longer check wide entities as they seem to be problematic.
31. Implemented a Ground utilities patch for miscalculations in the player’s remaining height position.
32. Warnings, reports & kicks will no longer have any chance of being identified as violations.
33. Did some maintenance to the Floor handler to make it more universal and accurate.
34. Corrected a rare command-tab null pointer console error.
35. The Item Attributes compatibility will now be enabled by default.
36. The verification connection will now be processed asynchronously.
37. The NoSlowdown bow shots detection will now be more lenient.

1. Implemented a new KillAura sensitivity sub-detection that checks how abstract the player’s sensitivity is.
2. The KillAura existing sensitivity detection will now be more lenient by decreasing violation points when not found to be hacking.
3. Implemented several mathematical improvements to the Player Opponent object that automatically improve the KillAura distance detection.
4. The KillAura rotations detection will no longer require stored pitch information to run and will be more lenient with wider entities.
5. The KillAura direction and aim detections will now require 5x times less directional distance to function.
6. Implemented a new KillAura detection named response that counts the ticks a player had at a close angle to an entity before hitting.
7. Implemented a new KillAura detection named strafe that compares the directional distance of a player.
8. Implemented a new KillAura detection named pattern (originally perspective) that uses linear algebra to compare one’s movement with predictions of that.
9. The KillAura movement & rotations detections will now be more lenient to protect against instabilities.
10. Further organized the code the KillAura check calls to run its movement-based detections.
11. Generally polished remaining KillAura detections from the description to the mathematics as we get closer to the completed rewrite of this check.
12. Implemented a new IrregularMovements liquids sub-detection named consistency.
13. Adjusted the way the IrregularMovements step detection calculates its limit to have more accuracy.
14. Restored the functionality of some of the raw commands.
15. The Research Engine will now recalculate cache in different scenarios and in a more efficient order.
16. False Positives will now be canceled by correct violations made by suspected & hackers to provide a balance.
17. The FastPlace check will no longer check air blocks as it doesn’t need to and can cause incompatibilities.
18. The Cancel Violation feature will now apply more appropriate limits based on a check’s problematic detections.
19. The Awareness Notifications feature will now optionally notify when there is any problem with the punishment algorithm.
20. Adjusted the code of the BlockReach check to run faster while forcing it to adopt greater limits when flying.
21. Greatly improved the movement identification method of the Spartan Player object to include damage.
22. Made some adjustments to the Spartan inventory menu so it’s more proper.
23. Test servers will now calculate evidence based on live but not historical information.
24. The Testing identification handler will now return more information to easier point out potential errors.
25. The IrregularMovements will now be more lenient when the player was recently legitimately flying.
26. The IrregularMovements check will now be more lenient with the hop detection.
27. Improved the block material list of the Block utilities.
28. Rewritten parts of the GhostHand check to work faster and more accurately.
29. Rewritten and simplified the Block Break handler with new accurate utilities that account a broader situation of the player.
30. The plugin will now calculate radians to degrees with higher precision.
31. The Information Analysis algorithm will now be faster at identifying the positions of numbers & decimals.
32. The Ground utilities will now consider all the bounding boxes of the snow block.

1. Rewritten the KillAura analysis detection with a new algebra-based design.
2. Rewritten the KillAura move-accuracy detection as Movement with a new logic-based design.
3. Improved the Rotations, Sensitivity & Direction KillAura detections using combat buffering.
4. Implemented more situations where the combat-based buffer of a player keeps running.
5. Extended the functionality of the KillAura time detection to check consistency.
6. The anti-cheat will now store its data in memory per check which will dramatically decrease unnecessary iterations but also CPU usage by requiring less hashing of keys.
7. The Cache system will no longer clear data against a list and know automatically where important information is stored.
8. The Cache system will now be able to clear data in the main thread without impacting performance and forcing single-threaded checks to be thread-friendly unnecessarily.
9. The plugin will now use 2 less threads and rapidly move a lot of data in the main thread and save performance wasted to unnecessary concurrency checks on the main thread.
10. The Ground utilities will now cache the block heights to decrease unnecessary logical comparisons.
11. The Ground utilities now offers more diverse and progressive location calculation if a player rides an entity.
12. The EntityMove check should now perform better when calculating the properties of a vehicle’s location.
13. Added support for Folia, although keep in mind this is experimental and can end up being problematic. (Take backups)
14. The Information Analysis object will now take data directly from the memory and not the storage of the server.
15. Improved the stability of the IrregularMovements hop detection in regards to its jumping checks.
16. The Speed check will now once again slightly increase its limit if found to be unstable.
17. Further completed the KillAura direction detection with a buffered sub-detection.
18. Updated the EcoEnchants compatibility class after being notified by its developer.
19. Implemented a basic auto-totem detection via the ImpossibleInventory check.
20. Adjusted the Spartan inventory menu to contain more and grammatically correct information.
21. Improved the Combat Processing handler by calculating the max of the recently cached variables.
22. Removed the Developer API method “warnPlayer” as it wasn’t used or consistent with other offerings of the API.
23. Brought the {punisher} placeholder/syntax to the Kick & Warn commands to be consistent with the rest.
24. Implemented a new method in Combat utilities to near precisely calculate the ticks per hit for more appropriate buffering.
25. The Click Data object will now calculate cps and other click information on multiple circumstances for more accuracy and consistency.
26. Movement checks will now create less strings & numbers and check less variables as a way to optimize performance.
27. The customer-support command can now be run without providing a description and will send more organized information compared to previously.
28. Improved the Research Engine handler’s method that’s responsible for identifying detection information for memory storage.
29. Moved the calculation of directional locations entirely on the Spartan Location object.

1. Rewritten the KillAura “modulo”, “yaw”, “pitch” & “stability” detections as part of a new simpler and more efficient detection named “sensitivity”.
2. The proxy-command has been optimized by having fewer iterations of a loop.
3. The spectate feature will now remove the player on its own instead of relying on third-party handlers aggressively.
4. Part of the FastPlace check will now function even when block placing is disabled.
5. Enabling individual-only notifications will disable suspicion notifications as they are unnecessary.
6. Improved the limits of several bedrock detections so they run more in par with java detections.
7. Improved the stability of the Killaura rotations and direction detections.
8. Set a limit to the max supported entities for the KillAura raytrace detection.
9. The Player Info inventory menu will now show information regardless of the player’s evidence state.
10. Improved the cache of the Spartan Location object to be more universal.

1. Completely rewritten the KillAura Aimbot detection with the new utilities and a pattern-based code design.
2. Completely rewritten the KillAura rotations detection with new utilities and a historical-based code design.
3. Dramatically improved the KillAura distance detection with more lenient but organized requirements.
4. Implemented a new FastBreak detection named indirected-surroundings-per-second which studies blocks broken that are not close to the previous block.
5. Delayed the Punishment Discord webhook slightly so other Discord webhooks can take its place if configured.
6. The inventory menu of Spartan will now have its own entire thread so loading times are low.
7. The staff player counters will refresh at least every minute instead of always when opening the menu.
8. Increased the precision of the Movement utilities jump movement.
9. Improved the decimal precision of the IrregularMovements hop detection.
10. The Combat utilities will now use trigonometry instead of ray-tracing to accurately predict the location of a hit.
11. The Math utilities have now been renamed to Algebra utilities and have received new methods.
12. Created a new type of utilities named Trigonometry to help organize certain important equations.
13. The KillAura check will no longer run when a player is gliding with an elytra.
14. Implemented a new messages.yml option named “notifications_modified” for when changing the notification frequency.
15. The Block utilities will now use the block breaking time calculator to understand whether a block is sensitive in newer versions.
16. The difference between yaw and pitch will now be calculated entirely using trigonometry.
17. Stopped using weak hashmaps for detections as they didn’t save nearly enough memory but caused minor inconsistencies.
18. Checks will now clear their cache more properly by updating existing cache instead of removing it all together.
19. Implemented a new “untested” command meant to be used to execute BungeeCord commands. (/spartan proxy-command <command>)

The customer-support command will now included more needed information for the resolution of a user-reported problem.

Click to expand...