Grief Prevention

Grief Prevention

AUTOMATICALLY PREVENTS ALL FORMS OF GRIEF, including build/break, theft, spam, fire, spawn camping, lava and more, so you don't have to undo any damage after the fact. 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 creativity.

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 any of these public servers. :) We maintain these servers personally, which helps us catch bugs and spot opportunities for new features and improvements. Have fun!

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.
    • New players get automatic claims around their first chests.
    • 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.
    • 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.
    • No pushing blocks in with pistons.
    • No pulling blocks out with pistons.
    • No TNT damage.
    • No creeper damage.
    • No damage from TNT cannons.
    • No explosive damage from other plugins, like Extra Hard Mode or Magic Spells.
    • No enderman block changes.
    • All doors may be automatically locked (optional, see config file).
    • No killing or luring animals away.
    • No stealing water.
    • No trampling crops, by players, animals, or monsters.
    • No growing trees inside the claim by planting outside.
    • No building overtop, all claims reach to the max build height.
    • No placing or breaking paintings / item frames.
    • Fluids will not flow into a claim from outside.
  • 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.
    • Almost no false positives.
    • Blocks server advertising.
    • 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.
    • 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.
    • It's impossible to get a player "stuck" inside a land claim.
    • 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.
    • Optionally, logs whispers and opens them to administrative eavesdropping.
    • /SoftMute command to shut down chat trolls without them knowing they're beaten.
  • PvP Protections.
    • When PvP is off, no setting fire or dumping lava near other players.
    • Absolutely bullet-proof anti-spawn-camping protection, 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).

The Manual

More Great Plugins!

  • Anti-XRay
    • Limits how quickly players can mine valuables, based on their play time / values mined ratio.
    • Keeps your valuables in the ground, so non-cheating players can find them (unlike ore loggers).
    • Practically free to run, unlike the tremendously expensive Orebfuscator.
    • Most legit players won't notice, but xrayers will ragequit and move on.
  • Population Density
    • Automatically assigns new players to wilderness where they'll find other new players and plenty of space, wood, and ore.
    • Optional teleportation system which can't be abused by players to escape combat or save them from being lost.
    • Login queue to guarantee fairness when the server is full.
    • Optional reserved spots for administrators.
    • Automatically removes idle players when the server is nearly full.
  • EnderHoppers
    • Allows the use of Hoppers with EnderChests inside a Claim
    • Items are taken from and added to the EnderChest inventory of the Claim owner
    • Supports The Better Ender Chest Plugin

Project Status and Future

From BigScary: I've re-joined the project. Yes, I know many of you had a very bad experience with the beta builds, there were many bugs. We've rolled-back the buggy features which were added after I left the project, and then I continued the project from there as if I hadn't left in the first place. So far, I've added UUID support, greatly improved performance during play time and boot time, blocked new grief strategies made possible by changes to the game since I last worked on the project, cleaned up the config files, and tweaked several features for much improved player and administrator experiences. I've even added some new anti-grief features.

My current plan is to wait for a new mod platform to emerge ( is looking promising), then build a new grief prevention plugin for that new platform. Until then, I will continue working on this project as I always have. No other project I've ever worked on in my career as a software engineer compares to GriefPrevention's mix of fun, challenge, and importance to the community.

How to Upgrade to 8.0+ Builds

Starting with GriefPrevention 8.0.3, you can keep any claims and player data that was created by the broken "beta" builds. You just have to customize your config file again (a new config.yml will be generated in a folder named "GriefPreventionData").

Starting with GriefPrevention 8.1 which supports UUID (player name changes), GriefPrevention will do a one-time data update during boot. This can take a very long time - up to 1 second for each player who has ever played on your server. This is because GP has to contact Mojang via the interwebs to get the correct UUID for each player. At this time, it seems this process works well for offline mode and online mode servers, but there are mixed reviews for the hybrid "Bungee Cord" configuration (try it, but back-up first!). In any case, please back up before you take on this major update. If you have any problems, restore your data from backup, use the older version of GP which was working for you for now, and get your logs to me so I can investigate. :)

Coming Soon

