MCPE-35647Blazes attack range too low
Steps to reproduce
- In a flat creative world, make a 4-block tall pillar.
- Spawn a blaze on the pillar.
- Move >50 blocks away.
- Switch to survival mode.
- Approach the blaze slowly.
Expected result
The blaze starts shooting at you at 48 blocks away (MC-112013)
Actual result
The blaze targets you at 48 blocks away (shown by its flaming up) but then stops, and does not shoot at you until you are within 16 blocks.
Blaze attack range.mp4
- You may notice that the blaze has very slow attacks and range. he does not attack with the fireball, even far away though and he may still detect us
Device: LG K10
Linked Issues
Attachments1
![[Mod] GoldenHelmet](../../../data/avatars/users/18951.svg){kind=small}
- Unresolved
Lio- 18
- 4
- Confirmed
- 588756
- Multiple
- Android 6.0
- attack blaze java-parity range
1.20.10.20 Preview - 1.21.51 Hotfix
1.20.10.20 Preview 1.20.0.20 Preview 1.19.80.24 Preview 1.19.80.23 Preview 1.19.80.22 Preview 1.18.30.29 Preview 1.18.30.28 Beta 1.18.30.27 Preview 1.18.30.26 Beta 1.18.30.23 Preview 1.18.30.22 Beta 1.18.20.30 Preview 1.18.20.28 Preview 1.18.20.29 Beta 1.18.20.27 Beta 1.18.20.25 Beta 1.18.20.24 Preview 1.18.20.23 Beta 1.18.20.22 Preview 1.18.20.21 Beta 1.18.10.22 Beta 1.18.10.21 Beta 1.18.10.20 Beta 1.18.0.27 Beta 1.18.0.24 Beta 1.18.0.23 Beta 1.18.0.22 Beta 1.17.10 1.6.0.6 1.6.0.8 Beta 1.6.0.30 Beta 1.7.0.2 Beta 1.7.0.9 Beta 1.17.40 1.18.0.25 Beta 1.17.41 Hotfix 1.18.0 1.18.1 Hotfix 1.18.2 Hotfix 1.18.10 1.18.30.21 Preview 1.18.30.20 Beta 1.18.12 Hotfix 1.20.0.22 Preview 1.20.0.21 Preview 1.20.0.24 Preview 1.20.0.23 Preview 1.21.51 Hotfix
Created Issue:
Blazes have much lower attack and sight range
- You may notice that the blaze has very slow attacks and range. he does not attack with the fireball, even far away though and he may still detect us
Device: LG K10
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
Steps to reproduce
- In a flat creative world, make a 4-block tall pillar.
- Spawn a blaze on the pillar.
- Move >50 blocks away.
- Switch to survival mode.
- Approach the blaze slowly.
Expected result
The blaze starts shooting at you at 48 blocks away (
MC-112013)Actual result
The blaze targets you at 48 blocks away (shown by its flaming up) but then stops, and does not shoot at you until you are within 16 blocks.
Blaze attack range.mp4
- You may notice that the blaze has very slow attacks and range. he does not attack with the fireball, even far away though and he may still detect us
Device: LG K10
Blazeshave much lower attack and sight rangeBlazes attack range too low
![[MCQA] v-weszaj](../../../data/avatars/users/18941.svg){kind=small}
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
relates to
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
I've been studying the .json files and documentation, as well as NBT data, and I think the problem with targeting ranges may be due to contradictions between minecraft:follow_range, attack_radius (within minecraft:behavior.ranged_attack), max_dist (within minecraft:behavior.nearest_attackable_target), and a lack of any specification for persist_time (also within minecraft:behavior.nearest_attackable_target).
Ghasts
follow_range = 64
attack_radius = 64
max_dist = 28
Comment: these values make it look like Ghasts are supposed to be able to follow and attack players from 64 blocks away, but that range is defeated by their inability to target beyond 28. Since the default persist_time is 0, even if they acquire targets within 28 blocks, they immediately drop those targets if they are > 28 blocks away.
In Java Edition ghasts target players at 64 blocks away, but only when they are also within 4 blocks vertical. That can be done in Bedrock Edition by using the following lines in "minecraft:behavior.nearest_attackable_target":
"max_dist": 64 (within the player filter)
"target_search_height": 4
See here for the Java code analysis.
Ravagers
follow_range = 64
max_dist = 16
These values make it look like Ravagers are supposed to follow targets up to 64 blocks away, but they can only select targets 16 blocks away. Like Ghasts, with no persist_time, they immediately drop targets beyond 16 blocks. However, Ravagers do have a max_dist of 64 under the hurt_by_target component, so they can target a player/mob that hurts their rider from that distance.
Java parity would be a max_dist = 32.
Zombies/Husks/Drowned/Zombified Piglins
<no follow_range specified>
max_dist = 35 (20 for drowned)
Zombie variants default to follow_range = 16, which defeats their targeting range. The reason some do pursue targets that are farther than 16 blocks away is that they can get a RandomSpawnBonus multiplier to the default range. Here is an example:
Husks also have a within_radius = 25 (in nearest_attackable_target). According to the updated documetation for 1.16, this is supposed to specify how far away a target can be followed if follow_range is not specified. I'm not sure how this is supposed to work; the way it reads to me is that in conjunction with the default persist_time = 0, within_radius would defeat any higher max_dist targeting range for melee attacks. In actual gameplay it seems to be defeated by the default follow_range.
Endermen
follow_range = 32
search_radius 64 (within minecraft:lookat, for aggro at players)
max_dist = 64 (for endermites)
Endermen agrro and target from 64 blocks, but this is defeated by their lower follow range. Related to MCPE-35306.
Blazes (MCPE-35647)
follow_range = 48
attack_radius = 16
max_dist = 48
Blazes should be able to target and attack from 48 blocks (see MC-51266 and MC-112013), but this is defeated by their attack radius. You can see them aggro when they target at > 16 blocks because they flame up and start to float but then quickly stop.
Blazes have never fired from more than 16 blocks away in Bedrock Edition: see MCPE-35647.
@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?
Cleaning up old tickets: This ticket has not been updated recently (~7 months+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue and is affecting the most recent versions, then please comment, or create a new ticket following the Issue Guidelines.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
I am still experiencing this issue in 1.14.60
Still not fixed in 1.16.20.50
Reopening because this is still an issue. The vanilla entities\blaze.json gives targeting and follow ranges of 48 blocks, but the ranged attack radius is only 16 blocks. This was reported as a bug in Java Edition in 2014 at
MC-51266and fixed in December 2016 (seeMC-112013).Affects 1.17.40.20