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.

http://dev.bukkit.org/media/images/76/965/gp_video.png

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 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.

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 (spongepowered.org 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. :)

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

  • Avatar of gigantictragedy gigantictragedy Mar 11, 2012 at 21:05 UTC - 0 likes

    it was just a suggestion but having to keep an eye on the map and go around and manually restore nature on all of them takes alot of time. I like the rn feature and i think its better than using the towny with no wild perms. it is just something to save us time.

    ok i agree now, i was going off of your video for the restore. it seams to be having trouble in the jungle bio, half of large trees hanging in the air, doesnt seam to restore to seed, the seed doesnt show up on the f3 anymore maybe its guessing. hopefully the tree griefing thing will kick in and replant them. still think its easy to use and at this time where we dont have an rb yet its still working :)

    Last edited Mar 11, 2012 by gigantictragedy
  • Avatar of John19800 John19800 Mar 11, 2012 at 20:28 UTC - 0 likes

    wow no change log on any of the updates?

  • Avatar of bigscary bigscary Mar 11, 2012 at 19:26 UTC - 0 likes

    @psyduck751: Go

    None of the commands work from the console. Log in to use them.

    @gigantictragedy: Go

    Yikes... I think a map wide restore nature sounds dangerous. I won't add that. Do you really have a big problem with ruins, or are you just anticipating one? In my experience, players almost never abandon their builds. The only ruins I get are ruined dirt huts from new players who don't stick around and whose claims are automatically cleaned up.

    @Memorex39: Go

    When there's an overlap, you should see the conflicting claim highlighted in lava and netherrack. Was it not the case for you? I've intentionally disabled /deleteallclaims for administrative claims because of the potential for bad stuff to happen (like when you trust that one guy and give him permission, then he runs one command to wreck the whole place).

    On the confusion regarding creating and resizing claims, sorry, I don't know how to make it any easier, maybe you could give some specific suggestions? I tell my players to watch the video. So far, you're the only commenter to complain that managing claims is too difficult.

    I don't want to automatically shrink claims until they fit, because I don't want players to mistakenly think that what they tried to claim was correctly claimed when it wasn't. Better to tell them there's a problem and let them figure out what to do about it than to automatically protect less than they wanted, I think.

    Last edited Mar 12, 2012 by bigscary
  • Avatar of Memorex39 Memorex39 Mar 11, 2012 at 18:03 UTC - 0 likes

    How do I do a /deleteallclaims administrator ?  Of course my question/example does not work.

    Took me a bit to find an "overlapping claim" when doing an administrative area.  Was pretty frustrating.

    Even if the administrative area was overlapping, why wouldn't it just resize?  I don't know but was pretty ambiguous and confusing for something that should have been so simple.

    The simple text (paraphrased), "...both points made now create your claim..." is frustrating and pointless imho, if you have both points shouldn't it be created automatically?

    I like the simplicity of the idea, but I am concerned that my young users won't understand how to expand, since I had so much trouble.

  • Avatar of gigantictragedy gigantictragedy Mar 11, 2012 at 15:08 UTC - 0 likes

    hi i just started using grief prevention on my small server. i was wondering if there could be a map wide restore nature command, or in the config set to do a map wide restore nature command settable for 2weeks or a month. it would save admins from running around doing it. say if someone unclaims an area and moves it leaves ruins that will need to be cleaned up. but if theres a map wide command or it does it threw the config it would save admins time. not sure if its possible. maybe add an enable and disable in the config for those that dont want to use it. thanks i like your mod

    Last edited Mar 11, 2012 by gigantictragedy
  • Avatar of psyduck751 psyduck751 Mar 11, 2012 at 14:41 UTC - 0 likes

    It's the same...if I say like trust psyduck751 or anyone else it keeps saying /Trust <player> ...how must I add the name in order for it to work?

  • Avatar of xSokix xSokix Mar 11, 2012 at 12:11 UTC - 0 likes

    @psyduck751: Go Example for my username: /deleteallclaims xsokix

    Example for your username: /deleteallclaims psyduck751

    Last edited Mar 11, 2012 by xSokix
  • Avatar of psyduck751 psyduck751 Mar 11, 2012 at 11:08 UTC - 0 likes

    I installed this plugin on my server and it works just fine...however ...when I need to use a command which requires either an amount or the name of a player the console does acknowledge it and repeats the command ...

    ex: deleteallclaims playernamehere becomes : deleteallciams <player> I don't know what to do...I added <> to the playername but nothing...please help... I just installed it 5 min ago ...I know my question noobish but cmon :)

  • Avatar of briankdk briankdk Mar 11, 2012 at 05:36 UTC - 0 likes

    @bigscary: Go

    Ahhhh, very nice. Problem solved ;-) thx :-)

  • Avatar of bigscary bigscary Mar 11, 2012 at 05:33 UTC - 0 likes

    @seriosbrad: Go

    Yep, I understand. After the videos were made, I fixed it so that /RestoreNature wouldn't work when players are in the restoration area, because players can be suffocated. So now you have to stand outside the area, but you can use the shovel from a distance so it's easy to manage.

    @Tux2: Go

    I'm using the claim block coordinate as a reference. That doesn't work for you? It is a unique identifier, but it might change over time.

    @Memorex39: Go

    You can run both, but I suggest you either disable GP's claims, or disable PS's claim blocks (while keeping the trampoline blocks and other goodies). If you keep TWO ways for players to claim an area, then they'll be confused and griefers may find creative ways to annoy.

    @briankdk: Go

    Allowing players to use lava just anywhere on the surface is a bad idea. Griefers can make a huge mess very quickly, which can be very difficult to clean up - if it's right next to a claim, /RestoreNature won't work, and lava doesn't always go away when you pick up the source block. Having said all that, if you REALLY want to let all players place lava wherever, use a permissions plugin to give all players the "griefprevention.lava" permission.

    @Tutimane: Go

    Thanks, I'll put that documentation update on the to-do list.

    @Galexrt: Go

    Yes, you can disable the theft protection while keeping the block build/break protection on.

    @Tulonsae: Go

    I will release when it's stable. Too many new features and undocumented code lines right now.

    @briankdk: Go

    How are they destroying buildings with axes? No claims? Anyway if you want lava back on for everybody, assign "griefprevention.lava" permission to all players. Using a permissions plugin, you can do that very quickly and conveniently.

    @briankdk: Go

    Put an admin claim around the railroad with /adminclaims. You can't accomplish that goal with a standard private claim.

    Last edited Mar 11, 2012 by bigscary

Facts

Date created
Dec 14, 2011
Categories
Last update
Oct 29, 2014
Development stage
Mature
License
GNU General Public License version 3 (GPLv3)
Curse link
Grief Prevention
Downloads
245,309
Recent files
  • R: 8.6.2 for CB 1.7.9-R0.2 Oct 29, 2014
  • R: 8.6.1 for CB 1.7.9-R0.2 Oct 29, 2014
  • R: 8.6 for CB 1.7.9-R0.2 Oct 24, 2014
  • R: 8.5.2 for CB 1.7.9-R0.2 Oct 23, 2014
  • R: 8.5.1 for CB 1.7.9-R0.2 Oct 22, 2014

Authors