mojira.dev
MC-184710

Some mobs don't have appropriate "stopping ranges" when attempting to attack an enemy.

stopping range = when a mob stops because it thinks it can attack

attacking range = when a mob actually attacks an enemy.

I thought this bug was isolated to baby zombies but it seems to apply to everything. Its just most noticeable for baby zombies because they are much smaller than the normal zombie size. They are using the stopping range of a normal zombie and this is making them miss. They stop to attack when they are too far away to even attack. This does however apply to normal zombies and other mobs just far less noticeable. I have provided clips of this bug. I recently tested this because I thought MC-147516 was a fix to it. But its still in the game.

https://streamable.com/omr8d9

https://streamable.com/fj1dqj

The stopping range of mobs should be adjusted to be consistent with their attacking range. You don't even have to be moving for this bug to occur with baby zombies. But you can get it to repetitively occur if moving.

Related issues

Comments

migrated

I am not entirely sure if 1.14 made this issue worse for all mobs. This issue suddenly became greatly exaggerated for wolves after 1.14 (see MC-155172) 1.14 Could of changed this for other mobs too. And now its just been sitting in the game unfixed. I do remember baby zombies being a lot more deadly in earlier versions of minecraft. Now because of this they are far less threatening.

migrated

I am not entirely sure if 1.14 made this issue worse for all mobs. This issue suddenly became greatly exaggerated for wolves after 1.14 (see MC-155172) 1.14 Could of changed this for other mobs too. And now its just been sitting in the game unfixed. I do remember baby zombies being a lot more deadly in earlier versions of minecraft. Now because of this they are far less threatening.

galaxy_2alex

Duplicate of now reopened MC-147516.

migrated

My issue does not resemble the issue in MC-184885. First my issue was incorrectly labeled as a duplicate of MC-147516 and now it has been changed to a duplicate of MC-184885. My issue is most likely related to MC-2310. I think you should reopen my issue.

migrated

My issue does not resemble the issue in MC-184885. First my issue was incorrectly labeled as a duplicate of MC-147516 and now it has been changed to a duplicate of MC-184885. My issue is most likely related to MC-2310. I think you should reopen my issue.

migrated

(Unassigned)

Unconfirmed

(Unassigned)

20w21a

Retrieved