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 Apr 3, 2012I´ve read the FAQ, but i still think it's a shame that the option to enable fire spreading outside of claims isn't there. It removes some of the SSP-feeling from SMP and it makes clearing large areas of forest quite tedious. so far we've used a work-around including lots of lava, but it is not optimal. I can of course see the arguments against fire spreading but those problems have never occurred on my server before i installed GP and including fire spreading as an option will only harm those who knew the risks when they enabled it. If it is hard to code then i can also see the reason to not include it :)
This is so far the only bad thing about this plugin i have found so far. This is the easiest plugin i have ever used and also the one with the biggest positive impact on my server.Great job and thanks for the continuous development!
-
View User Profile
-
Send Message
Posted Apr 3, 2012@bigscary
The build I'm using is stable and will be the new recommended build, however the changes since the RB are so arbitrary that I should of just stated it was the RB, maybe then you wouldn't of scoffed my report off. I did extensive testing and no matter what a user does they do not get any new claim blocks. This can be tested using 3.2 and above.
-
View User Profile
-
Send Message
Posted Apr 3, 2012@2Andri
Are you maybe not on the latest version? That sounds like a bug fixed many versions ago. I'll check on it later today just to make sure.
@simple_evil
I'll reduce the radius for lava for people who have the permission to 3 blocks. In the meantime, just tell people to move out of the way before you ban them. :)
@Jadedwolfs
Don't use dev builds. Also players who are just standing around or spinning or hopping up and down do not get blocks. They're assumed to be away from their computer.
@limdingwen
There's the awesomely awesome /restorenature command for fixing wilderness grief. If you really really want to take away the adventure aspect of the game and force people to mine directly under their houses only, then use the public API I've provided to create an extension to this plugin.
@limdingwen
I will never allow for vertical claim stacking. It would be a giant performance hit that would also confuse some players, and with a practically infinite world, there's no real need to stack player builds on top of each other.
If you change it to a wooden shovel, griefers will put claims everywhere just to grief people. The golden shovel makes them work for it, which most griefers don't have the patience for. Besides that, having it the same on every server means everybody can watch the same demo video and need no further instruction.
Use /containertrust public for that workshop.
-
View User Profile
-
Send Message
Posted Apr 3, 2012@simple_evil
"Lava Placement
Permission: griefprevention.lava
Players are allowed to place lava underground and away from other players. When placing lava on the surface, the player must be inside his claim, and the claim must be at least an hour old. Players with the griefprevention.lava permission may place lava anywhere they have build permission, but still not near other players. When PvP is on, players can dump lava and use flint/steel directly on other players."
-
View User Profile
-
Send Message
Posted Apr 3, 2012@simple_evil
i deleted my comment it was probably a Rage anyways ;)
i was raging you didnt see the lava permission nod eon the admin page, but then i saw it still didn't do what you wanted
-
View User Profile
-
Send Message
Posted Apr 3, 2012@cvxx7q
Not sure what your comment was my issue is I use Citizens and when trying to place lava for one of my cities or for my blacksmith I get the you can not place lava this close to a player thing which is really annoying considering I am an Op also might want to make it configurable to turn off if need be just a thought.
-
View User Profile
-
Send Message
Posted Apr 3, 2012@simple_evil
i deleted my comment, i failed to see your point, then i realised i was talking about the wrong thing, my fault sorry!
-
View User Profile
-
Send Message
Posted Apr 3, 2012@limdingwen
forcing them to mine for gold stops people pointlessly making claims and littering
wooden spade = claim spam
mining is a core element of the game and gold is useless in general so GP has effectively made the game better stick to its foundations, gold now is a reward instead of useless decor
as for the eye sore thing do you mean they may build a giant swear word and such then map it so other players see it?
and a quick fix for this is to use /restorenature on those damaged areas (once unclaimed)
although +1 for their cleverness in thinking that up, thats still a grief i agree, im not sure how that can be pursued though, i know bigscary isn't exactly interested in blocking wilderness modifications this harms the game play of minecraft ;)
ill be interested to see how this is handled
-
View User Profile
-
Send Message
Posted Apr 3, 2012Sorry if I missed out any points, but I may like to protect the wilderness from getting affected by the normal players. Now their form of griefing is by creating an eyesore and making the maps and claiming new land much more dangerous by destructing it to look like a mess. Other than that, I have another question. In some terrain generations that include arches normally include players that build below and above the arch, but the 'up to the sky' claiming makes it hard to do that. Also, the golden shovel is a bit hard to access and my players want to continue building instead of mining for gold first. And before I forget, is there any way to set trust to ALL the other players on the server? :) It is like I want to create a workshop for all the players but don't want them to destroy it.
Other than that this plugin is awesome!!! :D Thank you!
-
View User Profile
-
Send Message
Posted Apr 2, 2012For some reason with the latest dev build of bukkit and 3.2.1 of GP People are no longer receiving there claim blocks.
-
View User Profile
-
Send Message
Posted Apr 2, 2012This plugin is a great addition to my server but in your next release you might want to provide a permission node to let ops and admins place lava near others
-
View User Profile
-
Send Message
Posted Apr 2, 2012We have a problem on our server.
When we use the commands: /deleteclaim and /abandonclaim
It removes the claim, but when the server restarts like in every 6 hours. The claims return. That is really annoying, because it may have sometimes made 2 claims inside eachother. And GP is then not functioning correctly.
Please help me with this issue, as it's very frustrating.
EDIT: I think we found out that it was deleting the claim from the playerdata file of the player. But not the claim itself in the Claimdata folder.
-
View User Profile
-
Send Message
Posted Apr 2, 2012@Galexrt
Towny is really complicated - as proof, consider the immense manual. With Towny, you don't get fine-grained control over your protected areas. Plus it has lots and lots of features that have nothing to do with anti-grief, and doesn't include anti spam, anti spawn camp, fire spread, tree topping, and on and on and on...
Towny is cool if you want to build your whole server experience around it, but it's a land management plugin with a very incomplete anti-grief feature set. If you just want to do your own thing without worrying about griefers, it's way too much plugin, and grief prevention is a much better option.
For folks who run Towny, I think they should also run Grief Prevention, and just disable the claims so they get all the other nice protections.
-
View User Profile
-
Send Message
Posted Apr 2, 2012@bigscary Why not Towny??
-
View User Profile
-
Send Message
Posted Apr 2, 2012@Korbis28
The donation button is blue. It's at the top right of this page.
The likely problem with your claim overlap is that the existing claim is ABOVE where you're claiming. Because all claims extend all the way up to the sky, you can be standing underneath an existing claim (where the string will tell you there is no claim here). But when you try to claim, the new claim tries to reach upward and hits the existing claim.
@mynameismonkey
Thanks very much for that recommendation, I think that's the best one can do with GP alone.
-
View User Profile
-
Send Message
Posted Apr 2, 2012@bigscary
I have two arenas on the kids' server. I /ac claim the four areas around the playing field, and leave the field itself unclaimed with free replacement snowblocks nearby. I suppose it's true that the kids could figure out to claim the playing area itself, but it would be caught and fixed quickly enough. So, basically there is an /ac doughnut around the playing field. This stops people griefing the arena, seating, prep areas etc, but allows breaking (and building/replacing) on the field of play.
-
View User Profile
-
Send Message
Posted Apr 2, 2012@bigscary
Previously I could, but as (a) I can't now and (b) I wasn't supposed to be able to, let's forget I said anything :)
May I also add/respond to the many requestors here, that I for one choose this plugin as it is light weight, does what it's name says it does (prevent grief), and is not trying to be all things to all people. Thanks for a great plugin, and a commitment to quality through focus.
-
View User Profile
-
Send Message
Posted Apr 2, 2012@Korbis28
The donate button is at the top right of the page. Very top right.
-
View User Profile
-
Send Message
Posted Apr 2, 2012Hello,
First off I would like to say that I love this plugin and am wondering if you have a donation page. And I think that I have found a bug that I would like to report. After some time I have narrowed the bug down to a specific file where it doesn't seem like there is anything out of the ordinary in it. Here is the link to the file http:korecraft.com/downloads/GP.zip This bug has been found to happen in pvp world and p_v_p world around X:-56 Y:72 Z:-9. I haven't tested on other worlds. But when you right click with string around this area it says no one has claimed this block. But when you go to create a new claim with a radius of about 15 it says that it can't create because it overlaps, and it shows the outlines of the boarder. But it doesn't let me remove the one that it thinks is there, and the string doesn't show it. I deleted that file listed above and everything is working normally.
Just thought you would like to know about this. Thank you Korbis28
-
View User Profile
-
Send Message
Posted Apr 1, 2012@krisdestruction
Yes I saw that and it makes my head spin. I think you can accomplish your goal of managing the thing without subzones inside of subzones. For example, I don't understand why you can't do Town > Plots and Arena instead of four levels.
Maybe if you send me your server info, I can have a look and offer a more specific suggestion.