When using the command /execute in <dimension> run teleport ~ ~ ~, destination is not always consistent with start location for players in creative mode.
Steps to Reproduce:
Run the following commands in creative mode and from the overworld, noting coordinates before and after as well as the coordinates returned in chat by each command
/execute in the_end run teleport ~ ~ ~
/execute in the_end positioned 0 70 0 run teleport ~ ~ ~Run command /execute in the_nether run teleport ~ ~ ~ from the overworld and /execute in overworld run teleport ~ ~ ~ from the nether. Repeat and note coordinates changing after each input.
Observed Results:
Teleporting to the end places you at 0 0 0 regardless of starting coordinates, and teleporting to and from the nether wildly increases your x and z coordinates. Teleporting to the end relative to a position specified in the command places you at approximately your original x and z coordinates.
Expected Results:
Teleporting to the end and back would maintain the exact same coordinates in both dimensions, and teleporting to and from the nether would maintain properly scaled coordinates. Teleporting relative to a fixed location in the end would run relative to those coordinates, not your original coordinates.
Comments 2
Yes, I’m aware of the intended behavior for the nether teleport, and what I’m describing is not that. The intended behavior would mean repeatedly teleporting to and from the nether without moving otherwise should leave you at the same coordinate set in each dimension, but the current behavior seems much more exponential. Run the commands back and forth a few times and you’ll see very clearly what i mean by “wildly"
The behavior you’re seeing with the Nether is intentional. If you didn’t know, every 1 block in the Nether is worth 8 in the Overworld or End. Seems like using the “in” argument of “/execute” does the math for you, so instead of running “
/execute in the_nether run tp ~ ~ ~", run “/execute in the_nether positioned ~ ~ ~ run tp ~ ~ ~" to avoid the dilation.Can confirm the issue you’re seeing with the End in the latest snapshot, though. Odd that it doesn’t apply to 1.21.8.
It also seems like the first teleport you make to the end works fine, but any after that don’t? Not sure.