Skeletons spawned natrually are in the same height with Creepers.
Skeletons spawned with eggs are in the correct height.
On the left is a skeleton spawned with the command /summon.
On the right is a skeleton spawned with egg.
The left one can be pushed out but the right one cannot.
I' m not English so my English isn' t very well 🙂
Attachments
Comments 11
Actrually the skeleton spawned natrually is 1.8 meters tall, and the one spawned with egg is 1.99 meters tall. So the first one can be pushed out but the other one can't. But after restarting your game, they are all 1'99 meters tall again. I think that shouldn't happen so I report it here.
They rescaled Mobs in 1.9 so this can absolutely be a result of this. They probably forgot a place to cahnge the value.
maybe this picture makes it more clear: http://imgur.com/J3iELkP
If you reload the game, the naturally spawned skeletons will grow 🙂
The summon command is not naturally spawned, please check the real naturally spawned skeletons too (as well as other mobs)
if this bug gets fixed I hope the skeletons will keep their smaller size, which is also the 1.8 size and the size they currently spawn with. I don't see a reason to slightly change the height of skeletons. Changing the size would break contraptions, that work with the current skeleton size.
This is not fixed in the 1.10 release.
It looks like it was fixed in 16w20a with some of the refactoring for the mob variant spawn eggs, then unfixed when that was removed in 1.10-pre2.
The root of the problem seems to be that the height only gets set when the skeleton type gets set, but the code path for natural spawning never explicitly sets the skeleton type if it's a normal skeleton, so the height stays at the default (1.8) from the base "entity" class instead of getting set to 1.99 like it should be. The refactoring in 16w20a made it always call the "setSkeletonType" method, even for normal skeletons, thus fixing this bug.
Reading the skeleton's data from NBT will set the skeleton type if the "SkeletonType" tag is present, which is why reloading the world works around this bug. Spawn eggs save the new entity's data to NBT then reload it to apply anything in the EntityTag tag to the newly-spawned entity, which is why egg-spawned skeletons don't exhibit the bug. If you /summon a skeleton with SkeletonType explicitly set, that too works around the bug.
I don't see much wrong with this. The left screenshot's skeleton was fine, and so were the right's. The only discrepancy I see here is that the skeleton under the trapdoor in the picture on the right's head is poking out above the door slightly, but it's hard to measure since the skeleton spawned with an egg isn't under a trapdoor.