Blazes spawned from blaze spawners seem to have no path-finding AI. Pre 1.11, once a blaze descended to a block, it would spin a bit, then start moving around, usually path-finding on a diagonal. Now, they just descend to the block, and sit there, only moving when their hitbox collides with another entity (usually another blaze that spawned and descended on top of it).
I haven't been able to evaluate blazes naturally spawned in nether fortress boundaries (explicitly not those spawned by a spawner).
I've searched around the different bugs for different platforms and don't see anything describing this exact issue. Additionally, the 1.11.0 release notes do not mention this type of change for blazes. I did notice a 1.11.1 "fix" about spawners not obeying light level rules, which may be related to this, but may not be.
Linked issues
is duplicated by 4
Attachments
Comments 11
Yes, it is still an issue
Just checked my Blaze farm and can confirm that this is still issue in 1.14.1
Duplicated by MCPE-45973, if we are considering both naturally-spawned and spawner-spawned blazes. I don't see why they would be different.
Also, might relate in some way to MCPE-45559 where they jump around in circles.
I am attaching a video of a blaze just barely creeping along. If you watch the shadow closely you can see that the blaze moves in a small circle around one block before moving on to the next, and then it begins to circle that block. I don't know if these are the same circles described in MCPE-45559. Perhaps it is only able to pathfind from one block to another at a certain pixel location, like at a particular corner, and it circles looking for that passable point? Could that be due to a calculation error (formula typo???) in the pathfinding algorithm?
Update 1/28/20: This report is a duplicate of MCPE-45559, since it describes aspects of the same behavior. I started testing MCPE-45559 and ended up adding comments and videos to that ticket that are just as relevant to this one. In brief, it looks to me like blazes are setting very short pathfinding targets, to the point that they frequently target the block that they are already standing in.
Resolving issues that were marked as fixed in the 1.15 and 1.16 Betas, now that 1.16.0 is being released.
Current: 1.16.0: The pathfinding did fix from the last update for a bit but now it's totally broken again.
[media]
@@unknown can you elaborate? Your picture just shows a massive number of blazes on one side of a room. That could just be a manifestation of MCPE-45800 and MCPE-41092.
There is North West Bias, but the Blazes will not Pathfind onto my magma block trap that so happened to be in the South-East corner and just go straight to the north and west sides. I checked today and its still the same situation. I had it until the room was full and the blazes were in a triangle heading to the north-west corner. It has totally broken my Farm which sucks.
@@unknown: as of 1.16 blazes have a parameter to avoid blocks that cause damage in their navigation AI. So I think a magma block trap will not work on them. That's probably why they are on the opposite side of the room.
@GoldenHelmet I didn't necessarily mean that it was a magma block trap what I meant was there is a hole in the opposite corner of where they are trying to pathfind to. And blazes are resistant to fire damage so It would not damage them and they wouldn't need to avoid it.
It looks like blazes no longer wander onto air blocks where they can fall. They just won’t go over an edge. That’s a very different issue than this ticket was tracking, so I’ve made a new report at MCPE-89155.
Is this still an issue in the latest version?