Spawn protection, PvP and keeping new players safe

What spawn-protection actually stops, what the pvp setting does and does not cover, and how to build a spawn area where a brand new player is not killed or robbed in their first ten seconds.

6 min read · Updated Oct 21, 2026 · By GuavaHost Team

spawn-protection, and what it really does

spawn-protection is a number in server.properties. It is a radius in blocks around your world spawn point, and inside it, players who are not operators cannot place or break blocks. The default is 16, which is a small square around spawn.

Three things people get wrong about it:

• It only covers building. It does not stop PvP, mobs, fire or explosion damage, players opening chests, or someone standing in your spawn being a nuisance. It is a build permission, nothing more.
• Operators ignore it. If you are op you will never see it working, which leads to a lot of "spawn protection is broken" reports. Test it deopped.
• It is measured from the world spawn, not from your hub build. Move the world spawn with /setworldspawn and the protected square moves with it.

To change it, open the Server properties page under Minecraft tools and find spawn-protection, or edit server.properties on the Files tab. Editing server.properties covers the page and the file.

Sensible values:

Set it to 0 if you use a protection plugin, so only one system is guarding that area.

The pvp setting

pvp=true lets players damage each other directly. pvp=false stops it. That is the whole setting, and like spawn protection it is narrower than people expect.

With pvp=false a player cannot be hit with a sword or an arrow by another player, but fall damage, lava, fire, cactus, suffocation, drowning, explosions in some cases and mobs somebody lured to you all still work. In other words it prevents fighting, not killing, so a genuinely safe server also has to care about who can build traps, which is a protection plugin question rather than a server.properties one.

It is also all or nothing for the world. There is no vanilla way to have PvP on in one area and off in another, which is one of the main reasons survival servers install a region protection plugin.

Per area control needs a plugin

Once you want "PvP off at spawn, on in the wild", or "nobody builds in the hub but everyone builds outside it", you are past what vanilla does. The usual options:

• A region plugin. WorldGuard is the long standing one. You select a region with a wand, name it, then set flags on it: build deny, PvP deny, mob spawning deny, entry messages. This is the standard spawn safe zone setup, and far more precise than spawn-protection.
• A land claim plugin. GriefPrevention and similar plugins let players claim their own land, which solves the other half of the problem: a new player protecting their first base. Claims usually block building, chest access and often PvP inside them.
• A plot plugin, if your server is creative or build focused and everyone gets a square.

All three need a plugin server, and the install routine is in installing plugins on Minecraft Java. Whichever you pick, the permissions that decide who bypasses it are handed out with LuckPerms. Do not run two overlapping protection systems: three things that can deny a block placement is an evening spent working out which one did.

A world border is not a safe zone, but you still want one

People sometimes reach for a world border to keep new players in. It is not a protection tool. What a border does do is stop your world growing forever, which is a real performance win and makes pre-generation possible, so do it for that reason: set the world spawn, world border and pre-generate chunks walks through both.

If you want a contained starting area, build it: walls, a gate, a path out. Players respect a build far more than an invisible wall.

The settings that actually shape a new player's first minute

Spawn protection and PvP are two of maybe six settings that decide whether someone sticks around:

spawn-protection=64
pvp=false
difficulty=normal
spawn-monsters=true
gamemode=survival
force-gamemode=false

• difficulty decides how hard mobs hit, and peaceful removes hostile mobs entirely. Difficulty, gamemode and keepInventory covers these and the gamerule that stops players losing everything on death.
• spawn-monsters=false stops hostile mobs spawning across the whole world, which is a big hammer. Prefer lighting your spawn properly, or a region flag that denies mob spawning just there.
• force-gamemode=true puts every joining player back into the default gamemode, handy on a survival server where staff keep logging in still in creative.

Most settings need a restart, so change them, save, and restart rather than wondering why nothing happened.

How a spawn area is usually built

The pattern almost every established server converges on, because it works:

1. A clearly built hub, not a hole in the ground. Even a stone platform with a roof reads as "someone looks after this place".
2. Lit, enclosed and mob free. Light the area to stop spawns and wall it so nothing wanders in. A mob killing a new player at spawn is the fastest way to lose them.
3. Rules on the wall, on signs or in a book. Three or four rules, not twenty.
4. An obvious way out. A path, a gate, a portal, or warps to a resource world.
5. Protected properly. A region with build, PvP and mob spawning denied, rather than spawn-protection alone.
6. A starter kit, if you run EssentialsX. Basic tools and food, claimable once, turns the first five minutes from frustrating into playable: setting up EssentialsX covers kits and their permission nodes.
7. The world spawn in the right place. Stand where players should arrive and run /setworldspawn, remembering that the protected square recentres on that spot.

Two more things keep new players safe and are not about spawn at all: block logging so damage can be undone, which is undoing griefing with CoreProtect, and controlling who gets in, which is the whitelist guide. If you are about to open the doors, inviting your first players covers the social side.

If PvP is the point

On a server built around PvP, flip the advice around. Keep pvp=true but protect the spawn region so people cannot be killed as they log in, and build an exit that does not funnel everyone into one killbox. Take cheating seriously from the start, because PvP servers attract it, and anti-cheat on a Minecraft server is honest about what detection can and cannot do. Hide player positions on any live map you run, since a public map on a PvP server is a hunting tool: adding a live map with Dynmap covers that.

Common questions

Why can players still build near spawn when spawn-protection is set?

Almost always because they are operators, since ops bypass spawn protection entirely. Test with a deopped account, and check that your world spawn is actually where you think it is, because the protected square is measured from that point rather than from your hub build.

Does pvp=false make my server completely safe?

No. It stops players damaging each other directly, but fall damage, lava, fire, suffocation and lured mobs all still kill, so a player can still build a trap. A region or claim plugin is what you need if you want genuine safety rather than no sword fighting.

Can I turn PvP off at spawn but leave it on everywhere else?

Not with the vanilla setting, which applies to the whole world. That is what a region plugin like WorldGuard is for: you define the spawn region and set a PvP flag on it, leaving the rest of the world as it is.

Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.

• spawn-protection
• pvp
• minecraft
• java
• server.properties

Host a Minecraft Java server From $3.99/mo, with instant setup and DDoS protection.

Still need help? Our team is online 24/7 to answer questions.

Contact support