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 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.
    • 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 (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.
    • Fluids will not flow into a claim from outside.
    • No placing blocks via TNT/Sand/Gravel cannon.
    • No placing portals without build permission (even by walking through a portal in another world).
  • 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.
  • 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 bigscary bigscary Oct 08, 2015 at 16:37 UTC - 0 likes

    @GodsDead: Go

    Yep, there's already a ticket tracking custom ban command lines.

    Is there some exploit involved in a player sieging himself? If not, I'll leave it as-is... handy for testing, plus every time I change something something else breaks.

  • Avatar of GodsDead GodsDead Oct 08, 2015 at 12:27 UTC - 0 likes

    Players can Siege themselves...

  • Avatar of GodsDead GodsDead Oct 06, 2015 at 11:13 UTC - 0 likes

    @bigscary: Go

    Amazing! Its funny how quickly we fall into routines, I've been trying to change myself to a ticket system but I stil rely on my forum support tickets!

    Alright, then Ill just keep throwing things into here! They may stack up. On top of the things i've already mentioned:

    • The Auto spam banning system, Let us customize the command thats run, This will allow us to set custom punishments based on spam, for my specific reasonning, I use banmanager, which has its own ban commands, The web UI is far superiour for managing punishments, and its searchable. GP uses the built in ban system, which means we never know why people are banned without checking mutiple places, simple fix would be to allow us to set the command ran with {username} parameter for punishment for those Spammers.
    Last edited Oct 06, 2015 by GodsDead
  • Avatar of bigscary bigscary Oct 05, 2015 at 16:30 UTC - 1 like

    @GodsDead: Go

    I'm doing fine tracking comments here - I've had years of practice, plus lately I don't get so many comments because I've updated the plugin to solve most problems without asking a question (for example, if an admin doesn't have enough claim blocks to claim an area, the error message tells him about the /acb command). Anyway there's a ticket tracker here on bukkitdev - just click the blue tickets link above. Ironically, I always remember to read comments, but often forget to check on tickets. You might get a faster response from comments.

  • Avatar of GodsDead GodsDead Oct 04, 2015 at 19:20 UTC - 0 likes

    @bigscary: Go

    Its too late for me to turn back now, we are just re-creating the sub-claims, but there was an issue converting, what I will do is send you a copy of our GriefPrevention database, so that you have some real-world data to play with at some point. I have a few other issues to report, but I will wait until you are caught up. Where do you keep track of all your open tickets? Using the comments here must be impossible. Most people tend to have a github and use the issue tracker there?

  • Avatar of bigscary bigscary Oct 04, 2015 at 17:13 UTC - 0 likes

    Update 12.7.2 is here!

    @AriKira: Go

    You can't use the same database for two different servers, or share claim blocks across servers. If you really want to do either, my source is on github - you can make those customizations yourself or ask/pay someone to do it for you.

  • Avatar of AriKira AriKira Oct 04, 2015 at 17:06 UTC - 0 likes

    And could U add an option in config to custom the mysql tables name or prefix? I want to make different servers's tables in the same database.

    _(:з」∠)_嘿,这里是卖萌的Miku_Snow! _(:з」∠)_Hey,here is acting cute of Miku_Snow! _(:з」∠)_ね,ここは売って萌のMiku_Snow! _(눈_눈 」∠)_嘛 其实叫我千飞夏就行了

  • Avatar of AriKira AriKira Oct 04, 2015 at 16:57 UTC - 0 likes

    @bigscary: Go

    That mean...I cannot make players have the same claim point in different servers? Maybe i need use mysql trigger to synchronize 'griefprevention_playerdata''s date?

    Last edited Oct 04, 2015 by AriKira
  • Avatar of bigscary bigscary Oct 03, 2015 at 21:12 UTC - 1 like

    Update 12.7.1 is here!

    @G0ularte: Go

    Yep there's a claim mode for that - see setup/config page.

    @AriKira: Go

    Different servers should use different databases (but the databases can all live on the same database server).

    @MotheMan: Go

    Rather than blanking the list, reduce it to only a fake word no one will type like asdfasdfasdfasdfasdf22232. Due to a mistake on my part, leaving the list entirely blank results in all words being treated as profane. :( I'm working on the fix.

    @deathly809: Go

    I dunno which files are missing? Maybe the JUnit stuff. Try deleting the file with tests in it.

    @marubal21: Go

    I'm gonna have to work on making the docs on that more obvious. Unused only applies to creative mode worlds - it means a claimed area where few player-type blocks have been placed, making the claim "unused" in the sense that it doesn't protect a build, just reserves a wilderness area. Because players can by default create any number of land claims and in creative mode start with the golden shovel, griefers could potentially sprinkle small claims around just to be annoying. This would clean those up automatically.

    @ExDomino: Go

    Put a subdivision around the container, then /containertrust public in that subdivision.

    @Asile: Go

    Nope, sorry. Most of GP's rules (like no creeper damage above sea level for example) apply onto to worlds where land claims are enabled. I hope that helps?

    @GodsDead: Go

    I'll work on the first two issues right away. Please give me more information about your conversion - maybe you have some logs? My guess is the reason it doesn't go well for you is because your server is atypical - huge amounts of data from existing a long time, heavy load due to many players simultaneously, and running in database mode. That's not an excuse for my making mistakes of course - but it's almost impossible to test for your situation when I can't manufacture it on my test server (mine is a year old and in database mode, but I'll bet I see nowhere near your traffic levels).

    Last edited Oct 03, 2015 by bigscary
  • Avatar of Asile Asile Oct 02, 2015 at 21:23 UTC - 0 likes

    I am running GriefPrevention alongside MultiVerse. Is it possible to have a completely different GriefPrevention configuration on different worlds? For example, if I want FireSpreads to be false for one world, but true for another, is that possible?




Date created
Dec 14, 2011
Last update
Oct 04, 2015
Development stage
GNU General Public License version 3 (GPLv3)
Curse link
Grief Prevention
Recent files