1

When I'm opped on my private server other players cannot interact with certain things like chests and breaking blocks around spawn. When I de-op myself they can. So, what's causing this issue other than the fact that I'm OP?

  • 3
    That sounds like spawn protection, but... no idea why it's acting weird and allowing them when you de-op yourself. – Codingale May 7 '17 at 19:00
5

As suspected by @Codingale, this is indeed spawn protection. From going through some decompiled Minecraft code, I gathered that a player is allowed to build at the spawn point of a world if:

  • The world is not "dimension 0", i.e. it is a nether or end world.
  • The list of OPs is empty.
  • The player is OP.
  • spawn-protection is set to 0 or less in your server config.
  • The block is outside the spawn radius set in your server config.

As per that list and assuming you are the only OP on the server, de-oping yourself will cause the spawn protection to be bypassed.

If you don't like spawn protection, you can disable it by setting

spawn-protection=0

in your server.properties.

Note that the Minecraft Wiki claims the following on spawn-protection:

Setting this to 0 will not disable spawn protection. 0 will protect the single block at the spawn point.

However, this is not true. There is an explicit check in the code for that value and I've verified that setting it to 0 does indeed disable spawn protection for versions at least as far back as 1.8.

|improve this answer|||||
  • That totally makes sense. I didn't even think to check if there was any spawn protection or how it would be applied. :) – Knight Yoshi May 8 '17 at 0:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.