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

playerEntity.setVelocity() issues #11

Open
L4BORG opened this issue Feb 15, 2016 · 1 comment
Open

playerEntity.setVelocity() issues #11

L4BORG opened this issue Feb 15, 2016 · 1 comment

Comments

@L4BORG
Copy link

L4BORG commented Feb 15, 2016

playerEntity.setVelocity(knockback);

I would like to point out the fact that packets sent because of "setVelocity()" will have no effects whatsoever on hacked clients that have antiknockback, like nothing happened (tested with Wurst).

And some plugins such as NCP have no "antiknockback" check.

Maybe add warning about this or something... there isn't much that can be done about this, except maybe check if player really moved etc but that would prob. be too expensive (PlayerMoveEvent or task every few ticks).

Just a thought :)

@Techcable
Copy link
Member

I could teleport them if they get too far in (like how teleport mode does) 😄
This would require calculating distance and whatnot, but it should work well.

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

No branches or pull requests

2 participants