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

Villager is stuck in the permanent loop, unable to pathfind through the door.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Awaiting Response
    • None
    • 1.19.2
    • None
    • Windows 10 Home
    • Unconfirmed
    • (Unassigned)

      Recreated behaviour from MC-255062 in the vanilla env.

      What I expected to happen was...:
      Villager goes through the door and sleeps in the claimed bed.

      What actually happened was...:
      Villager is stuck in the permanent loop, going in and instantly back out through the door, cannot pathfind correctly to the claimed bed.

      After exiting villager is going away from the door for a short distance (like 5-10 blocks), then goes back to the door, goes through it and instantly back out (when another entity is in front of the door, like iron golem, the villager often doesn't even go through, just opens and instantly closes the door), and the loop starts again.

      Maybe useful notes:

      Single and double doors are affected.

      I tried to remove carpets as I know they can obstruct or cause some pathfinding issues, same for pressure plates, any not full blocks on the floor, ceiling, walls, or literally anything that can obstruct the bed.

      Removing the doors instantly helps, so I figured something with them is causing the issue.

      In some cases opening the door manually for the villager breaks the loop and he can go through it like normal.

      I've attached some screenshots of the three setups experiencing this issue. I tried to show the view from the outside and inside, so investigating would be easier. (in the second set of screenshots the problematic room is the nr 9 room)

      Steps to Reproduce:
      1. Create a setup like on the attached screenshots.
      2. Set in-game time to night.
      3. Spawn the villager outside the room.

        1. 2022-08-08_21.40.49_2.png
          2022-08-08_21.40.49_2.png
          868 kB
        2. 2022-08-08_21.40.49.png
          2022-08-08_21.40.49.png
          866 kB
        3. 2022-08-08_21.40.50.png
          2022-08-08_21.40.50.png
          869 kB
        4. 2022-08-08_21.41.11.png
          2022-08-08_21.41.11.png
          646 kB
        5. 2022-08-08_21.41.20_2.png
          2022-08-08_21.41.20_2.png
          659 kB
        6. 2022-08-08_21.41.20.png
          2022-08-08_21.41.20.png
          655 kB
        7. 2022-08-08_21.41.34.png
          2022-08-08_21.41.34.png
          719 kB
        8. 2022-08-08_21.41.36.png
          2022-08-08_21.41.36.png
          694 kB
        9. 2022-08-08_21.41.51.png
          2022-08-08_21.41.51.png
          657 kB
        10. 2022-08-08_21.41.58.png
          2022-08-08_21.41.58.png
          577 kB
        11. 2022-08-08_21.42.29.png
          2022-08-08_21.42.29.png
          325 kB
        12. 2022-08-08_21.43.00.png
          2022-08-08_21.43.00.png
          1.00 MB
        13. 2022-08-08_21.43.01.png
          2022-08-08_21.43.01.png
          1.01 MB
        14. 2022-08-08_21.43.10.png
          2022-08-08_21.43.10.png
          582 kB
        15. 2022-08-08_21.43.19.png
          2022-08-08_21.43.19.png
          642 kB
        16. 2022-08-08_21.43.21.png
          2022-08-08_21.43.21.png
          813 kB

            Unassigned Unassigned
            Trace404 Trace404
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: