-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False triggers #1024
Comments
provide steps to reproduce |
How do you know the player isn't cheating |
oh, do you use forge? |
I use forge optifine, I have no clue how to reproduce it and videos dont really help either, i have one where it looks like i hit 3.7 blocks and i believe this one triggered the anticheat too
|
What version are you on? Forge 1.18.2+ is a cheat and has extended reach with right click and left click. See MinecraftForge/MinecraftForge#9309 Latest versions of Forge 1.19.4 supposedly fix the issue, but apparently there are still issues with sweeping and large entity hitboxes. Haven't tested the fix fully yet. |
I use 1.19.2 |
Forge 1.19.2 has accidentally included cheats within the game. This is not a false with grim but rather the Forge devs fucked up their reach code so that the player has reach. There's nothing I can do to about this. You just have to update your forge client. |
Ive had over 50+ false triggers for reach without using any mdos other than optifine and with 30-40 ping constantly
possible issue with reach check
The text was updated successfully, but these errors were encountered: