MC-271254Villagers can't be interacted with and lose their trades ("Failed to load offers")
After updating our server to Minecraft 1.20.5, we encountered an issue where interaction with certain villagers was not possible (cf. attached video). When we first loaded the world, the logs displayed the error message "Failed to load offers: Item must not be minecraft:air" (cf. attached screenshot #1) and attempting to interact with the affected villagers resulted in the same message in the logs.
After reloading the server, the affected villagers lost their trades but not their levels (cf. attached screenshot #2 ; the librarian lost its trades while still being a master).
Linked Issues
relates to1
Created Issue:
Villagers can't be interacted with and lose their trades ("Failed to load offers")
After updating our server to Minecraft 1.20.5, we encountered an issue where interaction with certain villagers was not possible (cf. attached video). When we first loaded the world, the logs displayed the error message "Failed to load offers: Item must not be minecraft:air" (cf. attached screenshot #1) and attempting to interact with the affected villagers resulted in the same message in the logs.
After reloading the server, the affected villagers lost their trades but not their levels (cf. attached screenshot #2 ; the librarian lost their trades whiles still being a master).
Attachments3
After updating our server to Minecraft 1.20.5, we encountered an issue where interaction with certain villagers was not possible (cf. attached video). When we first loaded the world, the logs displayed the error message "Failed to load offers: Item must not be minecraft:air" (cf. attached screenshot #1) and attempting to interact with the affected villagers resulted in the same message in the logs.
After reloading the server, the affected villagers lost their trades but not their levels (cf. attached screenshot #2 ; the librarian lost
theirtrades whilesstill being a master).After updating our server to Minecraft 1.20.5, we encountered an issue where interaction with certain villagers was not possible (cf. attached video). When we first loaded the world, the logs displayed the error message "Failed to load offers: Item must not be minecraft:air" (cf. attached screenshot #1) and attempting to interact with the affected villagers resulted in the same message in the logs.
After reloading the server, the affected villagers lost their trades but not their levels (cf. attached screenshot #2 ; the librarian lost its trades while still being a master).
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
relates to
I cannot reproduce this with the steps provided (none). Are there any reliable reproduction steps that I can follow to reproduce this bug? Make sure that you can still reproduce the problem using your own reproduction steps.
I unfortunately do not have any reproduction steps as all we did was upgrading our Minecraft Java server from 1.20.4 to 1.20.5.
Can you share the world download?
Go up to a bugged Villager, and do a F3 + I and paste the output to a Text File, then upload it here.
See: https://bugs.mojang.com/browse/MC-269191
Maybe it could be that the " EmptyItemInVillagerTradeFix " Was not applied when upgrading your world ?
Having the full world download as well as the F3+I data of the corrupted villagers would be useful, please provide those.
Also, did you open your world in any snapshots prior to updating to 1.20.5?
This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
I can neither provide the world download or the F3+I data as the server owner deleted that save so as to reupgrade a backup from 1.20.4 to 1.20.5 (without encountering any issue this time). Sorry.