MC-15157Unable to alter a chunk in any way
Hi,
I am running a multiplayer server. Everything is plain vanilla directly from Mojang. No mod, no texture pack, no third party anything. 100% standard.
Besides the usual random bugs (dogs disappearing, ...) everything was fine until a few days ago when a section of the world stopped "working". Players noticed because it happened in their house, where their chests were. In this section, we are unable to open a chest, place or break any block, torches, anything at all. We are still able to move freely around. The problem extends whatever "height" we are. Near bedrock level, we are still unable to break any block so this seems to be related to that single particular chunk.
The problem occured when we were in 1.5.1. The move to 1.5.2 didn't fix it.
It then becomes interesting:
I copied the world folder content on my Save folder (for single player games) and if I open the world in multiplayer EVERYTHING IS FINE. Chests open, I can break blocks, remove torches, place new ones. If I copy the folder back into the server's world folder, I get to see the alterations I made in single player, but am still unable to alter it, open the chests, ...
How come the exact same data works for the same Minecraft.exe runner in a single player world, but does not work when connecting from the same Minecraft.exe runner connected to the multiplayer server? This tells me that the chunk is not really corrupted, or if it is, it is really subtle. Something that only the multiplayer server is bugging on.
My world folder is pretty big, but I could put it on my Google Drive if you'd like it for debugging.
Thanks
Environment
Windows 7, Java 1.7.0_21-b11
Created Issue:
Unable to alter a chunk in any way
Hi,
I am running a multiplayer server. Everything is plain vanilla directly from Mojang. No mod, no texture pack, no third party anything. 100% standard.
Besides the usual random bugs (dogs disappearing, ...) everything was fine until a few days ago when a section of the world stopped "working". Players noticed because it happened in their house, where their chests were. In this section, we are unable to open a chest, place or break any block, torches, anything at all. We are still able to move freely around. The problem extends whatever "height" we are. Near bedrock level, we are still unable to break any block so this seems to be related to that single particular chunk.
The problem occured when we were in 1.5.1. The move to 1.5.2 didn't fix it.
It then becomes interesting:
I copied the world folder content on my Save folder (for single player games) and if I open the world in multiplayer EVERYTHING IS FINE. Chests open, I can break blocks, remove torches, place new ones. If I copy the folder back into the server's world folder, I get to see the alterations I made in single player, but am still unable to alter it, open the chests, ...
How come the exact same data works for the same Minecraft.exe runner in a single player world, but does not work when connecting from the same Minecraft.exe runner connected to the multiplayer server? This tells me that the chunk is not really corrupted, or if it is, it is really subtle. Something that only the multiplayer server is bugging on.
My world folder is pretty big, but I could put it on my Google Drive if you'd like it for debugging.
Thanks
Environment
Windows 7, Java 1.7.0_21-b11
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Sounds realy weird...
Well if it's multiplayer-only, then either the server is having trouble coping and it's lagging, or the spawn protection is around that area.
Servers, even vanilla servers, have a protected area around the spawn. Only OPs and admins can place and break blocks. If I'm not mistaken, this is what you're experiencing.
Do you get any kind of information either from the server’s log or in the client?
Nothing in the log at all. I tried to activate the debugging (/debug start), but it doesn't seem to make the logging any more verbose in any occasion.
But what happens? Just nothing as in adventure mode? Does blocks re-appear when destroyed?
Please close this bug.
I thought I was op, but there was a typo in the op list so I wasn't.
Turned out it was indeed the spawn region protection. I don't know how or when this switch enabled itself, but that was it.
I put
spawn-protection=0
and that was solved.
I never altered that value directly in the first place and for the first few months everybody was able to place block near the spawn point (which is not 0, 0, 0 as I first assumed). Don't know what triggered that change.