MC-70327Blaze fireballs damage other blazes
Blaze fireballs now damage other blazes if there is one in between the firing blaze and the player.
Linked Issues
is duplicated by1
Created Issue:
Blaze fireballs damage other blazes
Blaze fireballs now damage other blazes if there is one in between the firing blaze and the player.
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
Added Assignee: 
ProfMobius (Thomas Guimbretiere)
ProfMobius (Thomas Guimbretiere)Deleted Comment:
A comment with security level 'Users' was removed.
Added Linked Issues:
is duplicated by
@Skylinerw: In 15w49a the second line of the pseudocode you quote changed to something along the lines of FireballCollisionData.theHitEntity != null && !FireballCollisionData.theHitEntity.isImmuneToFire(), probably as the fix for MC-70327. But since, as you noted, FireballCollisionData.getBlockPos is null when the fireball hit an entity, it breaks when it gets into the other code path.
Sounds intended.
Can confirm. This makes killing blazes too easy. Definately not intended behavior.
I have the same problem. I had created a blaze xp farm prior to the 1.8 update and it was working fine.
Now when I get close to them to collect xp and blaze rods they just kill themselves off leaving one or two.
Confirmed for 1.8. This was not mentioned on any of the 1.8 prerelease changelogs on the wiki and the Mojang website so its probably a bug.
Confirmed for 15w31b.
when they reworked the mob ai they changed how blazes worked therefore it is assumed this was intended