Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-96368

Zombie behavior inconsistent when pursuing targets.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Works As Intended
    • None
    • Minecraft 16w03a, Minecraft 16w04a, Minecraft 16w05b, Minecraft 16w06a, Minecraft 1.9 Pre-Release 3, Minecraft 1.9 Pre-Release 4, Minecraft 1.9, Minecraft 1.9.1 Pre-Release 1, Minecraft 1.9.1 Pre-Release 2, Minecraft 1.9.1 Pre-Release 3, Minecraft 1.9.1, Minecraft 1.9.2, Minecraft 16w14a, Minecraft 16w15a, Minecraft 16w15b, Minecraft 1.9.3 Pre-Release 1
    • Windows 8 Java 1.7.0_71-b14 32bit Minecraft Launcher 1.6.44
    • Unconfirmed

      Summary: Zombies will always pursue the Player first, even when nearby Villagers are closer to the Zombie than the Player is. It has also been observed that Zombies who are pursuing Villagers, will randomly stop attacking the Villager and will began attack the Player. Both these issues has only been tested on Hard difficulty. Can probably attribute it to improvements on pathfinding since 15w49a.

      How to Reproduce:
      1. Place a Monster Spawner and set the spawning mob to a Zombie.
      2. Get far away enough so that you aren't triggering the spawner, but not too far that you can't get a Villager near the spawner.
      3. Spawn a Villager, make sure it is in the trigger radius of the spawner.
      4. Hit the Villager a few times until there is enough space for you to get inside the trigger radius, also be sure the Villager is between you and the spawner, but make sure the spawner is visible.
      5. Note how the Zombie pursues you instead of the Villager.
      6. If you run far away enough, the Zombie might pursue the Villager instead, but if you get into the detection range, the Zombie will stop attacking the Villager and will begin to pursue the Player.

        1. 2016-01-30_14.35.53.png
          2016-01-30_14.35.53.png
          199 kB
        2. 2016-01-30_15.42.27.png
          2016-01-30_15.42.27.png
          150 kB
        3. 2016-01-30_15.48.29.png
          2016-01-30_15.48.29.png
          141 kB
        4. 2016-01-30_15.48.30.png
          2016-01-30_15.48.30.png
          143 kB
        5. 2016-01-30_15.48.36.png
          2016-01-30_15.48.36.png
          218 kB
        6. 2016-01-30_15.48.37.png
          2016-01-30_15.48.37.png
          219 kB
        7. 2016-01-30_16.07.39.png
          2016-01-30_16.07.39.png
          182 kB
        8. 2016-01-30_16.07.47.png
          2016-01-30_16.07.47.png
          125 kB
        9. 2016-01-30_16.19.06.png
          2016-01-30_16.19.06.png
          189 kB
        10. 2016-01-30_16.19.08.png
          2016-01-30_16.19.08.png
          198 kB
        11. 2016-01-30_16.38.31.png
          2016-01-30_16.38.31.png
          163 kB
        12. 2016-01-30_16.38.33.png
          2016-01-30_16.38.33.png
          161 kB
        13. 2016-01-30_16.38.38.png
          2016-01-30_16.38.38.png
          123 kB
        14. 2016-03-25_13.10.15.png
          2016-03-25_13.10.15.png
          228 kB
        15. 2016-03-25_13.10.18.png
          2016-03-25_13.10.18.png
          369 kB
        16. 2016-03-30_20.14.10.png
          2016-03-30_20.14.10.png
          163 kB
        17. 2016-03-30_20.14.14.png
          2016-03-30_20.14.14.png
          211 kB
        18. 2016-03-30_20.14.16.png
          2016-03-30_20.14.16.png
          204 kB
        19. 2016-03-30_20.15.41.png
          2016-03-30_20.15.41.png
          255 kB
        20. 2016-03-30_20.15.44.png
          2016-03-30_20.15.44.png
          257 kB
        21. 2016-03-30_20.15.48.png
          2016-03-30_20.15.48.png
          260 kB

            ProfMobius ProfMobius (Thomas Guimbretiere)
            foltrox Bren Rado
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: