What Is Griefing, and How Do Servers Stop It?

Griefing is when other players deliberately destroy, deface, or steal what you've built on a multiplayer server — breaking your walls, burning the place down with lava, blowing a crater in it with TNT, or emptying your unlocked chests while you're logged off. It's a social problem rather than a bug, so there's no single switch that fixes it. Servers stop it with a layered stack of tools sitting on top of active human moderation, and the communities that hold up best are usually smaller survival servers that screen who joins. If that's the kind of place you're after, the live survival list is the fastest way to find one.

What actually counts as griefing

Griefing always involves other players, which is the line that separates it from ordinary survival hazards. A creeper putting a hole in your wall is the game working as intended; a player baiting that creeper into your base, or planting TNT against the door, is griefing. The usual forms are random destruction — holes punched through walls, blocks scattered around for no reason — and targeted destruction, where someone systematically takes apart a whole build because it's yours.

It isn't only blocks, either. Stealing items from unlocked chests counts, and so does setting fires, luring mobs into populated areas, and repeatedly killing a weaker player who can't fight back, including spawn-camping them the moment they respawn. The common thread is that another person is choosing to ruin your time, which is why the fixes are part software and part moderation rather than one tidy setting.

How servers stop it, layer by layer

Owners don't deploy everything at once. They build the defenses in roughly the order below, each layer covering what the one before it misses.

Gate who gets in with the whitelist

The first line, and the simplest, is the vanilla whitelist. Turn it on with /whitelist on and only pre-approved accounts can connect at all; anyone else gets bounced with You are not white-listed on this server! before they ever load a chunk. You add people with /whitelist add <name>, drop them with /whitelist remove <name>, and the approved accounts live in whitelist.json. Bedrock uses /allowlist add <name> for the same thing. Operators always bypass the list, so staff don't lock themselves out.

For a small private server this is the strongest grief prevention you can get, because a stranger can't grief a place they can't join. On a large public server it's the opposite — you want anyone to wander in — so the whitelist gets dropped in favour of the layers below.

Let players claim and lock down their land

This is the core anti-grief layer on most public servers: regions where only the owner and people they trust can build, break, or open containers. A few models show up again and again.

GriefPrevention is the self-service one. You claim land with a golden shovel — right-click two opposite corners and it marks out the rectangle between them — and each block of that claim spends one claim block from a personal balance that builds up the longer you play. Inside your claim you hand out access with trust commands: /Trust for full build rights, /ContainerTrust for chests and crafting gear, /AccessTrust for buttons, levers, and beds, and /UnTrust to pull it all back. Standing in a claim, /TrustList shows exactly who can do what.

Towny works at the town level instead of the individual. Claiming pulls a 16x16 chunk out of the wilderness into your town; the first chunk you claim becomes the homeblock, and where you're standing becomes the town spawn. Towns wrap their land in protection from explosions, fire, hostile players, and griefing, and residents set per-plot permissions from there. If you'd rather build inside that kind of shared, governed space, the towny server list is where those communities are.

WorldGuard is the admin's tool, used mostly to protect spawn and other staff-built areas. A region created with /region define <id> denies building by default, and only the members or owners added to it can touch anything — the inverse of the wide-open wilderness, applied to exactly the area staff care about.

Faction claims are the deliberate exception. On factions servers land is held by a faction only while it has enough power, and raiding someone's claim is the whole point of playing, so these are competitive by design rather than grief-proof.

Log every block so damage can be undone

Prevention fails sometimes — a careless trust, a gap in a claim — and that's what CoreProtect is for. It quietly records every block placed or broken and every chest opened, so staff can see who did what and reverse it. /co inspect toggles a mode where clicking a block shows its full history, /co lookup searches that log, and /co rollback undoes the damage. A grief that took ten minutes to commit gets cleaned up with something like /co rollback u:Griefer t:2h r:#global, and if a rollback overshoots, /co restore replays it. This is the layer that makes griefing recoverable instead of permanent.

Back all of it with staff

None of the tooling replaces people. Servers temp-ban for minor or first offences and permanently ban for serious or repeat griefing, and a clear staff structure — built with something like permission ranks in LuckPerms — is what lets trusted moderators actually use the rollback and ban commands without handing everyone the keys.

Vanilla settings that help without plugins

If an owner isn't running plugins, server.properties still offers a few real protections. spawn-protection=16 reserves a 33x33 square around world spawn where only operators can build or break, which keeps the lobby tidy but doesn't cover anything else and doesn't stop PvP. online-mode=true blocks fake and cracked accounts, closing off a common way griefers dodge bans. Two gamerules curb mob-driven damage as well: /gamerule mobGriefing false stops creepers, endermen, and ghasts from changing terrain, and /gamerule doFireTick false stops fire from spreading. These are useful supplements, not a substitute for claims.

What you can do as a player

You can't install GriefPrevention or CoreProtect on someone else's server — that's the owner's job — so your protection is using whatever the server already runs, plus a bit of discipline.

• Claim before you build anything you'd miss. Mark out your plot first, then start the base inside it, not the other way round.
• Trust sparingly. Only /Trust people you genuinely know, and give casual friends the weaker /ContainerTrust or /AccessTrust instead of full build rights.
• Keep chests inside the claim. A container one block outside your border is fair game.
• Don't broadcast your coordinates. Handing out your exact base location in chat is how targeted griefs start.

When griefing is the point

One server type opts out of all of this on purpose. Anarchy servers run with no claims, no rules, and no rollback — griefing and raiding are the entire experience, and a build only survives as long as you can hide or defend it. Factions sit nearby, where claims expire with your faction's power and raiding other players is intended play. Neither is broken; they're just a different game. If you don't want your work torn down, pick a protected survival or towny community instead, and check that the server actually advertises claim tools before you settle in.

FAQ

Can griefing that already happened be undone?

Yes, but only if the server was already logging blocks when it happened. CoreProtect can't recover changes it never recorded, which is why owners install it before the first incident rather than after. When it is running, a staff member toggles the inspector with /co inspect, clicks the damaged blocks to pull up the responsible account and timestamp, then previews the cleanup with the #preview flag before committing a rollback scoped to that user, time window, and radius. If the rollback reaches further than intended, /co restore replays the changes it removed.

What's the difference between GriefPrevention's trust levels?

They're tiers of access inside your claim. /Trust grants full permission to build and break, so save it for people you'd hand a spare key. /ContainerTrust lets someone use chests, furnaces, and crafting gear but not alter your build. /AccessTrust is narrower still — buttons, levers, and beds only. /PermissionTrust shares your ability to grant trust to others, which you almost never want to give out. /UnTrust <name> revokes whichever level you handed over.

Does turning off mobGriefing stop players from wrecking my base?

No. mobGriefing false only governs block changes caused by mobs — creeper craters, enderman block-stealing, ghast fireballs. A player breaking your wall by hand or placing TNT is unaffected by it, because they aren't a mob. Stopping player-caused damage takes a land-claim plugin or the whitelist, not a gamerule.

A player I removed from the whitelist is still online — why?

By default enforce-whitelist is false, which means removing someone or running /whitelist reload doesn't kick accounts that are already connected; they stay until they log out, and only get blocked on their next attempt to join. If you want removed players booted immediately, set enforce-whitelist=true in server.properties. Until then, an offender you just delisted keeps playing until they disconnect on their own.