Direct answer

When only the area near world spawn is protected, check spawn-protection in server.properties. If the problem follows a claimed area elsewhere, investigate protection plugins or adventure mode.

What it means

Java server spawn protection is different from a WorldGuard/Towny region. It applies around spawn under its documented operator conditions; custom claims and game modes can also block building.

If you are a player

  • Try a block well outside spawn, and ask whether other players can build there.
  • Check whether your game mode is Adventure or whether a region protection message appears.

If you run the server

  1. Compare build permissions at spawn and at a distant wilderness coordinate using a non-OP test account.
  2. Review spawn-protection in server.properties and restart to apply an intentional change; 0 disables built-in spawn protection.
  3. If only certain claims are affected, use that plugin’s region/claim inspection command and permission rules.
  4. Do not give everyone OP just to test building; use explicit permissions or region membership.

Confirm the fix: After changing one setting, test placing and breaking blocks both inside and outside spawn while logged in as a normal player.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

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