Expected: Pos[] follows the player. If players is teleported 3 blocks up, Pos[] is also 3 blocks up from the previous position, Actual: Pos[] is twice as far as the actual position of the player, and it doesn't change with execute at @s run heading.
In Example 5, we can know that the position caught gets twice as far as expected after teleport commands in a function.
I also tested the teleport command in different coordination.
Example 4:
Expected: Player is teleported 3 blocks east, 3 blocks south and 3 blocks up from the previous position.
Actual: Player is teleported 3 blocks east, 3 blocks south and 3 blocks down.
Expected: Should be the same expectation.
Actual: Player is teleported 3 blocks west, 3 blocks south and 3 blocks up.
Expected: Player is teleported 3 blocks east, 6 blocks south and 3 blocks up from the previous position.
Actual: Player is teleported 3 blocks west, 3 blocks up, and 3 blocks south and north.
In Example 4, this bug is confirmed.
Example 5:
This works as expected, but if I try to catch the position:
Expected:
Pos[]
follows the player. If players is teleported 3 blocks up,Pos[]
is also 3 blocks up from the previous position,Actual:
Pos[]
is twice as far as the actual position of the player, and it doesn't change withexecute at @s run
heading.In Example 5, we can know that the position caught gets twice as far as expected after teleport commands in a function.