Grief Prevention


AUTOMATICALLY PREVENTS ALL FORMS OF GRIEF, including build/break, theft, spam, fire, spawn camping, lava dumping, chat trolling, advertising and more, so you don't have to undo any damage after the fact. It even teaches players how to use it so you don't have to! No configuration or database required. Stop responding to grief and prevent it instead. Grief Prevention will solve your grief problems without requiring you to manage a roster of trained administrators, juggle 10 different anti-grief plugins, take away cool standard game features, publish a training manual / tutorial for players, or add explanatory signs to your world. You can also choose to integrate PvP elements into build design to finally get a PvP experience befitting a sandbox game about creative building.

Grief Prevention stops grief before it starts automatically without any effort from administrators, and with very little (self service) effort from players. Solve all your grief problems with a single download, no database, and no configuration step.

Official Servers (Try it for yourself!)

You can experience this plugin for yourself (as a player) by joining this public server. :) I maintain this server personally, which helps me catch bugs and spot opportunities for new features and improvements. Have fun!

Downloads by Minecraft Version

Please choose the version that matches your Minecraft server version! :)

The Manual

Feature List

Yes, everything is customizable. See Setup and Configuration.

  • No database or world backups required.
  • Extremely efficient CPU / RAM usage.
  • Land claims are easy to manage.
    • Players create and manage their own land claims, so you don't have to do it for them.
    • New players get automatic claims around their first chests so they're protected even if they don't know how to create land claims yet.
    • Players who ask for help in chat get an instant link to a demonstration video.
    • Resizing claims and creating new claims is done with ONLY the mouse, no slash commands (slash commands are also available).
    • When a player appears to be building something nice outside his claim, he's warned and shown his claim boundaries.
    • Claim boundaries are easy to see, and don't require any client-side mod installation.
    • Extremely easy-to-remember, single-parameter slash commands for giving other players permissions.
    • Claim subdivision and granular permissions are available to organize towns and cities. Watch this video.
  • It's IMPOSSIBLE to grief a land claim. Watch this video.
    • No building or breaking.
    • No stealing from ANY containers.
    • No sleeping in beds.
    • No button/lever usage.
    • No adjusting redstone repeaters or other configurable blocks.
    • No pushing blocks in with pistons.
    • No pulling blocks out with pistons.
    • No TNT damage (including cannons).
    • No creeper damage.
    • No explosive damage from other plugins, like Extra Hard Mode or Magic Spells.
    • No enderman/silverfish block changes.
    • All doors may be automatically locked (optional, see config file).
    • No killing or luring animals away.
    • No stealing water (e.g. buckets).
    • No trampling crops by players, animals, or monsters.
    • No building overtop, all claims reach to the max build height.
    • No placing or breaking paintings / item frames / armor stands, etc.
    • Fluids will not flow into a claim from outside.
    • No placing blocks via TNT/Sand/Gravel cannon.
  • Pets and death loot are protected.
    • Players can't pick up what another player dropped on death without permission.
    • All types of pets are protected everywhere, even outside of land claims (can be configured per-world).
  • Excellent anti-spam protection
    • Warns, then mutes, then may kick or ban spammers (configurable - you choose).
    • Most spammers get only one message out before they're muted.
    • Blocks server advertising (IP addresses).
    • Blocks repeat message spam.
    • Blocks ASCII art (ex. Nyan Cats) spam.
    • Blocks similar message spam.
    • Blocks unreadable (gibberish) message spam.
    • Blocks CAPS.
    • Blocks macro spam (very different messages in quick succession).
    • Blocks login/logout spam, even when the spammer has multiple accounts.
    • Blocks death spam.
    • Blocks bot team spam.
    • Blocks slash command spam, including /tell, /emote, and any more you add.
  • Wilderness Protection and Rollback
    • Fire doesn't spread or destroy blocks.
    • Creepers and other explosions don't destroy blocks above sea level.
    • TNT doesn't destroy blocks above sea level.
    • No planting trees on platforms in the sky ("tree grief").
    • Instant, point and click nature restoration for not-claimed areas. Watch this video.
      • Insanely easy and fast fixes for penises, swastikas, and anything else unsightly.
      • Point at what you don't like and click, and it's fixed. Even from far away.
      • Never accidentally changes blocks inside land claims.
      • No need to investigate who built it, who broke it, or when they did it.
      • Doesn't matter if the griefer built with "natural" blocks, it will still be fixed.
      • No database.
      • No backups.
      • No chunk regeneration (it's dangerous for technical reasons).
      • Fixes bad chunk generations, like floating islands. It will be better than new.
      • Fills holes, even next to water to correct big spills.
      • Smooths noisy terrain.
      • No griefer construction is safe. If it's unnatural enough to be noticeable by players, it will be removed or filled-in.
  • Land claims can't be used as a griefing tool.
    • It's impossible to get a player "stuck" inside a land claim.
    • Land claims beyond the first require a golden shovel.
    • Minimum claim size prevents sprinkling small claims to annoy other players.
    • Max claim allowance grows with time played on the server, and can't be cheated by idling.
    • A simple administrative slash command will instantly remove all of a griefer's claims, no matter where they are.
  • Catches clever griefers.
    • Enhances the /ban command to ban ALL a griefer's accounts (not just his IP address).
    • Logs sign placements.
    • /SoftMute command to shut down chat trolls without them knowing they're beaten.
    • Abridged chat logs make reviewing what happened while you were away super-quick and easy.
    • Automatically mutes new-to-server players who use racial or homophobic slurs.
  • PvP Protections.
    • When PvP is off, no setting fire or dumping lava near other players.
    • Absolutely bullet-proof anti-spawn-camping protection including bed respawns, which requires no configuration.
    • No logging out, stashing items, or using plugin teleportation to escape combat.
    • Optional siege mode, to answer players who hide in their claimed houses to avoid combat.
  • Supports your server growth.
    • Permit players to exchange server currency for claim blocks (requires configuration and other plugins).
    • Grant claim blocks automatically for votes, donations, etc (console command provided, other plugins required).

Please Vote for Grief Prevention

I've also posted Grief Prevention on the Spigot site, where plugins are ranked based on reviews. If you love GP, please take a couple of minutes to give GP your rating and leave a short review. Better rating and positive reviews will help server owners who look for plugins on the Spigot site make the safe choice (GP) instead of downloading something sketchy or incomplete. :) Thanks so much for all your support!

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of GodsDead GodsDead Feb 23, 2014 at 20:16 UTC - 0 likes

    Following advice to move to mysql below from my catashrophy with grief prevention destroying my sunday, guess what, mysql is BROKEN in 7.8. Following this: I changed the config.yml to mysql, I added my mysql details, It connected, it generated tables, it added some rows, it DID NOT move over a single claim we have just spent hours re-creating, whats worse than this absolute mess is, even after createing a backup of the entire GP before this move to mysql (as I cannot trust this plugin) moving the data back, its put every single player into minus claims, Reverted from mysql to flat, This has gone from completly fucking shitstorm to even worse. How can I fix this? Did we get a new developer for 7.8 or something?

  • Avatar of GodsDead GodsDead Feb 23, 2014 at 18:26 UTC - 0 likes

    @stgram: Go

    Thank you for the responce, It took me hours to diagnose that this happened. Being on a shared node, it turns out it was another user that had incorrectly configured a third party backup plugin that created so much backups it filled the SSD very fast creating the crash, Wiping the player claim data? I lost more than the claims for griefprevention, I even thought about switching to SQL for GriefPrevetnion too, Im so anoyed with myself and my host for not having backups. We are pretty new, but now im stuck without any claim data at all. Im stuck in a terrible position, does anybody have any ideas how to proceed from here?

  • Avatar of stgram stgram Feb 23, 2014 at 15:40 UTC - 0 likes

    @GodsDead: Go

    If you run out of space, every plugin that writes data on shutdown will erase its own data, it is a terrible flaw. This is why I keep backups of essentials, and switched to SQL for GP. The data you need is absolutely lost in its current state.

  • Avatar of Bubbbaaa Bubbbaaa Feb 23, 2014 at 15:21 UTC - 0 likes

    @GodsDead: Go

    That is where "daily" backups come in handy for problems of this sort
  • Avatar of GodsDead GodsDead Feb 23, 2014 at 14:58 UTC - 0 likes

    I have a majour problem that I need assistance with ASAP, I have had no problems at all with GP for 11 months or so until today, the server crashed last night due to memory, when I restarted it, GP didn't load any of the claims at all, I can see the data is still there, New claims can be created and a restart saves them, but I need to use the data before this happened. The new claims look like they are following the correct ID number we have 358 or so. Its flat file, and I do have access to MYSQL.

    EDIT: I opened up some of the claim data files all 358 are completely blank, GP has wiped all claim data?

    Last edited Feb 23, 2014 by GodsDead
  • Avatar of user_549837 user_549837 Feb 23, 2014 at 03:03 UTC - 0 likes

    Getting this spammed in the console:

    Could not pass event EntityDamageByEntityEvent to GriefPrevention v7.8

    Any input on how to fix?

  • Avatar of Mysticforce12345 Mysticforce12345 Feb 23, 2014 at 00:46 UTC - 0 likes

    I was wondering if Grief Prevention could add like if someone like claims an area and somebody can use worldedit on the claim can u add like a permissions node or like something in the config that blocks worldedit grief? Thanks!

  • Avatar of Arton123 Arton123 Feb 22, 2014 at 23:26 UTC - 0 likes

    This should have a better setup for how permissions are show, the way it is now it kind of hard to even figure, atleast for me. I find this a good setup.

  • Avatar of stgram stgram Feb 22, 2014 at 22:30 UTC - 0 likes

    @BC_Programming: Go

    Thanks for the fix. I saw enough mysql errors for the rest of my life. :D

    As for the stable builds, perhaps some way of rating each version, or writing tickets to? If 3 people find the same terrifying bug in one build, the other 3000 should not download it, to limit the damage, while you work on it. And if a build gets enough upvotes, it is considered stable. Some sort of system like that, to help the community.

  • Avatar of BC_Programming BC_Programming Feb 22, 2014 at 19:31 UTC - 0 likes

    @Smac3223: Go

    Seems like it's just been dev builds for quite some time now. After last times horrid bug that deleted claims I'd rather hold off on the buggy dev builds till a stable one is released. As it stands my server is still running on the 7.8-beta-b213 and claims in 'The End' simply do not work. Upon the daily restart they just vanish. No idea why..

    I could tag any version as stable if I wanted to. There wouldn't be anything particularly "stable" about it. There are no unit tests so it can't be based of passing them, and Even spending an entire evening messing with it on my test server I can barely get any code coverage. Even tagging a build as beta brings with it more assumptions of stability than feel I am able to responsibly guarantee.

    Even so, I was going to try to get another beta available here soon. providing build 279 as a beta would be no less arbitrary than earlier builds.

    That said, the main concern would be what happens with the changes to PlayerData names, particularly in existing data that would be brought forward. It worked when I tried earlier with 7.7, but I "only" have three accounts (one of which I recently bought solely for testing GP with all-lowercase users).

    Even with a stable build/upgrade I think it will be prudent to replicate any database information GP is using and/or flat file information, to avoid a worst-case scenario that some unlucky individuals experienced from some of the dev builds.

    At least now that you've mentioned the version you have I can stop trying to reproduce your issue. That said I'm not sure why you would be booted to the overworld when you log back in in any case.


Date created
Dec 14, 2011
Last update
Sep 29, 2016
Development stage
GNU General Public License version 3 (GPLv3)
Curse link
Grief Prevention
Reverse relationships
Recent files
  • R: 15.2.4 for 1.10 Sep 29, 2016
  • R: 15.2.3 for 1.10 Sep 16, 2016
  • R: 15.2.2 for 1.10 Sep 08, 2016
  • R: 15.2.1 for 1.10 Aug 31, 2016
  • R: 15.2 for 1.10 Aug 28, 2016