The official Minecraft 1.15 compatibility update is coming! Some servers already appear to be using AntiAura on 1.15 without reported issues, however I cannot guarantee stability.
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Click here to learn about AntiAura's BungeeCord compatibility.
----------------------------------------------------------------------------------------------------------------------------------------------------------------
The little numbers in brackets correspond to more information in the "further detail" section below. (1)
Welcome to AntiAura!
AntiAura is the longest standing premium anti-cheat plugin on the market, giving users an effective anti-cheat plugin, without the high price(2). AntiAura offers a high level of protection from almost all detectable hacks on your server, and even blocks some hacks which can't be detected(3).
Version compatibility
- AntiAura will work with any Spigot (or PaperSpigot) server running Minecraft 1.8 or above.
- TrollPotion and KillPotion blockage only works on servers running Minecraft 1.12 or above.
- PaperSpigot users are recommended to use PaperSpigot's in-built Anti-XRay and disable the X-Ray check in AntiAura's configuration.
What is AntiAura?
AntiAura is one of the first ever complete Anti-Cheat solutions, blocking all major Minecraft hacks, including KillAura, Flight, Speed, and a lot more. It has hundreds of users and some of the most advanced detection out there(4)!
AntiAura is specifically designed for Survival, PVP, and KitPVP servers(5), boasting good KillAura detection as well as focusing on fast In-PVP hack detection(6).
Show me a video!
I have a problem with a hack. Does AntiAura block it?
Open the spoiler to view the list of hacks blocked by AntiAura!
This list is not complete or exhaustive. New hacks and new names for old hacks are being created all the time. Just because a hack is not listed here doesn't necessarily mean it isn't blocked. If in doubt, send me a PM.
PVP Hacks:
Forcefield/Killaura.
AutoClicker/FastClick.
ForcefieldLegit/KillauraLegit, on most clients.
Aimbot/ClickAimbot.
AntiKnockback/Unpushable.
AutoBow/FastBow.
Criticals.
AutoSoup.
Regen.
Reach.
NoPotion.
PotionSaver.
AntiFire.
TP-Aura (ranged reach attack).
TPAura (an attack where the hacker teleports around the target).
Render hacks:
ChestESP (MC 1.8+ only).
X-Ray (MC 1.8+ only).
Tracers/Minimaps/ESP
Freecam (Entities and tile entities only. Players can still see ordinary blocks).
Anti-Blind (Entities only. Players can still see blocks).
Movement hacks:
ElytraFly.
ElytraDistance (makes sure a player can't fly further than a legit player from their take off location).
Flight.
Glide.
Speed.
Step.
HighJump.
Spider.
NoFall.
Blink.
Teleport.
DontFall.
NoClip (up).
InventoryMove.
Some versions of Derp.
CheckerClimb.
ScaffoldWalk.
Tower
FastLadder.
Jesus.
Sneak.
Phase.
BoatFly.
CheckerClimb.
Towers.
NoSlowdown
NoWeb
Block hacks:
GhostHand.
FastBreak.
Nuker.
FastPlace.
Misc:
NoSwing.
Basic protection from Spambots.
Timer.
A few notes about detection:
PVP Hacks:
Forcefield/Killaura.
AutoClicker/FastClick.
ForcefieldLegit/KillauraLegit, on most clients.
Aimbot/ClickAimbot.
AntiKnockback/Unpushable.
AutoBow/FastBow.
Criticals.
AutoSoup.
Regen.
Reach.
NoPotion.
PotionSaver.
AntiFire.
TP-Aura (ranged reach attack).
TPAura (an attack where the hacker teleports around the target).
Render hacks:
ChestESP (MC 1.8+ only).
X-Ray (MC 1.8+ only).
Tracers/Minimaps/ESP
Freecam (Entities and tile entities only. Players can still see ordinary blocks).
Anti-Blind (Entities only. Players can still see blocks).
Movement hacks:
ElytraFly.
ElytraDistance (makes sure a player can't fly further than a legit player from their take off location).
Flight.
Glide.
Speed.
Step.
HighJump.
Spider.
NoFall.
Blink.
Teleport.
DontFall.
NoClip (up).
InventoryMove.
Some versions of Derp.
CheckerClimb.
ScaffoldWalk.
Tower
FastLadder.
Jesus.
Sneak.
Phase.
BoatFly.
CheckerClimb.
Towers.
NoSlowdown
NoWeb
Block hacks:
GhostHand.
FastBreak.
Nuker.
FastPlace.
Misc:
NoSwing.
Basic protection from Spambots.
Timer.
A few notes about detection:
- KillAura detection does not use NPCs. Killaura detection works by watching player behavior. The longer a PVP fight is, the higher the chance of a killaura detection occurring. The worst servers for detection are servers where players die in few hits hits, because this does not give AntiAura much time to study the players' behavior. If you have a server where PVP fights end very quickly, I recommend you change the killaura configuration and lower the thresholds.
- ElytraDistance is not as precise with rocket propelled Elytra at the moment, however ElytraFlight is. In other words, if a player uses a rocket, ElytraDistance will be disabled until the player lands.
- AntiAura blocks hacks such as ESP, ChestESP, and X-Ray by hiding the entities or blocks that you can't see. This was what I meant on the first paragraph when I say I "block hacks that can't be detected". I can block ChestESP, however I can't detect it, and therefore a player will never be detected or kicked for using it.
- The hack detection names are as accurate as they can be, however it is impossible to detect precisely which hack a client is using. On some clients for example, Flight can be detected as NoFall (because the Flight tries to fake ground packets and that's what NoFall does too).
- At this moment in time, FastBreak protection is not able to prevent clients breaking blocks slightly faster, say 10%. The main reason for this is that AntiAura has more time spent on PVP detection as opposed to world or block related detection.
- AntiFire and AntiPotion will, by default, require the player to lose their effect multiple times. You can configure it not to, however if you did that, a simple /heal when you are on fire would put the fire out and incorrectly detect you for AntiFire.
- There are many clients who claim to have a Criticals hack which actually just jump up and down. In a lot of these cases, a vanilla Minecraft client jumping up and down with well-times hits can often get more critical hits than the hacked client can! If you have a client with Criticals that just jumps up and down and it isn't detected, that doesn't mean Criticals detection isn't working. It just means you're using a useless client.
- The X-Ray check successfully blocks the vast majority of X-Ray, and the performance is excellent, however it may use more bandwidth than other X-Ray blocking plugins. I'll get around to improving this ASAP!
---------------------------------------------------------------------------------------------
Is AntiAura false positive free?
There currently aren't any "100% false positive free" Anti-Cheat plugins on the market. AntiAura has a detailed, simple to use configuration that you can modify ingame(7). AntiAura's default configuration should give enough leniency for all servers, however some servers may wish to make some checks more lenient, which can be done with the configuration(8).
Advantages of AntiAura:
Command-based configuration
Do you just hate messing around with configuration files and reloading your configuration every time you want to make a change? Me too! That is why AntiAura allows you to modify almost all of it's configurable parameters in-game with commands! With one simple command, you can modify configuration values and test out the results immediately! You can also allow your administrators to configure AntiAura for you, without needing to give them console access(7/8)!
Built for PVP/KitPVP servers
AntiAura is built for PVP/KitPVP servers. A lot of time has been made making and perfecting killaura checks, and over a year has been spent on perfecting in-PVP hack detection(5).
No notifications, unless you want them
Ever hated those annoying spammy messages telling you someone may be hacking? Luckily for you, AntiAura doesn't have any! It will only display messages when it is certain of somebody is hacking and has already kicked them. Of course, you can configure it to notify you or install another plugin to notify you, if you wish(9)!
No bots
AntiAura's killaura checks work by studying player behaviour. AntiAura does NOT use bots to detect killaura(10).
BungeeCord compatible
Do you want to punish players from your BungeeCord ban plugin? Well, now you can! Click here to read all about AntiAura's BungeeCord compatibility.
Quality support
Do you have a problem with the plugin? Feel free to send a PM asking any questions! Support requests are typically answered in less than two days, and the majority of problems encountered are usually solved.
---------------------------------------------------------------------------------------------
Why should I buy AntiAura?
Affordable -
AntiAura is affordable, at only £7. For this cost, almost all hacks on your Minecraft server will be blocked. All updates are completely free, so you will be protected against the latest hacks(2)!
Advanced -
AntiAura is the first ever Anti-Hacking plugin to effectively block important hacks like KillAura, AntiKnockback, and more. It has had the most time to perfect it's techniques and a high amount of users to do so, making PVP hack detection fast and efficient(11).
Sensitive -
Because AntiAura just punishes the hackers, this allows it to be more sensitive plugins that can send notifications. This allows me to implement forcefield checks based on studying player behaviour, as well as making checks more sensitive(9).
Compatible -
AntiAura is compatible with almost all existing plugins on your server, including launchpads, and more! Make sure to read the incompatibilities list before buying.
Configurable -
AntiAura gives you over 100 configuration options, so you can modify the punishments for hacking, or tweak hack detection as you wish! If you think a large configuration is too difficult, AntiAura is split into two configurations! This makes AntiAura easier to configure, while keeping a wide variety of possibilities(7).
Silent -
AntiAura will run automatically in the background, detecting hacks on your Minecraft server! You won't even notice it - Until it kicks someone for hacking.
Optimized -
The truth is, there is no "light weight" anti-cheat. Any anti-cheat plugin is going to cost you some performance due to the amount of data it has to store and analyze. However, AntiAura processes as much as it can (which is a lot) asynchronously, which makes AntiAura very efficient(12).
---------------------------------------------------------------------------------------------
Compatibility
AntiAura has special code to make it compatible with some plugins.
- McMMO.
- MagicSpells.
- Magic (Please note that this is not fully tested. Please report problems)
- CrackShot.
- Heroes.
- Launchpad plugins.
- ViaVersion (No special code to make it compatible, just listing it here so people don't keep spamming me about it).
Commands
- /areload - Reloads most configuration values of AntiAura!
- /atps - Get the actual TPS right now, not the average TPS.
- /anotify - Get notified of all drag-backs in your server.
- /aconfig - Modify AntiAura's configuration with in-game commands. Click here to read a tutorial on how to use it.
- /aconfiga - The same as /aconfig, however it modifies the advanced configuration.
Even if CommandPermissions is false, permission is still needed to use the /aconfig command.
Permissions
- antiaura.bypass - Don't get kicked by any of AntiAura's checks.
- antiaura.reload - Use the /areload command.
- antiaura.command - Use AntiAura's commands.
- AntiAuraAPI.ViolationEvent for an event when players are detected as hacking.
- AntiAuraAPI.DragBackEvent for an event where players are dragged back.
- AntiAuraAPI.API for various methods. API features are added by request.
Support
While support is available all week, expect quicker replies on Weekends and Wednesday.
- If you have a query, question, problem or bug report, please click here to PM me. PMs receive replies quicker than Discord.
- AntiAura also has a Discord server, however replies may take longer.
Installation
- Click here to download ProtocolLib. AntiAura requires ProtocolLib to be able to run. After downloading, put it into your plugins folder.
- Download "AntiAura.jar" from this resource page and put it into your plugins folder.
- Restart your server - AntiAura will be enabled!
- (Optional) If the ProtocolLib you downloaded did not contain "+ PacketWrapper" in the name, you may install PacketWrapper to block ChestESP and X-Ray hacks. You can also read instructions on how to bundle PacketWrapper into ProtocolLib.
- Make sure you have no incompatiblities (read here, or PM me if unsure). Also, if your server runs Minecraft 1.11 or newer, please make sure your server has Java 8. This is a requirement by ProtocolLib, not AntiAura.
- Read the installation instructions and realize that you need ProtocolLib installed to also run AntiAura.
- You need to have basic knowledge to modify simple configuration values, just in case the plugin does not work 100% out of the box for you.
- There won't be any refunds after you purchase. If the plugin somehow doesn't work this is either the users' fault or their server setup.
Are you interested in learning more about killaura detection? How it works, and how you can help AntiAura to detect killaura better on your server? If you are, please click on the spoiler below!
AntiAura analyses player's fighting in order to detect killaura. Some plugins use bots (these are invisible fake players which surround the player, and if the player hits them they are detected) to detect killaura, and AntiAura does not.
The main reason AntiAura doesn't use bots is simply that, while they provide quick detection for clients with basic killauras, they aren't so effective against more advanced killauras, while adding potential glitches to the server.
For example (and this is a very simplistic explanation), a player could turn their head quickly to try to hit an opponent and hit one of the invisible bots instead, causing a hit to not be registered on the server.
Now we've talked about why AntiAura doesn't use bots, let's talk about what it does use. AntiAura looks at parameters such as...
Now naturally, the main advice I wish to discuss here is simple: AntiAura needs time to collect data. In other words, the longer a player is in a battle, the better AntiAura is able to detect their killaura. Some checks, such as the Consistency check, only even start analysing after the player has hit an entity 17 times.
There are various behaviours which you should encourage in your fights to ensure better killaura detection:
There have been known to be KitPVP servers in which opponents are literally killed in 3 hits, and that sort of combat was not the best to be able to detect Killaura on that server.
Also, please keep in mind that, while complicated, the configuration is there for a reason. Use it!
The main reason AntiAura doesn't use bots is simply that, while they provide quick detection for clients with basic killauras, they aren't so effective against more advanced killauras, while adding potential glitches to the server.
For example (and this is a very simplistic explanation), a player could turn their head quickly to try to hit an opponent and hit one of the invisible bots instead, causing a hit to not be registered on the server.
Now we've talked about why AntiAura doesn't use bots, let's talk about what it does use. AntiAura looks at parameters such as...
- Accuracy of hits compared to misses
- Angle of hits (in other words, so you can't hit enemies behind you)
- Position of hits on the opponent (is a player consistently hitting the head, or the feet?)
- Head rotation before hits
- Distance away from the player when hitting opponents
Now naturally, the main advice I wish to discuss here is simple: AntiAura needs time to collect data. In other words, the longer a player is in a battle, the better AntiAura is able to detect their killaura. Some checks, such as the Consistency check, only even start analysing after the player has hit an entity 17 times.
There are various behaviours which you should encourage in your fights to ensure better killaura detection:
- Longer fights, especially in PVP. You don't want players to kill another player in 3 hits, or each and every mob in 1 hit - otherwise, where is the data for AntiAura to analyse?
- Fights that don't have pauses in them. Some checks, such as Accuracy, will give players leniency over time, and so players pausing and not hitting for a while can cause AntiAura to not detect as efficiently. Please keep in mind this rule only applies to some checks.
- If you can, have players fighting multiple entities. While AntiAura can detect killaura in 1V1 duels, It is easier for a killaura to calibrate itself to a single enemy and make itself harder to detect. In testing, AntiAura detects killaura quicker when fighting multiple enemies.
- Don't test killaura detection against a static player who isn't fighting back. Killaura detection works better when the player is fighting an opponent that is moving.
There have been known to be KitPVP servers in which opponents are literally killed in 3 hits, and that sort of combat was not the best to be able to detect Killaura on that server.
Also, please keep in mind that, while complicated, the configuration is there for a reason. Use it!
If you were wondering what all the small numbers such as (1),(2),(etc) were, they are further explanations and detail about parts of the description.
If you like detail, open the spoiler below!
If you want to view this spoiler on another tab or window while reading the overview, here you go: https://www.spigotmc.org/resources/antiaura-premium-anti-cheat-plugin.1368/update?update=4745
(1) You found this section! Hooray!
(2) AntiAura is the first paid anti-cheat plugin on Spigot that is still maintained. I am not aware of any paid anti-cheat plugins before the release of AntiAura, however there is no way to verify this (as inactive premium resources are removed).
Partly because I was once a poor, 12-year-old server owner myself, I have always striven to keep AntiAura's price affordable. The plugin was originally available for $5, then £5, and now £7. This, in comparison, is cheaper than most of the other mainstream anti-cheat plugins. At the time of writing (02/07/2019), Spartan costs 20EUR and Reflex costs 10EUR.
(3) There are some hacks that cannot be detected. For example, there is a hack to see players through walls. As this is simply a render hack, then it is impossible for the server to detect this behaviour and kick the player. However, it is possible for AntiAura to hide the player (or entity) on the other side of the wall, so that the hacked client cannot see players through walls.
(4) AntiAura has had over two thousand people purchase the plugin, and this has allowed time to develop and improve many of it's checks. There are many anti-cheat plugins out there, and what is best is always a matter of opinion. AntiAura's hack detection has always been kept as advanced as possible, with advanced features such as checks being run async and hack detection that works based upon observing player behaviour.
(5) AntiAura originally started just to block Killaura - hence the name: AntiAura. Over time, AntiAura spread into blocking many PVP-related hacks, such as antiknockback, tracers, noswing, fastclick and more. Finally, AntiAura took the step into becoming a complete anti-cheat solution by adding blockage of hacks such as Flight, Speed, FastPlace, etc. However, AntiAura's primary focus has always been upon the combat checks.
(6) AntiAura has over 5 checks with the aim to catch combat and killaura-related hacks. There are no foolproof checks, however these checks aim to catch a wide range of clients and combat hacks.
(7) AntiAura's configuration can be modified ingame with the /aconfig and /aconfiga commands. AntiAura has two configuration files: a simple configuration, and an advanced configuration. This makes AntiAura easy to configure, however also allows server owners to fine-tune the checks in the advanced configuration if they wish.
(8) Making a check more lenient is very simple - you simply adjust the "Strictness" value for that check. For example, if the Speed check was too strict, I would type "/aconfig Speed Strictness" - this would say something like "The Strictness value for Speed is 6". I could then type "/aconfig Speed Strictness 5" to make the check more lenient.
(9) By default, AntiAura will kick players instantly after they appear to be hacking. This can actually allow me to make AntiAura more sensitive to kick players faster compared to plugins that send notifications, as server owners generally don't want false notifications. This means that AntiAura by default generally kicks players faster because it doesn't send notifications. That said, all commands executed when a hack is detected are 100% configurable.
(10) AntiAura's killaura checks work by studying player behaviour, rather than using bots. This has both advantages and disadvantages: the advantage is that players do not experience any disruption or strange glitches during combat, which can occur with some plugins that use bots. The disadvantage is that players generally need to be in continuous combat for a period of time for non-bot checks to be the most effective.
(11) Something I haven't really spoken about yet was that AntiAura was actually one of the very first publicly available plugins that was designed to automatically detect hacks such as killaura and anti-knockback. Back in the olden days of Minecraft, these hacks were generally considered difficult or impractical to block, and for that reason not included in plugins such as NoCHeatPlus.
(12) A complete anti-cheat solution often (especially if your server has, say, 100+ players online) has thousands of tasks to do every second. It has to track player movement, interactions, packets, and so on. It then has to store all of this data for a certain period of time, and then compare it to future data to check if the player is hacking. There are no "light weight" complete anti-cheat solutions.
One of the main ways AntiAura runs smoothly on servers is by running tasks Asynchronously. This means that for many of the more performance-heavy checks, the "compare it to future data to check if the player is hacking" part occurs on a different thread. If you are interested in how this works, please read : https://en.wikipedia.org/wiki/Asynchrony_(computer_programming) and https://visualstudiomagazine.com/articles/2011/03/24/wccsp_asynchronous-programming.aspx
To quote the second article, "The main benefits one can gain from using asynchronous programming are improved application performance and responsiveness".
(1) You found this section! Hooray!
(2) AntiAura is the first paid anti-cheat plugin on Spigot that is still maintained. I am not aware of any paid anti-cheat plugins before the release of AntiAura, however there is no way to verify this (as inactive premium resources are removed).
Partly because I was once a poor, 12-year-old server owner myself, I have always striven to keep AntiAura's price affordable. The plugin was originally available for $5, then £5, and now £7. This, in comparison, is cheaper than most of the other mainstream anti-cheat plugins. At the time of writing (02/07/2019), Spartan costs 20EUR and Reflex costs 10EUR.
(3) There are some hacks that cannot be detected. For example, there is a hack to see players through walls. As this is simply a render hack, then it is impossible for the server to detect this behaviour and kick the player. However, it is possible for AntiAura to hide the player (or entity) on the other side of the wall, so that the hacked client cannot see players through walls.
(4) AntiAura has had over two thousand people purchase the plugin, and this has allowed time to develop and improve many of it's checks. There are many anti-cheat plugins out there, and what is best is always a matter of opinion. AntiAura's hack detection has always been kept as advanced as possible, with advanced features such as checks being run async and hack detection that works based upon observing player behaviour.
(5) AntiAura originally started just to block Killaura - hence the name: AntiAura. Over time, AntiAura spread into blocking many PVP-related hacks, such as antiknockback, tracers, noswing, fastclick and more. Finally, AntiAura took the step into becoming a complete anti-cheat solution by adding blockage of hacks such as Flight, Speed, FastPlace, etc. However, AntiAura's primary focus has always been upon the combat checks.
(6) AntiAura has over 5 checks with the aim to catch combat and killaura-related hacks. There are no foolproof checks, however these checks aim to catch a wide range of clients and combat hacks.
(7) AntiAura's configuration can be modified ingame with the /aconfig and /aconfiga commands. AntiAura has two configuration files: a simple configuration, and an advanced configuration. This makes AntiAura easy to configure, however also allows server owners to fine-tune the checks in the advanced configuration if they wish.
(8) Making a check more lenient is very simple - you simply adjust the "Strictness" value for that check. For example, if the Speed check was too strict, I would type "/aconfig Speed Strictness" - this would say something like "The Strictness value for Speed is 6". I could then type "/aconfig Speed Strictness 5" to make the check more lenient.
(9) By default, AntiAura will kick players instantly after they appear to be hacking. This can actually allow me to make AntiAura more sensitive to kick players faster compared to plugins that send notifications, as server owners generally don't want false notifications. This means that AntiAura by default generally kicks players faster because it doesn't send notifications. That said, all commands executed when a hack is detected are 100% configurable.
(10) AntiAura's killaura checks work by studying player behaviour, rather than using bots. This has both advantages and disadvantages: the advantage is that players do not experience any disruption or strange glitches during combat, which can occur with some plugins that use bots. The disadvantage is that players generally need to be in continuous combat for a period of time for non-bot checks to be the most effective.
(11) Something I haven't really spoken about yet was that AntiAura was actually one of the very first publicly available plugins that was designed to automatically detect hacks such as killaura and anti-knockback. Back in the olden days of Minecraft, these hacks were generally considered difficult or impractical to block, and for that reason not included in plugins such as NoCHeatPlus.
(12) A complete anti-cheat solution often (especially if your server has, say, 100+ players online) has thousands of tasks to do every second. It has to track player movement, interactions, packets, and so on. It then has to store all of this data for a certain period of time, and then compare it to future data to check if the player is hacking. There are no "light weight" complete anti-cheat solutions.
One of the main ways AntiAura runs smoothly on servers is by running tasks Asynchronously. This means that for many of the more performance-heavy checks, the "compare it to future data to check if the player is hacking" part occurs on a different thread. If you are interested in how this works, please read : https://en.wikipedia.org/wiki/Asynchrony_(computer_programming) and https://visualstudiomagazine.com/articles/2011/03/24/wccsp_asynchronous-programming.aspx
To quote the second article, "The main benefits one can gain from using asynchronous programming are improved application performance and responsiveness".
Common issues:
My players are being kicked without using hacks!
Please read this. It contains some basic information about configuring. You will need to use the configuration to lower false positives.
AntiAura is lagging my server!
For large servers who would like to optimize AntiAura as much as possible, please read this guide. It should tell you most things you want to know about reducing as much lag as you can.
I have another issue with the plugin!
Please read the FAQ before contacting me:
What does the config look like?
Here is the config from AntiAura 10.94: https://pastebin.com/g56Ejzwz
Configurations never change drastically, so use this as a rough idea as to what the configuration will look like.
Why is AntiAura not showing up in my plugins list?
Make sure that you have got ProtocolLib installed to run the plugin. You can download the correct version from http://endcraft.net/deps. There should be no other reason the plugin does not load. If there are any errors on the console that prevent the plugin from loading, contact me and send me the error.
Why is AntiAura not detecting anyone at all?
If you have done a /reload, make sure that all players on the server log out and re-join. If they don't, AntiAura will not know they are there, and will not check them for hacks.
Why is AntiAura detecting legitimate players as hackers?
Depending on the hack, there are always configuration options inside the configuration to make detection weaker so to not catch legitimate players. The default configuration should not get any false positives, but if it does, the configuration is incredibly detailed and will help you solve them.
I use launch pads on my server, but players keep getting dragged back when they use them.
If you use launch pads, enable "FlightCompatibility" in the configuration. This will temporarily disable flight detection when a player is given a large velocity by another plugin (for example, that of a launch-pad). If the launch pad launches them far away, you will also need to enable "SpeedCompatibility" so that they do not get dragged back for moving too fast.
If these options are enabled and people still get dragged back, please report it to me as a bug.
AntiAura should take into account of velocities automatically. If a player is dragged back for this sort of issue, please PM me.
More FAQ coming soon. Please ask me a question via PM for me to put it here.
What other AntiCheat plugins can you recommend?
NoPos (free) - Prevent people from viewing their location by pressing F3 on the keyboard!
NoCheatPlus (free) - Blocks the majority of movement and block-related hacks. Although AntiAura mostly replaces it, it still is a possible alternative.
AntiCriticalCheat (paid) - A sort-of (possibly expensive) add-on to AntiAura, which blocks criticals much better than I do, and blocks AutoFish (whatever that is).
Any other plugins that may go well with AntiAura?
HideAntiCheat (free) - Hides Anti-Cheat plugins from users without permissions.
Here is the config from AntiAura 10.94: https://pastebin.com/g56Ejzwz
Configurations never change drastically, so use this as a rough idea as to what the configuration will look like.
Why is AntiAura not showing up in my plugins list?
Make sure that you have got ProtocolLib installed to run the plugin. You can download the correct version from http://endcraft.net/deps. There should be no other reason the plugin does not load. If there are any errors on the console that prevent the plugin from loading, contact me and send me the error.
Why is AntiAura not detecting anyone at all?
If you have done a /reload, make sure that all players on the server log out and re-join. If they don't, AntiAura will not know they are there, and will not check them for hacks.
Why is AntiAura detecting legitimate players as hackers?
Depending on the hack, there are always configuration options inside the configuration to make detection weaker so to not catch legitimate players. The default configuration should not get any false positives, but if it does, the configuration is incredibly detailed and will help you solve them.
I use launch pads on my server, but players keep getting dragged back when they use them.
If you use launch pads, enable "FlightCompatibility" in the configuration. This will temporarily disable flight detection when a player is given a large velocity by another plugin (for example, that of a launch-pad). If the launch pad launches them far away, you will also need to enable "SpeedCompatibility" so that they do not get dragged back for moving too fast.
If these options are enabled and people still get dragged back, please report it to me as a bug.
AntiAura should take into account of velocities automatically. If a player is dragged back for this sort of issue, please PM me.
More FAQ coming soon. Please ask me a question via PM for me to put it here.
What other AntiCheat plugins can you recommend?
NoPos (free) - Prevent people from viewing their location by pressing F3 on the keyboard!
NoCheatPlus (free) - Blocks the majority of movement and block-related hacks. Although AntiAura mostly replaces it, it still is a possible alternative.
AntiCriticalCheat (paid) - A sort-of (possibly expensive) add-on to AntiAura, which blocks criticals much better than I do, and blocks AutoFish (whatever that is).
Any other plugins that may go well with AntiAura?
HideAntiCheat (free) - Hides Anti-Cheat plugins from users without permissions.
By having purchased AntiAura ("the plugin"), you agree to the following...
All code is Copyright of Joehot200(https://www.spigotmc.org/members/joehot200.147/), and any code should not be redistributed, copied, or modified.
The plugin is a paid plugin, and should not be distributed to any non-purchaser, with the exception that any server owners may send the plugin to a developer with the sole purpose of the developer using the API (Application Programming Interface) of the plugin, and not to run the plugin on their own server(s).
People other than the server owner may purchase the plugin for their server owner - As long as they are not then distributing AntiAura to multiple servers that are owned by different owners.
Please note that the term "server" here replies to one single server or network of servers connected to with the same IP address.
While this plugin attempts to stop cheats, there is no guarantee that this plugin will stop all cheats or that it cannot be bypassed.
The plugin is allowed to send data to a remote server about itself. This means that AntiAura can send data about itself or its own performance, however will not send any information about your server (for example, it will NOT send any player information, world information or plugin information).
You understand the plugin will create and modify files on your server (such as a config.yml, logs folder, etc).
You also understand that the plugin is provided as an assistant to stop cheaters in Minecraft, and that you use it as your OWN RISK. I am not responsible for any sort of damage caused by this plugin.
You will not modify this EULA.txt file.
All code is Copyright of Joehot200(https://www.spigotmc.org/members/joehot200.147/), and any code should not be redistributed, copied, or modified.
The plugin is a paid plugin, and should not be distributed to any non-purchaser, with the exception that any server owners may send the plugin to a developer with the sole purpose of the developer using the API (Application Programming Interface) of the plugin, and not to run the plugin on their own server(s).
People other than the server owner may purchase the plugin for their server owner - As long as they are not then distributing AntiAura to multiple servers that are owned by different owners.
Please note that the term "server" here replies to one single server or network of servers connected to with the same IP address.
While this plugin attempts to stop cheats, there is no guarantee that this plugin will stop all cheats or that it cannot be bypassed.
The plugin is allowed to send data to a remote server about itself. This means that AntiAura can send data about itself or its own performance, however will not send any information about your server (for example, it will NOT send any player information, world information or plugin information).
You understand the plugin will create and modify files on your server (such as a config.yml, logs folder, etc).
You also understand that the plugin is provided as an assistant to stop cheaters in Minecraft, and that you use it as your OWN RISK. I am not responsible for any sort of damage caused by this plugin.
You will not modify this EULA.txt file.