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 Jul 28, 2012im running this on tekkit and was wondering is you could some how allow players to kill another player if there on there claim people are stealing and raiding in my server :| and cant protect there stuf because of the you cant injure defenseless players
you don't have to many ways to configure this :|
-
View User Profile
-
Send Message
Posted Jul 28, 2012Heya. Plugin is working great now! Thanks a lot. One suggestion, would it be at all possible to add a block list in the config which lists blocks that can ONLY be placed inside a players claim, and not in the wild.
For example, I've set it so the block Nuclear Reactor in Tekkit, when it explodes it damages blocks inside the claim, but I ONLY want players to be able to place them inside a claim. If this is possible it would solve so many problems on our Tekkit server, Thanks a lot -Semajnad
-
View User Profile
-
Send Message
Posted Jul 28, 2012there is breakable block that can be Brock in the config , like - DIRT - GRASS - LONG_GRASS - COBBLESTONE - GRAVEL - SAND - GLASS - THIN_GLASS - WOOD - WOOL - SNOW when i delete them an restart it comes back on start up, i want all black unbreakable
-
View User Profile
-
Send Message
Posted Jul 27, 2012Curious, is it possible that maybe one day we could separate the doors so you can lock an iron door and a wooden gate but not a wooden door?
-
View User Profile
-
Send Message
Posted Jul 27, 2012@newfiekids
Or, you could read the documentation. :P It's AddItemsToClaimedChests. Turn that off.
-
View User Profile
-
Send Message
Posted Jul 27, 2012@NagatoSC2
You did post in the right area. :)
No sorry, making chests raidable would be a disaster. Remember it's not always a fair fight, so making the result of defeat losing ALL of your valuables rather than just what you have equipped would be really extreme. Imagine the scenario were three guys in diamond armor walk around /sieging everybody they find at home and taking all their stuff. Also, players would work around this by putting solid blocks on top of their chests when they're not in use.
There's currently a 5 minute timer, I think, before you're ejected. You can enter the build, which gives you a chance to collect anything the player dropped when he died, and if he had friends in there, now you can get at them to fight with them more directly. But no, you can't raid the chests.
Making every block breakable eliminates the strategic building part of siege pvp, since now attackers don't have to look for a weak point - they just run up to any wall and bust in. Also any sort of defensive gadget or trap would be pointless, since attackers could just destroy the mechanism rather than outsmart it. The result would be that builders would have to "grind" to make a strong fort (by collecting an immense quantity of obsidian) rather than exercise their creative muscles.
@schmidtbochum
You mentioned files updating to the new format. Do you mean to files with IDs for names, or do you mean you migrated your data to the database?
You said you deleted some claims. Did you directly delete files, or did you delete claims in game? If you were deleting files, is it possible you accidentally deleted the important "next claim ID" file? If you did, you may be able to recover by finding that file and updating its content so that it's 1 number higher than your highest claim file number.
Are you sure about the claims where you have one of the new size and one of the old size? If you /reload without logging out your client, you can have the leftover "visualization blocks" from the previous claim size still showing in your client, then also get the new visualization blocks for the new size when you right click the new size with the stick. So it APPEARS in your client that you have two claims on top of each other, but that's just because your client didn't wipe out the old visualization. You can confirm this by logging out and back in, which will erase any "ghost" blocks.
@newfiekids
Yes, you need to do two things. First, go to GP config and disable the "left click to donate items" option. Second, put a land claim around your shop. Everything should work fine (I haven't personally tried it). Due to the land claim, no one will be able to break your blocks/chests or open your chests, except for you, the creator of the land claim. They can still left-click the chest to make purchases.
-
View User Profile
-
Send Message
Posted Jul 27, 2012i also have QuickShop ( http://dev.bukkit.org/server-mods/quickshop/ ) installed is there a way that i can alow people to buy from me and yous this to stop them stealing the items?
-
View User Profile
-
Send Message
Posted Jul 27, 2012we have massive problems updating from 4.7 to 5.5.1 We restarted, and it converted the claimfiles to the new format.
We deleted some claims and restarted again. After the restart, the deleted claims were there again, and even worse: Claims we resized were doubled (one of the old size, one new size)
Also, some claims just disappeared.
-
View User Profile
-
Send Message
Posted Jul 26, 2012Hello, I'm not sure if this is the right place to ask this. But I couldn't find a forum to post in. Is there anyway to implement these PVP settings with Grief Prevention?
My apologies if this is the wrong area to post this in.
-
View User Profile
-
Send Message
Posted Jul 26, 2012Absolutely fantastic work bigscary! :)
EDIT: Removed long question asking about expiring claims that was answered by simply reading the administrative details page. :) Thanks!!
-
View User Profile
-
Send Message
Posted Jul 26, 2012Very glad to hear you both got your problems solved. :)
Hey everyone, I've finished updating the administrative details page. I hope it will be much easier for you all to find the answers to common questions, now. I'll update the API documentation next.
-
View User Profile
-
Send Message
Posted Jul 25, 2012Awesome! After removing the world from the "CreativeRulesWorlds" item drop worked. We are using a plugin "itemstay" which showcases the items so it was hiding the items floating. The only thing we don't want people able to drop is armor, weapons, and gold but I believe we can do this with another plugin.
Thanks for the reply so quickly this plugin rocks! We'll be using it tons!
-
View User Profile
-
Send Message
Posted Jul 25, 2012I've put this "griefprevention.claims" in the permissions of the default user and it's still not appearing when a default user types /help or /help griefprevention.
Only OP users have the list of all the commands in the /help..
Edit: Ok, just forget that, i've just updated the plugin and its working with that node.
-
View User Profile
-
Send Message
Posted Jul 25, 2012@netherfoam
They get a warning because if they continue, they'll either get a kick or a ban (depending on your settings). It's true they're effectively not spamming because the anti spam is that good, but not giving any warning would probably lead (non-griefing) players to feel a little abused, because most would have adjusted their chat if they had realized they were getting too spammy.
This might lead you to suggest that since the mute works so well, maybe I should have an option to not kick or ban, and just mute spammers. The trouble there is that spam of the most trollish sort (flood by macro or custom client), may actually lag your server if there's nothing done to actually prevent it once it gets completely out of hand, because it costs cpu cycles to process all those messages and decide whether the player is still spamming or not.
Thanks for the thoroughly prepared commentary! :) It's not often folks really think very hard on the feature set and submit such thoughtful feedback.
-
View User Profile
-
Send Message
Posted Jul 25, 2012Hi again, My issue with the spam detector is that your plugin is telling people off for spamming when the event would be cancelled (thus not spamming), not that i cant catch the event.
Cheers :)
-
View User Profile
-
Send Message
Posted Jul 25, 2012@Modelitup
I still don't fully understand, but I think I can help a little. First, check your config file. Make sure you've ONLY listed the creative worlds under "creative rules worlds". Take any survival worlds out of that list. This should fix your problem with survival worlds.
I'm not sure what you mean by "creative mode through permissions". It should be the case that players running in creative mode don't get item drops when they destroy most blocks. Are you running some kind of non-standard creative mode for some players? Why do you expect players who are in creative mode to get item drops, and why do you want them to get drops?
@PIPOKID
Almost all of grief prevention's player commands require the "griefprevention.claims" permission. For the admin commands, you want "griefprevention.admin.*". There's one command (/trapped) which requires no permissions. But it's not important to have in the help, because when players need it, they will be told about it (by this plugin).
-
View User Profile
-
Send Message
Posted Jul 25, 2012This is what i need:
A player type /help griefprevention and get listed all the commands (and it's description) he can use. (the /trust, /abandonclaim, /PermissionTrust etc).
And to get this i need to know which permission node to put in the config of my group plugin.
thanks :)
-
View User Profile
-
Send Message
Posted Jul 24, 2012We are running creative mode through permissions which allow us to drop either way.
After disabling and enabling plugins I found GriefPrevention is the plugin that is preventing the items from being shown when attempting to drop. In Survival mode & in Creative.
After disabling the plugin the dropping was working. I'm open to any suggestions you may have.
-
View User Profile
-
Send Message
Posted Jul 24, 20125.5.1 Fixes!
@PIPOKID
Sorry pipo, I'm not sure I understand your question. Do you mean what permissions node are the grief prevention commands listed under? Those which are related to claim management use the "griefprevention.claims" node. The /trapped and /siege commands don't require any permissions, though.
-
View User Profile
-
Send Message
Posted Jul 24, 2012Hi, i don't know if this question was asked or not, but here it is.
What are the nodes we can use?
I need normal players to have acess to the griefprevention help and i don't know what node to put there.
I have tried the griefprevention.* but it just shows non important comands to them (admin comands).