I have a blaze farm that makes blazes fall down a into a 1x1 hole so i can kill them. But for some reason they are jump for no reason and are going around in a circle and not moving. Just found out this can be any blaze naturally or spawned with eggs. I made a new seed and blazes behaved normally then broke for no reason.
Blaze moves for a short time normally then brakes and jumps in circles. Currently making blaze farms broken
Linked issues
is duplicated by 3
Attachments
Comments 11
this can happen to any blaze. Updated title and description.
seems to be fixed in beta 1.12.0.2 will leave this open until 1.12 is released
Added a video, which shows
The blaze stays still about 7 seconds after spawning before it starts jumping.
When jumping blazes stay within a single block.
Both of these points suggest that this behavior relates to pathfinding. The jumping probably starts when the blaze begins trying to pathfind. The jumping is like MCPE-45256 and MCPE-60160 where mobs jump repeatedly when trying to pathfind to a block they cannot reach.
Following the previous comment, I tried to get my jumping blazes to move with various configurations. They would not move down a 1-block step or stairs, or from a block to a lower half-slab. Nor would they move up from a block to an adjacent carpeted block or up to a half-slab. If you put carpet under them and half-slabs adjacent, they will sometimes get over the edge of the half slab and jump from that, but always back to the carpeted block. You can see this in the second video. I think it is due to the hitbox of the blaze overlapping the slab just enough to jump off of it, but not enough for the AI to think it is located on that block.
I also noticed that the movement is not quite circular. it is more of an arc shape where each jump takes it about 200 degrees (or 160 degrees if you think of it the other way around), like a spirograph.
Edit: a [hypotrochoid|http://en.wikipedia.org/wiki/Hypotrochoid].
With further testing I have observed:
Sometimes amidst the 1-block hypotrochoid jumping blazes will move up to an adjacent block, and then continue to wander. This explains why they can still jump out of nether fortresses and end up on the ground or lava below.
In the attached video, you can see that when the blaze moves out of its 1-block hole and then begins wandering, itonly moves 1-3 blocks at a time before briefly resuming within-block jumps.
If you hit a blaze off of the block it is jumping on, it will move straight back to it! (Video attached.)
These observations suggest that the blaze AI is very frequently setting the block where it is already located as its pathfinding target. (This brings to mind the possibility of a formula typo as I mentioned commenting on MCPE-45469.) Perhaps accidentally moving to an adjacent block because of a step-up triggers a recalculation of the target, which then also makes subsequent target calculations more variable; but being artificially moved by a player hit does not trigger a recalculation so it returns straight to its original block.
Thanks for all the videos and taking the time to test this. Seems like the blaze A.I/pathfinding is super broken. Even more than i originally thought. It has almost been like this for a year now. Hopefully they know about it but with how the smooth quartz texture(been like that since it was introduced) and still has not been fixed. I doubt it will be fixed anytime soon.
Maybe since they are both nether features they will finally be fixed lol.
@Jacob2of3 they did remove smooth quartz from the crafting table recipes, by the way. In 1.14 I think.
Oops, you make smooth quartz by cooking, not crafting.
I expect that the fix to MCPE-45469 in the 1.15.0.51 beta should fix this issue as well. If anyone watching this report can test blaze wandering in a any of the 1.15 beta versions that would be much appreciated.
This looks to be fixed in 1.15.
[media]
Resolving issues that were marked as fixed in the 1.15 and 1.16 Betas, now that 1.16.0 is being released.
This is the same behavior I see as well on 1.11.0 for Nintendo Switch and I think it's related to what I reported in MCPE-45469 . Do you notice this behavior from naturally spawning blazes? I'm thinking not, but really haven't had a chance to investigate yet.