Janmm14
commented
1 year ago
- Something else that would be nice is spoofing the server's plugins from hacked clients. I have plugin-hide but I can still see my server's plugins by running .server plugins massscan/bukkitver in meteor client.
Denying the proper permissions blocks tab complete of specific commands like /ver or /icanhasbukkit. Using spigot config you can set like 3 min chars for general command tabcomplete.
. Most Antibot should still be capable to even identify bots when using the measures you provided.
Mounting stuff on player hides player nametag usually.
Not-a-Tyler
Photon-GitHub
1: Add some kind of shield hitting check. I have not found a single anticheat that can detect you blocking your shield and hitting someone at the same time, so I have to make a skript to detect this. My skript false flags sometimes if a player has high ping, so it currently just cancels the hit.
Add some kind of killaura bot that other anticheats can use when they flag killaura. I have several suggestions for this to not get bypassed by AntiBot. Always have the bot loaded in the player's render distance and teleport to the player when a command gets ran. Another thing you could do is have the bot steal someone else's name/skin on the server that's not the guy the suspected cheater is currently fighting.
Something else to prevent AntiBot would be to lie about everything being sent to players that a normal player couldn't see. Below I will list some examples I thought of.
For example to bypass the ping check in Antibot, if a player has anywhere from 0-150 ping just tell every other player that they have 0 ping, and every other bar just has the minimum amount of ping for that bar.
Another example would be spoofground (I'm not sure if this is possible since I don't know java) but AntiBot in some clients has an invalid ground check so maybe just show that every player is floating 100% of the time.
Another example could be gamemode, if you somehow spoof a survival mode player into creative (again I'm not sure if this is possible), if a hacked client thinks all players are in creative then it is not going to attack them.
Another example would be to stop clients from checking if a bot is on the server or not. If every player had a different tablist, tab-completion, and the player name above their head, then it would be extra hard for a client to determine if a bot is actually a real player in the server or not. You could do this by having some kind of zero-width space or alternate character that looks the same as the normal font different in all 3 of these places. The zero-width character works but it would have to be different on different versions, there isn't a character that works on every Minecraft version. I don't believe It would work as well on premium servers since clients will have the uuid of a player's skin due to the player's face in tablist and could base off of that rather than the name, but you could add an option to not render the players face so that this would work.
Another thing to spoof is item durability along with item amounts. Maybe also potion effects. I guess you could not send item nbt but check if the item has an enchant and send the spoofed one if it does.
Make the nametag of players not be from the player, but instead have them be from a separate entity, like have an invisible armor stand following every player with their name, instead of the actual player having the name.
Something else that would be nice is spoofing the server's plugins from hacked clients. I have plugin-hide but I can still see my server's plugins by running .server plugins massscan/bukkitver in meteor client.
Better xcarry detection. Using meteor client I equip random items as armor and leave them in my crafting area.
Prevent entity owner. In meteor client I can enable entity owner and see who owns what animal.
These are just things I thought you could add to AnticheatAdditions to make it better.