---
title: "Can't break or place blocks? Spawn protection and other causes"
url: https://help.endercloud.in/docs/cant-break-blocks-spawn-protection
category: "Minecraft Hosting › Troubleshooting & Performance"
type: Troubleshooting
tags: ["config", "permissions", "players", "troubleshooting"]
keywords: "spawn-protection, spawn protection, can't break blocks, can't place blocks, blocks reappear, blocks come back, cannot build, adventure mode, worldguard, griefprevention, claims, you don't have permission to build here, build permission, op bypass, block nahi tut raha, can't break blocks near spawn, blocks not breaking, cant place blocks, cannot build at spawn, disable spawn protection, spawn protection off"
difficulty: beginner
time: "5 minutes"
updated: 2026-11-14
source: Endercloud Knowledge Base (official)
---

# 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.

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.

1.  Open the **Properties** tab and search for `spawn-protection`.
    
2.  Set it to `0` to turn it off (or a smaller number for a smaller area).
    
3.  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](/docs/server-properties-explained).

## Fix 2: Protection and claim plugins

-   **WorldGuard**: stand in the area and run `/rg info` to see which region you are in and its flags. Add the player as a member (`/rg addmember <region> <player>`) or remove a `build` flag 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](/docs/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 PlayerName
```

If every new player starts in the wrong mode, check `gamemode` and `force-gamemode` in **Properties**. See [Gamerules, difficulty and gamemode](/docs/gamerules-difficulty-and-gamemode).

## Fix 5: Other causes

-   **Login plugins** on offline-mode servers block all actions until the player uses `/login` or `/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](/docs/how-to-fix-minecraft-server-lag).
    

## Frequently asked questions

**Q: 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](/docs/whitelist-op-and-ban-players).

**Q: 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.

**Q: I changed spawn-protection but nothing happened**

Restart the server after saving. server.properties is only read when the server starts.