Open Baylem opened 2 years ago
Well normally if you try change the rotation of the player you need use Player#teleport then you call the event, the same in this case with change the destination of the PlayerMoveEvent, checking the upstream the logic its like this if the destination was changes then use the same Player#teleport for handle this change for apply all the logic related to this (not run if player is vehicle, dismount if is a passenger, wakeup, close inventory)....
i mean for handle this can be detect if the location only change the yar/pitch and if x,y,z are the same call the internal teleport for avoid call the event.. but not sure if is valid.
Thanks to @Owen1212055 i think can handle this now, xd
Created https://github.com/PaperMC/Paper/pull/8176 for this.
Expected behavior
If I override player movement in a
PlayerMoveEvent
, it should not call aPlayerTeleportEvent
. I believe this is a genuine oversight, while it is niche I do believe it needs to be addressed for consistencyObserved/Actual behavior
When using the above logic to override the player movement, it calls
PlayerTeleportEvent
,Steps/models to reproduce
Plugin and Datapack List
N/A
Paper version
[01:23:50 INFO]: This server is running Paper version git-Paper-61 (MC: 1.19) (Implementing API version 1.19-R0.1-SNAPSHOT) (Git: cd215af) You are running the latest version
Other
No response