The world save is here. The structure is quite simple, but please note that this issue is not 100% reproducible—in fact, the trigger probability is relatively low. However, the scenario does exist, and reloading may sometimes cause the facing direction to become incorrectly locked.
I can confirm there are no other nearby targets that could trigger the zombie's aggression. Additionally, this bug does not occur consistently with every reload. The behavior feels more like during reloading, the zombie determines its facing direction first, and then gets locked by the minecart’s orientation—as seen in the video, if you reload again, there's a high chance its direction will change back to the correct one.
Then why are the drops from Ghasts killed by Ghast fireballs deflected back by players not destroyed by the explosion? Additionally, the Ghast music disc only drops when a Ghast is killed by a direct hit from a fireball, not when killed by the explosion damage—even though both types of damage can instantly kill the Ghast.
The latest beta release notes mentioned a fix for this issue, but it's evident that the problem hasn't been fully resolved. It appears the developers only adjusted the Zombie Villager behavior, while the other mobs referenced in this bug report remain unfixed - they still cannot properly pick up spears as weapon replacements like they do with swords. This is completely unreasonable.
yes,and the wither_skeleton It also won't fall, which is unreasonable.
However, still firing randomly instead of aiming at the target when the attack target has already been locked is obviously wrong.
可以的,问题不大
In version 26.0.27, although this bug was supposedly fixed, the developers forgot to remove the patch previously applied to prevent naturally spawned baby zombie villagers and baby husks from riding chickens. This oversight has now created a conflict with the recent fix, resulting in an even more severe bug: currently, naturally spawned baby zombie villagers and baby husks have become unable to ride any mob at all—clearly contradicting the expected behavior described in the release notes.