-
Notifications
You must be signed in to change notification settings - Fork 338
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
antiweb cringe bypass 2024 #1786
Comments
is this a troll or real? @SamB440 ? |
I took this code from the cheat client |
What client is this from? |
|
This is a 0.03 issue, I will look into fixing this |
Although it might not be fixable on 2.0 engine due to how it calculates the possibility of 0.03 |
Is the 0.002 on modern clients really enough uncertainty to let this bypass? Do we give 0.03 to clients that should only have 0.002? |
BadPacketsX and Z catches the ignore mode version of this. Enable experimental checks. We really need to refactor and rename all the checks... |
it doesn't break blocks? |
The Ignore version is fixed by BadPacketsX/Z #1818 #1817 The fly version is not yet fixed but it can be mitigated on new versions by using the newer movement threshold. #1820 With the changes above on the latest MC version we go from easily bypassing at Fly Speed >=1.22 -> a max bypass speed of 0.64 while sprinting. 0.65 will instantly flag simulation and setback. |
Describe the bypass and how to replicate it
working at 0.39 speed.getValue()
(if (mode.getValue() == Mode.Fly) {
final double[] dir = MovementUtility.forward(speed.getValue());
mc.player.setVelocity(dir[0], 0, dir[1]);
if (mc.options.jumpKey.isPressed())
mc.player.setVelocity(mc.player.getVelocity().add(0, speed.getValue(), 0));
if (mc.options.sneakKey.isPressed())
mc.player.setVelocity(mc.player.getVelocity().add(0, -speed.getValue(), 0));)
Grim version
latest
Server version
1.19.4
Plugins
grim, LP, packetevents
The text was updated successfully, but these errors were encountered: