Goat facing logic bug (Command Block)

Goat Facing Logic Bug (Command Block)

Back when I was experimenting with the /summon command, I noticed something was off with goats. Never mind other goat-related commands—the goat's facing direction is just wrong.

Here's the story. It all started when I first tried out 26.1 Snapshot 2. I entered the following command:

/summon minecraft:goat <coordinates> {NoAI:true, Rotation:[0f,0f]}

In the Rotation tag, 0 0 is supposed to represent the default facing direction—perfectly fine, right? But when I summoned it, it just appeared with its default orientation. When I changed the first 0 to 180, it still faced the default direction. No matter how I adjusted it, it either wouldn't turn at all or only turned a tiny bit—as if it had a mind of its own. When I changed the second 0 to other values: 90 makes it look down, like when a goat is eating grass; but entering 180 causes its head to detach and snap backwards toward its tail, splitting the head from the body.

Don't tell me I messed up the command—I've checked every source I could find. I also tested other mobs like cows (minecraft:cow) and pigs (minecraft:pig), and they behave normally. At 180°, they simply look upward (their heads face the sky) and don't detach. Their cardinal direction facing works perfectly too—this applies to all mobs. The goat is one of the few mobs where this issue occurs.

If I want the goat to face the desired direction, I have to use the command /tp <goat_UUID> ~ ~ ~ ~ ~ to manually adjust it. Even then, it feels locked in place and refuses to turn unless I spam the command about ten times. For example, if I want it to turn around and face backward, I have to enter the command roughly ten times before it finally obeys.

Once I've adjusted it properly, if I exit and re-enter the world (without fully closing the game), the goat's facing direction resets to the default. Other mobs do not exhibit this behavior.

Affected Versions:

· Confirmed in: 26.1 Snapshot 2

· Previous version status: I had hoped this bug would be fixed in the 26.1 full release, but that was not the case.

· Tested in: 1.21.11, where the goat still behaves the same.

Speculation: This bug likely originated around version 1.21.8 or even earlier. This is an obscure bug that most players wouldn't notice, and its impact is primarily on command users and map makers.

For details, see the video below. The video is a bit long.