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 18, 2013@Macht65
GriefPrevention.Enabled in the world config disables/enables it.
@asgernohns
That was added over a month ago in the dev build.
-
View User Profile
-
Send Message
Posted Jul 18, 2013Hi i have a bug, that i want to be fixed! :) I was trying some stuff with the plugin. i tried to shoot a wooden button with a bow. and the door did open, and i got out. it was just a little heads up, for a bug fix
cheers!
-
View User Profile
-
Send Message
Posted Jul 18, 2013Is it possible to turn off GriefPrevention?
I'm using multiple worlds, Like Survival, Kingdoms and some more...
But I want to have GriefPrevention enabled in Survival world, and disabled in the kingdom world.
But I didn't found a turn off line in the world configs and or command.
Please let me know :D I love this plugin in every way. :D keep it going ;)
-
View User Profile
-
Send Message
Posted Jul 17, 2013@brian163b
transferclaim is only for transfering a claim from a player to an admin claim.
-
View User Profile
-
Send Message
Posted Jul 17, 2013Testing under GriefPrevention #136, craftbukkit-1.6.2-R0.1 Anyone else having a problem with /transferclaim? I'm standing in the claim and type /transferclaim <player> and it says "enter /transferclaim again to switch claim back to admin claim" (sic). I use a stick to check the claim owner and it's still admin. Check /trustclaim and see nothing either. If I'm doing something wrong, please advise.
-
View User Profile
-
Send Message
Posted Jul 17, 2013Can you make it so there is permission to make it so when someone places a chest the person without that permisson won't be able to have an auto claim on a chest
-
View User Profile
-
Send Message
Posted Jul 16, 2013Could you enable AutomaticNatureRestoration when a player unclaim his place? Or something to "clean" the rest after some days/hours? :3
@EDIT: another sugestion: could you make something to "ban" commands to people who don't have trust? Some players use /sethome on other houses.
-
View User Profile
-
Send Message
Posted Jul 16, 2013@BC_Programming
I am using GP version 5.5.1, as Tekkit runs with MC 1.2.5 and CraftBukkit 4.0
-
View User Profile
-
Send Message
Posted Jul 16, 2013For some reason the when I try to subdivideclaims it doesn't work. It say it will overlap another subdivided claim. which I have never made before. and it also says that the area is to small which I know isn't true. I'm the owner of my server so I trying to set up subdivision for shop. thanks
-
View User Profile
-
Send Message
Posted Jul 16, 2013I need to disable PvPNoContainers Text: You can't access containers during PvP combat.
-
View User Profile
-
Send Message
Posted Jul 16, 2013@smc87
My question is if i decide someone has a valid reason to have a smaller claim, and decide to /adminclaim and then /transferclaim to them, after a server restart will their claim be removed?
Yes.
Personally i dont think auto purge is a great idea (admitably i dont have any internal understanding of the mod), I'd have thought an "on demand purge" would be better or at least making auto purge a globally configurable option, defaulting to false.
If the setting for a minimum claim size is set, than it should be followed, no exceptions- if smaller claims are desired, the setting should be changed.
Note that (as it is) admin claims will also be deleted by this logic. I didn't realize they had a nonsensical special case where you can resize them to smaller than the defined minimum size.
Because of these esoteric special cases I'll probably revert it anyway. It was more intended to hack-fix what I thought was a more general bug that turned out to be misconfiguration on the user's part.
-
View User Profile
-
Send Message
Posted Jul 16, 2013Hello, I've read some Q&A's below about build 130# but i'm still a little concerned. I also notice you mention the functionality of /transferclaim has changed:
Leashes can be used on tamed mobs belonging to the player in any claim. When claims are loaded, if they are smaller than the worlds minimum claim size they will be deleted — bc_programming / detail
My question is if i decide someone has a valid reason to have a smaller claim, and decide to /adminclaim and then /transferclaim to them, after a server restart will their claim be removed?
Personally i dont think auto purge is a great idea (admitably i dont have any internal understanding of the mod), I'd have thought an "on demand purge" would be better or at least making auto purge a globally configurable option, defaulting to false.
It just doesn't seem a good idea to ever auto remove any claim by default except maybe initial ones that never get used.
Apologies if you have already covered all of this in help documentation or if you have implemented similar (or much better) options than those above.
-
View User Profile
-
Send Message
Posted Jul 16, 2013@slimedog007
/adjustbonusclaimblocks <player> <amount>
-
View User Profile
-
Send Message
Posted Jul 16, 2013Hi, in the video the narrator said you could give claim space through voting. What command do I tell my listener to execute when someone votes in order to give them more claim space?
-
View User Profile
-
Send Message
Posted Jul 16, 2013@dom1298
Provide GP Version.
-
View User Profile
-
Send Message
Posted Jul 16, 2013Hi, I am running a Tekkit Classic (1.2.4 CB 4.0) server, Velikcraft.
I am continually getting rather long error messages in my console, I have caught one and here it is: http://pastebin.com/A6Nw0wYG
If any of you know what this is bieng caused by and if I can fix it, please reply.
Thank you!
-Dominic Cotterill (Velikcraft Server Owner (www.velikcraft.net))
-
View User Profile
-
Send Message
Posted Jul 16, 2013How do we enable flint and steel? Is there a permission or is it in the config.
For some reason since the 1.6.2 update our players have no permission to use flint and steel.
-
View User Profile
-
Send Message
Posted Jul 15, 2013@BC_Programming
Thank you very much!
-
View User Profile
-
Send Message
Posted Jul 15, 2013@BC_Programming
You were right. That was actually the first time I used the plugin manager to update grief prevention. A restart fixed both resize and transferclaim problems.
-
View User Profile
-
Send Message
Posted Jul 15, 2013@deleted_9935739
Using #130 claim resizing works fine for me.
/transferclaim only gives admin permission now and does not accept any arguments, or rather, I reverted it to it's original behaviour. If anything /giveclaim will be overloaded with the ability to forcibly change claim ownership.
I don't know if there are problems using PluginManager, but it might explain some of the curious behaviour you seem to get.
@DQone
What is an unknown command?