MC-112013Blaze Attacking from long distance
This is on a Realms Vanilla (obviously) Survival SMP Server.
While digging out a large area in the nether, Blazes are attacking from 50-75 blocks away. I know they can "call" others up to 50 blocks away, but I thought that was just to move closer, then shoot when they're in range. Regardless, I looked around and there weren't any closer than the ones shooting. (Screenshot attached of aggro'd blaze, the others were in cooldown, and I've been attacked from further away too).
Environment
Win10, Java 1.8.0_51 64Bit, Running Multiplayer REALMS server.
Linked Issues
is duplicated by5
Attachments1
Created Issue:
Blaze Attacking from long distance
This is on a Realms Vanilla (obviously) Survival SMP Server.
While digging out a large area in the nether, Blazes are attacking from 50-75 blocks away. I know they can "call" others up to 50 blocks away, but I thought that was just to move closer, then shoot when they're in range. Regardless, I looked around and there weren't any closer than the ones shooting. (Screenshot attached of aggro'd blaze, the others were in cooldown, and I've been attacked from further away too).
Environment
Win10, Java 1.8.0_51 64Bit, Running Multiplayer REALMS server.
Attachments1
relates to
is duplicated by
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Thank you for your report!
However, this issue has been closed as a Duplicate of MC-112013.
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
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
![[Mod] GoldenHelmet](../../../data/avatars/users/18951.svg){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.
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-112013, which was marked as Intended.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
I noticed a similar situation in single player survival. Blaze shoot fireballs from roughly 50 blocks away on hard difficulty. When further away they remain idle, but attack immediately when they target the player at roughly 50 blocks.
Seems like
MC-51266was fixed.Works as intended.
I really don't agree that it's intended behavior. I can't find that anywhere in the release notes. They're so far away you can't see or hear them, they just spawn in (as a pack) and start attacking. If it IS intended behavior, then it's a terrible change, but I know this isn't the place for those conversations. Thanks for everything you guys do for the community.