execute as @e[type=armor_stand,limit=1] at @s if block ~ ~-1 ~ stone if block ~-1 ~-1 ~-1 stone if block ~1 ~-1 ~-1 stone if block ~-1 ~-1 ~1 stone if block ~1 ~-1 ~1 stone if block ~-1 ~-1 ~ cobblestone if block ~1 ~-1 ~ cobblestone if block ~ ~-1 ~-1 cobblestone if block ~ ~-1 ~1 cobblestone run function what:ever
This is a command I'm trying to use in the end. If I include it in a function and list it in the tick tag, it works just fine in the overworld, but it doesn't work in the end, This is also the case when I place a repeating command block in the overworld spawn chunks. However, If I place a repeating command in the loaded end chunk, the function is properly executed. Even if I add a [nbt={Dimension:1}] argument in the selector, entity selectors in general seems to not support cross-dimensional detection even when both dimension are loaded.
Linked issues
Comments 3
I examined the data of entities in different dimensions and found out the ones in the overworld have a dimension tag of 0, and the ones in the end have 1. Considering how the folders for the chunk files are named(DM1, DM-1), I thought that specifying this nbt tag in the selector could allow cross-dimensional entity detection.
Looks like a duplicate of MC-122893.
Where did you get the idea for the {Dimension:1} selector? I haven't seen anything like that before.