Thanks for the response. I had a hard time reproducing the error, and in the end I found out how. This was some subtle interaction with a mod that we tried three years ago and removed (but apparently not completely). Why it only showed up at 1.16, I'll never know. Anyway, eliminated the mod, and thereby the problem.
Thanks for the response. I had a hard time reproducing the error, and in the end I found out how. This was some subtle interaction with a mod that we tried three years ago and removed (but apparently not completely). Why it only showed up at 1.16, I'll never know. Anyway, eliminated the mod, and thereby the problem.