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

Enderman automatically re-aggros just by being in their line of sight

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • None
    • 1.19.4 Pre-release 4, 1.20, 1.20.1, 23w32a, 23w33a, 23w35a, 1.20.2 Pre-release 1, 1.20.2 Pre-release 2, 1.20.2 Pre-Release 3, 1.20.2 Pre-Release 4, 1.20.2 Release Candidate 1, 1.20.2 Release Candidate 2, 1.20.2, 23w40a, 23w41a, 23w42a, 23w43a, 1.20.4, 24w04a, 24w05b
    • Confirmed
    • Mob behaviour
    • Normal
    • Gameplay

      In situations where an angered Enderman normally should stop being hostile towards the player, the Enderman instead continues being hostile, as long as the player is visible. The only way to turn them permanently neutral again is if the player dies.

      The Enderman can turn temporarily neutral if the player is not in their line of sight when:

      1. The Enderman loses interest and teleports away due to daytime, or
      2. The player changes to creative mode

      Normally, this should be "permanent". But due to the bug, as soon as the player is back in survival mode and in their line of sight, they automatically turn hostile without provoking them.

      To reproduce

      1. Summon or find an Enderman.
      2. Set time to day, and gamemode to survival.
      3. Provoke the Enderman by looking at it or attacking it
      4. Enter a building where the Enderman doesn't have a line of sight to you (use glass blocks to see them becoming neutral again).
      5. Wait.
      6. Enderman loses interest, and is no longer hostile. (The stare sound also plays again - MC-216648).
      7. Leave the building.
        → The Enderman instantly sees you and is suddenly aggressive again without being provoked.

      The issue in the code might be that the Enderman never forgets about the player even after becoming neutral, and only forgets if the player dies.

      Possibly related to/caused by MC-197635 becoming fixed, which seems to be related to the fix of MC-188506 in the same snapshot.

            Unassigned Unassigned
            jouppi22 Jon1337
            Votes:
            5 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              CHK: