When a player 'rescues' a zombie villager (through the process of throwing a potion of weakness, throwing a golden apple, and waiting the allotted time for the villager entity to change from zombie --> normal ). Immediately as the last tick happens which changes the zombie villager state from zombie --> no-zombie, the villager disappears. This has happened to 5+ players regardless of OS system (Win/OSX/Linux) or mod status on the server.
When a player attempts to trade with a villager enough that it would prompt the villager to 'level up' from Copper --> Silver. I have not seen the error happen with silver–>gold or any of the higher leveled villagers. This (also) has happened to 5+ players regardless of OS system (Win/OSX/Linux) or mod status on the server.
I'll include some of the console logs that have been pulled from our server in case the breadcrumbs of the error show something that I'm missing.
This issue appears to be happening again on 1.16.4. We're running a small Paper server and we've been able to recreate the issue with different players in different worlds (both 'normal' world/nether/end & resource world/nether/end, https://www.spigotmc.org/resources/%E2%9C%85-resource-world-%E2%9C%85-never-run-out-of-resources-must-have.75994 ) There appear to be two triggers:
When a player 'rescues' a zombie villager (through the process of throwing a potion of weakness, throwing a golden apple, and waiting the allotted time for the villager entity to change from zombie --> normal ). Immediately as the last tick happens which changes the zombie villager state from zombie --> no-zombie, the villager disappears. This has happened to 5+ players regardless of OS system (Win/OSX/Linux) or mod status on the server.
When a player attempts to trade with a villager enough that it would prompt the villager to 'level up' from Copper --> Silver. I have not seen the error happen with silver–>gold or any of the higher leveled villagers. This (also) has happened to 5+ players regardless of OS system (Win/OSX/Linux) or mod status on the server.
I'll include some of the console logs that have been pulled from our server in case the breadcrumbs of the error show something that I'm missing.