We had this issue on my new 1.13 Server today. It didn't happen to all doors, but to some, but they weren't affected before and now they don't have the issue anymore. It seems to be only for a few minutes or something, then it will be back to normal
Please force a crash by pressing F3 + C for 10 seconds while on the world/server this occurs and attach the crash report ([minecraft/crash-reports/crash-<DATE>-client.txt|http://hopper.minecraft.net/help/guides/finding-minecraft-data-folder]) here.
I was having this problem in the previous snapshot. It seems like if you hit the door with something ike a sword it opens. Also, I could usually go through the door even if half the door was still visible.
This also affect my 1.14.4 client. Worked fine for the whole time until release, then suddenly started this behaviour (while in-game, no modifications) after simply returning from the Nether (which was also performed dozen of times before).
Hello @unknown, you don't need to make a comment of which version is affected when you can change the "Affects Version/s" yourself. By adding the version affected and also comment it will send two emails instead of one to the "Watchers" of this ticket. Thank you 🙂
Seeing this on a 20w21a also, but only near spawn.
My setup: I set up a 20w19a server on my iMac, but upgraded it to 20w21a a few days ago. I'm playing as a moderator on the same iMac, and have had no issues.
My two daughters are on PCs, starting today, they can't interact with chests, and when they try to open the door to our house, only the bottom half opens and they can't pass through. If I open the door for them, they can go through.
We have a few pens with lots of animals nearby, and we experienced some lag also, but culling the herds hasn't helped.
Away from spawn / our house, everything is fine OK.
It sounds like that is just some intended behaviour of the spawn chunks. When you are not an OP on a server, you can't break blocks or do anything around some of the chunks around spawn.
This issue was present in 1.18.2, but no longer occurs in versions above or equal to 22w11a. With that being said, this issue has been fixed in 22w11a.
Did this happen in a new world or a world from an older version?