i think, this is like an animation for an attack, like a iron golem trows up his arms. But when in this animation, the hitbox doesnt change. They must remove the animation, the change of hitbox because of the animation would be much more difficult i think.
I've identified the cause of this. All entity models are created 1.5 blocks below where they should render, and then moved up by a little over 1.5 blocks in the rendering process. I don't know why it's done this way but it is. The issue is, the guardian model does not set a pivot/rotation point, and it defaults to [0, 0, 0] (relative to the entity position) which is above where the model is. When the model is rendered, everything is shifted up 1.5 blocks, putting the model in the correct place, but the pivot point is now at [0, 1.5, 0] which is way too high.
The correct location for the pivot, in my opinion, would be at 0.5 blocks above the bottom of the guardian, or 1.0 blocks below the default pivot.
In MCP 1.12.2 naming the code solution would be, in the constructor of net.minecraft.client.model.ModelGuardian, the following line needs to be added:
I'd like to request ownership of this ticket since the current reporter has been inactive for several years. I'm willing to continue to provide all of the necessary details and will keep this report updated accordingly.
i think, this is like an animation for an attack, like a iron golem trows up his arms. But when in this animation, the hitbox doesnt change.
They must remove the animation, the change of hitbox because of the animation would be much more difficult i think.