These are my top priorities right now. It's not a complete list of everything I plan to do. :)

  • Allow owners to interact with their pets even when in other players' land claims.
  • Protect tamed animals everywhere in non-PvP worlds, with the exception of those left in other players' land claims after the animal's owner logs out.
  • Stop negative splash potion status effects from applying to players who should be protected from PvP. (Damage is already blocked)
  • Look into killer bunnies not being damageable in other players' land claims.
  • Improve boot speed for flat file mode.
  • Prevent nether portal traps.
  • Prevent placing a nether portal in a land claim by building a portal in another world.
  • Fix sand/gravel cannons.
  • Require players to move at least a block after logging in before allowing them to chat (anti-bot strategy).
  • Update /RestoreNature for new block types in 1.8.
  • Update /RestoreNature to handle water better.
  • Update /RestoreNature to regrow trees.
  • Prevent claiming land inside a world guard region unless the claimant has permission to build in the region.

I'm aware there are issues specific to modded (not CraftBukkit or Spigot) servers. I do plan to address those, but I'm waiting for Cauldron to update to 1.8.

Please Vote for Grief Prevention

I've just posted Grief Prevention on the Spigot site. 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 ridddle ridddle Dec 18, 2014 at 08:26 UTC - 0 likes

    I'm already planning to run the per player limit on number of land claims, if that's what you're referring to. Why is the total number of land claims important to you, anyway?

    People being able to claim too many areas. I’m not happy how automatic abandoning works and when I had it enabled it led to unhappy playerbase (my rules allow anyone to grief/steal from unclaimed territory). On top of that capping claim number means that people start being conscious what they claim and how they do it. Lastly, their /claimslist screen isn’t a mess. We did a 3rd party “modification” and redesigned that list and split it into two but it would still be a mess for a player with 200 claims:

    If you had waited another 24 hours, you would have had a fix for this.

    Hehe, we are in different time zones it seems. Thanks for the fix.

    I'm open to suggestions about /trapped in the nether. I haven't come up with anything that feels "safe" for as you said, less technical users.

    On top of the algorithm that looks for an air pocket (which is the hardest thing, I realize), we are also checking what the floor is made out (ignoring liquids, fire, cactus, bedrock) of and giving player 10s of Resistance V, giving them immortality (so they don’t instadie when get ported into a hostile mob).

    About the spam thing - can you describe a situation which produces this type of spam so that I can improve the feature?

    Well crap, I thought that BuildingOutsideClaims message would be displaying every 10 blocks like in 7.x branch. I placed a few hundred of them now and can’t get it to display. Oh well.

    As long as you've been commenting here, your tone has always sounded lecturing to me. You'll get better results from plugin devs everywhere if you sound more understanding and patient, instead of judgmental and condescending.

    My tone definitely needs improvement. Truth be told, what happened with Grief Prevention during last year caused a few grey hairs to appear on my scalp. I think I don’t have to tell you exactly what was wrong but if a staple plugin changes major features or breaks basic functionality every 2 months, players get unhappy and leave.

    I’ve had so many issues with GP and I had to change so many design decisions around it changing that I think I may simply be burnt out in regard of my goodwill. I thought everything was rather stable and then 9.x branch comes in and introduces major changes that I have to try to relay to my community, without them burning me at the stake. :)

    That said, you are maintaining this page in an exemplary way so I’ll try my best to be an exemplary administrator, working with you for a better plugin. I saw your future plans and I may have some experience to share regarding blocking portals from cutting into claims – we fixed it with 3rd party code on our server, it’s been working fine for last year. Once again, I’m sorry for my tone.

  • Avatar of Duffa13 Duffa13 Dec 18, 2014 at 05:39 UTC - 0 likes

    @bigscary: Go

    Thanks for the response. If I have surface explosions enabled players shouldn't be able to explode TNT inside players claims should they?

  • Avatar of bigscary bigscary Dec 18, 2014 at 05:31 UTC - 0 likes

    9.6 Updates

    • Players may now give away pets with /GivePet.
    • Pets are now protected from many build-based attacks, for example flint/steel, lava buckets, and sand/gravel (suffocation), keeping them safe when you take them with you outside your land claims.
    • Admins may now damage other players' pets using /IgnoreClaims, and can use /IgnoreClaims to transfer another player's pet with /GivePet.
  • Avatar of bigscary bigscary Dec 17, 2014 at 21:29 UTC - 0 likes

    @ridddle: Go

    About water - because giving someone permission to build in a subdivision shouldn't mean he can also build in the top level claim via water bucket dumping. On the inverse situation, why not? Because now we're splitting hairs and I don't want to write special purpose code and risk bugs over a difference I think few will care about. My usual policy applies here - if more complain I will revisit. Just wouldn't be responsible of me to implement asks on a first come first serve basis instead of prioritizing based on how many want it or would likely benefit from the change.

    I'm already planning to run the per player limit on number of land claims, if that's what you're referring to. Why is the total number of land claims important to you, anyway? Just curious - your answer might push the priority on this up. Also, can you recommend a default for this setting?

    About horse trading, I know how Minecraft works and what players to with horses. If you had waited another 24 hours, you would have had a fix for this. I already promised it and I will deliver it, and suggested two different workarounds, one of which doesn't involve killing the horse (and which you conveniently ignored).

    Yes horses are pets. However you can specifically exclude horses from GP's rules in the config, if you want to. I recognize they're more than a little different from other types of pets.

    Sheep are protected, ender pearls require access trust on the destination end. Cattle require container trust, so I don't understand your question about villagers. Why not try some of this yourself and then tell me if you don't like it the way it is? Trying it yourself will get you answers in a few minutes rather than waiting hours or a day for my responses.

    Don't know what you mean about "sensible defaults", please be more specific.

    I'm open to suggestions about /trapped in the nether. I haven't come up with anything that feels "safe" for as you said, less technical users. I worry they'll shoot through the bedrock ceiling or end up in some lava.

    About the spam thing - can you describe a situation which produces this type of spam so that I can improve the feature?

    As long as you've been commenting here, your tone has always sounded lecturing to me. You'll get better results from plugin devs everywhere if you sound more understanding and patient, instead of judgmental and condescending. For example, a compliment "insightful tester" vs. an insult "combative nitpicker" both work in this context, but the tone is entirely different and the response would be very different. If the idea of "being nice" makes you uncomfortable, think of it as skillful manipulation of inferior beings. :)

    @Cammo009: Go

    Not sure I fully understand what you want from towns. You want players to not break blocks there unless they claim first? It's not really a solution - players could claim, break, then unclaim to work around the protection you're asking for.

    @alhamli99: Go

    Make sure you're on spigot or bukkit for 1.8. That's the most likely reason for everything not working. You have to have Minecraft 1.8 for the latest versions of grief prevention to work.

    @Duffa13: Go

    Not explicitly. The surface explosion protection only applies to worlds where land claims are enabled, though. Does that help?

    @modzmarvin: Go

    I think that's fixed in 9.5.

    Last edited Dec 17, 2014 by bigscary
  • Avatar of Duffa13 Duffa13 Dec 17, 2014 at 15:57 UTC - 0 likes

    I used to be able to control settings such as surface explosions etc per world, can this no longer be done in the config? Thanks :)

  • Avatar of modzmarvin modzmarvin Dec 17, 2014 at 12:54 UTC - 0 likes

    Hello, got a issue in the latest version (same for all the versions.) No one can get more claim blocks when they vote so i tried to typing the adjustclaimblocks bla bla bla and it always gives out the same error. Using the version from 7 hours ago.

    Kind regards

    The cow goes "baaa"
  • Avatar of alhamli99 alhamli99 Dec 17, 2014 at 11:46 UTC - 0 likes

    The problem when i do a right click holding the shovel or the stick nothing happen even when i put the chest nothing happen

  • Avatar of MrARCO MrARCO Dec 17, 2014 at 10:14 UTC - 0 likes

    Thank you Big!

  • Avatar of Cammo009 Cammo009 Dec 17, 2014 at 10:08 UTC - 0 likes

    Thanks grief provention to the Pet tamer. love you guy, so happy to get that issue fixed. Cheers

    By the way, is there a way to protect a full town region so players cant brake towns unless players place land claims? if town region can be added this be a perfect plugin. we can set admin claims to protect buildings that dont want areas for players to claim in the town regions

    Last edited Dec 17, 2014 by Cammo009
  • Avatar of alhamli99 alhamli99 Dec 17, 2014 at 08:03 UTC - 0 likes

    hello this plugin dosn't work in my server i don't know what is the problem answer me on skype ID: ii_alhamli

    Last edited Dec 17, 2014 by alhamli99: spelling


Date created
Dec 14, 2011
Last update
Dec 18, 2014
Development stage
GNU General Public License version 3 (GPLv3)
Curse link
Grief Prevention
Recent files
  • R: 9.6 for 1.8.1 Dec 18, 2014
  • R: 9.5 for 1.8.1 Dec 17, 2014
  • R: 9.4.1 for 1.8.1 Dec 16, 2014
  • R: 9.4 for 1.8.1 Dec 14, 2014
  • R: 9.3 for CB 1.8 for 1.0.0 Dec 10, 2014