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

Search range for beds of "imported" Villagers is reduced

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Awaiting Response
    • None
    • Minecraft 1.14.1
    • None
    • Windows 10 Home (Version 1803)

      Java 1.8.0_191-b12
    • Unconfirmed
    • Village system

      Setup: I created a village in a survival (Realms) world by "importing" two Villagers from an existing village and then starting a new village in the middle of nowhere. I gave these two Villagers their own names through the use of a Name Tag and let them create 5 new Villagers in this new village, who all remained nameless due to the lack of a Name Tag.

      Bug: Since I am still building the village, I am constantly moving the beds around. The 5 new Villagers all have no problems with this and can find a new bed when night falls. However, the two "imported" Villagers just stay standing around at night and don't even move at all. Only when I place a bed really close to them will they find it and sleep in it.

      Observations: It seems that the detection range of beds for normal Villagers is around 42 blocks (taxicab distance in all dimensions), but the imported Villagers stop detecting around 8 or 10 blocks. I haven't tested the detection range of Job Site blocks for the Villagers.

      Speculation: It is no coincidence that these two Villagers are the ones who have trouble. I imagine it is either the fact that they originally came from another village or the fact that they've been named. I don't have the resources to easily test different cases.

        1. NotRouteToBed.jpg
          NotRouteToBed.jpg
          352 kB
        2. 2019-05-24_22.22.21.png
          2019-05-24_22.22.21.png
          972 kB
        3. 2019-05-24_22.08.57.png
          2019-05-24_22.08.57.png
          854 kB

            Unassigned Unassigned
            Nurio Nurio Marayana
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: