Affects Version/s: 1.15.1, 1.15.2 Pre-Release 1, 1.15.2, 20w06a, 20w07a, 20w09a, 20w10a, 20w11a, 20w12a, 20w13a, 20w14a, 20w16a, 20w17a, 20w18a, 20w22a, 1.16 Pre-release 2, 1.16 Pre-release 3, 1.16 Pre-release 6, 1.16.2 Release Candidate 1, 1.16.3, 1.16.4, 20w45a, 21w03a, 1.17 Pre-release 2, 1.17.1
Fix Version/s: None
/teleport commands without <targets> argument specified can change the executor's rotation in certain command context.
You are not moved at all.
Your rotation is changed. This is definitely intended because /teleport command should resolve relative pos arguments by the current command context.
Your rotation is changed.
Your rotation should not change because you didn't specify anything about your rotation in the /teleport command.
yarn's mappings, 1.15.1, sorry.
When registering the /teleport <location: pos> command, there's a default argument DefaultPosArgument.zero() for the <rotation> argument, which makes
I suggest you replace it with null.
Thanks for t1546542 telling me this bug. I'm not sure whether this was reported before though, I couldn't find anything.