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

Vex do not chase their targets if they aren't actively charging at them

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Works As Intended
    • None
    • 1.19.2, 22w45a, 22w46a, 1.19.3 Pre-release 1, 1.19.3 Pre-release 2, 1.19.3 Release Candidate 1, 1.19.3, 23w03a, 23w04a, 23w05a, 1.19.4, 23w13a
    • None
    • Confirmed
    • Mob behaviour

      The bug

      Vex do not chase their targets they're hostile towards, unless they're actively in their "attacking" mode where their charge their target and strike them. They follow and track their opponent in this mode, chasing them down until they can get a hit or they avoid it. However, when in their "waiting" state where they're still actively focused on a target and could charge at any random time, although they will look at whatever they're attacking, they won't follow it.

      This means you can easily just sprint, or even walk away from a Vex and they won't follow you and easily give up, as demonstrated in this video:

      VexRangePlayer.mp4

      This is especially noticeable when an Evoker tries to attack a villager; the Villager simply runs and they Vex do not follow unless they're in their "red" state, as can be seen here:

      VexRangeVillager.mp4

      This means that Zombies, Pillagers, Ravagers, and Vindicators are infinitely better at chasing villagers.

      How to reproduce

      1. Spawn an Evoker in an open field and have it summon some Vex, or just summon few Vex yourself
      2. Run, or even walk away from them
      3. They will follow you at first as they charge at you, but even though they will still be tracking you, they won't chase after that and very easily give up
      4. You can also try this with a Villager; the villager can very easily just walk away

            Unassigned Unassigned
            DiamondDragon721 Orbic
            Votes:
            5 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: