Direct answer

spawn-protection in server.properties prevents many non-operator interactions near world spawn when at least one operator exists. Set it to 0 to disable this built-in area rule.

Recommended procedure

  1. Check the server’s current world spawn and the exact spawn-protection value in the generated property file.
  2. Edit the setting with the server stopped; for example spawn-protection=0 disables that built-in mechanism.
  3. Restart, then test as a non-operator account by placing and breaking blocks just inside and outside the affected spawn area.
  4. Check whether WorldGuard, GriefPrevention or another claims/permissions system blocks the action independently.

What to do next

If you need advanced role-based regions, use a protection plugin and configure its rules explicitly rather than pretending spawn protection supports per-player groups.

How to verify the result

Confirm default players cannot grief intended protected areas but can build where they are meant to.

Version and compatibility notes

The Paper documentation describes the built-in spawn protection in terms of a side length and notes it requires at least one operator. Third-party plugin claims can override your test results.

Official references

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000