I considered it might be viewed as a feature request, but I thought it could be potentially a bug because the execute stored output stores the distance and not the coordinates, which the player sees when the player personally runs it- which seems like an oversight to me if the intended data wasn't the thing being stored. If you can get parsing working, what I'd really like to do is put the X and Z values into the lodestone position item component of a compass- no need for teleporting. My goal is to create enchantable compasses to point toward biomes or structures.
Can replicate. This happens with any custom item regardless if you add it to the Primary Items subset, or if there are regular weapons/tools covered by the enchantment set, etc etc. I cannot find a case where it works properly for custom items.
I considered it might be viewed as a feature request, but I thought it could be potentially a bug because the execute stored output stores the distance and not the coordinates, which the player sees when the player personally runs it- which seems like an oversight to me if the intended data wasn't the thing being stored.
If you can get parsing working, what I'd really like to do is put the X and Z values into the lodestone position item component of a compass- no need for teleporting. My goal is to create enchantable compasses to point toward biomes or structures.