That is really unfortunate! (and I'm kind of angry because of that)
This means that I have to write 33% more test cases with relative coordinates than I would have to if anchored would work with relative coordinates too.
Because of the unpredictable nature of local coordinates (player rotation) I can't use them as they are working now. If there was a way to round the camera rotation to the cardinal points (N, E, S, W) (at least I can't find one - neither in the gamepedia-wiki nor with google) I could reduce the test cases to about 1/12 of what I have to do now!
If that is not a Bug I think this at least is a bad design choice
and a missed opportunity for local coordinates
FYI:
I need to test if the player is inside a specific constellation of blocks that can exist mirrored and in 4 rotations. Because the player could stand on a block that isn't the full height I have to test for the constellation in 3 heights (eye-height, foot-height and "foot-height" on the small block)
This makes up for 24 times in total of repeating all tests of the constellation for the different orientations.
Oh and because there is lava and water involved in the constellation and in my case it doesn't reliably get detected as flowing or being still I have to double that 24 times again (though I guess I could write an alias for that...)
Debugging and maintaining that mess of code-quadruplication is extremely tedious.
... please don't take this rant personal ^^
can't reproduce anymore... but yesterday I was able to safely reproduce it though.
... If only I knew earlier that flowing liquid is only "flowing" while it checks if it could spread.
It would have saved me half a day debugging and a big headache.
thanks, it is working now
DANG! I didn't want to open this again!
the distance thing put aside, are you suggesting having it work the way I did it actually is the bug? Because the spawning works until the egg got moved (left-clicked with the mouse) in inventory. So I guess clicking the item makes the nbt update and break.
by the way... what a horrible mess of escaping having to use json format inside a json string field: