Version Compatibility
AAC is a complete anti-cheat solution for servers blocking every major combat hack, and many others. Here is a video showing AAC vs. the hacked client Wolfram
There are videos showing client X bypassing AAC!
It is unlikely the video was made with the latest AAC and the fully default config. I urge you to test any "bypassing" clients on test.kons.co as that is the only public server with a guaranteed default config and the latest public version of AAC. If it bypasses there, you have my attention.
But wait, I heard that AAC's Killaura detection is easily bypassed!
That strongly depends on how you define "bypassed". What you won't find if you're running AAC is any killaura that gives the user a significant advantage. Some good "smooth aim" or "triggerbot" cheats are undetectable (heuristics are trying its best), no matter what anyone tells you. It's also basically useless, no matter what anyone tells you.
Features
CONFIGURABLE - AAC has a comprehensive configuration file. You can enable or disable any component in AAC. You can change how each one works and you can change the thresholds they work with. If you want unnoticeable, automated hack detection, AAC can do that. If you want tons of information to report to staff to catch hackers faster, AAC can do that too. If you have a lot of staff, and want something to just alert staff, AAC can do that as well. Want to see the config for yourself?
Current Config: https://gist.github.com/konsolas/b283c1abcad3fa214d1788769c7c2db1
Want to execute commands/punishments based on certain conditions? Check out Conditional Commands.
AUTOMATED - AAC has a fully automated punishment system. After AAC is certain a player is hacking (the lenience can be configured), the player is automatically kicked. After a configurable number of kicks, that player is automatically banned. Both auto-kick and auto-ban can be turned off completely or modified for your server's existing punishment system.
VERBOSE - AAC can give detailed information about suspected players to staff. Staff with the permission ‘AAC.notify’ are notified whenever a player is suspected of hacking, but has not been automatically kicked. AAC saves a log file of every failed check, kick and ban. If a player gets kicked, the log file will show the details of why they were kicked. This enables staff to check all the reasons a player was kicked for. Staff with the permission AAC.verbose get to see every detail of AAC's internal workings (also must be enabled in config).
LIGHTWEIGHT - AAC is relatively lightweight. All entities used are client-side, meaning the server never needs to process them. However, keep in mind that AAC does need to process every movement by every player on the server, so it will be by no means completely unnoticeable.
KILLAURA DETECTION - AAC's Killaura detection doesn't "suck". AAC has over 100 intricate methods of detecting Killaura and it successfully blocks advanced clients that give a significant advantage. Hackers are detected even if they limit their FOV, hit with random intervals or try any other tricks. Practically every public client and many private clients in existence are blocked. If it isn't, report it!
GUI - AAC has an easy to use GUI so that your staff can easily manage output sent to them, check statistics on possible hackers, and enable or disable checks in real time, whilst the server is running.
ANTI-SPAM - The Spam check in AAC is most certainly not an afterthought. It's both less intrusive and faster than many other plugins. Despite not being a solution for ads/swear or the like, it really is an effective solution to stop spammers.
Still not convinced?
Here’s the IP for a test server where you can join and try out AAC for yourself.
Test Server: test.kons.co
Dependencies
Java
To run AAC, you should be using a Spigot server with Java 8 (Java 7 not supported)
Server Version
AAC v4.0+ supports Spigot versions 1.8.8, 1.12.2, 1.13.2, 1.14.4 (ViaVersion supported)
- AAC is only compatible with Spigot 1.8.8, 1.12.2, 1.13.2, 1.14.4, 1.15.1
- AAC does not and will never support 1.7 or earlier versioning.
- Do not use a review to report bugs/errors. Those will be ignored!
- For feature requests and reporting errors, bugs and bypasses, utilize the Official Issue Tracker.
- When reporting bugs/bypasses, show video from the official test server: test.kons.co
- For simple questions about AAC, ask in the resource discussion.
- For piracy and resource ownership related issues, PM Konsolas.
- For general discussion and support join our Discord group
AAC is a complete anti-cheat solution for servers blocking every major combat hack, and many others. Here is a video showing AAC vs. the hacked client Wolfram
There are videos showing client X bypassing AAC!
It is unlikely the video was made with the latest AAC and the fully default config. I urge you to test any "bypassing" clients on test.kons.co as that is the only public server with a guaranteed default config and the latest public version of AAC. If it bypasses there, you have my attention.
But wait, I heard that AAC's Killaura detection is easily bypassed!
That strongly depends on how you define "bypassed". What you won't find if you're running AAC is any killaura that gives the user a significant advantage. Some good "smooth aim" or "triggerbot" cheats are undetectable (heuristics are trying its best), no matter what anyone tells you. It's also basically useless, no matter what anyone tells you.
Features
CONFIGURABLE - AAC has a comprehensive configuration file. You can enable or disable any component in AAC. You can change how each one works and you can change the thresholds they work with. If you want unnoticeable, automated hack detection, AAC can do that. If you want tons of information to report to staff to catch hackers faster, AAC can do that too. If you have a lot of staff, and want something to just alert staff, AAC can do that as well. Want to see the config for yourself?
Current Config: https://gist.github.com/konsolas/b283c1abcad3fa214d1788769c7c2db1
Want to execute commands/punishments based on certain conditions? Check out Conditional Commands.
AUTOMATED - AAC has a fully automated punishment system. After AAC is certain a player is hacking (the lenience can be configured), the player is automatically kicked. After a configurable number of kicks, that player is automatically banned. Both auto-kick and auto-ban can be turned off completely or modified for your server's existing punishment system.
VERBOSE - AAC can give detailed information about suspected players to staff. Staff with the permission ‘AAC.notify’ are notified whenever a player is suspected of hacking, but has not been automatically kicked. AAC saves a log file of every failed check, kick and ban. If a player gets kicked, the log file will show the details of why they were kicked. This enables staff to check all the reasons a player was kicked for. Staff with the permission AAC.verbose get to see every detail of AAC's internal workings (also must be enabled in config).
LIGHTWEIGHT - AAC is relatively lightweight. All entities used are client-side, meaning the server never needs to process them. However, keep in mind that AAC does need to process every movement by every player on the server, so it will be by no means completely unnoticeable.
KILLAURA DETECTION - AAC's Killaura detection doesn't "suck". AAC has over 100 intricate methods of detecting Killaura and it successfully blocks advanced clients that give a significant advantage. Hackers are detected even if they limit their FOV, hit with random intervals or try any other tricks. Practically every public client and many private clients in existence are blocked. If it isn't, report it!
GUI - AAC has an easy to use GUI so that your staff can easily manage output sent to them, check statistics on possible hackers, and enable or disable checks in real time, whilst the server is running.
ANTI-SPAM - The Spam check in AAC is most certainly not an afterthought. It's both less intrusive and faster than many other plugins. Despite not being a solution for ads/swear or the like, it really is an effective solution to stop spammers.
Still not convinced?
Here’s the IP for a test server where you can join and try out AAC for yourself.
Test Server: test.kons.co
Dependencies
Java
To run AAC, you should be using a Spigot server with Java 8 (Java 7 not supported)
Server Version
AAC v4.0+ supports Spigot versions 1.8.8, 1.12.2, 1.13.2, 1.14.4 (ViaVersion supported)
![AACBungeeConnect [AAC] [AACAdditionPro]](/data/resource_icons/2/2619.jpg?1718365282){kind=icon}
