Study the overall progress of the anti-cheat has gathered from stored when opening the Spartan inventory menu.

Knowing a player's live violations is very useful, but knowing their violation history is noticeably more useful. Read a player's violation history upon opening the Player-Info inventory menu.

Knowing a player's mining history will help you know if they were using any illegal modules such as x-ray or texture-less resource packs. Read a player's mining history upon opening the Player-Info inventory menu.

Open a menu that will list all live suspected players that are likely using hack modules, which is known based on their violation count and developer limits.

Find and punish players that used hack modules and were able to get away from the anti-cheat's violation system. Since logs are always stored, identification never goes away.

Spartan analyzes player activity and after a careful process deems players as legitimate and exempts them from all checks. This feature provides you with an inventory menu listing all legitimate players for you to study.

All Spartan reports will be stored in the logs but also added in an inventory menu, so you can take actions upon them.

Receive notifications about potential hackers automatically when you join the server, so you are always up to date.

Advance the default reporting system by moving to an inventory menu with a fully-configurable list of reasons which makethe process of reporting faster and more reliable.

Spartan comes with the Search-Engine feature that analyses logs and player activity. The Search-Engine is limited to 10MB of data, which this feature brings up to a total of 50MB.

With this feature you are granted permission to use all the locked inventory-menu items that redirect you to this feature documentation menu.

Join the official Discord server via the invite https://vagdedes.com/discord and receive a unique role that offers several cool features, such as dedicated support, extra permissions, early product trials, and many more.

This feature gives you the ability to completely hide the Spartan command and replace it with a help message found in the plugin's configuration.

Every Spartan version is by default limited to a few IPs & ports. This is made to prevent customers from sharing their software copy with multiple users. With this feature, you bypass this limitation with a total of infinite IPs per version.

No longer worry about low violation false positives with this feature, because it will pick the perfect timing and configure any crucial variables for you.

The anti-cheat will attempt to prevent a hack module if the cancel violation is reached/surpassed. This variable is refreshed every 1 hour based on your configuration & server performance, which this feature brings the delay down to just 30 minutes.

Spartan supports cross-server notifications by temporarily storing messages on the Cloud and sharing them with your servers. They are refreshed and sent every 30 seconds, which this feature brings the delay down to just 15 seconds.

Spartan is able to identify Bedrock Edition players and exempt them from being checked. With this feature, the anti-cheat will adjust its detections and include such players to its checks, allowing for higher security.

Spartan offers a cross server notifications feature to distribute notifications across a network. With this feature, you will also be able to distribute report command & staff chat messages for a more organised & professional experience.

This feature automatically sends redundant false positives to the Cloud, which helps the development team correct them, but also helps improve stability for other customers. It doesn't collect any private information and is purely used for issue resolution & stability purposes.

This feature is used manually to deliver useful information to the development team for specific issues. It delivers information such loaded plugins, compatible & incompatible plugins, violation logs, TPS stability data, etc. It doesn't collect any private information and is purely used for issue resolution purposes.

This feature automatically identifies malfunctioning checks by analysing reports made by customers. It then proceeds to notify them about potental instabilities, ensuring they are aware of a situation before damage is caused. It doesn't collect any private information and is purely used for awareness purposes.

This feature automatically checks the plugin's versions and compares it to the Cloud database. This allows the ability to notify the user when they are using an outdated plugin version, because updating often is important. It doesn't collect any private information and is purely used for awareness purposes.

The development team is given the ability to manually queue configuration changes for the user base, either individually or in masses. This feature helps prevent major issues/spam, correct temporary/semi-permanent issues, but also save time by not always explaining to the user what & when to change something in the plugin configuration. It doesn't collect any private information and is purely used for issue resolution & ease of use purposes.

The development team is given the ability to temporarily/semi-permanently disable detections of the plugin for a user or masses. This feature helps prevent major issues/spam, correct temporary/semi-permanent issues, but also save time by not requiring more hardcore code solutions. It doesn't collect any private information and is purely used for issue resolution & ease of use purposes.

This feature automatically sends specific plugin notifications to the Cloud, which are then distributed to other servers of the user running the same plugin version. Since this feature is internet-wide, you can share notifications between different server network/proxies and without the requirement of hosting it on your side. It doesn't collect any private information, its data is periodically & automatically cleared, and is purely used for ease of use purposes.

In order to help users find answers to their question easier, saving time for both the user & support team, this feature has been implemented. Simply use the FAQ command in your server and type in your question. The system will attempt to find a few relevant answers, and if not, suggest them to the development team. It doesn't collect any private information and is purely used for ease of use purposes.

When the plugin has significant evidence a player is using a modified client to gain an unfair advantage against legitimate players, it stores them on the Cloud. This list of stored punished players is then used in other plugins to prevent these players from joining if the system believes they are trying to evade their punishment. This feature may collect encrypted player IP addresses for the purpose of comparing them when they join a server, and is purely used for punishment evasion purposes.

This feature limits a user's IP & Port count to a specific amount. This is mainly to protect against potential piracy/redistribution, but may also be used to monetise our business. These limits can be manually updated by the support team, and you are free to contact them when you encounter such an issue. This feature may collect encrypted server IP addresses to use as a way to identify a user's servers, and is purely used for anti-piracy, anti-redistribution & monetisation purposes.

This feature automatically collects information about your server such as CPU cores, RAM megabytes, plugin count, server version, server description, server port, etc. The collected data is then used to build statistics that helps us identify issues, monetise our business, prevent piracy/redistribution & show our achievements. This feature may collect encrypted server IP addresses to use as a way to distinguish servers from each other, and is purely used for issue resolution, anti-piracy, anti-redistribution & monetisation purposes.