Players Can't Break Blocks? Fix Spawn Protection

If players can't break blocks, place blocks, or open chests near spawn, it's almost always spawn-protection in server.properties set above 0. Set it to 0 to disable it, or raise it to protect a bigger area for OPs only. This is one of the most common early-game surprises. It's on by default.

Symptoms

• Non-op players can hit blocks near spawn but nothing breaks
• Chests, doors, or buttons near spawn don't respond for regular players
• OPs can build fine in the same spot; everyone else can't
• Problem disappears once players walk far enough away from spawn

Why this happens

Minecraft ships with spawn-protection set to 16 by default. This creates a 16-block radius around the world's spawn point where only operators can modify the world. It's meant to stop griefing before you've set up proper permissions. Most server owners don't realize it's there until a player reports they "can't build anything." It's not a plugin, not a permissions issue, and not corruption. It's a single line in your server config.

Spawn protection only affects the area around the original world spawn point, not every location. If you're building a base far from spawn and still can't edit blocks, the cause is something else (permissions plugin, gamemode, or claims).

How to fix it

1. Open your server's Server Properties page in the panel.
2. Find the spawn-protection setting.
3. Change the value:

• Set it to 0 to disable protection entirely, or
• Set it to a small number (e.g. 16) if you want to keep a protected safe zone for OPs only.

1. Save the change.
2. Restart the server using the Restart button at the top of the server page: changes to server.properties don't apply until the server restarts.
3. Have a non-op player test breaking a block near spawn to confirm it worked.

If you're setting up a fresh world or skyblock/oneblock-style modpack, double check the world version matches your server's modpack version too, a mismatched world can cause block issues that look similar but aren't spawn-protection related. See how to upload your own world if you need to swap in a compatible one.

If you're troubleshooting this because a mod install broke something else on the same server, check the Console for missing dependency errors. That's a separate issue covered in Fix "Missing Dependency" and Mod Conflict Errors.

Still stuck?

If spawn-protection is already 0 and players still can't build, the cause is likely a permissions plugin, claim plugin, or gamemode setting rather than this config value. Check how to give yourself Operator permissions to rule out OP status issues, or review gamerule and gamemode settings. If none of that explains it, open a ticket with our support team and we'll check your config directly.