-
Bug
-
Resolution: Incomplete
-
None
-
1.18.20.23 Beta, 1.17.40.23 Beta
-
None
-
Unconfirmed
-
Windows
Bug:
Player rotations seem to be affected by a delay.
Versions:
I have tested this on the 1.17.40.23 Beta and the 1.18.20.23 Beta.
Result:
When firing a vanilla bow with a vanilla arrow projectile, moving the mouse right before firing exposes that the player's rotation is slightly behind, as the arrow fires where the crosshair was a split second ago, instead of when it was fired.
This also applies to other projectiles, such as vanilla snowballs.
Additionally, I have tested this with running commands using caret notation and it seems that is also affected by the same bug. Although it is not shown in the video, executing a caret notation command on the player while they are rotating will cause the command to execute at a delayed position, instead of at the crosshair.
Expected Result:
Projectiles and caret notation commands, as well as other systems affected by player rotation, use a recent rotation vector instead of one that is delayed. Arrows should fire in the direction of the crosshair when firing, even if the crosshair has moved in the moment leading up to the projectile firing.