Woah hold on. 1 anticheat that just stops basic things and 33kb?? what
Is there some other random thing happening here.

Terrible, this is the wprst anticheat every hate on youthis was not worth downloading, and by the way, it's a virus.

This plugin is not usable in its current state. There are way to many false positives for this to even be remotely usable. I agree with everything TheDoominator says, but I found more false positives. For example, walking on the edges of slabs in water (Jesus) and riptide trident flying in the rain (Flight). This is utterly ridiculous, and if it's in beta (especially this early in beta) it shouldn't be on spigot yet. If this plugin gets fixed in a later update, ill update my review accordingly. If not, my review is staying as-is.

Do not use it in its current state. Before I begin yes I know it says please report issues and not review first. But I have reported the many issues a week ago you can get by walking/attacking entities lmao. If it's been a week it's fair game imo.
And yes it is in beta but even a beta anticheat shouldn't be THIS bad, at least before being published on SpigotMC. I do hope this can improve, just note it is not something you should actually use on production or anything other than anticheat testing.

I was also blamed for one of the falses (I am not a dev). I said I will test the latest PUBLIC version of AxoWatcher and review it/report falses. He then said he would send the latest file that he had that was being developed. I said no thanks. This was because I didn't want some half-finished checks wouldn't be fully completed/tested (Which turned out to be valid) and have falses. He then said he was going to update the plugin https://imgur.com/a/gsh3Ykx (I admit I didn't actually say why I wouldn't test the latest dev build so it may have seemed a little unfair, sorry) so I waited to test it. I tested and found the false (Right or Left clicking any entity). I reported the falses and he blamed me for the issue https://imgur.com/a/cUXpJwp. If he had just sent the file it would still have the false issue.


He also called someone a "dumbass user" (Jadrin, a couple of reviews below me). This can be fair sometimes, if they review actual console errors and make a review that has nothing to do with the actual plugin then fair enough but the review was fair. It falses and the review stated that. Not everyone agrees with not reviewing if you find some falses/bypasses. But IF you do this please re-review it once the issues are fixed otherwise yea that's being dumb (I will re-review this once I see the issues fixed).

First some weird stuff about the plugin.
The config file does not use the Bukkit config system at all. The actual file is named "AxoWatcher\Settings.txt" and there is a folder for it but it's called "AxoWatcher\", the config file isn't even in the folder. The config file only contains "true" or "false" with no indicator for what it is. That is fine just a bit strange and confusing.

Also, PacketEvents is not shaded so you need to install it as a plugin yourself which is annoying but not too bad. It's an improvement to just events which is good

Now some falses
- Right/Left clicking any entity - BadPackets
- Running/walking sometimes - SpeedA, BadPacketsB and sometimes Flight
- Taking Fall Damage - FlightA
- Swimming out of water/going onto land from water - JesusA
- Creative mode and I assume spectator as well - Some BadPackets check and prob more
- Walking on boats - NoFallA
- Entering boat - BadPacketsB
- Flying with an elytra - Flight and maybe Speed?
- Levitation/Slow Fall - Flight

This was all found really easily and will affect anyone playing if punishments are on.

I do like that there is a GUI menu for enabling/Disabling punishments though and a command to toggle alerts on/off, very nice! A couple of suggestions for the future. Try to use the built in Bukkit config system, it is much easier and better to use. Maybe make it so in the config you can edit the messages/alerts too.

I do really hope this anticheat improves, can't wait to see it improve. Good luck!
And if you say "they dont happen for me" try testing on a server that isnt local and you have above 0-1ms of ping. Most people wont be on the local machine and will probably have 20-200 ping, anything above 250 ping is probably fair enough if they are falsing the anticheat in a beta state.
I will re-test and re-review this once I see the issues are fixed.

Also for the meme, not hating on this

This anticheat didn't watch my axolotls :(. I dropped them at school and they were not watched at all! They cheated all the tests because there was nothing watching to stop it :(

Gives a bad packets sometimes hitting, walking and when jumping out of water gives you flying false and when flying with elytra, levitation, slow falling and more.

Issues:
- Using packet IDs rather than PacketEvents' built in PacketType system. Rather than just having to update your dependency (which would be required anyways) you now have to update all of your checks too.
- What is the point of creating a "Settings.txt" file? There are no benefits over just using the regular Config...
- Since you currently do not use the Replace method at all, I see no reason for you to create Strings through "String.format" and just adding the pieces together. Strings are wildly inefficient in Java and could be heavily optimized within your anticheat by using StringBuilders.
- BadPacketsB falses on any hit.

Recommendations (not necessary):
- Update your Plugin.yml, you're onto version 1.0.2
- If you're going to use PacketEvents, I'd go all in. Shade it (for ease of use) and
- I'd recommend trying to cut down on how many times you grab the blocks around the player. There's no harm in doing it a few times, but with as many methods as you run you may start drawing a decent amount of performance. I'd recommend saving the nearby blocks each time the player's position changes.

The developer has decided to spam me with messages on Discord due to my previous review, currently totaling at 18 messages received. Due to this, I will leave an updated review... but still pointing out the issues.

First, in the PacketEvent class you seem to be swapping variable types for no reason. For example, regularly when listening to the Flying packet with PacketEvents you receive a Vector3D for their position... which you have decided to convert into a Bukkit Location. This is just unnecessary and may waste vital resources.

Second, please label your packages correctly. In no way would "BadPackets" checks usually be an exploit. They rather belong in the Player package as they usually catch misc. cheats anyways.

Third, try to use string builders. They're much more efficient than building strings manually.

Fourth, add some proper handling for things like 0.03 in your fly check. Currently it doesn't look great with you having to exempt on "airticks % 36" and "airticks % 52" due to improper handling.

Fifth, try to get rid of the buffer on the NoFall check. If you add a buffer it just means that the check can (and most likely will) false flag, with a buffer just being a quick patch.

Sixth, manually using PacketIDs. Mojang can change these at any point and it'd be much more reliable to use the PacketTypes built into PacketEvents, this way all you need to do after an update is update your dependency.

Seventh, what are you doing config wise... why are you manually saving a "settings.txt" file rather than just using Bukkit's built in config function. Bukkit caches it at load and whenever you reload the config, so there's no performance benefit.

Eighth, SpeedA and FlightA look identical to Jonhan's tutorial checks with very shotty additions only added because he doesn't show proper 0.03 handling. It's a great base to start with, but I'd really recommend to try to fix the issues with proper methods.

Good anticheat for the checks it has as of 01/03/2022! Please add 1.8.x support.

------------------------
Normal anticheat but i give you 5 start for make this anticheat

This anticheat becomes quite questionable when you take a look at the source code.

First off, the anticheat collects information in two different places, the PlayerData class and the PacketEvent class. A much better solution would be to just collect it in one place.

Second, in the PacketEvent class you seem to be swapping variable types for no reason. For example, regularly when listening to the Flying packet with PacketEvents you receive a Vector3D for their position... which you have decided to convert into a Bukkit Location. This is just unnecessary and may waste vital resources.

Third, please label your packages correctly. In no way would "BadPackets" checks usually be an exploit. They rather belong in the Player package as they usually catch misc. cheats anyways.

Fourth, try to use string builders. They're much more efficient than building strings manually.

Fifth, add some proper handling for things like 0.03 in your fly check. Currently it doesn't look great with you having to exempt on "airticks % 36" and "airticks % 52" due to improper handling.

Sixth, try to get rid of the buffer on the NoFall check. If you add a buffer it just means that the check can (and most likely will) false flag, with a buffer just being a quick patch.