Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-45270

Villagers do not link to the nearest bed/workstation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Works As Intended
    • None
    • 1.11.0
    • None
    • Community Consensus
    • Windows

      The linking between villagers and their workstations/beds seems to be a random process.
       
      Test-case

      • Have some unemployed, homeless (read: no bed) villagers in the world (blocked in a 1x1 glass box for testing purposes).
      • Place a bed in the world.

      Observed facts

      • Beds are detected by the location of the pillow.
      • Villagers seem to have a centered detection "square" (needs further testing, might be cube) of ~ 32x32 for beds (workstations untested).
      • Placing a bed's pillow outside the detection range of all villagers means said bed remains undetected by any villager.

      Expected result
      The nearest, homeless villager will spot the new bed and bind to it.

      Actual result
      The nearest, homeless villager will spot the new bed, but the homeless villager that binds to it is picked randomly.

      As a result, it is very difficult (if not impossible) to let villagers bind to specific sets of beds.
      Obviously this affects "Trading Halls" which could arguably be unintentional, making this 'feature' a WAI. But even than this behavior is annoying when for example trying to make a nice, maybe segmented village and ending up with mad villagers that are unable to reach their bed/station as they picked one they can never see/reach again.

      In my opinion, this behavior should be more controllable. For example by only choosing one of the villagers that can actually see the object by itself or, even better, determining the closest one of them.

        1. Minecraft 25-4-2019 22_11_07.png
          2.68 MB
          CoalBuster

            CoenB95 CoalBuster
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: