This is an odd bug, and I have not been able to make sense of it.
I am running an in-house server with 1.11.2 on my personal computer, as well as playing on the server with the same computer. I have a second computer / player also running 1.11.2 with the same Win10 and JRE versions, and that player is unable to open some player-placed single doors near the world spawn area. Double doors seem to work, and spawned doors (village, woodland mansion) work, but at least some of the single-panel doors I've placed do not work for this player.
When I open the door, the player can walk through, and a pressure plate causes the door to shut. If I remove the door and the player tries to place one, the game shows a lower-half door in the upper half of the door way, and nothing in the bottom. The player sees visual glitches (door in the wrong place), but nothing seems amiss from my view.
The server log shows no errors. There are no mods running on either the server or the client that is glitching. I will check the problem client's logs when I have access to the machine in a while.
I can provide the server's save file, and coordinates of an example glitching door. The 7z of the save game is about 130MB.
Please let me know if there is additional troubleshooting I should take, or if I should provide the server file archive on DropBox.
Attachments
Comments 6
Other player is not OP. They are able to interact with other things in the region (double doors, crops, chests, etc). Maybe I'm using the term "worldspawn" incorrectly - I mean the region of the world where the players initially spawn. The world is configured as a Survival world, and both players are in Survival mode. All of the construction has been done in survival mode. I don't understand why the other player would need to be OP to interact with doors on this world - I haven't seen this on previous server worlds we've run in-house, going back to 1.7.10.
Some elements of the construction I've done near that chunk of the world (specifically, some single doors) do not work for the other player, but other elements do work, including pressure plates adjacent to the single doors that are not working for the other player. If I remove one of the problem doors, the other player is unable to replace it with a door from his own inventory. I can replace the door, and it works normally for me, but it still does not work for him if he clicks on it.
Yep, that's spawn protection. All blocks in a certain radius (spawn-protection in the server.properties) cannot be changed by non-admins in any way (pressure plates are the only exception).
The client log in question shows several errors around the time the player tried to interact with the door. I'll attach the log, FWIW - the interaction with the "problem" door is around 09:15:xx in the log.
[09:15:26] [Client thread/ERROR]: Null returned as 'hitResult', this shouldn't happen!
@violine1101 – Ohhhh. I've never encountered that before. Those blocks must be right on the edge of the radius. I just reviewed the description on the wiki for that parameter. It looks like it's happening now because one of us is OP, and the other isn't.
Sorry for the misunderstanding. I'll adjust the parameters appropriately and/or de-OP myself. I guess this can be closed as "not a bug".
Has the other player OP? Otherwise they are not able to interact with stuff in the worldspawn.