mojira.dev
MCPE-73279

Blazes take a long time to aggro onto the player.

When you approach a blaze in bedrock edition they can take up to 10 seconds to attack or even look at the player. In java edition they instantly attack the player like there supposed to.

Linked issues

Attachments

Comments 7

migrated

Same problem, they may never see players and attack them. If they do, their attack rate is very slow and ineffective. The only way to make them react and damage the player is to bumb into them to trigger the "thorn effect", or hit them.

migrated

I notice that the blazes are possibly being distracted by other mobs in the vicinity, causing them to not shoot, or shoot in an untimely manner. This was a red herring. It appears they are alternating between their current facing and facing the player, no relation with mobs.

EveryCabbage884

Does this still occur in the latest version?

migrated

Now seems to happen only when the player is very close to the blaze (2-3 blocks). Otherwise it seems to shoot as expected.

migrated

I think this is now fixed in 1.16.100, they shoot fireballs correctly and use melee within 3 blocks

migrated

If blazes are intended to only perform (or attempt to perform) melee within 3 blocks of the player then yes, this can be considered fixed.

lizking10152011

Incase this bug ever comes back (Since it is fixed during the time of this post), from my experience with it, the Blazes were usually slowly spinning in place, usually in a counterclockwise direction instead of detecting the player unless:

  1. The Player came into Direct View within 16 blocks of the Blaze infront of it.

  2. The Player hit the Blaze and was within 16 blocks of it.

  3.  The Thorns Enchantment effect is triggered on the Blaze.

So it maybe safe to say that their pathfinding was bugged prior to 1.16.100 which is what may have had them spin in place in a counterclockwise direction unless any of the three prerequisites above were met.

migrated

(Unassigned)

Community Consensus

Multiple

1.16.0.58 Beta, 1.16.40 Hotfix

1.16.100

Retrieved