I had a similar issue that occurred in the trading hall on the server I play on (strictly vanilla) after a bell was placed, and possibly rung, and then removed (this may not have been the cause of the issue). Most villagers who had x-ed out trades simply did not restock their trades, even after their supposed time to do so, for several in-game days. We sought to troubleshoot and fix this using operator methods (like changing gamemodes and such, and using commands, mainly /data) because, well, we had spent time getting the right trades. After many different attempts, I managed to fix the restocking issue in my case by using:
/data modify entity <villager id> uses set value 0
I tested this by advancing game time multiple times to tick values that had potential trade restockings tied to them, and in every case the villager restocked their trades (after being maxed out), so I applied this to all affected villagers and it seems to have worked so far. Maybe this will work for other people?
Corben Jubian
I had a similar issue that occurred in the trading hall on the server I play on (strictly vanilla) after a bell was placed, and possibly rung, and then removed (this may not have been the cause of the issue). Most villagers who had x-ed out trades simply did not restock their trades, even after their supposed time to do so, for several in-game days. We sought to troubleshoot and fix this using operator methods (like changing gamemodes and such, and using commands, mainly /data) because, well, we had spent time getting the right trades. After many different attempts, I managed to fix the restocking issue in my case by using:
/data modify entity <villager id> uses set value 0
I tested this by advancing game time multiple times to tick values that had potential trade restockings tied to them, and in every case the villager restocked their trades (after being maxed out), so I applied this to all affected villagers and it seems to have worked so far. Maybe this will work for other people?