This is an update on Bug Report of now Invalid report MCPE-108171 now that I understand what is going on and have seen this bug in action enough times.
Edit One: Seems to be a glitch with the website when uploading the video MP4 file I have that I cut down to under 10 MB with Openshot. It only plays the audio when uploaded, so if you want to see this in action, download the video here from my MediaFire: Removed for Second Edit.
Edit Two: Due to Mediafire not working, here is the video file from Mega.nz : https://mega.nz/file/Mcw2iZpI#aubfmK1fAUl-oxbnVgo4l6n-llqCu6xPvVwZVmQDu3w
Whenever a Blaze fires a Blaze Fireball if having a wall infront of it (This is rather hard to do), it has a chance of glitching out and firing it's Fireballs behind it instead of at it's target. These reversed fired Blaze Fireballs have the following attributes while they are present for 10-30 seconds; or before they hit something whichever comes first:
The reversed fired Blaze Fireballs have a slower moving speed. This can go as slow as a player walks.
The reversed fired Blaze Fireballs are sometimes acknowledged as a Mob by other Mobs. I have had Wither Skeletons stop chasing me to look at the bugged fireball, then look back at me and resume the chase.
The reversed fired Blaze Fireballs can be jumped on, though will dissipate and hurt the player as normal when this is done.
Steps to Reproduce:
Goto a Nether Fortress and fight some blazes.
Try to get a Blaze to fire Blaze Fireballs with a wall infront of it while firing.
Observed Results:
In some instances, the Blaze will fire it's Fireballs in a reverse direction at slower speed. These reversed fired Fireballs have some quirky attributes as mentioned above.
Expected Results:
The Blaze should either not fire it's Fireballs until a Target is clearly visible; or the Blaze should fire it's Fireballs forward into the wall infront of it.
Linked issues
Comments 26
This likely happens due to a collision between the fireball and the blaze. Fireballs are indeed entities like mobs. They are affected by collision with mobs (unlike items) because entities\small_fireball.json contains the line
"minecraft:pushable": {
"is_pushable": true,It seems debatable whether blaze fireballs should have this property at all, since fire is immaterial. It may just be a default that was put in the small_fireball.json without consideration. XP orbs and player-thrown tridents have the same issue (MCPE-87711 and MCPE-60895). Ghast fireballs have collision as well, but that makes sense because ghast fireballs explode desctructively, which would seem to imply lore-wise that they contain a core of explosive material. If blaze fireballs are supposed to more like pure fire (as I imagine them to be), then I can't see why they'd be pushable. Moreover, ghast fireball collision is important for some technical contraptions like cobblestone farms and tree farms, but I am not aware of any tech based on blaze fireball collision.
Aside from the issue of fireballs having collision, this bug might alternatively be attributable to the offset used for spawning blaze fireballs. That is, given that fireballs have collision, a blaze's fireball probably bounces backward when the blaze is against a wall because the fireball originates from inside the blaze's head. My guess is that when the blaze is against a wall the fireball "hits" the wall immediately after being spawned and loses its forward momentum, and then before it can be despawned on the next tick it gains momentum in the opposite direction from the wall due to overlapping the blaze collision box.
It is possible to set blaze fireballs to originate from the edge of the blaze's body (where I'd imagine they come from) by using something like this for the offset (compare my solution for MCPE-35202):
"offset": [ ".25 * math.sin(query.body_y_rotation)" , .5, ".25 * math.sin(query.body_y_rotation - 90)" ]@GoldenHelmet, here is the video where you can see a Wither Skeleton acknowledge the glitched Blaze Fireball: https://www.mediafire.com/file/6ttr4tkap2ku3rr/Minecraft_2020-11-25_21-20-30.mp4/file It's more towards the end but you will see it pass it to get to me, then look at it quick and then back to me, which I have never seen a Wither Skeleton do with any other mob or projectile. So it's interesting to see that if the Blaze Fireball is slow enough, other mobs may acknowledge it by looking at it for a duration.
Perhaps your suggestions can be tested in a future hotfix to see if any of them can fix this bug?
@GoldenHelmet, I uploaded it to Mega.nz with the link above in the description . Let me know if you are still having issues viewing the video.
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 ?
No, because it occurred long before that.
For future reference, it is not necessary to comment about every affected version. Adding the affected version on the ticket header is sufficient.
Closing as Cannot Reproduce. If this issue still occurs, please reopen this ticket or create a new one.
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.
Since this bug has technically existed since the 1.16.101 Hotfix as per the now Invalid MCPE-108171 report, can somebody add the 1.16.101 Hotfix, and 1.16.220 Hotfixes to the Bug Report as Archived Versions please?