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).
Hey Tux2
What does exactly restore nature do? Does it only restore on once claimed, but now un-claimed land? I have it set to false, somehow for my survival world. The weird thing is, grass blocks are staying dirt? If i turn it on now, will it restore nature around the claims? ( Meaning if players have a farm or something just outside there claim area, will it go away?) Or just on claimed then un-claimed areas? Thanks
1) I have a 4-5 worlds in survival and one creative. The Creative world is not pvp, and ppl can not toss items on the ground. How come?
2) i have never seen the nature restored due to unclaiming, why is this?
@pnkllr
It appears that the config is FORCING CreativeRulesWorlds: - <world name>
Wont let me have it as
CreativeRulesWorlds: []
Which mean its forcing the player to make a claim befor he/she can build.. How to fix this as putting the [][ doesnt work, and server will just add all your world there
Players cant build unless its inside their claims.. How to fix?
Two questions:
How do i set up land protection so players can't build or destory without claiming land? and Is there a way I can setup player Ranks so they get a set amount of blocks they can claim based on their rank..
IE if they are a member they can claim 100 blocks, but if they are a Adv-member they can claim 300 blocks?
Question on Grief Prevention and Timber - I have a player who has a tree house in a claimed bit of land, we couldn't work out why the trunk kept disappearing. Also have logblock and nothing was being recorded.
Turns out, I think, that it is due to the Timber plugin. Chop the bottom of the truck with an axe and the whole tree comes down before Grief Prevention can take any action to stop it, and then can't put it back. So some sneaky griefer keeps cutting it down each time we re-build it.
Can't think of a solution other than to take out the Timber plugin. Suggestions? Thanks very much.
Update 22 Apr 2013. Switched out "Timber" plugin for "Tree Assist", seems to work much better with Grief Prevention. Problem solved.
@Tux2
my server is 1.5 and i using 1.5 grief prevention, what's going wrong :(
Tux2,
Is there a command to list admin claims?
@elirock12
Try updating your version of craftbukkit to something more recent.
@jongre93
Currently planned, although only admins should have access to world edit anyways.
@TRBuildBros
Do you have essentialsProtect installed?
I'm having a slight issues. On my server I have the trust claim for an area that i got from the admin (me) but when i try to build i get a red text saying "you do not have permission to use [item name]". What is that all about? I've been messing around with some pluggins so I might have broken GP, if so how do i fix it?
I got a problem. WorldEdit overrides the claims.
Hello, is it possible to make a that everyone can create a slogan or more only for the creation of a second To pay claims? Excuse my bad english, I am from Germany! :)
@roggbart
Works Good.
Anyone tried to run this plugin on bigger servers with 100 players. How well does it run?
Hey a while ago i said i couldn't claim with a shovel and u asked for any errors in the console, and versions and stuff heres a a link to all the info i was able to get http://paste.yu8.me/?6d5ef169e1e02c76#DSEf23zwXpm1w25afrpFNfxfxdqRdf2T61g+W1NwvF8=
@Tux2: We are using version 7.6.2 which is for CB 1.4.7. It's not a huge deal if it doesn't work, but would be nice to have it back to normal.
@Tux2 - I have a request for consideration:
There are some situations where I would like to allow dropping of items in creativerulesmode. I use Clearlagg so even if players drop a lot of items it will remove them every so many minutes. That being said, we can't get certain redstone circuits to work properly where dispensers are concerned and I'm thinking it may be related to the restrictions on dropping of items. In a perfect world, as ADMIN I'd love to be able to set a flag inside any specific claim that would allow dropping of items so that dispensers work properly. Otherwise, the ability to simply turn off the restriction for creativerulesmode across the board would be great. I don't want to necessarily remove creativerulesmode altogether as I like most of the rule sets.
Are there any other workaround/solutions that anyone can think of?
Warmest Regards, JAG100
@Tux2
Latest version of Java 1.7_4.
My apologies for the large complaint, but I'm just so frustrated with the amount of lag this plugin has been causing and my claims being rejected as bogus by BigScary in the past, I actually completely forgot that you took over the project... 3 different NoLagg scans (each at an interval of 10k), one of which reporting 98k ms (http://wocl.net/errors/ServerLag/GPLAG2.png) of activity by GriefPrevention. BigScary assured everyone that the plugin was AS EFFICIENT as it could possibly be... but is that really true? I just can not see how one plugin could be causing so many problems... I've tried literally everything else to try to correct the lag, but nothing appears to be helping whatsoever. I'm currently reserving 4gb RAM on a linux desktop with a 3.6ghz quadcore processer, it should not be lagging at all... :/
Here is the exam (if you have NoLagg, just execute the jar with java and open this file) so that you can look more into it perhaps: http://wocl.net/errors/ServerLag/2013_04_15-15_39_32.exam. The issue appears, to me, to being caused by BlockPlaceEvent and I even notice this said lag when I am not in a grief prevention claim strangely enough.
I could've sworn I already made this comment the other day, but I'm not seeing it... so my apologies if this is somehow a duplicate:
I first began using GriefPrevention with 1.4.5... and with that, and through 1.4.7 the subdivision permissions worked "bottom up" rather than inheriting the permissions of the top-level claim. It appears this is no longer the case, as I've had multiple instance of players being able to use their permissions from the top-level claim in the subdivisions inside it.
I don't know if I'm experiencing a bug (either from before or currently) or if this is an intended change to the plugin. The "player experience" page still suggests that subdivisions are meant to be "independent" of the top-level claim with respect to permissions, so I'm *assuming* this is not intentional. But before I made a ticket, I wanted some clarification. :)
Love this plugin, but I do have a suggestion. Add a new configuration option AdminExtendIntoGroundDistance for admin claims. Allow it to be set to -1 for it to protect all the way to the bedrock. I would like it on my server if players couldn't tunnel under my spawn point but I don't want them to be restricted under ALL claims. Thanks for the great work!