Skip to content
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

BadPacketsJ/RotationPlace/AimModulo360/Post when entering vehicles #899

Open
SamB440 opened this issue Jan 3, 2023 · 2 comments
Open

BadPacketsJ/RotationPlace/AimModulo360/Post when entering vehicles #899

SamB440 opened this issue Jan 3, 2023 · 2 comments
Labels
false positive False positive

Comments

@SamB440
Copy link
Contributor

SamB440 commented Jan 3, 2023

Describe the false positive and how to replicate it

  1. Place down an oak boat
  2. Spam shift and right click buttons to keep entering it
  3. BadPacketsJ, RotationPlace, AimModulo360 will flag, possibly Post

Video is here: https://www.youtube.com/watch?v=96iLF0N-xiw

Tested on Vanilla 1.19.3 client on the Grim test server.

AimModulo360 doesn't flag as often but it can. Also have seen Post (interact entity) flag sometimes.

Grim version

2.3.32, Grim test server

Server version

Grim Test Server (1.19.2)

Plugins

Grim Test Server

@MWHunter
Copy link
Collaborator

MWHunter commented Jan 7, 2023

Is this still an issue on latest github actions?

@SamB440
Copy link
Contributor Author

SamB440 commented Jan 7, 2023

It's a lot better now - seems AimModulo360 and Post are fixed.

I tested over 3 minutes and BadPacketsJ flagged once (I think this should be considered fixed too, it's very hard to flag), RotationPlace is still the biggest problem and flagged 24 times.

Edit: Actually tested again and was able to get BadPacketsJ flagged to 8x within 10 seconds.

Also more bad news, unfortunately I managed to find a way to flag Timer and AimDuplicateLook. By holding an item and spamming right click to enter the vehicle, you can flag those checks. Possibly related to 1.17 mojang stupidity packet?

Also seems that 100-150ms is the sweet spot for testing this.
image

I feel like this is going to be super annoying to fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
false positive False positive
Projects
None yet
Development

No branches or pull requests

2 participants