An example:
Entity of type "Snowball" is at the position 0 0 0. A CommandBlock running the command "tp @e[type=Snowball,c=2] ~ ~10 ~" is at the position 10 0 0
What should happen:
The Snowball should move to the position 10 10 0 since the coordinates are affected by the position of the commandblock. Instead, the entity moves to 0 10 0.
So, the command "tp @e ~ ~10 ~" is the same as "execute @e ~ ~~ tp ~ ~10 ~". This already exists since version 14w07a.
I hope this is not on purpose.
Linked issues
duplicates 1
Comments 9
Relative Coordinates work, but not correctly. It uses the coordinates of the Entity, not of the command sender. And that should be changed
EDIT:
I dont want to teleport the Snowball to ~10 ~10 ~10. I want to teleport the Snowball to the position of the command sender (command block) and 10 blocks above, to the position 10 0+10 0
= 10 10 0.
The Snowball is at the position 0 0 0
The Command Block at 10 0 0
Using relative coordinates of the command block, the position I want the snowball at is at ~ ~10 ~.
But instead it used the relative coordinates of the entity, so the snowball moves just 10 blocks up
This should be called a bug since /execute @e[type=Snowball,c=1] ~ ~ ~ tp ~ ~10 ~ would be the command for whats happening
Duplicate of MC-50347.
And by the way, you can teleport rellative to both command. Blocks and entities using numbers or execute
Since this is a bug, why is the duplicate marked as "works as intended"? You confirm this as a bug and mark it as resolved, whats the point of doing this?
Relative Coordinates don't work like that for entity based commands: tp, execute, particle, ...
Instead, use numbers: tp @e[type=Snowball,c=2] 10 10 0