I would like to re-open this bug. While at a Nether Fortress on a friend's server, I figured out a new way to trigger this bug. While I figured out the old ways can be performed, something in 1.18.2 made those old methods unreliable and not work most of the time. Here is video proof that the old methods while they don't work as often as they used to, they still can: https://mega.nz/file/hcgwjToS#3wQMxPTyw6SC7tpEfMc1U2g6ayPMaKzHVe0K_lyD_wY
I have figured out that you can make a Blaze chase you and hold it's charge if you remain within a distance close enough for it to target you but not close enough to fire (18-25 blocks), and then have it fire into a stairs type block while trying to get you by letting it come to you while you wait near the top of steps and go to the top of them once the blaze starts ascending the steps, this has a high chance of having this bug occur, with video proof of course:
https://mega.nz/file/AAx20bzJ#QtbhSdOv2idGMcOlyFfgqzDeIg4qCjc3mZ6S9Xaglp0
https://mega.nz/file/lFg0UJjR#nKY8uvedeauFh-Wrf-JEe9nw5CCCmPCojLZWZcgvwzQ
Perhaps with this development, more people can pull the bug in question off, and progress can be made to figure out why it can occur.
I need verification from another person, but this bug no longer seem to be happening as of the 1.18.2 hotfix. Every method I have used to previously triggered it doesn't seem to trigger it anymore.
@GoldenHelmet, I remember you stating that this bug can be caused by lag. Do you think it is/was related to MCPE-149214 ?
This bug is still occuring as of the 1.18.2 Hotfix.
This bug is still occuring as of the 1.18.2 Hotfix.
This bug is still occuring as of the 1.18.2 Hotfix.
Somebody linked these but didn't mention that this bug relates to MCPE-143689
This bug is still occuring as of the 1.18.1 Hotfix.
This bug is still occuring as of the 1.18.1 Hotfix.
This bug is still occuring as of the 1.18.1 Hotfix. On a side note, how can this bug be related to another one that is marked as 'Confirmed', but not marked as 'Confirmed' itself?
Just updated to Hotfix 1.18.1. This bug is still occuring as of this release.
@GoldenHelmet, I just got your response pertaining to MCPE-35647, it was a messup as I was taking in the testing hallway I used being both sides having Blazes attack from both sides, as it is 30+ Blocks (The one in the video in the description). But the other behaviours I did note as different/changed. I do apologize for that. I watched my older videos of the bug as well just to make sure and you are correct.
I did note something though since you stated in a prior comment that MCPE-129070 since you stated this bug can be caused by lag. All my testing of this bug has been done on Realms and since @Skaijie and @Natthan were able to reproduce the bug, it leaves me with a question.
@Natthan and @Skaijie, since you both were able to reproduce MCPE-129070, did you do so on a Realms World, a Multiplayer World, or Single Player World?
This bug was fixed in Minecraft Hotfix 1.17.34. Can it be marked as resolved with this as the fixed version?
This bug is still occuring as of the 1.18.0 Release.
It is however somewhat harder to pull this bug off due to some notable changes in the Blaze AI with 1.18.0. They don't seem to fire their fireballs from farther distances (30+ Blocks) as they did in 1.17, and their physical aggro (Where they try to hit the player) seems to have been increased from 3 blocks to 5 blocks from my observation. Also unless they are far away, they don't seem to hold their charge nowhere as frequently as they used to via animation bug to instantly fire if you were to pull around a corner and then go back out. Curious to see if anybody else has noted any of this.
This bug is still occuring as of the 1.18.0 Release.
This bug is still occuring as of the 1.18.0 Release.
This bug is still occuring as of the 1.17.41 Hotfix.
This bug is still occuring as of the 1.17.41 Hotfix.
This bug is still occuring as of the 1.17.40 Hotfix.
This maybe an opportunity to do something for those who use Redstone and do a reverse parity and allow Large Dripleafs to be placed on Hoppers in Java Edition, which would allow for some new interesting mechanics in Redstone Contraptions.
Naturally this would be up to the development team at the end of the day, however, sometimes new game mechanics can come from bugs as such, and this can be an opportunity for that.
@@unknown this bug appears to have been fixed as of the 1.18.12 Update. I have tested it and the Drowned behave as they should now when losing their target.