When trading with villagers that have a low number of trades by default, those villagers can have all trades permanently locked. This occurs because there is no mechanism that refreshes the villager after every trade has become locked.
To reproduce:
1. Get a low trade number villager like Leatherworker or Fletcher (4 trades)
2. Trade until all trades are unlocked
3. Continue trading with villager the maximum amount for each trade
4. After some time (it took me ~10 minutes) you will get unlucky and trades will all lock
I believe that this can happen to other villagers but is much less likely due to higher number of trades.
Here is a link to a picture album showing that this is possible: http://imgur.com/a/QsvRy
Linked issues
is duplicated by 1
Attachments
Comments 8
I saw MC-749 but reported this because it is a totally separate bug from the description of MC-749. This bug has to do with trades naturally becoming locked after opening all trades. It can occur through natural trading in the world without leaving the world itself. Meanwhile, MC-749 deals with a villager's first trade(s) becoming locked which is caused by rapid unloading of the world after completing the first trade(s). This can be seen when the reporter of MC-749 says that he has a villager with only one trade. This is impossible normally since villagers refresh trades after each new trade is completed. Without the rapid unloading of the world that bug doesn't occur. Since the conditions for producing MC-749 are different from this bug, it is separate from MC-749 and should be reopened.
I thought it got worse, but after not interacting with the villager for about 10 seconds all trades seem to reset. If this works the same in survival, and consistently I'd say this bug is solved.
If someone more patient than me would like to check this bug can join the many other resolved bugs 🙂
I tried to leave my villager alone for some time (a few minutes), but all trades are still locked.
My villager is a fletcher with a total of 4 trades.
Using Minecraft 1.10.2
Resolved as a dupe of MC-749 because its description was updated to include this case.
Please stop updating this ticket. It's already resolved as duplicate of MC-749. I've made you the author of that ticket, please update the affected versions there instead.
Could be or relates because the description there is different MC-749