mojira.dev
MCPE-121042

execute detect from command block not working in other dimensions

When using an execute detect command from a command block or function that originates in another dimension, will result in false positives.

 

Example code snippet (repeating command block executing a function within a tickingarea in the Overworld)

execute @e[type=!item,tag=!initialised] ~~~ detect ~ 127 ~ bedrock 0 tag @s add inNether
execute @e[type=!item,tag=!initialised] ~~~ detect ~ 1 ~ air 0 tag @s add inEnd
execute @e[type=!item,tag=!inNether,tag=!initialised] ~~~ detect ~ 1 ~ bedrock 0 tag @s add inOverworld

tag @e[type=!item] add initialised

 

Expected results-

Newly spawned entities in the Nether to have the 'inNether' tag.

Newly spawned entities in the End to have the 'inEnd' tag.

Newly spawned entities in the Overworld to have the 'inOverworld' tag.

 

Actual results-

All entities regardless of dimension will get the 'inOverwold' tag.

 

Possible cause-

Running this same code from a command block located within the End will successfully give newly spawned entities the 'inEnd' tag. 

Running this same code from a command block located within the Nether will successfully give newly spawned entities the 'inNether' tag.

It seems that the dimension that the code is being executed from is not cross-dimension compatible.

 

Linked issues

Comments 10

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Is this still an issue in the latest version? If so, can you please add it to the affected versions (or mention it if you are not the reporter).

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Is this still an issue in the latest version? If so, can you please add it to the affected versions (or mention it if you are not the reporter).

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Confirmed still an issue in 1.16.220

Confirmed still an issue in 1.16.220

This is also still an issue in 1.17.0

This is also still an issue in 1.17.0

I found a workaround for this is to use /execute twice (e.g. /execute @a ~ ~ ~ execute @s ~ ~ ~ detect ...)
Disturbing, isn't it? 🙂

I found a workaround for this is to use /execute twice (e.g. /execute @a ~ ~ ~ execute @s ~ ~ ~ detect ...)
Disturbing, isn't it? 🙂

I believe this is fixed with the new execute in 1.19.10

I believe this is fixed with the new execute in 1.19.10

Dhakos

(Unassigned)

627375

Confirmed

Windows

1.16.220, 1.16.210, 1.17.0, 1.19.10

1.19.10

Retrieved