This command executes at feet height, even though it should be executed at eye height as far as I know:
/execute anchored eyes run summon armor_stand ~ ~ ~
This works as expected, even though both should describe the same position:
/execute anchored eyes run summon armor_stand ^ ^ ^
This command uses the regular relative coordinates for the actual summoning, but works as expected:
/execute anchored eyes positioned ^ ^ ^ run summon minecraft:armor_stand ~ ~ ~
Linked issues
is duplicated by 1
Attachments
Comments 6
Isn't it meant to shift the execution position to the eye height, which depends on whether the player is standing, sneaking or crawling or on the eye height of the entity? And "positioned" does not do anything with eye height. And no, "anchored" is not just about other parts of /execute, as seen in my second example command. It definitely does not look intended that something like "/execute positioned ^ ^ ^" is required, which isn't supposed to change the execution position at all.
Sorry if I wasn't clear about part of my point, but anchoring specifies the starting point for angles and perspectives, which isn't limited to the execute command. The usage of carrorts (^), whether part of execute or not, are determined based on a starting point. By default, this is set to feet, but anchoring changes it. The actual position at which the command executes does not change until an explicit "positioned" option is selected, or else a carrot is used to apply the modified point. The same can be said about the facing option, though this naturally is only used within the execute statement itself.
In short, it changes the starting point for angle-based calculations, but does not shift the position.
Edit: removed the example, as I realize it doesn't make sense :Z
That sounds complicated and unexpected. Are you sure that that's how it's supposed to work? It would be much more intuitive and worked the same in most cases if it simply moved the execution position upwards.
But that would mean that `/execute positioned ^ ^ ^` actually changes the execution position, which is extremely weird. And the screenshot even has someone else saying that it's unintuitive.
I think this report should be reopened for a developer to either fix this if it's a bug or reconsider this if it was at some point intended.
I think you're getting the "anchored" and the "positioned" options mixed up. While "positioned" changed the location of where the command is executed, "anchored" acts as a modifier for other components of execute, these being the carrot notations (^) and the "facing" option. Without either of these, "anchored" effectively does nothing.