You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :)
The text was updated successfully, but these errors were encountered:
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.
SpawnShield/base/src/main/java/net/techcable/spawnshield/tasks/KnockbackTask.java
Line 50 in 3e9a56e
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 :)
The text was updated successfully, but these errors were encountered: