Bravewind
Comments
Confirmed in 1.15 versions randomly including base (1.15.0)
Confirmed in 1.13-pre3 (asked)
1.14.1
and 1.15 versions at random inclusing base (1.15.0)
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
To whom is reading this, this issue MC-153997 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, each additionally stated version, 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
Drowned with and without trident spawn in water. Step into water and they become hostile. Step out, and only without tridents pacify. Tridents still attack. Daytime only, as nighttime both with and without stay hostile. Yes?
They did that, and it lasted until 1.14.2, but by 1.14.3 it was patched and made impossible by normal (non-specific command) methods such as survival and creative. 14.2 yes, 14.3 no, 14.4 bug, as well as those were different enchantments stacked, this is the same one stacked, if only at different levels. I don't know what caused it but crossbows have been bug ridden since creation
Screenshots are from Xisumavoid's YouTube channel, Hermitcraft 6 Episode 837, however I have tested this myself under the same circumstances and additional circumstances, and while it takes time to replicate, it does happen.
Confirm in 1.14.4pre1,2 as of changelogs, confirm current versions with additional proof via MC-155876
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.
I have not been spamming comments to bump my own issue. As stated, detailed, and summarized above, MC-153997 (this) has a few minor commonalities shared by the other issues, and very much is not covered wholly or by a 'good enough' standard by the other issues. As I would rather this not become a heated argument, and that we do not seem to be getting on the same page, may I ask that my issue be 'assigned' to a different staff member for review?
Issue needs reopening please
Issue needs reopening please
Confirm for versions stated, even as a duplicate, as the Official Minecraft Wiki's only source for information has been the Official Mojang logs for Minecraft, albeit the launcher news, the Minecraft.net website, or other sources BY MOJANG I am missing
Confirm in 1.14, 1.14.1, 1.14.2, and
in 1.14.3 as of changelogs as well as changelogs for 1.14.3-pre1 through 1.14.3-pre4
Yes the line spacing is intended, note the space for confirmation basis(s)
Confirmed in 1.14.2 and
in 1.14.3 as of changelogs for 1.14.3 and changelogs for 1.14.3-pre1 through 1.14.3-pre4
Yes the line space is intended, note it for confirmation basis(s)
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
Confirmed in 1.14.3 as of 1.14.3 changelogs as well as changelogs for 1.14.3-pre1 through 1.14.3-pre4
Needs reopening please... hopefully not 'whenever'
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
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
Confirmed in 1.15-pre1, 1.15 base (1.15.0), 1.15 randomly throughout, and in 1.16 snapshots
Issue Not Resolved