[MC-152997] The dimension of @s is not updated when teleporting non-player entities

When running this function

execute at @s run setblock ~ ~ ~ green_concrete
execute at @s in the_nether run tp @s ~ ~ ~
tellraw @a ["Dimension: ",{"nbt":"Dimension","entity":"@s"}]
execute at @s run setblock ~ ~1 ~ red_concrete

using the following command from within the overworld:

/execute as @e[type=pig,distance=..3] run function dimensions:test

I'd expect to find a green concrete block in front of me and a red one in the nether. Instead, I see a stack of a green and red concrete block, even though the tellraw reports the pig being in dimension -1.

This does not happen, when a player is teleported instead of a pig: Then everything works as expected and a green block is placed in the overworld, and a red one in the nether.

Linked issues

is duplicated by 1

MC-188858 Teleports execute late when teleporting inter-dimensionally using a datapack function Resolved

Comments 9

J_Aetherwing 2019-07-01T10:27:57Z

Also affects 1.14.3

uyp 2020-09-03T22:15:22Z

confirmed in 1.16.2

uyp 2020-11-04T20:53:49Z

confirmed in 20w45a

akoimeexx 2020-12-15T02:04:35Z

Confirmed in 20w49a

akoimeexx 2021-01-30T23:17:20Z

Confirmed in 21w03a

uyp 2021-03-16T10:36:14Z

To switch dimensions, non-player entities are entirely recreated, but `@s` still targets the previous entity. (`@e` and the uuid select the new entity)

Connor C 2021-06-15T22:41:55Z

This may be able to be resolved by adding a Dimension nbt tag to entities like players have. This would mean the entity is not resummoned and instead is actually moved.

vdvman1 2021-06-15T22:57:01Z

That doesn't resolve the problem at all. The issue here is that when you teleport `@s` to another dimension it causes `@s` to no longer point at the correct entity, being able to get the dimension from NBT would not do anything here, and setting from NBT will almost certainly result in desyncs between client and server

KawaMood 2022-04-25T13:35:31Z

Confirmed in 1.18.2