Sometimes when you rotate an armor stand with the /tp
command, the client doesn't update it: the armor stand twitches or does nothing at all.
In this glitched state the stand won't update if you try to /tp
it to itself. It will update if you rotate it again, teleport to another location, reopen the world or wait some time for it to fix itself.
For a NoGravity
armor stand it will always be the first rotation, but it won't happen again if you teleport it to another coordinates first.
Example command:
/execute as @e[type=armor_stand,limit=1] at @s run tp @s ~ ~ ~ ~45 ~
Linked issues
is duplicated by 8
Attachments
Comments 31
I ran into this problem right away after introduction of ArmorStands, because one of the first things I did with them was making a circle by teleporting them in one spot in usually 45 or 22.5 degrees. I never considered it a bug, although it certainly would be great if it could be fixed }=)
As for the "workarounds" for mapmakers: The only way I found or did was to just tp the ArmorStand/ArmorStands again with that value, so if I e.g. had 16 AS in a circle, the 16th wouldn't update rightaway, so I just circled all the 16 AS again to have it tightaway optically updated.
As for the workaround for normal players which is mentioned in the bugpost: Additionally to reopening the world, the updating of the AS will happen automatically after a while!
I forgot how many minutes realtime it is, maybe around 5 or so.
I can test around a bit after work and provide a bit more information, either the realtime after when the AS updated itself, or a little video where one can see it demonstrated.
It will update if you rotate it again, teleport to another location, reopen the world or wait some time for it to fix itself.
That's true, but you can't really reopen the world or give it time to fix itself in a map. Also, I eventually found a fairly decent fix myself; Whenever you rotate the armor stand, wait one tick then rotate it slightly, then wait 3 ticks and rotate it back. It should work 100% of the time, hopefully.
Here's a video showcasing the bug in 1.18: https://youtu.be/KJfcfw9OM24
The functions running here are too complicated to set them up for a bug report, but as you can see, the rotation is constantly incorrect (sometimes facing 0 0, while other times, facing -90 0 (should be facing -135 0)).
The function for spawning Neville can be found here (note line 5/6 are immediately teleporting the spawned entities to the command's rotation context)
The moving of Neville seems to be required, as I cannot reproduce with just a simplified function for the spawning (see chair, which only changes Pose, not location). The function for the moving is here (note line 18-19).
I will try to find a simple setup which people can easily test in the near future.
I attached a data pack which can be used to reproduce this issue. Do note that it will not work as reliably as the Neville video, so a bunch of attempts may need to be made. Having server-side lag helps with reproducing this.
Face away from the 0 0 rotation, and run the function "summon".
Affects 1.19.2.
If @unknown doesn't mind, I'd be willing to become the reported and keep this updated. My commands keep triggering this rather reliably.
Can confirm, but I'm pretty sure there's already a report of this issue. Can't find it at the moment though.