Villagers detecting beds and workstations they can't reach
Updated description by [Mod] GoldenHelmet
Steps to reproduce
- Place a bed and workstation.
- Fully enclose the bed and workstation in opaque blocks.
- Spawn a villager.
Expected result
The villager does not link to the bed and workstation.
Actual result
The villager links to the bed and workstation, even though he can neither see them nor pathfind to them.
Original description
Very similar to MC-155238 I have a village behind my house, blocked in by fences/gates, the villagers are detecting my workstations through the walls and also my bed, which is a floor up and involves a spiral staircase made of slabs. Seems the villagers are not using a pathfinding algorythm but are instead just going off raw distance
You can easily work around the specific problem of villagers claiming beds and workstations you don't want them to by placing them where a villager can't detect them.
First, you need to slightly adjust how you think about villagers detecting POI blocks (beds and workstations for our purposes). Without going down the technical rabbit hole, think of it as follows:
- A villager can only discover POI blocks that are within 16 blocks horizontally and 4 blocks vertically of their position.
- When a villager discovers a POI block, it immediately communicates the kind and position of the block to all the other dwellers in its village.
- If a POI block is broken, all the village dwellers instantly know about it and forget the block.
- Any villager can claim any POI blocks that isn't already owned, regardless of which villager discovered it initially.
- The block has to be rediscovered by one of the villagers every few minutes (the exact time is unknown or unpredictable) or it will be forgotten.
Given the above rules, it's easy to see that all you have to do is keep your personal POI blocks at least 16 blocks horizontally and/or 4 blocks vertically away from anywhere a villager might stand. Ways to keep the villagers away might include:
- Placing your blocks on a hill or in a valley where they can't pathfind to (but make sure there are no hills or caves they can get to that could get them in range).
- Building a defensive wall or fence around the village, then subdividing it with another fence or wall to make yourself an enclave. Make sure your blocks are at least 16 blocks from the dividing fence.
- Dig a hole about 7 blocks below the lowest point in the village and build your mini-base in it. Make sure there are no caves around that villagers could get into.
If an accident happens and your POI blocks are discovered, just fix the problem that let the villagers get too close, get them back where they belong, and then break the POI blocks and replace them.
Linked Issues
is duplicated by45
MCPE-47519Villager Professions. Not Visual?DuplicateMCPE-57166Villager job site issuesDuplicateMCPE-59149Villager POI Selection/Switching not honoring Valid PathDuplicateMCPE-60525Villager detecting workstations through wallsDuplicateMCPE-62186Villagers brokenDuplicateMCPE-64509Villager AI problems???DuplicateMCPE-67760DUPLICATE!!!!!!!!!!! IDK HOW TO DELETE IN JIRA. THE UI IS SO UNINTUITIVE.DuplicateMCPE-76397Villagers are able to change their profession without being in direct contact with workbenches. This has caused many problems because my house is in a village.DuplicateMCPE-81777Villagers lock onto player beds that they can't pathfind to and will not sleep in the beds next to their workstations.DuplicateMCPE-82862Villagers don't sleepDuplicateMCPE-87574Villagers desynchign with beds and toolstations and synching with ones they cannot accessDuplicateMCPE-111051Villagers pathfinding workstationsDuplicateMCPE-112909villagers can connect to beds for absurd distancesDuplicateMCPE-117677Villager take block of profession if it stands above them or behind the wallDuplicateMCPE-118411Villagers will claim job site blocks that are otherwise unreachable.DuplicateMCPE-119196Villagers detecting workbenches from too farDuplicateMCPE-122603Villagers *Big Bug*DuplicateMCPE-127437Villager Mechanics and Iron GolemsDuplicateMCPE-129678Parity issue: Villagers don't reach their workstation before claimingDuplicateMCPE-133529Villagers will claim a workbench that they can't pathfind to, including changing the specific work bench every time you relog, resulting in the majority of the villagers in a trading hall unable to refill their trades.DuplicateMCPE-137665Villagers can link to work stations though blocksDuplicateMCPE-139121Villagers will randomly choose a job block they cant pathfind to,DuplicateMCPE-140283Villager path finding problemsDuplicateMCPE-143501The Villagers sees through the wallsDuplicateMCPE-145436Villager professions are broken and will path find professions through blocks, glass and closed fence gatesDuplicateMCPE-148680Villagers claiming workstations that they can't see or accses DuplicateMCPE-151791Villagers getting a job without touching the workbench.DuplicateMCPE-151996Villager link to workstation they are unable to pathfind to.DuplicateMCPE-152812villager can link to workstations behind a blockDuplicateMCPE-153938Villagers Take Job Despite Being Many Blocks Away From Job BlockDuplicateMCPE-160812Villagers do not retain workstations after 1.19.20DuplicateMCPE-161282Villagers link to other workstation and sometimes lock their job after you sleepDuplicateMCPE-166824Villagers take worktables and beds too far away from themDuplicateMCPE-167426Villagers see through the ground!DuplicateMCPE-168701My villagers don't claim the closest workstationDuplicateMCPE-168776Villagers can claim beds/workstations despite if they are reachable or notDuplicateMCPE-171241Villager Path FindingDuplicateMCPE-172651villager does not take the nearest profession.DuplicateMCPE-173900Villagers professioning more than 20 blocks awayDuplicateMCPE-174437Villager Job Finding not workingDuplicateMCPE-179220Villager ProblemDuplicateMCPE-181935Villagers have super rank when picking up a jobDuplicateMCPE-184734I've encountered issues with Minecraft Bedrock villagers' AI. They can't pathfind correctlyDuplicate
REALMS-8095villager linking issuesDuplicateREALMS-11719Villagers Broken After 1.20Duplicaterelates to4
MCPE-63311Villagers claim workstations and beds that are too far away and/or get stuck unemployedConfirmedMCPE-143680Villagers do not consistently sleep in large villages with available beds.ConfirmedMCPE-46157Villagers of the same profession switching workstationsFixedMCPE-42912Villagers cannot pathfind around walls to their bedsConfirmed
![[Mod] GoldenHelmet](../../../data/avatars/users/18951.svg){kind=small}
- Unresolved
ricstrr- 123
- 55
- Confirmed
- 318266
- Multiple
- Windows 10
- java-parity
1.19.80.21 Preview - 1.21.44 Hotfix
1.19.80.21 Preview 1.18.20.21 Beta 1.17.30.23 Beta 1.17.11 Hotfix 1.17.10 1.17.10.20 Beta 1.16.210.59 Beta 1.16.200.56 Beta 1.13.2 1.14.1 Hotfix 1.11.4 1.12.0 1.14.30 Hotfix 1.14.60 Hotfix 1.16.0 1.16.100 1.16.200 1.16.201 Hotfix 1.16.210 1.16.221 Hotfix 1.17.2 Hotfix 1.17.30 1.17.40 1.17.41 Hotfix 1.18.2 Hotfix 1.18.12 Hotfix 1.19.0 1.19.20 1.19.60 1.19.62 1.19.71 1.19.72 1.19.83 Hotfix 1.20.1 Hotfix 1.20.12 Hotfix 1.20.15 Hotfix 1.20.62 Hotfix 1.20.81 Hotfix 1.21.2 Hotfix 1.21.44 Hotfix
Created Issue:
Villagers detecting beds and workstations they can't reach
Very similar to https://bugs.mojang.com/browse/MC-155238 I have a village behind my house, blocked in by fences/gates, the villagers are detecting my workstations through the walls and also my bed, which is a floor up and involves a spiral staircase made of slabs. Seems the villagers are not using a pathfinding algorythm but are instead just going off raw distance
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10
- 1.12.0
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
duplicates
Thank you for your report!
However, this issue is a Duplicate ofMCPE-45270.That ticket has already been resolved, which means this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
duplicates
is duplicated by
is duplicated by
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
relates to
is duplicated by
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Very similar to
https://bugs.mojang.com/browse/MC-155238I have a village behind my house, blocked in by fences/gates, the villagers are detecting my workstations through the walls and also my bed, which is a floor up and involves a spiral staircase made of slabs. Seems the villagers are not using a pathfinding algorythm but are instead just going off raw distanceVery similar to
MC-155238I have a village behind my house, blocked in by fences/gates, the villagers are detecting my workstations through the walls and also my bed, which is a floor up and involves a spiral staircase made of slabs. Seems the villagers are not using a pathfinding algorythm but are instead just going off raw distance
is duplicated by
is duplicated by
relates to
relates to
relates to
is duplicated by
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
Very similar to
MC-155238I have a village behind my house, blocked in by fences/gates, the villagers are detecting my workstations through the walls and also my bed, which is a floor up and involves a spiral staircase made of slabs. Seems the villagers are not using a pathfinding algorythm but are instead just going off raw distanceUpdated description by [Mod] GoldenHelmet
Steps to reproduce
- Place a bed and workstation.
- Fully enclose the bed and workstation in opaque blocks.
- Spawn a villager.
Expected result
The villager does not link to the bed and workstation.
Actual result
The villager links to the bed and workstation, even though he can neither see them nor pathfind to them.
Original description
Very similar to
MC-155238I have a village behind my house, blocked in by fences/gates, the villagers are detecting my workstations through the walls and also my bed, which is a floor up and involves a spiral staircase made of slabs. Seems the villagers are not using a pathfinding algorythm but are instead just going off raw distance
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Updated description by [Mod] GoldenHelmet
Steps to reproduce
- Place a bed and workstation.
- Fully enclose the bed and workstation in opaque blocks.
- Spawn a villager.
Expected result
The villager does not link to the bed and workstation.
Actual result
The villager links to the bed and workstation, even though he can neither see them nor pathfind to them.
Original description
Very similar to
MC-155238I have a village behind my house, blocked in by fences/gates, the villagers are detecting my workstations through the walls and also my bed, which is a floor up and involves a spiral staircase made of slabs. Seems the villagers are not using a pathfinding algorythm but are instead just going off raw distanceWorkaround by [MCPE Mod] AuldrickYou can easily work around the specific problem of villagers claiming beds and workstations you don't want them to by placing them where a villager can't detect them.
First, you need to slightly adjust how you think about villagers detecting POI blocks (beds and workstations for our purposes). Without going down the technical rabbit hole, think of it as follows:
- A villager can only discover POI blocks that are within 16 blocks horizontally and 4 blocks vertically of their position.
- When a villager discovers a POI block, it immediately communicates the kind and position of the block to all the other dwellers in its village.
- If a POI block is broken, all the village dwellers instantly know about it and forget the block.
- The block has to be rediscovered by one of the villagers every few minutes (the exact time is unknown or unpredictable) or it will be forgotten.
Given the above rules, it's easy to see that all you have to do is keep your personal POI blocks at least 16 blocks horizontally and/or 4 blocks vertically away from anywhere a villager might stand. Ways to keep the villagers away might include:
- Placing your blocks on a hill or in a valley where they can't pathfind to (but make sure there are no hills or caves they can get to that could get them in range).
- Building a defensive wall or fence around the village, then subdividing it with another fence or wall to make yourself an enclave. Make sure your blocks are at least 16 blocks from the dividing fence.
- Dig a hole about 7 blocks below the lowest point in the village and build your mini-base in it. Make sure there are no caves around that villagers could get into.
If an accident happens and your POI blocks are discovered, just fix the problem that let the villagers get too close, get them back where they belong, and then break the POI blocks and replace them.
Updated description by [Mod] GoldenHelmet
Steps to reproduce
- Place a bed and workstation.
- Fully enclose the bed and workstation in opaque blocks.
- Spawn a villager.
Expected result
The villager does not link to the bed and workstation.
Actual result
The villager links to the bed and workstation, even though he can neither see them nor pathfind to them.
Original description
Very similar to
MC-155238I have a village behind my house, blocked in by fences/gates, the villagers are detecting my workstations through the walls and also my bed, which is a floor up and involves a spiral staircase made of slabs. Seems the villagers are not using a pathfinding algorythm but are instead just going off raw distanceWorkaround by [MCPE Mod] AuldrickYou can easily work around the specific problem of villagers claiming beds and workstations you don't want them to by placing them where a villager can't detect them.
First, you need to slightly adjust how you think about villagers detecting POI blocks (beds and workstations for our purposes). Without going down the technical rabbit hole, think of it as follows:
- A villager can only discover POI blocks that are within 16 blocks horizontally and 4 blocks vertically of their position.
- When a villager discovers a POI block, it immediately communicates the kind and position of the block to all the other dwellers in its village.
- If a POI block is broken, all the village dwellers instantly know about it and forget the block.
The block has to be rediscovered by oneof the villagers every few minutes (the exact time is unknown or unpredictable) or it will be forgotten.Given the above rules, it's easy to see that all you have to do is keep your personal POI blocks at least 16 blocks horizontally and/or 4 blocks vertically away from anywhere a villager might stand. Ways to keep the villagers away might include:
- Placing your blocks on a hill or in a valley where they can't pathfind to (but make sure there are no hills or caves they can get to that could get them in range).
- Building a defensive wall or fence around the village, then subdividing it with another fence or wall to make yourself an enclave. Make sure your blocks are at least 16 blocks from the dividing fence.
- Dig a hole about 7 blocks below the lowest point in the village and build your mini-base in it. Make sure there are no caves around that villagers could get into.
If an accident happens and your POI blocks are discovered, just fix the problem that let the villagers get too close, get them back where they belong, and then break the POI blocks and replace them.
Updated description by [Mod] GoldenHelmet
Steps to reproduce
- Place a bed and workstation.
- Fully enclose the bed and workstation in opaque blocks.
- Spawn a villager.
Expected result
The villager does not link to the bed and workstation.
Actual result
The villager links to the bed and workstation, even though he can neither see them nor pathfind to them.
Original description
Very similar to
MC-155238I have a village behind my house, blocked in by fences/gates, the villagers are detecting my workstations through the walls and also my bed, which is a floor up and involves a spiral staircase made of slabs. Seems the villagers are not using a pathfinding algorythm but are instead just going off raw distanceWorkaround by [MCPE Mod] AuldrickYou can easily work around the specific problem of villagers claiming beds and workstations you don't want them to by placing them where a villager can't detect them.
First, you need to slightly adjust how you think about villagers detecting POI blocks (beds and workstations for our purposes). Without going down the technical rabbit hole, think of it as follows:
- A villager can only discover POI blocks that are within 16 blocks horizontally and 4 blocks vertically of their position.
- When a villager discovers a POI block, it immediately communicates the kind and position of the block to all the other dwellers in its village.
- If a POI block is broken, all the village dwellers instantly know about it and forget the block.
- Any villager can claim any POI blocks that isn't already owned, regardless of which villager discovered it initially.
- The block has to be rediscovered by one of the villagers every few minutes (the exact time is unknown or unpredictable) or it will be forgotten.
Given the above rules, it's easy to see that all you have to do is keep your personal POI blocks at least 16 blocks horizontally and/or 4 blocks vertically away from anywhere a villager might stand. Ways to keep the villagers away might include:
- Placing your blocks on a hill or in a valley where they can't pathfind to (but make sure there are no hills or caves they can get to that could get them in range).
- Building a defensive wall or fence around the village, then subdividing it with another fence or wall to make yourself an enclave. Make sure your blocks are at least 16 blocks from the dividing fence.
- Dig a hole about 7 blocks below the lowest point in the village and build your mini-base in it. Make sure there are no caves around that villagers could get into.
If an accident happens and your POI blocks are discovered, just fix the problem that let the villagers get too close, get them back where they belong, and then break the POI blocks and replace them.
Please remove beds from the summary and description as villagers don't reach their beds before claiming in java.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
villager-1.png
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[MCQA] Bartłomiej Słodkowski](../../../data/avatars/users/18941.svg){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
I play on a realm and sometimes my villagers are not linking up to workstations. When 3 or more people are online my villagers stop linking up to beds or workstations.
This report concerns villagers not linking at all to easily accessible POI (beds, workstations, bells), especially in multiplayer worlds. There are several other reports that address similar-looking situations that actually have very different causes. Before commenting here, please try to confirm that you are experiencing this bug, and not one of the following:
- Villagers do not always link to the closest available POI: this is intended behavior per
MCPE-45270 - Villagers detect and link to POI they cannot reach: MCPE-50441
- Villagers link to POI that are unreasonable distances from them: MCPE-63311
- Villgers cannot pathfind around obstructions to reach POI: MCPE-42912
- Villagers cannot pathfind over or through various blocks to reach POI:
MCPE-45560 - Villagers de-link and switch POI:
MCPE-46157 - Newer villagers steal POI from older villagers:
MCPE-43071 - Villages overpopulate (leaving some villagers with no POI to link to): MCPE-47212
- Villagers appear not to link to workstations, in that they won't refresh trades: precursor to
MCPE-62080andMCPE-56889
A user has offered technical analysis of this bug in this YouTube video and this comment. It is suggested that the bug is triggered by abruptly leaving a village too soon after you entered it, either by quitting the world or by using a Nether portal. This means you could work around the problem by waiting a couple of minutes before taking either of these actions. You shouldn't need to wait before walking out of the village, though.
As a reminder, please limit comments to new information, and add a vote to show your interest in getting this issue addressed.
Thank you for your report!
We're already tracking this issue at MCPE-50441, so I will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're already tracking this issue at MCPE-50441, so I will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Mobs get stuck on chests too.
I think it is important to keep two issues separate, which unfortunately are conflated in this report:
- Villager AI failing to pathfind around walls. This can manifest like a combination of
MCPE-49607and MCPE-50441, or it can manifest as MCPE-42912, or probably in other ways too. - Mobs getting stuck on non-full blocks. This is similar to
MCPE-47075but occurs when there is a solid block underneath the problem block. On this issue this report overlapsMCPE-11727, which was closed just for lack of updates rather than because it was fully fixed.
Villagers not pathfinding around walls to their beds is MCPE-42912.
Claiming beds they cannot reach is MCPE-50441.
Getting stuck on various blocks is MCPE-45560.
Thank you for your report!
We're actually already tracking this issue under MCPE-50441 so I've requested this report be resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
We're tracking this issue as MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you aren't already, please don't forget to use the search feature, the less time volunteers spend linking duplicates the more time we have to update new reports.
Voting on an existing report has a greater impact on getting the bugs most important to you fixed!
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue as MCPE-50441, so this ticket is being resolved and linked as a duplicate.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
We can only track one issue per ticket. Villagers linking to blocks they cannot reach is covered by MCPE-50441.
@Hawk J this is a Bedrock Edition big report. Snapshots are Java Edition. You should follow up MC-148733.
@Wolff and Eyeth: it’s important that we keep several issues distinct.
- Villagers not necessarily linking to the nearest workstation is intended behavior according to
MCPE-45270. - Villagers detecting workstations that they cannot pathfind to is tracked at MCPE-50441.
- Villagers changing their linkages when you relog is tracked at
MCPE-46157. - The thing that gets reset when you relog, allowing villagers to claim POI and breed, is the queue of POI queries. The issue of that getting jammed is tracked at
MCPE-49580.
Setting those issues aside, the main issue in this report is that villagers link to POI at unreasonable distances. I think that should be considered as a distinct bug because of the problems it can create. These include:
- Excessive village expansion (
MCPE-46581) - Villagers with beds and workstations that are too far apart from each other, which complicates pathfinding and their ability to restock trades.
- Villagers going outside of simulation distance to try to get to POI, which can lead to overpopulation and workstation stealing and swapping (MCPE-47212,
MCPE-43071,MCPE-46157).
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
@Josiah Altschuler That is correct, villagers do not independently select POI and distance and pathfinding has nothing to do with linking to POI. You might want to vote for MCPE-50441.
There have been improvements to villager pathfinding in recent months such that my comments above about this being the intended behavior may no longer be true, We need the developers to weigh in on whether the behavior described herein is intended or is the result of a bug. Normally we would handle that by reopening this ticket and forwarding it to them, but it turns out that a previous ticket that does so already exists, so this ticket will be re-resolved as a duplicate.
You may want to upvote and watch MCPE-50441 for developments.
I’m not sure if villagers will change the bed they link to when they fail to reach it. They do unlink from the bed, but I’m not sure how that affects the order of which villager gets linked to the the next bed that is found. Linking is not done separately for each villager, it is done by the village based on the order villagers and beds/workstations are added to the village. The developers did not intend each villager to take the closest bed (MCPE-45270). However, linking to beds they cannot reach is already an open bug report at MCPE-50441. I might have this ticket resolved as a duplicate of that one based on the information you have provided. Before I do, could you tell me which Java snapshot you were referring to where a change was made related to this, so I can check against that?
You can vote for MCPE-50441 on the linking to workstations they can't pathfind to. Also MCPE-43071 on the issue of seniority in linking, which was added in a recent Java snapshot.
I wonder if the issue is villages having a limit to how many workstations they can hold in a detected-but-not-linked list. I am going to try to test that.
Update: Yes, in 1.14.60 there is a limit of 32 unlinked workstations that a village can detect. However, this list is not saved permanently, it is remade every time you relog.
Based on the problem being that the villager would not link to a bed that was right next to it because the game wanted it to use an unreachable bed, I will have this ticket resolved as a duplicate of MCPE-45270 and MCPE-50441.
These issues are tracked at MCPE-46157 and MCPE-50441.
We're tracking this issue as MCPE-46157 and MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you aren't already, please don't forget to use the search feature, the less time volunteers spend linking duplicates the more time we have to update new reports.
Voting on an existing report has a greater impact on getting the bugs most important to you fixed!
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
This report is already resolved as a duplicate. If you have information to add about the issue, please add it to an open report like MCPE-50441 or MCPE-42912.
Village mechanics in Java edition are quite different from Bedrock, so the Java reports you've found are not likely to be relevant to your Bedrock experience. And yes, reports can be similar but not duplicates if an issue is fixed in one version but comes up again in a later version.
Thank you for your report!
We're actually already tracking this issue at MCPE-50441, so I will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue at MCPE-50441, so I will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MCPE-50441 and MCPE-63311, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki – 📖 FAQs
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
Thank you for your report!
We're tracking this issue in MCPE-50441 and MCPE-63311, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
The duplicate link to MCPE-50441 is correct because part of the issue reported here is that the villagers are linking to beds and workstations in places they cannot reach. However, the issue with bells destablizing iron farms is covered by MCPE-54183 so I have added that as an additional duplicate link.
Bells define a village meeting point, so villagers will try to pathfind to them in the afternoon. Whenever 3 successive pathfinding attempts to a POI fail, the village breaks links to the POI. Whenever village POI links change, the village center can shift.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for the file. The short answer to why your villagers are not all sleeping is that many of them are not able to reach the beds they are linked to. There are three reasons they can't reach their beds:
- Some villagers are fenced in and cannot access any beds.
- Some beds that the villagers detect are locked behind iron doors. (MCPE-50441)
- The village is too large to be within simulation distance all at one time, so some villagers are never active at the same time that the chunk containing the bed they are linked to is active. (MCPE-63311)
A broader explanation is that villages change size and assign beds (and workstations) through a centralized, linear process that is unable to adjust links and villager behavior in some of the ways we might intuitively expect (MCPE-45270, MCPE-63311). Village mechanics in Bedrock Edition are particularly unsuited to the kind of large-scale, organized, cellular design that you have built. As a result of the way villages work in Bedrock Edition and the way you have constructed yours, you have a single village about 250 by 400 blocks in size, which contains 234 villagers. The village mechanics simply aren't robust enough to get every villager in bed at night in a village that size.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-50441, MCPE-73804, and MCPE-131043, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thanks for providing the world save. I see you reporting multiple issues with villagers. Bug reports need to focus on a single, reproducible issue. The problems you had with villagers linking and relinking unexpectedly seem to be covered by MCPE-50441, MCPE-63311, and MCPE-131043. Do note that it is intended for villagers to not always choose the nearest bed and workstation, per MCPE-45270. I realize this can make villagers difficult to work with, but Mojang has said it's the intended design.
I was not able to reproduce the famers not harvesting or sharing food. The farmer near -350, 85, 60 harvested and shared with the nitwit while I watched, and I was able to get a farmer to harvest under -305, 107, 56 by giving it a bed and workstation. Without a bed and workstation it kept trying to pathfind toward the other villagers at -350, 85, 66. That is likely because it detects that it is near but outside of the closest village, since village boundaries are based on where beds, workstations, and bells have been claimed.
If you still feel that you are experiencing a distinct bug that I didn't mention, please make a new report focused on a single, reproducible issue.
Thank you for your report!
We're tracking this issue in MCPE-45270 and MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki – 📖 FAQs
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
If the trading hall involves locking villager into a separate "cell", then this is tracked in MCPE-50441.
Thank you for your report!
We're tracking this issue in MCPE-45270 and MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
As you mentioned, the detection range for villagers on bedrock is 16 blocks horizontally and 4 vertically.
I don't believe that increasing the villagers' vertical detection range is a good idea, especially considering that bugs such as MCPE-50441 would be exacerbated by it.
This isn't a bug as it's a limitation that's been set by the developers, which you're suggesting should be changed.
Thank you for your report!
We're tracking this issue in MCPE-42912 and MCPE-50441, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main tickets it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Would MCPE-50441 describe your issue?
No because I connected a minecart line pretty far from my town for the villager spawning area and they still became clerics but a few managed to not be clerics but when I sent them to my town they just disappeared but I can try doing the things instructed on MCPE-50441. Thank you kelianor.
Individual villagers in Bedrock Edition do not have any priority for linking to the closest workstation: see MCPE-45270 and MCPE-63311. You seem to be expecting that they should.
The information in the panel on MCPE-50441 may help you get your village set up the way you wish, but if any villagers have difficulty moving between their beds, meeting places (bell or village center), and workstation, they can unlink and allow another villager anywhere in the village to take the workstation. That can make large villages unstable unless you completely prevent the villagers from moving by trapping them in 1x1 cells.
I am going to resolve the report as a duplicate of MCPE-45270 and MCPE-63311 based on the information provided.
This mechanic is stated in the 1.16.0 changelog:
- Increased golem spawn rate and modified spawn rules (
MCPE-47157)
- At least 75% of the villagers must have worked in the past day
- Minimum 20 beds and every villager has a bed
- Only 1 golem will spawn for every 10 villagers
However, it is an unintuitive and frustrating requirement for many players. Sometimes a villager may attach to a village without a player knowing. For example, see MCPE-63311 and MCPE-50441.
Accessibility has no impact on connecting to POI (beds, workstations). Only distance within built-in detection range matters.
@Umija5895M - You keep repeating that and you are completely wrong. Accessibility is a significant requirement as is evident in Java where these features work correctly. Range is secondary to accessibility.
https://minecraft.gamepedia.com/Villager#Job_site_blocks
"A job site block can be detected as long as it is in range, not already claimed and the villager can pathfind to the block to claim it."
Last I checked a job site that is within range can be picked even if the villager cannot pathfind to it. It also doesn't care if another Villager has chosen that job site. The same issue exists with beds.
I'm not arguing that accessibility is not a desirable feature as it certainly is. However, just because the feature works a particular way in Java doesn't mean that it is intended to, or will ever, work that way in bedrock (unfortunately, most of the time). That would be a "parity request" and is consider invalid for the bug tracker. I have also been told by moderators that the wiki is not an "official reference" to how it is supposed to behave.
I was merely pointing out how linking to POI's currently works in bedrock. It is not for me to decide whether this is actually how it is intended to work, and since this bug report has been "confirmed", we can hope that the intent is to have accessibility to workstations and beds matter (even though that will "break" some popular iron farm builds).
Please include more information including steps to reproduce the problem:
Also, a simple .mcworld test world that showcases the issue would be useful.
Test world uploaded, Villagers aren't very smart.mcworld
The world consists of a small enclosure with 3 beds and 3 workstations, a dispenser and command blocks. The dispenser is filled with villager spawn eggs. 1 bed and 1 workstation are accessible to villagers through doors; 2 beds and 2 workstations are fully enclosed in solid walls and not accessible. The command blocks can be used to quickly change to morning and evening, and to kill villagers to reset the test.
To run the test, press the button on the dispenser to spawn villagers. The villagers will be just as likely to claim the inaccessible beds and workstations as the accessible ones.
Affects 1.16.100
Affects 1.16.200.56 Beta
Affects 1.16.201
I have yet to discover any range limit besides render distance. My villagers don’t care how far away the work stations are.
I've noticed this too. its really bad because then they cant refresh there trades cause they lock to a station that they cant reach
Please remember that the bug tracker is not a discussion site. Comments here should provide additional information that will help the developers find and fix the bug. Other uses are subject to removal because they make it harder to find the information the developers need. For discussion, please use the Minecraft Discord.
(We also usually allow sharing of workarounds, but village functioning is such a complex topic that it would take far too much text in this case.)
Kai Maldonado: I think you're basing that suggestion on the belief that this will be treated as a parity issue, but I have doubts that Mojang is going to handle it quite like you expect. The village mechanics in Bedrock are quite different from Java's, and I think that's because it has to be to fit the game onto a mobile platform. So I was frankly surprised that Mojang even accepted this bug report instead of closing it as Working As Intended,.
I reckon the reason they accepted it is as a focal point for discussing ways to mitigate the user experience problem rather than to duplicate Java mechanics. That will include discussing not only how they might change the behavior to be less troublesome, but also how much effort it would take them to implement such a change and whether the effort is justified compared to any workarounds available to a player.
Speaking of which, this makes me realize that there is a workaround for this problem, one that I use myself all the time. It just didn't occur to me to write it up until now. Since it's not specific to your comment, I'll add it to the description above a few minutes from now.
This workaround only works if your goal is to get you villagers not to attach to POIs period. As someone who works heavily with villagers, I need them to connect to specific POIs; this is near-impossible when villagers over 100 blocks away want are prioritized over the villager literally touching it.
Justin: The behavior you're talking about isn't related to the bug in this ticket. However, I can tell you that there are ways to solve your problem, not by modifying villager mechanics but by understanding how their designed mechanics work well enough to exploit their current behavior. (It is a little harder to do with a large village, though. You might want to shrink the village if you can.)
Unfortunately, the bug tracker isn't the place to discuss this. There are plenty of technical people and server communities who have this knowledge and will share it. Try asking about them at the Minecraft Discord. You could also check out some technical YouTubers' channels, as many have addressed this specific problem in their tutorials on building trading halls or even iron farms. Two I can recommend are Old Guy and SilentWisperer. Good luck!
Reminder: This is not a discussion forum. Comments are for providing additional information to the developers that might help them find and fix the problem. Other comments are off topic and subject to removal.
Bed placement is not 16x16 square in the below test FYI. Came up as 16, 16, 15, 15.
I placed a villager at 70, 4, -70. I then marked out 5 block spaces from there ( villagers at base 0). 2 of the 4 sides only reach 15 spaces whereas the other two sides reached 16 spaces.
Reply from [MCPE Mod] Auldrick:
I think the reason you're seeing those results is that you're counting blocks rather than measuring distance. The block space the bed is in is not the center of the square, because the center of a square is a point, not a block space. If you instead measure from the northwest corner of that block space, I think you'll measure it as 16, 16, 16, 16. Edit: This also implies that the glowstone blocks on the left and top sides are inside the square, while those on the right and bottom are in the adjacent squares.
Sorry, not sure how to reply to your post. But I think I understand it now. Thanks for your help! For others who run into this, maybe this will help.
can confirm for 1.19?
Confirmed in 1.21.44
this is not a work around.
why is it that in java villagers will only claim bed and blocks that they can actually reach, but this so called work around.... so villagers are broken in bedrock then.
also, villagers are detecting bed and blocks withing 16 chunks or something, not 16 blocks