-
Notifications
You must be signed in to change notification settings - Fork 324
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
New input packet #1702
Comments
No it doesn't give us cool new checks, we already have this information from the prediction engine, it's useful to heavily improve performance though. Client also sends an END_TICK packet now too, so idle tick is back. |
already having the information from the prediction engine is exactly why this is cool, we can compare them for discrepancies, synthetic movement likely wouldn't have the corresponding input in the packet, can also validate sprinting, jumping and sneaking |
That's already what the prediction engine does, validates inputs. All that's changed is we no longer need to bruteforce the possible inputs. |
It could be a good way to check if a client sent a sprinting or smt packet without an input packet or am i wrong |
Using toggle sprint would flag if we checked for this |
Then if a player is moving but not pressing any key? (Could actually fix auto walk duh now that i think about it) |
Yes, we will probably use the client input instead of bruteforcing it
No, the client can modify this. |
I know but trash ass clients wouldn't know that the packet exists so it will just start walking without any input |
Everyone just sets the walking keybind pressed state to true, its one line, and the client handles all the movement correctly like usual. Don't see a reason why this wouldn't behave the same with the new snapshot. |
Feature description
Latest snapshot 24w36a just added a keyboard input packet.
This opens up the possibility for a huge amount of cool new checks.
The text was updated successfully, but these errors were encountered: