When baby mobs such as foxes, chickens, zombies, and others jump while underneath a block (jumping up a block into a 1 block tall gap, such as certain cave walls and new 1-high houses) I have noticed them suffocating, and suspect the fact that jumping under normal circumstances propells the mob 1.25 blocks high, thus putting them briefly into the block above and taking suffocation damage.
As well, this is NOT EXCLUSIVE to baby mobs. I have seen some mobs such as sheep and cows perform this, adult sheep and adult cows, and fully suffocate themselves. Other mobs like the chicken take what appears to be 1 half-heart of damage, and after 4 times of doing so perish, all the while under normal pathfinding.
I understand this report contains many similarities to other bugs, those solved and those not. I am trying to highlight ALL the mobs affected under this issue, and acknowledge SOME have been fixed, but many have not. Those which have not are why I am reporting this, and while I cannot think of all of them at once, I ask the community to confirm which have been fixed, and to add in comments which they have found that are also bugged.
Comments 10
I cannot confirm in 1.14.3 as I have not tried it, however the resolution(s) mention(ed) in 1.14.3 are very minimal in scope to this issue, and do not cover all the bases of this issue. If indeed everything they said they have fixed has been fixed, but ONLY that of which they said has been fixed has, then this is still an issue as there are multiple cases that I have seen of baby and full sized entities taking this kind of damage that they did not mention fixing
This issue is not invalid, and is labelled wrong. Simply because I cannot put it as 1.14.2 and got around to reporting it when 1.14.3 came out does not resolve it. I have not tested it in 1.14.3, and thus put in the name that it was 1.14.2. I was hoping a bug tracker community member could confirm either different pieces or the same pieces I mentioned in 1.14.3 as I have not had time to test it nor report it until now. It is a bad flaw that for people wanting to report bugs behind the current version, that the current version does not fix, that they cannot set it at the version they need to, example being 1.14.2 of 1.14-1.14.3, and then have someone confirm where they cannot. As stated, What I am reporting is a bug that is PARTIALLY CLAIMED to be fixed in 1.14.3 by mojang, but not completely, and their [ Believeable ] claim to fixing them has not been confirmed. If I'm not mistaken, It was you who said (on another of my issues which still needs reopening) some staff of the bug tracker work in their spare time, and I would believe that would be the case of many bug reporters alike myself. What I am saying here is that some of it has been said to be fixed, but nobody in the minecraft community has made sure those fixed have stayed in place, and while not all of what I have said has been fixed, the 'not all' part is mainly what I am reporting.
Thank you
Confirmed (applicable) full sized mobs in 1.14.3 as of changelogs for 1.14.3 as well as changelogs for 1.14.3-pre1 through 1.14.3-pre4
Even if this issue is still happening in 1.14.3, you didn't even bother to put what actually the issue is in the description of this ticket. As such, we're unable to understand what the issue is, and therefore the issue cannot be fixed. So, I resolved the ticket as incomplete.
Please review the guidelines linked below before making further reports.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
I have put a detailed description of what the issue is in the description section of the issue. I review the guidelines and template of an issue each time before creating and reporting one. The issue, restated in an incompletely short summary, is that baby mobs such as zombie and chicken, as well as full size mobs such as chicken, will take suffocation damage if they jump onto a block with a solid block above them, and eventually die after enough times taking 1/2 heart of damage.
To whom is reading this, this issue MC-155162 is still active, awaiting another staff member to reopen it as the resolution was premature and is invalid. It has been retested and confirmed in the original version, Base version 1.14 (1.14.0), randomly in the latest versions since, and in the current version. Any professional courtesy for another set of eyes to look this over and give it proper consideration and vetting would be appreciated.
This message was not auto-generated
This bug is reported as fixed in 1.14.3