Grief Prevention

Grief Prevention

AUTOMATICALLY PREVENTS ALL FORMS OF GRIEF, including build/break, theft, spam, fire, spawn camping, lava, treetopping 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 using crafting equipment.
    • 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 bans (configurable) spammers.
    • 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 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.
    • Griefers can't dump water or lava above sea level, unless they claim the land first.
      • The fluid will not flow out of the claim.
      • Deleting the claim removes the fluid to prevent spillage.
    • 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.
  • 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 added necessary anti-grief features for new game elements (leashes, hoppers, mounts). I've also added UUID support, and the current focus is improving performance.

Because all of the Bukkit staff have simultaneously quit the project, it's extremely unlikely that Bukkit will ever be updated to support Minecraft 1.8 or later servers. Also, there's a legal issue which resulted in all craftbukkit builds being removed from the internet in general. The law is slow, so that makes future bukkit versions even less likely.

Due to these circumstances, 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, Tux and I will perform the minimum maintenance needed for this project, which includes fixes for grief (including UUID support), bug report investigations, and bug fixes. Depending on how quickly the sponge platform gets ready to go, there may be time for me to slip in some minor tweaks here and there as well. There will be no major feature adds (like new config options or per world configs).

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!). I'm not sure how GP can make it work for Bungee configs 100% correctly - if anyone has specific information on how solve this problem, please share it.

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

  • Avatar of bigscary bigscary Oct 21, 2014 at 17:05 UTC - 0 likes

    @asonofashadow: Go

    Use /accesstrust public to grant all players access to doors, buttons, switches in a land claim.

    The players can use the /trapped command to escape, unless it's an administrative land claim.

    Don't use the config file to stop protecting doors and buttons, because they will make buttons/levers accessible in ALL land claims everywhere, not just the one land claim where you want players to have access.

    @xSnowBlitzz718: Go

    Sorry no, there's no option to delete all admin claims at once. I don't think your situation is recoverable (meaning there's no code fix to make migration work for your case). There's no harm done in leaving administrative claims around - the builds will be protected, and if the players do return to play again, then you can /transferclaim back to them at that time.

    @mcly: Go

    I don't want to make the change about deleting permission information because the current design ensures that if the player logs back in later, it will start working again.

    Look up YAML syntax (Google/Bing search it). Probably you need to add some special characters to allow for a colon in your message. OR, you could just drop the http: part of your new URL. :)

    @dutchrastacraft: Go

    Was working for me last night on the test server - I will check on that. Unless you were trying underwater? It doesn't pass through water blocks when aiming.

  • Avatar of dutchrastacraft dutchrastacraft Oct 21, 2014 at 15:50 UTC - 0 likes

    "Doubled the effective range of claim tools (golden spade, stick) to 100 blocks from 50."

    It is not possible anymore to claim from a distance. You have to click on the block itself to claim in 8.4?

  • Avatar of mcly mcly Oct 21, 2014 at 11:03 UTC - 0 likes

    I also can't change the Land Claim Help message. No matter how I change the message and the URL, it always show "Land Claim Help:". Can you please fix it?


  • Avatar of mcly mcly Oct 21, 2014 at 10:46 UTC - 0 likes

    Problem with admin subclaims on my server (maybe player claims too):

    I do scheduled recycle on my server, which removes idle players who hasn't joined for a while. As a result, their plots (subdivideclaims of admin claims) got permissions change from their username to "someone".

    Can you please fix it? For instance, if the player data got removed, the claim owner can be removed too. Thanks.

  • Avatar of xSnowBlitzz718 xSnowBlitzz718 Oct 21, 2014 at 03:37 UTC - 0 likes

    @bigscary: Go

    My server used to be cracked so it had some cracked player files(now its premium), I believe the cracked player files and claim files did not convert and turned into admin claims? Is there a way to delete all admin claims at once? (I think /abandonallclaims only works for own claims and haven't tested it on admin claims)

    But for now I'll use the backup and go back to the previous version, do some testing on a test server and transfer when I can.

    Thanks for the reply. That was faster than I expected.

  • Avatar of asonofashadow asonofashadow Oct 21, 2014 at 01:16 UTC - 0 likes

    @Bobcat00: Go

    OMFG that looks exactly like what I need. I'll report back after testing XDDDDDDDDDDDDDDDDDDDDDDDDDDDDD.

  • Avatar of Bobcat00 Bobcat00 Oct 20, 2014 at 23:35 UTC - 0 likes

    @asonofashadow: Go

    See "Claim Security" at Also look in your config file. I think there might be additional options of use to you.

  • Avatar of asonofashadow asonofashadow Oct 20, 2014 at 22:42 UTC - 0 likes

    Hello, I am really loving your plugin. I do have a dire request ( to my small world ;] ) request if it is at possible for the next update or hotfix.

    I need players to be prevented from griefing, on purpose or not, yet still be able to use doors, chests, levers, ETC. without having to trust each individual player in a marked plot. If there is already a way to globally trust doors, containers, switches, ETC, with preventing block placing and destruction I will be over joyed and primed for your reply.

    If this feature is not already present, then here is my request:

    Could you please add, either a new feature to the trust system, or admin plots if need be, that would put someone into Adventure Mode when entering said plot, then back to Survival after leaving, or whatever their previous gamemode they were in.

    So in the end a castle could be setup to be raided, monster battled and defeated, but no breaking or modifying of it's structure, in a survival server, oh shoot even a creative one.

    Thank you so much for your work to the community so far and I hope all is well for you.


    One last thing, it is actually possible for a player to get stuck in a land claim. I have a protected village and people have tried to follow them into the houses only to be locked in, ROFL. I personally find it quite amusing, but this is another thing that brought on this request.

    Last edited Oct 20, 2014 by asonofashadow: addition
  • Avatar of dutchrastacraft dutchrastacraft Oct 20, 2014 at 20:53 UTC - 0 likes

    @bigscary: Go

    Well I have no idea what I'm looking at :D I'm just looking at the percentages :P

  • Avatar of bigscary bigscary Oct 20, 2014 at 17:19 UTC - 0 likes

    @Turbotailz: Go

    You can delete the old "griefprevention" folder. You need only "griefpreventiondata".

    Yep, I know it's not ideal. There was a time when there was no upgrade option at all from the beta versions produced by BC. So this is a big improvement, and recustomizing your config file is a one-time thing.

    @xSnowBlitzz718: Go

    Send me your logs from the first time you booted with the updated version. There should have been a migration process which turned all your old data (player names) into player UUID's. For now, you should restore a backup and go back to using the older version until I figure out what went wrong for you.

    @sparts: Go

    What's build #36? Did you grab something from the continuous integration server, which we're not using anymore? If yes, then you got an old build with bugs. Take your builds from our uploaded files (here on Unfortunately, I do not have access to take down the CI server, or fix it. I tried to contact Tux but he's been radio silent for weeks now.

    I think you should leave the expiration off for a while (a few weeks at least) to give your current players time to log in, which updates their last login time with grief prevention so they won't have the wrong one anymore. Then you can turn the expiration back on, and only those players who haven't played while you had it disabled will be impacted.

    Villagers are not protected from monsters, only from players who don't have permission. If you're observing something different, let me know and I'll investigate.

    @dutchrastacraft: Go

    I disagree. :) The main problems are still interact, block break, and block place. I don't have a solution for login/logout (other than pushing that work to other events, which doesn't change anything overall). However I have a fuzzy idea about what I can do to reduce the three big ones mentioned above.

    Thanks for the timings!

    Last edited Oct 20, 2014 by bigscary


Date created
Dec 14, 2011
Last update
Oct 19, 2014
Development stage
GNU General Public License version 3 (GPLv3)
Curse link
Grief Prevention
Recent files
  • R: 8.5 for CB 1.7.9-R0.2 Oct 19, 2014
  • R: 8.4 for CB 1.7.9-R0.2 Oct 17, 2014
  • R: 8.3 for CB 1.7.9-R0.2 Oct 14, 2014
  • R: 8.2.3 for CB 1.7.9-R0.2 Oct 10, 2014
  • R: 8.2.2 for CB 1.7.9-R0.2 Oct 09, 2014