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 Sep 11, 2012Is it possible to enable/disable mob-spawning within a claim?
-
View User Profile
-
Send Message
Posted Sep 11, 2012Damn, so now we've just seen the bad effects of this plugin when you run a server that uses multiverse and has a few different worlds.
Players in our other SMP worlds and creative worlds can't use dispensers to dispense water or lava from buckets, because GP doesn't stick to the worlds it has been told that it should only affect :(
It was a very nice plugin, the siege side of it was most excellent, but we can't run a plugin that is going to do this to us.
Time to remove it :(
And yes, the only world set in the config file, is the world we want to have GP enabled on.
Our creative world is managed by 'PlotMe' and it does an awesome job, plus it only affects things in the world it is set up for in its config file. All our other plugins that affect block placement, etc... are multi-world aware too and only affect what they are allowed to in the worlds they are set up for.
-
View User Profile
-
Send Message
Posted Sep 11, 2012Is their any votifier support so that we can give our members claim blocks for voting. I know i have seen other servers do that but i cant find the listener.
-
View User Profile
-
Send Message
Posted Sep 11, 2012Hey,
I am using Griefprevention for a while now and i really like it. Big Kudos for making it, however i have had the following issue with your plugin. i used version 6.0, but then 6.1 came out, and as you stated i had to do /containertrust public if i wanted people to use doors and so forth. I installed the plugin anyway, and completely frustrated i was on my way to one of the like 300 adminclaims that needed this fix -.- and then well the thing is, i couldnt do that command at all.. because i had no permission even though i had griefprevention.* XD so i went back to 6.0.. Still couldnt do it at 6.2 then 6.3 came out and the thingy about restore nature scared me off.. Now 6.4 is out and i noticed you have addressed the problem about /containertrust so now it should be possible to do. However i am really afraid of this:
Now automatically cleaning-up claims which aren't protecting anything AND which belong to inactive players (two weeks). This will improve performance.
can this be turned off?? because whenever a claim is removed it is going to do lots of damage (at the very least all the lava and water will be removed! which is already causing me many complaints by people who are removing claims to replace them) but i am afraid it will now even use restore nature on peoples creations (which is on by default when abandoning a claim since 6.2 or 6.3 isnt it?) i just dont dare to upgrade and need some insight basically what i would like to know is 1. can removal of water/lava after abandonclaim somehow be turned off? this is causing me alot of pain and stress >.< seriously lost some people over this because for example one worked on a fountain for about 3 days and when it was done he tried to claim it... but there was a chest placed right there.... then he tried to remove both claims he made... and poof gone was all the water >.< then he got pissed off and when i figured out it could not be rollbacked i offered him to help him fix it but he just logged off and never came back... i liked him alot :( 2. will restorenature take action when abandonclaim is done? with the newer version? if so can this be turned off as well somehow? i really already see half of my players leave because half of them is screwing up claims constantly -.- explaining them how to do it really is a pain sometimes as it is often too late and they already have multiple claims where only 1 should be... 3. can the removal of claims after 2 weeks be changed to 3 months? because 2 weeks i find this a little short (and still i dont want restorenature to happen because this will definately cost me heaps of my playerbase also turning off the removal of lava/water would be fantastic...)?
please enlighten me! and dont get me wrong! i love your work! i just really dont think that a claim should be removed together with anything in it, be it just lava, water or anything else be it done by hand, or automatically and i somehow have the feeling alot of people do aggree with me on this! your plugin IS the best option for those people that just dont understand stuff like zmod at all(that makes most people), however those are exactly the people that are having a hard time using the golden shovel in the beginning and sometimes create like 5 zones over their house and then have to remove all 5 of them to create 1 big one later without having a clue how to do it, and it isnt unlikely that those kind of things happening comes with the purging of alot of water/lava on our server... alot of people just finally figure it out after the 10th time they get it explained XD even though its so friggin simple...
please please tell me that and how those functions can be disabled! thanks in advance! someone who really likes GriefPrevention 6.0 xD except for 1 tiny little bit of code that keeps removing water and lava that is
-
View User Profile
-
Send Message
Posted Sep 11, 2012@bigscary
Actually it isn't something we suffer from at all. This plugin excellent it is, is the only one with this issue for us.
And running 2 seperate servers means our player base can't mingle with each other, and when a person wants to switch from survival to creative in order to test something in their plot on our plotme world, they would have to log out and in to the other one.
That's just a bad set up if you force your users to do that.
I still like the plugin, and we will still continue to use it, it's just a shame you have this view.
And it isn't that difficult running a server. I've been running servers for about 10yrs now, web servers, unix servers, etc...
There is also no headache in our set up.
-
View User Profile
-
Send Message
Posted Sep 11, 2012I'm getting "You are not permitted to build" for new players. I want to let default build.
-
View User Profile
-
Send Message
Posted Sep 11, 2012Hey is This config right? So Far I Should have protected every chest in tekkit along with the redstone lamps from tekkit. http://pastebin.com/jtsWibxW
-
View User Profile
-
Send Message
Posted Sep 11, 2012@Valentari
Use The 5.5.1 version. You are using the 1.3 version of this plugin. To make it work on tekkit you must use any 1.2.5 version.
-
View User Profile
-
Send Message
Posted Sep 11, 2012@DrFusion
Do you mean temporarily deactivate it because you rebooted the server? Sounds reasonable, but most folks don't reboot their servers regularly so I don't think I'll code it. Just another thing I'd have to test every version.
@ray73864
No, sorry. I don't think I'll add an option to only award blocks when you're in a claim enabled world. I think we're starting to split hairs on config options now. :)
It's pro-rated.
Yeah, those are the hazards of running two servers in one server instead of two servers for two different player groups. I'm sure this is just one of many challenges you face due to that decision. :\ Consider that by splitting your server into two servers, you're doing your players a favor because now they don't have to learn a new trick to switch modes (slash commands, portals), as they already know how to disconnect and connect to a different server. Plus, you'd be making your life easier because a simple server means simple permissions and simple plugin configuration. But, maybe it's too late to change your mind now. Good luck! :)
@ha11oga11o
I thought I already answered that question, hmm... maybe when someone else asked it. Anyway, that's a Mojang bug. The client doesn't confirm with the server whether or not it's allowed to place a block before placing it on the client side, so there's a tiny sliver of time where the player can "stand" on a block which really isn't there on the server. There's absolutely nothing a plugin can do about this, since plugins all run on the server side. A fix is needed on the client.
@Perfk
First, not with basic GP. But you can get the real estate extension plugin linked above.
Second, do you mean a cooldown between sieges? That's already implemented. A player can't siege the same player twice in a row, or even the same claim twice in a row (with different players as the defender).
-
View User Profile
-
Send Message
Posted Sep 11, 2012can a user give a claim to another user? like. handing over the land to another user.
+ can i set the time a user can /siege another user?
-
View User Profile
-
Send Message
Posted Sep 10, 2012@ha11oga11o
I agree with possibility that i made wrong choice of plugins, why not :) Ill try to find which one is causing problem because Griefprevention is more important anyways :)
can you please read second part of mine post about placing blocks. can you please tell me is it bug or MC working that way. Im asking about that issue 3rd time here, but no one cant say anything about it.
-
View User Profile
-
Send Message
Posted Sep 10, 2012I think the worst part about saying you can get claim blocks for playing in any world, is if we have a person who only ever plays in creative, and they rack up 80000 claim blocks, one day, they could come into our SMP world and instantly get a big claim just by getting a gold shovel.
Not really fair on the people who have been playing in the SMP world and maybe can't be on as often as that creative world person.
-
View User Profile
-
Send Message
Posted Sep 10, 2012Also, is the claim blocks thing prorata'ed, or is it specifically you have to be on for an hour? Since we have some players who are never getting additional claim blocks at all, they are usually only on for about 30mins because of school reasons and they are active in the world (building, mining, etc...)
-
View User Profile
-
Send Message
Posted Sep 10, 2012@bigscary
Can we get the ability to turn this intentional rewards feature off? we would rather they only score them in the world we have set up for GP
-
View User Profile
-
Send Message
Posted Sep 10, 2012can u let the plugin's "wait # min then log on" thing be active when the server restarts?
-
View User Profile
-
Send Message
Posted Sep 10, 2012@madsod
Yes, but you need to add the block ID's for the blocks you want treated as containers, and some IDs for blocks which can blow themselves up (like nuclear reactors). You can do that in the config file.
@jbanto
Oops, typos. I'll try to remember to correct those. I don't want to reset the visualizations when the shovel is equipped, because often players want to do something like this:
It would be a real pain in the ass if every time you used the golden shovel, you had to do it blindly. :)
@lochlain000
Intentional. Basically, you're rewarding players for being loyal to your server, regardless of the world they're playing in.
@MaxboredREAL
Pistons explode if you try to push a block into a claim from outside. This is to prevent grief and also save CPU cycles (in case of redstone clocks, this stops the piston from trying to fire even when it can't move). So, to fix it, make sure your entire setup for the door is INSIDE your land claim.
@Valentari
I'm using BeastNode for my Tekkit server, and I don't have any issue. But I didn't use any fancy BukGet thing... is it possible that BukGet is downloading the LATEST bukkit instead of the correct Bukkit version for Tekkit (which runs on Minecraft 1.2.5)? If that's the case, follow BeastNode's troubleshooting guide to upload exactly the version of Bukkit you want to run. Also, you need to get GP 5.5.1, which is compatible with Minecraft 1.2.5. If you get the latest version, it won't work because it's made for Minecraft 1.3.1.
By the way, great choice. BeastNode is an excellent hosting provider. I run all three of my servers on their service, and may add a fourth soon. If you can't figure this out, file a ticket and they will be happy to help you figure this out.
@ha11oga11o
I'm not going to try and code around your bad plugin choice (no offense intended). Whatever plugin is doing weird things with bans on your server, you should consider removing it. All you need is the Vanilla commands - /ban /pardon /ban-ip /pardon-ip
@TeddyNielsen
For future players, increase default claim blocks in your config. For current players, use /acb to grant extra blocks.
@BoureyS85
You need to NOT op the tekkit accounts. That means any griefer can build a quarry to destroy another player's build, because all quarries will ignore all land claims. The best workaround is to put your quarry inside your claim, on the edge, facing outward, so that the quarry machine is inside your claim, but it's changing blocks outside your claim.
The problem is that tekkit was not designed for multiplayer, and it needs fixes to integrate with bukkit. So for now, you have odd workarounds like this one.
Also, you want to get TekkitCustomizer. Many Tekkit items are IMPOSSIBLE to limit with anti grief, so they must be banned from the server altogether.
-
View User Profile
-
Send Message
Posted Sep 10, 2012@Valentari
i am having the same problem
-
View User Profile
-
Send Message
Posted Sep 10, 2012Done update with 6.4 :P
-
View User Profile
-
Send Message
Posted Sep 10, 2012@ray73864
So GP is working great then? If the OPs do not have permissions within the said claim, or didn't setup the claim for themselves (or by using /adminclaims) then the owners privacy and protection is intact. ;)
Take a look at the GP admin page, especially at "Player Claims - Overriding" and the /ignoreclaims command. See if that solves your problem(s).
-
View User Profile
-
Send Message
Posted Sep 10, 2012@ray73864
/ignoreclaims
so admins can do what they need to do.