Multiple villagers are attached to the same profession block
The bug
I am trying to build a trading hall on my world and I notice that jobless villagers entering the area are automatically taking certain jobs when there aren't associated work blocks for them to attach to. When I run the /data get entity [ID] Brain command, the newly entering villagers are attaching to blocks that are already claimed by other villagers. Breaking that block and rechecking doesn't change the associated block.
How to reproduce
From Pelle Reinke in this comment
- Have an enclosure with a couple of villagers in
- Place one jobsite block of any type
- Trade with the villager who aquired the job to lock it in outside working house (2000-9000 tick) quickly break the jobsite block and replace it with the same type and observe a new villager have aquired a profession and both the locked in and new villager will show they have claimed the same jobsite.
→ 
When the time of the day reaches 2000, both will begin to work at the same jobsite. Logging out and back in to the game wont change this.
Linked Issues
is cloned by1
Normalis duplicated by57
MC-150503Two villagers have the same job siteDuplicateMC-151030Armorer, Weaponsmith, ToolsmithDuplicateMC-151209Several villagers can get a profession from one profession block.DuplicateMC-152087Villagers are claiming already claimed workstationsDuplicateMC-152253Multiple villagers claim the same job site blockDuplicateMC-152399Villagers are taking professions already owned by another villagerDuplicateMC-152761Placing job blocks prioritize transforming default villagers over relinking with existing professionsDuplicateMC-152950Multiple villagers claim the same stationDuplicateMC-153114Unemployed Villagers take over claimed job blocksDuplicateMC-153302Job Stations forget which villager owns it. DuplicateMC-153336Villagers with established professions stealing others' professions after removing their workplace.DuplicateMC-153403Villagers are losing their workstation/ stealing othersDuplicateMC-153673Multiple villagers claiming the same work station.DuplicateMC-153778Villager overtaking other villagers' workstationsDuplicateMC-153877Villagers, that had a profession before, claim a different Job Site that has been claimed alreadyDuplicateMC-154424Villagers Forget Job Sites RandomlyDuplicateMC-154490Villagers linking to same jobsite blockDuplicateMC-154806Jobless Villagers "steal" workstations from apprentice+ villagersDuplicateMC-155839villagers occupy their jobsDuplicateMC-156104Multiple Villagers Claim The Same WorkstationsDuplicateMC-156167Villagers randomly leaves/steal workstations, unemploying the original villagers.DuplicateMC-157459Villager claim eachother's workstationsDuplicateMC-157503Villagers will randomly lose/shuffle around workstationsDuplicateMC-157556Villagers are sharing workstations, when the workstation is removed, the villagers remain as it was. I am on a server and re-logging does not help this issue. As shown in the picture, there is only 2 work stations.DuplicateMC-157576Villagers taking over workstations of other villagersDuplicateMC-157998Villagers assigned to workstations lose their workstations to unassigned villagers within vicinityDuplicateMC-158572Two Villagers Will Take the Same JobsiteDuplicateMC-158639one composter two farmersDuplicateMC-159675Villagers with XP in a profession do not get prioritized when a new workstation of their craft is placedDuplicateMC-159704Villagers become librarians even though the lectern is already being used by another librarianDuplicateMC-160509Villager gets profession for already occupied profession blockDuplicateMC-161070New villagers stealing job blocksDuplicateMC-161462Villagers Take the profesion of a block used already by another villager and sometimes get stuck in their profesions.DuplicateMC-162168A villager not traded with not changing jobs even after connected job site is destroyed, multiple villagers connected to one job siteDuplicateMC-162747Villager are not detecting used job siteDuplicateMC-162830Point of interest bugDuplicateMC-163621Unemployed villagers randomly decide to steal an employed villager's workstation.DuplicateMC-164780Villager workstation AIDuplicateMC-164842Villagers don`t follow daily scheduleDuplicateMC-168155Villagers taking an already taken profession blockDuplicateMC-168968no-one else have found it beforeDuplicateMC-169638unemployed villagers can take jobs from job blocks that have been already claimed by another villagerDuplicateMC-171900Many villager have same job but there is only one block of workDuplicateMC-172535Villager Leaves workbench and wont returnDuplicateMC-176300Villagers becoming linked to the same job blockDuplicateMC-176663Villager with profession loses jobsite block to unemployed villagerDuplicateMC-178526Villager work stations not working rightDuplicateMC-178839Multiple Villagers binding to the same station or switching stations after traded and bound to a stationDuplicateMC-179246Villagers work on taken workstationsDuplicateMC-179597Two villagers use the same worktableDuplicateMC-179756villagers linking to claimed work stations DuplicateMC-182198Villagers Switching Profession BlocksDuplicateMC-182407Villager problemsDuplicateMC-183341Villagers claiming already-claimed work stationsDuplicateMC-183802Villagers acting weird with their workstationsDuplicateMC-187083Villagers professions not working correctlyDuplicateMC-190686Villager claims workstation that's already claimed (old bug thats back in 1.15.2)Duplicate
Created Issue:
Multiple villagers are attached to the same profession block.
I am trying to build a trading hall on my world and I notice that jobless villagers entering the area are automatically taking certain jobs when there aren't associated work blocks for them to attach to. When I run the /data get entity [ID] Brain command, the newly entering villagers are attaching to blocks that are already claimed by other villagers. Breaking that block and rechecking doesn't change the associated block.
Environment
Realms server, converted from 1.13.2 to 1.14.
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
is duplicated by
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
is duplicated by
![[Helper] gaspoweredpick](../../../data/avatars/users/80904.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
is duplicated by
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
is duplicated by
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
is duplicated by
Realms server, converted from 1.13.2 to 1.14.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Multiple villagers are attached to the same profession block.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
Very Importantis duplicated by
relates to
is duplicated by
is duplicated by
![[Helper] Misode](../../../data/avatars/users/93314.png){kind=small}
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
is duplicated by
![[Mod] Urielsalis](../../../data/assets/gravatar/urielsalis.jpeg){kind=small}
is duplicated by
is duplicated by
is duplicated by
I am trying to build a trading hall on my world and I notice that jobless villagers entering the area are automatically taking certain jobs when there aren't associated work blocks for them to attach to. When I run the /data get entity [ID] Brain command, the newly entering villagers are attaching to blocks that are already claimed by other villagers. Breaking that block and rechecking doesn't change the associated block.
The bug
I am trying to build a trading hall on my world and I notice that jobless villagers entering the area are automatically taking certain jobs when there aren't associated work blocks for them to attach to. When I run the /data get entity [ID] Brain command, the newly entering villagers are attaching to blocks that are already claimed by other villagers. Breaking that block and rechecking doesn't change the associated block.
How to reproduce
From Pelle Reinke in this comment
- Have an enclosure with a couple of villagers in
- Place one jobsite block of any type
- Trade with the villager who aquired the job to lock it in outside working house (2000-9000 tick) quickly break the jobsite block and replace it with the same type and observe a new villager have aquired a profession and both the locked in and new villager will show they have claimed the same jobsite.
→
is duplicated by
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
relates to
![[Mojang] Cory Scheviak](../../../data/avatars/users/92893.png){kind=small}
[Mojang] Cory Scheviakis duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is cloned by
Duplicate of MC-150806
This looks like MC-150806 but with steps to reproduce in the comments.
I am playing in 1.14.4 and this bug is still happening. Can we please get this report re-opened? It's not a duplicate of MC-150806 either.
There is a naturally generated village right next to both the world spawn and my base which currently has six iron golems: two along the edges of the town, three fountain with the bell, and one stuck on top of a house roof with no way to get down. I've added three houses which each have two beds and four doors, but I don't think that any new villagers have been bred since the lectern I place next to the well hasn't picked up a librarian yet, and the few times I've need a pair of villagers generate hearts the display of hearts ended with the "angry cloud" effect.
Two things that result in the villagers gossiping a lot more than usual (since gossip is now what generates new iron golems):
- The world spawn and my base (which I spend a lot of time at/near) is right next to the village, to the villagers are loaded and active a lot more than normal.
- I've placed all of the job station blocks right next to the town's fountain (except for the town's three farmers) meaning that the the villagers are close enough to gossip even when working (assuming villagers need to be physically close to gossip).
The only changes I've made to the village (besides the three new houses) is to move the weapon smith's blast furnace block from his workshop to next to the fountain, added several profession blocks of my own around the fountain, used the Dirt to Path mod to add some paths to the front doors of the new houses, and also repeatedly removed and placed back several village profession blocks in order to change what associated villager traded at the novice level.
Might merely be a duplicate of MCPE-47157 (Iron farms are broken as well as unbalanced) assuming that the cause of the bug is village mechanics shared between Java and Bedrock. I'm also suffering from MC-150806 (Multiple villagers are attached to the same profession block) in case that has any relevance.
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
This issue duplicates MC-150806.
If you have not already, please use the search function to see if your issue has already been reported.
- Villagers not able to pathfind down ladders
- Villagers multiple assign themselves to Workstations (
MC-150806), maybe fix with a "hard link" between block location and villager (e.g. block has isClaimedByVillager attribute, Villager has workplace coordinates as attributes, if Villager dies set "isClaimedByVillager" to false to allow villager reassignment) (possible concurrency problem) - Villagers could farm their fields in an orderly fashion, not the Monte-Carlo way they use now (possibly
MC-148013) - Villagers not sharing wheat as a food source (Farmers don't craft bread either, a village running solely on wheat can not create new villagers)
- Villagers with XP in a profession (no longer able to change profession) do not get prioritized when a new workstation of their craft is placed, maybe fix with a worker pool per village, assign villager without workplace and highest XP in profession first (possible concurrency problem with multiple villagers assigning them to same workstation fix)
Observed Behaviour:
Villagers with XP in a profession (no longer able to change profession) do not get prioritized when a new workstation of their craft is placed.
What should have happened:
Villagers with highest XP in profession should be assigned first to a workstation to prevent cycling through jobless villagers if they are present
Possible fix:
maybe fix with one worker pool per profession per village, assign villager without workplace and highest XP in profession first (possible concurrency problem with multiple villagers assigning them to same workstation fix, see MC-150806)
e.g.: 3 fishers, one with 100XP, the others with 50, 5 jobless
- Workplace of the fisher with 100XP gets destroyed, add him to the village "fisher job" worker queque.
- Workplace of the fisher with 50 XP gets destroyed, add him to the village "fisher job" worker queque below the 100XP fisher.
- New barrel gets placed, get and remove head element of the "fisher job" queque and assign him to the workplace
- if "fisher job" queque is empty, default to "jobless" queque, if that fails aswell, leave jobsite vacant
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
Duplicate of MC-150806
Duplicate of MC-150806
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ?☃DCD6 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Duplicate of MC-150806
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
I brought back most of the bees that flew north-west and put them into an enclosed area with empty beehives inside. They did not use the new beehives, only newly bred bees did. However, when I took the outside beehives and the bee nest (with silk touch, in case it matters) and put them back, they suddenly used the new beehives inside the enclosed area.
This seems to indicate that they still considered the outside beehives as theirs, but couldn't get in because they were full (not anymore, but they were probably full when they tried to get into them) and thus flew away. As soon as they noticed they were gone, they stopped seeing them as theirs and were free to find a new one.
So, when bees try to find a beehive, that code should probably be synchronized (mutex, critical section), so that it's impossible that 2 bees get assigned the last free spot in the beehive when actually only one can get it. (I don't think it's multi-threaded, but it can also happen in single-threaded code if all bees check for a free slot first before getting assigned to one.)
As a side note, this is a similar behavior like for villagers and beds/workstations as described in MC-150806, so these issues might be related and the faulty code could be in a parent class of bees and villagers, probably some general POI assignment code.
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Between 2000 and 9000 ticks.
Are there possibly any other workstations that the villagers might try to pathfind to? Note that villagers think that trapdoors are air and will try to pathfind through them. If you have other lecterns around, that might prevent them from losing their job (even if there's another villager already assigned to it, see MC-150806).
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
This is supposed to be fixed in MC-149443, but it is still affecting the latest release. Steps to reproduce:
1. Cure 2 zombie villagers in a designated area with 13 beds and 13 working sites (all professions)
2. Trade and offer potatoes to meet breeding criteria
3. Stay out in a night to have few zombies scare the villagers, so that Iron Golems can spawn
4. After a few days, you are getting the result of the uploaded screenshots. 13 villagers which is the expected and desired from the bed population, but more than 35 Iron Golems!?!?
During this test scenario you will also meet the other issues reported, like some villagers are acquiring the same job site (MC-150806) and the Iron Golems are stuck on the same spot (MCPE-49607). Please to fix as it is very irritating.
Duplicates MC-150806
Duplicate of MC-150806
Duplicate of MC-150806
Duplicate of MC-150806
How is this a duplicate? At most it is related to but it is certainly not a duplicate of MC-150806
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-150806, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Resolved as a duplicate of MC-150806, which will be fixed in 1.16.
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Thank you for your report!
We're tracking this issue in MC-150806, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed. The fix will arrive in the next version or is already included in the latest development version of the game, you can check the Fix Version/s field in that ticket to learn more.
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
– I am a bot. This action was performed automagically! Please report any issues in Discord or Reddit
This is supposed to be fixed, see MC-150806. Please provide a video with the debug screen enabled (hit the F3 key) demonstrating the issue.
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
Please provide some screenshots or videos of this issue occurring whilst the F3 debug screen is enabled. This appears to be the same as MC-150806 however, this was fixed in 20w22a.
According to the comments in MC-150806 this still seems to be an issue even after the fix.
Can confirm this also happens on Minecraft 1.14.3 Pre-Release 3 if anyone is interested.
I'm very interested, Mr. Villa-Lobos. Thank you. The pathfinding updates seem to have made this happen less often, but it is still occuring.
I have found that it is easy to cause two villagers to claim the same job site block by rapidly breaking and placing it (can take several tries — noticed when I was trying to get librarians with specific enchanted books). However, when this is the case, they will both lose their jobs if the block is broken again.
Sometimes it can even cause more than two villagers to claim the same block — I managed to get three.
I think that there are two related problems that cause (at least some of) these issues:
1) Villagers randomly disconnect from their workstations
2) Villagers that have had their trades locked (by having at least one completed trade) do not automatically try to connect with a workstation (or, possibly, do not try to connect to a workstation until after unemployed villagers have done so, but when locked villagers have lost their workstations I've never seen one automatically reconnect to one, regardless of how many or what types of other villagers and/or workstations are or are not nearby).
These two problems together mean that villagers will lose their workstations and those workstations will be picked up by a different villager, leaving the original villager unassigned and unable to renew its trades.
sigh
Still happens in 1.14.4…
I would like to mention this is still a problem in 1.14.4. It seems that unemployed villagers have first dibs on workstations which messes things up when you're moving a workstation with unemployed villagers present.
This would explain why I cant get any villagers to trade after the first few ones. I guess I need to have workstations up before they grow up so they can immediately claim a workstation not claimed by any other villager. I noticed that only the first few villagers will trade with me, all others just shake head all the time although they have workstations already present.
This still happens in 1.14.4; I have a small village with 3 composters, a brewing stand, and a stone-cutter, but after some mining, I came back to find that I had an extra farmer and an extra mason. The original farmer and mason, who where the only villagers I had leveled up, had been disconnected from their blocks (the jobless villages "stole" them) so the could not refresh their trades. neither of the other farmers, nor the priest, none of whom had been leveled at all, had their workstations stolen. it would seem that only villages who have been leveled up are susceptible to having their workstation stolen.
A possible fix could be, that each block that is workable by a villager has a "claimed" attribute, perhaps linking to the villager UUID or a boolean. If the block is claimed, no other villager seeking for a job is assigned. The claimed attribute is removed if the assigned villager (coordinates of workplace are also saved in a tag) is killed (remove tag from workplace coordinates block) or the pathfinding fails. For possible concurrency problems a semaphor might be used instead.
Furthermore, this could also be enhanced by the system I proposed in
MC-159675, but this might cause concurrency problems aswell.Here is a very simple way to reproduce the bug (1.14.4) : Make a container for 2 or more villagers (you can make it out of glass so you can see the profession of the villagers), then put down a work station which is 10 or more blocks away from the containers, and break and replace the work station quickly several times until you see that all of the villagers become whatever the profession is. At the end you can leave the workstation placed down, then release the villagers, and they will all go and work at that work station. This is related to the possible bug that novice villagers won't immediately lose their profession if a work station placed more than 8 or 9 blocks away is broken.
This is still happening in the latest Snapshot. I've been playing q new world and managing villagers its been hard.
still happening in 1.15 pre6
At first, I had this problem in a creative world, but not in my survival world. Then recently the problem started happening in the survival world too. I don't know why it has only recently started happening in the survival world but it's been causing a lot of problems in my trading hall.
I discovered this glitch on my own in 1.15.2, and i have some new info about it
this seems to only happen when the villagers are meeting.
it seems to be fixed in 20W06A.
The problem mainly comes in how the villagers prioritise what blocks to sync up with. It seems to be based on the order in which the villagers, and the blocks, are added to the village. Every so often the village jumbled this data up, causing them all to reset.
The whole villager sync portion just needs to be changed, making villagers check for beds and profession blocks based on how close they are to them, once synced he stays synced as long as he can still reach the bed and block... if he can't, he then scans again for the closest unclaimed bed and block he can get to, and will sync with those.
Also, profession blocks need to be able to be turned off, so they can be used as decoration without messing up villagers.
my experience makes it look more like the breaking the site block makes the villagers forget about the job site but not change profession, but when you place it back it remembers it but a new one claims it.
Affects 20w06a.
Possibly related to
MC-166980beecause bees seem to beehave similar with beehives: bees can stay attached to a beehive they can't use anymore (potentially by breaking and replacing or just over time) and then get stuck wandering to the north-west and refuse to get into another beehive until the original one is broken. See this comment: https://bugs.mojang.com/browse/MC-166980?focusedCommentId=632081&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-632081Villagers who lost their workstation also tend to wander to the edge of the village (many also accumulate in the north-west corner, but not all and it might be a coincidence), and combined with
MC-2025that makes them glitch through walls surrounding the village and then can't get back in, this makes it quite difficult to work with villagers (and bees).I just had this happen. I have 2 villagers in stalls in the same chunk with their workstations (composter) in front of them. I have a villager opposite of them that had a lectern as a workstation. However, the villager was stationed just outside of the chunk, but the worksite location was 1 block in front of the villager, on the inside border of the chunk (so, 3 workstations in 1 chunk). When I broke the lectern and went to place it again, I saw the villager became a farmer (composter was 11 blocks away). Note - the other 2 villagers were already farmers and traded with. The former librarian has not been traded with. As a result, I seem to have to wait up to 3 Minecraft days before the villager loses its' profession.
Also, I've noticed the villagers wandering to the edge of the village problem. The first village I tried to "secure" by removing beds and work-stations, the villagers moved to the opposite side of the village from where I had put all of the beds and workstations in.
To comment on an above quote - I think it may have something to do with locked trading villagers not having priority, so the game loops through a collection of loaded villagers that is sorted by un-traded villagers, then villagers that are trade-locked. A bit more testing, and it seems to happen when the intended villager (the librarian in this case) looks at their lectern for a long time (not the nodding). A short time after that, breaking/placing the lectern back will cause the villager to select the wrong workstation.
A few work-arounds -
1 - Seal off the offending villager and place a work-station in front of another unaffected villager. It seems to reset the occupation of the job thief. (Work fraud and wage theft seems rampant in these villages... I mean, it's been 10 years before their economy changed.
)
2 - Completely wall in the villager you're trying to assign a job to. That way, they shouldn't path-find to a new workstation.
Have had this issue since at least 1.14.2, still experiencing the bug as of SS20w06a
Please fix it´s so annoying
Still present in 20w13b.
Don't know if it's the same bug or a different one, but the same happens with beds. My villagers keep having one too many babies than there are beds - leading me to the conclusion that one of the beds must have been claimed by two villagers. One of them is unable to sleep.
I have the same problem on my server. Two villagers can take one work station, when first villager inside trapdoors, and second is sitting in the boat.
It's still present in 20w15a.
1.15.2 Same thing still happening in naturally occurring villages. As villagers multiply, more than one villager will take on a profession, even though there is only one related workstation. The result is that some villagers do not replenish their trades. Example: Newly discovered village had only two workstations, both composters. I crafted and placed one loom, and one villager took on the profession of shepherd. After trading with this villager for several days, a second shepherd suddenly appeared and started hanging out around the loom. The original shepherd, who used to hang out near the loom, was found on the other side of the village. Breaking the loom and replacing it in the same place does not cause the loom to be associated with the first shepherd again. This problem is extremely annoying in villages with multiple farms and multiple farmers. You end up with many farmers with locked trades because they don't replenish their trades.
Are you testing with new villagers on each version?
still present in 20w16a
I think it might be related to
MC-164233where a skilled villager don't get precedence over a jobless villager in picking a new jobsite.I have found that this bug with multiple villagers attached to the same jobsite is more prevalent when the villagers have been skilled than if their trades have not been locked in.
Edit: A way to reproduce this:
1) Have an enclosure with a couple of villagers in
2) place one jobsite block of any type
3) trade with the villager who aquired the job to lock it in
4) outside working house (2000-9000 tick) quickly break the jobsite block and replace it with the same type and observe a new villager have aquired a profession and both the locked in and new villager will show they have claimed the same jobsite. When the time of the day reached 2000, both will begin to work at the same jobsite. Logging out and back in to the game wont change this.
still present in 20w17a
It seems logical to assume that this could be resolved by something where villagers of higher tiers can kick lower tier villagers off of their jobsites.
Can confirm, present in 20w17a.
still present in 20w18a
Also I would imagine this relates to
MC-164233Since this is now "In Progress" it might be a good idea to look at this bug also, which I think might be related also. Cured villagers can work at wrong jobsite.
MC-177505Additionally villagers are able to pathfind to workstations that are inaccessible to them; on the other side of a wall for example. I believe this adds to this bug. Villagers should only be able to link to a workstation they can properly pathfind to.
still present in 20w19a
I have the same issue although in a regular village. I put down two smithing tables and traded with both toolsmiths that appeared until they were both master level. Then a new villager appeared as an apprentice toolsmith. This new apprentice toolsmith will on occasion keep the master level toolsmiths from renewing their trades at the workstation which is why this is an issue for me.
Still present in 20w20b
Still occurs in 1.16 RC1
I have exactly 1 brewing stand and two clerics standing next to it.
I agree with Scott Caton's comment.
I am also still seeing this in my village in 1.16.4. I place a job site block, a villager claims it, and I will level that villager up all the way to Master. Then, I will come back later and find a Novice villager working at that job site block, and the Master will be wandering around. I guide the Master back to their original job site block (by breaking and replacing it), and yet I will still see a Novice working at the job site block when I come back later.
Still present 1.16.5
Still present 1.19.3