MC-49446Teleport Entities to Absolute Cooridnates
When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine
EDIT: okay, i tried that stuff again today and i found out, that this only hapens, if i execute the command rapidly (eg. with a fast setblock clock)
EDIT2: so I updated the thing to '-10' because this provides a better visible bug behaviour, this way the sheep won't die and just float slowly to y=-10 or just stay on the ground - the behaviour changed a bit.
/tp @e[name=OpenShop] ~ -10 ~
[ /summon Sheep ~ ~ ~ {CustomName:"OpenShop"} ]
Created Issue:
Teleport Entities to Absolute Cooridnates
When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type in eg. [type=!Player], if i just write @e it works fine
sorry, must have been kinda lag issue, tried the same thing again today and everything just worked fine, sry for your time (;
When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type
in eg.[type=!Player] , if i just write @e it works fineWhen I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine
When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine EDIT:
When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine
EDIT:When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine
EDIT: okay, i tried that stuff again today and i found out, that this only hapens, if i execute the command rapidly (eg. with a fast setblock clock) [command: /tp @e [name=OpenShop] ~ -100 ~]
When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine
EDIT: okay, i tried that stuff again today and i found out, that this only hapens, if i execute the command rapidly (eg. with a fast setblock clock)[command: /tp @e[name=OpenShop] ~ -100 ~]When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine
EDIT: okay, i tried that stuff again today and i found out, that this only hapens, if i execute the command rapidly (eg. with a fast setblock clock)/tp @e[name=OpenShop] ~ -100 ~
When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine
EDIT: okay, i tried that stuff again today and i found out, that this only hapens, if i execute the command rapidly (eg. with a fast setblock clock)/tp @e[name=OpenShop] ~ -100~
When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine
EDIT: okay, i tried that stuff again today and i found out, that this only hapens, if i execute the command rapidly (eg. with a fast setblock clock)/tp @e[name=OpenShop] ~ -10 ~When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine
EDIT: okay, i tried that stuff again today and i found out, that this only hapens, if i execute the command rapidly (eg. with a fast setblock clock)
EDIT2: so I updated the thing to '-10' because this provides a better visible bug behaviour, this way the sheep won't die and just float slowly to y=-10 or just stay on the ground - the behaviour changed a bit.
/tp @e[name=OpenShop] ~ -10 ~
When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine
EDIT: okay, i tried that stuff again today and i found out, that this only hapens, if i execute the command rapidly (eg. with a fast setblock clock)
EDIT2: so I updated the thing to '-10' because this provides a better visible bug behaviour, this way the sheep won't die and just float slowly to y=-10 or just stay on the ground - the behaviour changed a bit.
/tp @e[name=OpenShop] ~ -10 ~[ /summon Sheep ~ ~ ~ {CustomName:OpenShop ]
When I teleport a Entity to a relative Position, everything works fine, but if I teleport it to a Absolute Position, it will just bug through the ground, but only, if I type [type=!Player] or simillar, if i just write @e it works fine
EDIT: okay, i tried that stuff again today and i found out, that this only hapens, if i execute the command rapidly (eg. with a fast setblock clock)
EDIT2: so I updated the thing to '-10' because this provides a better visible bug behaviour, this way the sheep won't die and just float slowly to y=-10 or just stay on the ground - the behaviour changed a bit.
/tp @e[name=OpenShop] ~ -10 ~[ /summon Sheep ~ ~ ~ {CustomName:"OpenShop"} ]
Please provide the entire command issued.
okay, i tried that stuff again today and i found out, that this only hapens, if i execute the command rapidly (eg. with a fast setblock clock)
I'll check later today
Reopened, thanks