GrimAnticheat / Grim

Fully async, multithreaded, predictive, open source, 3.01 reach, 1.005 timer, 0.01% speed, 99.99% antikb, "bypassable" 1.8-1.20 anticheat.
GNU General Public License v3.0
1.02k stars 288 forks source link

Enchantments cause falses due to new 1.21 attributes and PacketEvents unable to read enchants #1583

Open Devuxious opened 3 weeks ago

Devuxious commented 3 weeks ago

Describe the false positive and how to replicate it

Here are some issues I encountered within the first five minutes of using this anticheat:

There are likely more issues, but I haven't had the chance to test further yet.

Grim version

2.3.65

Server version

Paper 1.21-38-master@1f5db50

Plugins

CoreProtect, Delta (custom core), FastAsyncWorldEdit, PlaceholderAPI

SamB440 commented 3 weeks ago

It's not ignoring them, it's because Mojang completely changed the calculations in 1.21

Cats1337 commented 3 weeks ago

I've also found this issue. Efficiency sets off fastbreak alert, depth strider sets off simulation alert and drowns players. I tried to modify the config to help with it but to no avail. Packets clearly aren't being handled correctly.

SamB440 commented 3 weeks ago

Please read what I said, it's not a packet issue, it's an issue with viaversion + Mojang changing everything to use attributes which also changed the movement calculations. My attribute-rework branch fixes this, but it is complicated to fix: https://github.com/GrimAnticheat/Grim/blob/16a90bb41db1841c9e821ed7352ecd109186e44a/src/main/java/ac/grim/grimac/utils/data/packetentity/PacketEntitySelf.java#L58-L78

Incluuu commented 2 weeks ago

I've also found this issue. Efficiency sets off fastbreak alert, depth strider sets off simulation alert and drowns players. I tried to modify the config to help with it but to no avail. Packets clearly aren't being handled correctly.

I have te same problem image

SergioK29 commented 12 hours ago

Can confirm this issue