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.
Got a question or found some random bug? Check the documentation!
Got a problem or bug you can reliably reproduce? Or a feature request? Report it on the issue tracker!
Also, you might be able to catch me/others on the #GriefPrevention IRC channel for help (please state your question and exercise patience if you use this option).
Downloads for older Minecraft Versions
You may also view recent update notes on Github
The Manual
Feature List
Yes, everything is customizable.
- 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!
http://www.spigotmc.org/resources/griefprevention.1884/
Got a question or found some random bug? Check the documentation!
Got a problem or bug you can reliably reproduce? Or a feature request? Report it on the issue tracker!
Also, you might be able to catch me/others on the #GriefPrevention IRC chat channel for help (please state your question and exercise patience if you use this option).
-
View User Profile
-
Send Message
Posted Jan 4, 2013@fungreenfox
It looks like restorenature is broken or something. I'm not a coder but I can read. :)
SUGGESTION:
Customizable colors for messages.
I know you can change the messages but how can you change the colors if this is already implemented?
-
View User Profile
-
Send Message
Posted Jan 4, 201319:50:41 [SEVERE] Exception in thread "pool-1-thread-35"
19:50:41 [SEVERE] org.apache.commons.lang.UnhandledException: Plugin GriefPrevention v7.2 generated an exception while executing task 257295
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.removeSandstone(RestoreNatureProcessingTask.java:204)
at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.run(RestoreNatureProcessingTask.java:112)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
... 3 more
19:50:41 [SEVERE] Exception in thread "pool-1-thread-36"
19:50:41 [SEVERE] org.apache.commons.lang.UnhandledException: Plugin GriefPrevention v7.2 generated an exception while executing task 257299
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.removeSandstone(RestoreNatureProcessingTask.java:204)
at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.run(RestoreNatureProcessingTask.java:112)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
... 3 more
19:50:41 [SEVERE] Exception in thread "pool-1-thread-34"
19:50:41 [SEVERE] org.apache.commons.lang.UnhandledException: Plugin GriefPrevention v7.2 generated an exception while executing task 257301
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.removeSandstone(RestoreNatureProcessingTask.java:204)
at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.run(RestoreNatureProcessingTask.java:112)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
... 3 more
19:50:41 [SEVERE] Exception in thread "pool-1-thread-37"
19:50:41 [SEVERE] org.apache.commons.lang.UnhandledException: Plugin GriefPrevention v7.2 generated an exception while executing task 257298
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.removeSandstone(RestoreNatureProcessingTask.java:204)
at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.run(RestoreNatureProcessingTask.java:112)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
... 3 more
19:50:41 [SEVERE] Exception in thread "pool-1-thread-33"
19:50:41 [SEVERE] org.apache.commons.lang.UnhandledException: Plugin GriefPrevention v7.2 generated an exception while executing task 257293
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.removeSandstone(RestoreNatureProcessingTask.java:204)
at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.run(RestoreNatureProcessingTask.java:112)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53)
at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
... 3 more
GP 146 and bukkit version 2589 beta
-
View User Profile
-
Send Message
Posted Jan 4, 2013@bigscary
Master configurer :D Thats about my limit, i've tried coding many times, never very well. I accept what you say about animal spawn grief, i hadn't thought of that. But i'm looking in to a server in SURVIVAL MODE but with GP set to CREATIVE. I know it sounds crazy but.. Tthe ideal is they have unlimited blocks. But not GM1. I know the little sods will make spawn eggs though. I didn't want them to have to mine at all, so only building on what they buy would be ok. The idea was supposed to keep everyone happy. The PVPers with anger management issues can kill away and the creative types can build and kill mobs for cash.
And the winner is me , who gets to delete the current creative world which is massive btw. For some reason people like building in hills not plots.
You're right about plot me, its basic protection and easily worked around, but it is also a generator so thats useful. But I don't know if MC predicts land formations as you move. If it does plotme would (i think) be faster than MC's wilds generation. But if not, there's no advantage.
I might switch to wilds anyway, just for the hell of it, they like to be kept busy :D
I have a spare 24/7 server sunning on beta.stargatemv.com I have it using your creative mode in survival. It works great but its poor with no mobs to kill for cash. They do get the time accrued blocks of course. But they do like to kill.
-
View User Profile
-
Send Message
Posted Jan 4, 2013I like this plugin and im going to install 146 today.
I have a suggestion for survival players and the way of claiming.
I have a hard time getting ppl to set their claims before its to late and the builds are griefed away.
I would like an option for setting claiming a must for building, but trees and chopping set to be free, accessible without claiming.
And please remove the annoyoing bug in creative mode, where removing a claim, will cause a carpet of 1 layer stone and one layer grass to appear in 10 blocks hight at the size of the removed claim area.
-
View User Profile
-
Send Message
Posted Jan 4, 2013Hi! I think Grief Prevention is great and very easy to use. It was the first anti-grief plugin I tried and since installing it everything has runned smooth. I have recently installed a shop plugin called Shop Keepers. I would like to have a few shops in some of the buildings in my towns. Unfortunatly I'm not sure how to do this in a good way. If I create a shop in an area which have an administrative claim with access or containertrust it doesn't seem to work. (The shop keeper keeps respawning). I have used the "Trust public" command but then anyone can tear down and demolish my shops. :-( Is it some configuration I can change or some other way I can make it so my shop keepers are working and protected?
Also a comment / questions it took my a long time to understand that I could use ."/accesstrust all" to give access to everyone on my server for the claimed area. The videos explained the claiming process and how to share the claim with other users but I'm not sure if it mentions sharing with everyone?
Another comment / questions: I'm using bPermissions and have four user groups: Default, poweruser, moderator and Admin. It would be great if I could give access or build rights to specific areas / claims based on these user groups. I assume this is not possible right now would it be very complicated to implement?
All In all I like the video tutorials a lot but I would very much like to have one place where all commands and possible parameters/options are listed in clear text. If you forget something it is really complicated to find out which video it was mentioned in and where in the video or you have to start over from the beginning... Keep up the good work. Best Regards
-
View User Profile
-
Send Message
Posted Jan 4, 2013@bigscary
Thanks for the update! :D
-
View User Profile
-
Send Message
Posted Jan 3, 2013@bigscary
Sadly, I've tried this to no avail. I even removed the whole plugin and re-added it (all while the server was off) and that did not solve it either. It didn't occur when I was using the file storage system, but I would much rather use a database (which is when the console spam began).
-
View User Profile
-
Send Message
Posted Jan 3, 2013The antispam here works fantastic! The only suggestion I have is to add the ability to issue commands instead of a ban. Have maybe 3 commands executed when someone has reached the ban limit. You could then change it to something like:
etc. etc.
Thanks for reading!
-
View User Profile
-
Send Message
Posted Jan 3, 2013A few players tested on my server Siege into themselfs, then they noticed that they are stucked (siege lasts one hour) and wrote /kill command. The result was that they lost everything on inventory. Well they very soon learn not to do that again :)
The weird behaviour happened when there was 2 admins and another wrote /siege to himself inside personal claim, that blocked all claims owned by admins on a way that it was impossible to build until siege was stopped. This is rather exotic way of using /siege, so not a big deal.
Griefprevention is great plugin when making TNT cannons, you do not need to add water because cannons do not break when built inside claim, it makes possible to design a new type of TNT cannons which cannot be made using a normal minecraft.
-
View User Profile
-
Send Message
Posted Jan 3, 2013What if I accidently use nature restore and delete an unprotected building I made? Is there a way to undo it?
-
View User Profile
-
Send Message
Posted Jan 3, 2013@zrocweb
Nope, there are no claim names. I understand that to a very few players who have like 10's of claims it could be useful for remote management, but I've decided not to add something like that because it's a lot of coding, and I think very few would use it. The current feature set allows for editing the claim you're standing in, or all of your claims at once, but not for editing a specific remote claim. On average, each player has 3 claims.
@shaitand2
The default setting requires access trust to use a fence gate. That change was made after the video was published. :)
@woodsnake420
Still waiting for Bukkit guys to approve. You can get it early by clicking the blue "files" link at the top of the page. :)
@LegndPowerdNube
Sorry, I've decided not to do it. It really hurts performance to have to consider oddly shapen claims, and players can already create some simple shapes like L's, U's, and O's by stitching a few rectangular claims together.
@jaketampere
I left it in for testing purposes. I'm unaware of any bad results that can happen as a result of a player sieging himself - can you explain what problems you've seen?
@grimmie
Yeah, my thinking is that if a player is too lazy or too stupid to protect his stuff when it's as simple as place a chest and/or right click twice with a golden shovel even after seeing it explained and demonstrated in a video, then he deserves to be griefed and has no business playing on public servers.
Some plugins have attempted a fully automated land claim system where the plugin guesses what should be claimed based on where blocks are placed (and what type of block they are). It sounds like a good idea at first, but then players run into their claim limit and suddenly realize they have a nightmare ahead of them trying to figure out all the places where they have automatic land claims, which they want to keep, and how to remove those they don't need. Then they want to temporarily disable the automatic claiming to conserve claim allowance, and forget to turn it back on - and get griefed. If on the other hand there is no limit on claim allowance, then griefers run all over placing chests to claim all the land, and now nobody can build anywhere until an administrator comes to clean it up. It's a mess. :)
@voodoo12334
I understand a few players want to build up in the air, and it's a valid point. But there aren't many, and the downside to adding an /expand command is that it would allow players to claim areas they haven't explored yet, for example a new player could claim all the way down to bedrock, including all the ore there, even though he hasn't earned the gear necessary to go collect it. You have the option in your config file to make all new claims go to bedrock automatically, if don't agree with this thinking. :)
-
View User Profile
-
Send Message
Posted Jan 3, 2013@iBeCreeping
It looks like maybe you updated the plugin with the server running. Usually this isn't a problem, but I've seen it happen a (very) few times. Try giving your server a proper reboot to see if it fixes it.
@MrProtagonist
Please provide some details, and also update to the new version (assuming you've updated your server to CraftBukkit 1.4.6).
@Pixiyo
Sorry, it's a formatting issue with your YML file. It's very frustrating I know, but I'm not volunteering to fix it for the Bukkit team. :\
@ManBeastPigDev
Yes, the reason I'm not adding it is that it would be a huge deal to code, very disruptive to an area that I haven't touched in months. Also, it's not strictly anti grief, and I don't want to continue expanding the real estate management feature set. What's already available (claim subdivision) was only added after some serious arm twisting last January. :)
I haven't explored the details of PlotMe, but I suspect that it overlooks issues like launching minecarts into neighboring plots and spamming animals or projectiles to lag the server. Grief Prevention takes care of that sort of thing, so I think y ou'll be happier overall, once you've figured out how to make a smoothish transition. Good luck!
@ManBeastPigDev
The reason for no mobs/animals in creative worlds outside of land claims is that a griefer can quickly take down your server by simply spamming an insane number of animals with spawner eggs (or workarounds like chicken eggs in a dispenser). Even if it were disabled, that's not the only creative mode feature which will make your life difficult in a survival world, though, because players are also not allowed to break blocks outside their claim, making mining impossible and getting "stuck" more likely. Because you run such unique servers, it may be time for you to make the jump from masterful configure-er to amateur coder by making some experimental changes to the Grief Prevention source code. :) It sounds to me that you want players to be able to collect wood and mine in the wilderness (and replant trees?), but not build except for chests (to make an initial land claim). It's very doable as a customization project.
-
View User Profile
-
Send Message
Posted Jan 3, 2013Please, make an /expand command. It's not convenient to claim territory in the underground or in the air.
-
View User Profile
-
Send Message
Posted Jan 3, 2013@grimmie
We have the same problem ,but there isn't a more simple system out there (i checked) I used to have a super simple system that just bought land and blocked basic builds, They wouldn't even learn that system. And i had 2 commands only. So now i make all noobs do a little maze training course on spawn. They hate it of course but it keeps the whining down a bit...
-
View User Profile
-
Send Message
Posted Jan 3, 2013@RandomQuark
We are mainly having issues with lazy players on our servers who can't be bothered to learn how it works. Some even go far as always abandoning their automatic chest claim and never creating their own claim.
Everyone on our server has learned how to use it after trying it out. There isn't a single person who hasn't figured out how it works. It's really simple and easy, and that's what makes it such an amazing plugin.
-
View User Profile
-
Send Message
Posted Jan 2, 2013Great plugin! But on my server, I still require CoreProtect because it seems like GP is way to complex for newcomers, even though it is amazingly simple to use.
-
View User Profile
-
Send Message
Posted Jan 2, 2013Siege player itself should be disabled, player can siege himself and that will cause weird behaviour.
There should be added a check that you cannot make a siege to yourself.
It would be nice to have TNT damage enabled option on siege + option to loot chests if Siege is won.
-
View User Profile
-
Send Message
Posted Jan 2, 2013SUGGESTION:
Like WorldGuard where you can have different shaped claims instead of just the square. It will make it a lot more suitable for servers that use Custom terrain and things of that nature! :)
-
View User Profile
-
Send Message
Posted Jan 2, 2013@shaitand2
You can block access in the config!
-
View User Profile
-
Send Message
Posted Jan 2, 2013Am I missing something? Can I get the 7.2 update somewhere? Or are we all waiting for bukkit to approve? Is there a jenkins? :)