
Spartan AntiCheat - Java/Bedrock 4.0.5.3
Very Optimised | Super Customisable | Minimal False Positives | Folia Support | Geyser Detections
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.
- Rewritten the Exploits undetected-movement detection.
- Removed unused methods from some objects.
- Made the chunk cache more thread safe by decreasing recurrency.
- Updated the Move utilities with more universal variables.
- Listed more dependent plugins in the plugin.yml file.
- Made some changes to the API’s events to adapt to the rewritten systems.
- Improved the management of the Cloud feature’s exceptions.
- The plugin will now update profile permission knowledge when permissions are checked.
- The Research Engine will now need both profile and log requirements to start functioning.
- Rebalanced the permissions that would identify staff players.
- Optimized the permissions feature by decreasing memory calls.
- Checks will not be silent by default, which was a mistake of the past update.
- Checks who do not support silent mode will not have the option, just like past the previous update.
- Removed the spartan.punishment permission as it was malfunctioning and wasn’t being used in general.
- Living entities will now need to have their AI enabled to be supported by Spartan’s checks.
- Removed the Low Violation handler as this is no longer considered a proper way to deal with violations.
- The API will now support giving bypass permissions to players via the addPermission method.
- The Player Info inventory menu will no longer update when there is no change in violations.
- The Check object’s silent method will no longer try to check world data twice.
- The entity AI method will no longer be used in versions that don’t offer it.
- Improved the SQL feature with better errors, less variables/memory used, and more protections against mistakes.
- Adjusted an invalid SQL query when deleting player information from the database.
- Implemented a new checks.yml option for the Exploits check to manage the building detection.
- Mining notifications will no longer be logged in the console.
- Improved how the plugin identifies player swimming.
- An API event will no longer be triggered asynchronously.
- The Speed & IrregularMovements will now be more lenient towards bouncing blocks in certain scenarios.
- Implemented a new type of utilities to manage characters in Java.
- Drastically improved & optimized the way the plugin handles its check data.
- Implemented a new awareness notification about the Discord Webhooks feature.
- Adjusted the colors of the Spartan command’s content depending on certain scenarios.
- 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.
- Many static class methods have been made part of new/existing objects to improve performance.
- Completely rewrote the Performance Optimizer feature to be more universal, more organized & better.
- The Speed ground detection will now account for a player’s building process.
- The unban command will now properly clear the cache of the ban feature.
- The SQL Config and SQL Logs are now combined as the SQL Feature.
- Potion Effects will now have their own organized cache to prevent false positives.
- The “Logs.log_file” option will now reappear in the settings.yml configuration.
- Decreased the amount of threads Spartan uses and replaced it with existing ones.
- Many checks.yml & config.yml options will now be generated when first used.
- Removed forgotten configuration options & functionalities from several checks.
- Removed Configuration Recommendations and replaced them with proper listing of problematic detections.
- The checks.yml configuration will no longer be existent when the config.yml configuration is used.
- Check with no ability to punish will now show punishments as disable in the inventory menus.
- All players will be treated as testers when the server is identified as a testing environment.
- Awareness notifications will now be delivered to all staff players.
- The XRay check will now notify staff players when it has insufficient data to work with.
- The plugin will now look for surrounding blocks when trying to identify if the player is in a water bubble elevator.
- The plugin will now detect decimals in detection information more accurately.
- Mining notifications will now be logged in the plugin’s files regardless of the check’s or player’s state.
- Added more information to be sent with the use of the customer-support command.
- Check objects will now handle more or less memory depending on their needs.
- Violations will no longer reset every minute for all players but individually.
- Removed the messages.yml option “violations_reset” as it’s no longer needed.
- Rewrote a big part of the Punished Players algorithm, mainly to improve consistency & security.
- Checks can no longer be named with the name of another check.
- The Research Engine will no longer cache for longer than a minute.
- The IrregularMovements check will now require the player to move slightly to be checked for a specific cobweb movement.
- The False Positive Detection will now adjust its decimal points for the MorePackets check also.
- Bedrock & Java player information will now be analyzed and structured separately.
- The Velocity check’s detection will now detect things more accurately by accounting for online hackers in the data flow.
- The Product Offer feature will no longer be so forceful with notifying staff users.
- The Cross Server Information feature will now work better.
- Improved the stability of the IrregularMovements check when it comes to bedrock players.
- The Bedrock Detections notification will now appear less frequently and when needed.
- Problematic Detections will no longer be included in hacker/suspected player calculations.
- Made the variables and functionalities of the compatibility configuration more universal.
- Players will no longer be able to pickup items when using Spartan’s spectator mode.
- The Player Info inventory menu will no longer use magic color codes when the user has opted out of the ecosystem options.
- Some information from the AntiCheat Updates item will now appear on other inventory menus.
- The File GUI will now appear as a recommendation in the Manage Configuration menu.
- Implemented a new settings.yml option to toggle bedrock detections for those that own it.
- The Suspicious Fights feature will now return more relevant results based on a pre-existing more organized algorithm.
- The HitReach check will now consider the average hit reach of the server’s players for better stability & detectability.
- Improved the tab completion by detecting what to recommend based on the command’s arguments.
- The Wave & Ban features will no longer do transfers from their old configurations due to them having been removed for a long time.
- Rewritten how the raw command feature works with an awareness notification to always support command options.
- Implemented a new awareness notification option to accompany the spectate command.
- The Wave feature’s API method is now a boolean and not a void.
- The Ban feature will now support SQL and also offer a creation date.
- Slightly optimized the item search of all inventory menus with a direct equals method.
- You can now dismiss reports via the inventory menu by clicking on the reported player item.
- Implemented an automatic calculation of the size of the Plugin Ecosystem inventory menu.
- The plugin will now identify its original platform when using a token.
- Extended the Cloud feature with more useful methods.
- Improved how the plugin shows URLs.
- Some product information will now be synchronized with the Cloud.
- Improved the plugin’s Awareness Notifications with new and more proper messages.
- The Piracy handler will now operate at much faster speeds due to the implementation of multiple threads.
- The plugin will now require more to ban a player via the Cloud feature.
- The String utilities methods will now return more fail-safe results.
- The Cross Server Information feature will now have better backwards option compatibility.
- The IrregularMovements levitation detection will no longer run when the player’s head is inside a block.
- A player’s check evidence will no longer be returned if they have bypass or are in other states of canceled checking.
- Listed additional bounding blocks for stonecutter blocks in the Ground utilities.
- Removed the Plugin Ecosystem inventory menu as it was rarely used by users.
- The Minigame Maker compatibility will now open its menu via commands.
- Adjusted the queries of the SQL feature to be less problematic & more universal.
- Created a new settings.yml option named “Cloud.synchronise_files” to toggle cloud file changes.
- Removed the settings.yml option “Important.cloud_feature” as all Cloud features will fail properly if unavailable or not connected.
- Moved the settings.yml option “server_name” to the newly created “Cloud” category while maintaining backwards compatibility with the 2 older options.
- Awareness Notifications will now longer include the disabling message part when sent on Discord.
- The messages.yml option “notifications_clickable_command” has been transferred to settings.yml as “Notifications.message_clickable_command”.
- Improved the Auto Updater feature with universal variable outcomes.
- Adjusted some material libraries in the Block utilities for the better.
- Improved the notification of the Floodgate compatibility.
- Implemented additional awareness notifications.
- Potentially improved the compatibility of mcMMO & TreFeller plugins.
- The synchronization algorithm will now understand the type of variable it is dealing with.
- The synchronization algorithm will now be faster & account for when the server is unavailable.
- Adjusted the Research Engine handler to use the YAML configuration more properly.
- Custom check names will now be available for certain customers.
- Slightly improved the functionality of some of the items in the Spartan inventory menu.
- Changed how items are shown in the Spartan inventory menu to be simpler.
- Removed the MinecraftServerWebsite compatibility due to the plugin becoming outdated.
- Bedrock players will now be treated more leniently by the Lag Leniencies feature.
- The Extra Functionality system will now longer attempt to verify existing customers.
- The MorePackets check will now be more lenient with the CrackShot plugin features.
- Adjusted the settings.yml configuration system creation algorithm to be more universal.
- Some Awareness Notifications will now be sent in masses instead of one after another periodically.
- The Customer Support feature will no longer always fail when there’s an insufficient amount of data.
- Improved the Inventory utilities with new universal methods.
- Spartan will now synchronize configurations via the Cloud for certain customers.
- Tightened the log requirements of the Research Engine handler.
- The Configuration system has been made less prone to exceptions.
- The SQL feature will no longer add data to a column when not needed.
- Certain check modifications & staff chat will no longer be logged.
- Implemented new Block utilities methods to judge water-logged blocks.
- Adjusted the IrregularMovements liquids detection to judge water-logged blocks more leniently.
- Implemented new Base64 methods in the String utilities.
- Certain Cross Server Logs will require to be retrieved from similar server types.
- Removed unused variables from the Cloud feature.
- Suspected/Hacking Evidence of disabled checks will no longer be calculated or shown.
- The XRay check will still use the memory but no longer log information if disabled.
- Optimized the plugin’s configurations with faster & more consistent codes.
- Improved the plugin’s player finder tab completion handler.
- Renamed the SQL table column “spartan_build” to “plugin_version”.
- Renamed the SQL table column “date” to “creation_date”.
- Renamed the SQL table column “info” to “information” and adjusted its max length to 4096.
- Renamed the SQL table column “hack_type” to “functionality”.
- Removed the SQL table column “silent_check” and will use “cancel_violation” set to NULL to represent silent checks.
- Removed the SQL table column “detection_information” and will use “information” in its place.
- Removed the SQL table column “mined_item” and will use “functionality in its place.
- Removed the SQL table column “false_positive” and will use “type in its place.
- Introduced a new SQL table column named “player_latency”.
- Completely rewritten the Step detection with chronic value storage.
- Further improved the Customer Support command with disallowance when the Cloud feature is disabled.
- Improved the String utilities with new useful methods for the SQL & Cloud functionalities.
- Improved the SQL feature with more fail-safe methods.
- Removed some unused variables from the Player Info inventory menu.
- Changed the developer-report tab completion to customer-support.
- Files will now be used as a backup when the SQL feature fails.
- Adjusted the Move utilities jump effect motion calculation method to be more precise.
- The Notifications.cross_server_notifications option has been changed to Important.server_name with backwards compatibility.
- To combat SQL connectivity issues, the Cloud feature will now automatically synchronize logs amongst your servers.
- A new sql.yml option has been introduced to allow the replacing of special characters.
- Adjusted the Modify Server Configuration option/feature to support the new folder changes.
- Suspicion Notifications will now be distributed via the Cross Server Notifications feature.
- Most of the Cloud feature will now work without it being enabled in the config to improve the ecosystem & synchronicity.
Corrected a connection issue with the Cloud feature, updating is strongly recommended.
Made some corrections to the newly introduced Customer Support feature.
- Rewritten the Developer Report feature with a more proper functionality and renamed it to Customer Support.
- The Information Analysis object will no longer return faulty decimals for small length strings.
- Provided some additional optimisations to the Player Profile object, Damage handler & Event listeners.
- The Damage & Explosion handlers will now be applied on passengers of vehicles for more universal methods.
- Implemented additional useful methods to the Damage handler to universally support damage causes.
- The Spartan command will now show information about the gift status.
- The Information Analysis object will now further check its variables to avoid exceptions.
- Implemented additional warnings to the Spartan inventory menu.
- Discord Webhooks will now always be processed to avoid confusions.
- Major incompatibilities detectors can now be toggled via compatibility.yml.
- Discord webhooks will now execute asynchronously to not cause issues with the server.
- Implemented new useful methods to the String utilities.
- Rewritten parts of the Command Execution handler to improve its readability & performance.
- The Discord Webhooks feature will now properly handle staff chat messages.
- Slightly increased the security of the Cloud feature with more proper inputs.
- Implemented new methods in the Buffer object to have more versatility.
- Rewrote parts of the NoFall check to improve its performance, readability & accuracy.
- Moved parts of the Player Violation object off the main thread to help with performance.
- Completely rewritten how Spartan judges a player as hacker or suspected.
- Updated the Spartan inventory menu to have shorter & easier item documentations.
- Suspected players will now be treated more strictly only in checks they are suspected for.
- Balanced out the default cancel-violation thresholds.
- The AntiCheat Progress item will now work and show the correct numbers.
- Further balanced the Suspicion Notifications feature with more accurate results.
- Made the codes of the combat legitimacy identifier & Building protection more universal.
- Made the item description of the Player Info inventory menu more consistent.
- Decreased the usage of heavy Move utilities methods in the checks.
- Removed unused codes from the Hack Prevention object.
- The Vehicle Access handler will now be more strict towards hackers & suspected players.
- The IrregularMovements bouncing blocks identification has improved thus leading to less bypasses.
- Suspicion Notifications will no longer notify you about yourself as a player.
- Suspicion Notifications will no longer take place together with Detection Notifications.
Some Awareness Notifications will now be sent once instead of multiple times.
Logs:
- Mangrove-door blocks have been listed & properly handled in the Block utilities.
- The IrregularMovements horizontal-detection will now be more lenient towards increased velocity scenarios.
- Updated the in-game join notifications to repeat and be more accurate.
- Ban and Warning messages will now be treated like other messages and forcefully include the prefix in some versions.
- The NoSwing break detection will no longer target sensitive held items.
- The IrregularMovements step detection will now be more lenient when the player is falling.
- The Research Engine will now do safety checks before reading logs data to prevent algorithmic failures.
- The Research Engine will no longer confuse yaw & pitch rates of winner players versus loser players.
- The Speed water detection will now be more lenient around ice blocks.
- The IrregularMovements downwards detection will now consider more variables when checking a player.
- The Speed check’s horizontal detection will now be more lenient towards ice blocks in certain scenarios.
- The Speed water detection will now return the entity type instead of the entity object in the detection information.
- The Speed water detection will now be more lenient when the player has been recently building/placing blocks.
- The SpartanWebhooks plugin recommendation has been removed from the inventory menus as it’s no longer valid.
- The Chat Protection feature will no longer consider only decimal messages as repetitions.
- Detection Notifications will now be sent instead of Suspicion Notifications when a player is likely testing.
- The KillAura direction detection will now be more lenient around many entities.
- The Cloud feature now supports decimal versioning so features like external auto updaters can work more properly.
- The Elytra handler will now be more lenient when the player was recently gliding.
- Mangrove-door blocks have been listed & properly handled in the Block utilities.
- The IrregularMovements horizontal-detection will now be more lenient towards increased velocity scenarios.