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 May 17, 2014Somebody help me, i updated the the latest GP version and every 5 minutes GP deletes around 100 "unused claims" i set the claim expiration to "-1" because i want all claims to be permanent, but this damn update keeps deleting everything... HELP! message me.
-
View User Profile
-
Send Message
Posted May 16, 2014@kemmeo
Unfortunately as far as PvP goes, I have PvPManager on my server so people can participate if they choose. If I set PvP to false in GriefPrevention, instead of just not touching PvP it literally disables all PvP functionality. I just don't want it to even know PvP exists.
It's so sad to see this plugin in this shape :(
-
View User Profile
-
Send Message
Posted May 16, 2014Hi, I'm actually setting this plugin on my server. I saw in configuration help this variable: claims.worlds. It says: use the claims.worlds configuration variable to list which worlds players may create claims in. Ok. But where must i put this variable, and how to use it? I didn't find any exemple or help on using this.
Same for: griefprevention.claims.creativerulesworlds. It is the list of the worlds where players additionnaly follows creative-mode rules. How to use that? In that files, the world file or the config file? And how to list the worlds? How to use that...?
-
View User Profile
-
Send Message
Posted May 16, 2014@kemmeo
You should be the new Maintainer of this plugin. I know more quantum physicists in person than I do people on the internet who know to operate this wreck. Kudos to you.
-
View User Profile
-
Send Message
Posted May 16, 2014@jet315
set it to 100, dont be cheap. GrÃefPrevention awards claimblocks every 5 minutes, but if you get it to 10 an hour it gives the player like 0.000000000000001 claimblocks every 5 minutes which it most likely just rounds up to 0. therefore people on your server get no claimblocks.
just set it to 100, its no big deal really :)
-
View User Profile
-
Send Message
Posted May 16, 2014@saiismad823
I dont think so.. you'll just have to claim all the land you've already protected using WorldGuard, which isnt that big of a deal I would say :)
-
View User Profile
-
Send Message
Posted May 16, 2014@ThePassingStar
its actually pretty easy -.- go to the config.yml file
and set GlobalSpamEnabled: false
as for PVP. go to the WorldConfig folder now go to the world folder you want to effect (default is "world") and set all of the Boolean values under the PvP: section to false..
as for your Spawn.. stand inside your spawn and use "/containertrust all"
its not that complicated, if you just take your time to learn the plugin its one of the most complete and feature rich anti-grief engines out there, so stop saying its a pain.
-
View User Profile
-
Send Message
Posted May 15, 2014This plugin is slowly becoming one of the biggest pains of all plugins ever. The author/maintainer need to pick it up or just fossilize this project. It is NOT user-friendly to most server owners!
-
View User Profile
-
Send Message
Posted May 15, 2014I sent this to the inbox of the author but he's notorious for not responding to anyone:
Hello,
Is there any way to disable the pvp and chat-guard functionality for Grief Prevention? It's incredibly annoying and the config is difficult to navigate. I also want to cite that on the spigot/essentials irc's I went to, nobody suggested that I use GP because it's a pain in the ass in every manner possible. Unfortunately, due to some internal affairs, I am forced to use this plugin for the server's plot protection engine.
I don't want this plugin to touch pvp or chat. How do I disable the functionalities?
Also, how do I get enchantment tables to work for other players within an admin claim? My spawn is admin claimed but players can't use the enchantment table provided there.
, Pass.
-
View User Profile
-
Send Message
Posted May 15, 2014Hey, i really like this plugin and it makes it soo much easier to control players deleting my town i created.
But i have one issue, when i login as the server admin and claim my area's, it all works great, but when i login as another admin and try to destroy/build it "says cannot build here [op's name] " which is good.
But that message only appears to another admin? if i remove the OP status and try again it just rebuilds it "no error message" i need it to say that to a normal players how can i do that? By default when someone Joins/Plays my server there normal users.
Thanks again for the awesome plugin!
-
View User Profile
-
Send Message
Posted May 14, 2014I'm pretty sure it said not for admin claims? But, that being said thanks!
-
View User Profile
-
Send Message
Posted May 14, 2014@Conorserver
Do "/Subdivideclaims" This will change the shovel to subdivide mode, which allows you to claim smaller area inside your main area. Then you can trust the player inside the subdivided area which will allow them to only build there.
-
View User Profile
-
Send Message
Posted May 13, 2014Hi i'm having trouble with the plugin. I have a spawn (big one) and its a town with player owned houses. I was wondering is there a way to claim the town so no one can break blocks anywhere and then claim plots over the town claim? So town is admin claim then subdivided into smaller house plots for player which are basic claims? I might have missed something but this is really giving me trouble!
-
View User Profile
-
Send Message
Posted May 12, 2014is it possable to add items to griefprevention data that u are holding in game. like if i was holding a wooden door and i type a command to add it to the list. is there a way to do this?
-
View User Profile
-
Send Message
Posted May 11, 2014Hi, Im currently using worldguard for all region protection types but alot of players find it hard so I want to use GriefPrevention for players claims and world guard for admin claims.
My question is... Is there a way to stop players from claiming land with GriefPrevention in WorldGuard regions?
-
View User Profile
-
Send Message
Posted May 11, 2014@jet315
Hi, I am not in anyway connected with this plugin. Not a developer, not part of its "team" of people who create it and spend countless hours to maintain it.
However I answered your question about accrued blocks, because when we first started our server, we noticed the same issue. So we simply started searching the internet for an answer. It turns out there is a ton of information about griefprevention. Everything from commands, to complete explanations of the config files and what each thing means.
As far as your spawn? When you created it... the first thing you needed to do was make that a region using world edit and world guard. And then it would have been protected. The only ones who would have been allowed to build there? Would have been you or anybody you added to the region. Griefprevention seems to be more for players claiming personal space out in the wilderness outside of your spawn area. I use admin claims for protecting pvp arenas and such and for events or other things. But we always use regions for that stuff also so we can set flags and permissions like we want them.
Also with griefprevention, if needed you can do an admin claim and then transfer it to another player if you wish to.
There is a lot of information on this plugin, and at first it can be confusing? but it depends on how new you are to the whole server thing, the config files, etc...
If you have previous experience already, then look on the web for a page on the griefprevention config set up, then go into and look at the griefprevention config files for your worlds. One of the first things you need to do when starting a world is make sure the config files are set how you need them.
It starts to make sense if you read them over carefully. Even the banning? can be shut off. In fact, just about everything is configurable on this plugin. It makes it more complicated yes, but then it also means it does a whole lot more.
Im really sorry you are having issues, and hope you get things up and running. We have only been running our Bteam server for about 4 months, its my first experience with this,and Im the one who had to learn about all the plugins, modpacks and configuration files. Its tough? but like I said, the more you have to mess with it, the more you learn, and it starts to make sense after a bit.
I guess what Im trying to say is, don't blame the griefprevention people, they aren't exactly getting a steady paycheck for all their time and efforts, and try to remember that when you create a plugin or modpack, it has to work on tons of different systems, and get along with everybody elses plugins and modpacks at the same time. That's a daunting job for anybody and all they can do it make it the best they can.
Good luck and hope you get it working!
-
View User Profile
-
Send Message
Posted May 11, 2014This plugin is turning out to be one of the worst plugins I have ever installed:
Firstly, I didnt know accrued blocks per hour HAS to be higher than 10, Players have been playing for weeks now (some have quit) because I set it to 10 and it turns out 12 is the minimum. NOWHERE does it say this in the excess of irrelevant information posted above.
Secondly, there needs to be some form of anticlaim area rather than just admin claim..admin claim is explained as an area admins can claim only, I had to use IRC to find out commands to add people to admin area that were not admins, I shouldnt have to..it should be intuitive....Fist week of using the plugin and the whole spawn was claimed by random players...little did I know I needed to admin claim the area, then allow chests to be accessible by all (so players can use enderchests in the spawn). Possibly the most unintuitive design I have ever encountered in a plugin.
FINALLY and this is the big one, this plugin is randomly banning players who spawn in. I have NO idea why, from the message file I found "Auto-banned {0}({1}). See logs for details." This is how I found out it was this plugin banning players. It dosnt say any reason at all as to why they have been banned. Nor did it say it was grief prevention doing this. I had to assume and luckily assumed this plugin first. Nowhere can I find this log file.
In a nutshell, the ambiguity of this plugin has ruined my survival server and im probably going to have to start it all over again.
Parts of this plugin are absolutely brilliant, but it seems like in its brilliance the raw basics have been completely forgotten..
EDIT: just checked my banned players file, around 20 players have been banned. I havnt banned anyone so im assuming its all been down to grief prevention. Who the hell enables banning to default to true on a plugin?? Much thanks grief prevention turns out you griefed the server more than any single player you were trying to stop....ironic...
-
View User Profile
-
Send Message
Posted May 10, 2014me to i installed Bpermissions and people can grief spawn, and all the claimed land
-
View User Profile
-
Send Message
Posted May 10, 2014Hello,
Quite a few of us server owners are having a really big issue and need help if possible please.
We use griefprevention on our server. Up until we started running a bteam server it was fine. Our problem is we are having a major griefing issue. And Claims as well as regions are not immune to it. I noticing when searching the net that we are not the only ones.
The problem is the statues mod. Its doesn't matter if the area is protected, claimed, regioned. Anybody with a hammer can turn the existing blocks into statues.
If there ANY we can prevent this? Something in the config file we can change? I was hoping to find a way to at least ban the hammer just from a specific region, but no luck.
And we really hoped griefprevention would prevent them from at least griefing claimed property. But that is not the case. I think its because the use the hammer to "open" the blocks, then change it around to the statue they want, then hit the sculpt button which changes the blocks into the statue and "closes" . Im going by what I saw using prism. It wouldn't roll it back either, it seems to see it similar to if you "open" inventory.
Not only has our spawn been griefed? But quite a few players houses also, all claimed and protected with griefprevention.
Help ? Please? Anybody? Thank you Terri
-
View User Profile
-
Send Message
Posted May 10, 2014@jet315
Hi, I had the same problem, my blocks accrued per hour was set at 10 also. Cant remember where exactly I saw it, but there was an explanation about this. It turns out that the lowest you can set the accrued blocks per hour is 12. If you set it any lower than that? You wont receive your blocks.
I reset mine to 12 for each of my worlds, and it works perfectly now.
Hope that helps Terri