Can't break or place blocks? Spawn protection and other causes
Players who can't break or place blocks near spawn are usually inside spawn protection. Set spawn-protection to 0, or check claim plugins, permissions and game mode.
- Difficulty:
- Beginner
- Time:
- 5 minutes
On this page
If players can't break or place blocks, or blocks pop straight back, the most common reason is spawn protection: an area around the world spawn where only operators can build. Other causes are protection plugins, missing permissions, adventure mode, or a login plugin waiting for the player to log in.
Fix 1: Spawn protection
The spawn-protection setting in server.properties protects a square around spawn. The default is 16, which blocks building 16 blocks in each direction from spawn (a 33 × 33 area). Operators are not affected, which is why it often works for the owner but not for friends. If the server has no operators at all, spawn protection is switched off automatically.
Open the Properties tab and search for
spawn-protection.Set it to
0to turn it off (or a smaller number for a smaller area).Save and restart the server.
Want a protected spawn but with control over who can build? Turn spawn protection off and use a region plugin like WorldGuard instead. See server.properties explained.
Fix 2: Protection and claim plugins
WorldGuard: stand in the area and run
/rg infoto see which region you are in and its flags. Add the player as a member (/rg addmember <region> <player>) or remove abuildflag with/rg flag <region> build(no value clears it).GriefPrevention and other claim plugins: the area belongs to another player. The owner can give access with
/trust <player>.Other protection or anti-grief plugins usually tell the player in chat why they can't build. Read that message, then check that plugin's settings.
Fix 3: Permissions
If you use a permissions plugin such as LuckPerms, a missing or negated build permission (or a plugin that requires one) can stop players building. Check the player's group. See LuckPerms ranks and permissions.
Fix 4: Game mode
Players in Adventure mode can't break or place blocks normally, and Spectator mode can't interact at all. Set the right mode from the Console:
gamemode survival PlayerNameIf every new player starts in the wrong mode, check gamemode and force-gamemode in Properties. See Gamerules, difficulty and gamemode.
Fix 5: Other causes
Login plugins on offline-mode servers block all actions until the player uses
/loginor/register.World border: players can't build outside it.
Blocks reappear after breaking everywhere, not just near spawn: this is often server lag, not protection. See How to fix server lag.
Frequently asked questions
Should I just make everyone an operator?
No. Operators can run powerful commands, change game modes and ban players. Turn off spawn protection or use a permissions plugin instead. See Whitelist, OP and ban players.
Does this apply to Bedrock servers?
The Bedrock dedicated server doesn't have a spawn-protection setting. On Bedrock, check player permission levels and game mode instead.
I changed spawn-protection but nothing happened
Restart the server after saving. server.properties is only read when the server starts.
Was this article helpful?
Related articles
Most bots go offline because the code crashes, runs out of memory, uses an invalid token or missing intents, hits Discord rate limits, or the service is suspended for an unpaid invoice.
Your invoice is paid but no server or email arrived? Work through these checks.
Users → New user → enter their email, an optional expiry date and the permissions they need → Invite User. Save common permission sets as Presets. Remove access any time.
Fix missing emails for the billing panel or game panel password reset.
