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 Nov 16, 2013Hello, I need a little help. Is it possible for me to be able to turn off claiming with chest placement and leave it to gold shovel only? Thank you.
-
View User Profile
-
Send Message
Posted Nov 15, 2013@DetectiveButler
That isn't working around GriefPrevention, since players can throw negative or positive potions inside claims. The Dispenser isn't even really necessary.
Either way the dev build has rules that can be used to control Dispensers and where they can dispense various elements (Water, Lava, Positive Potions, negative Potions, etc).
-
View User Profile
-
Send Message
Posted Nov 15, 2013This has probably already been covered. However, a spl pot inside of a disp, will allow a griefer to damage animals inside a claim. As a suggestion, can GriefPrevention just simply stop these items from dispensing altogether?
-
View User Profile
-
Send Message
Posted Nov 15, 2013@stgram
The migration from flat to flat was ok, but to mysql...it failed. It created tables, inserted the correct nextclaimid, set the 5 permission claim blocks, and everything else is empty.
I honestly have no idea what you are talking about. How are you migrating 'to MySQL'?
As for the configs...daamn. These could be made shorter.
You can continue to use 7.7 if you want. Honestly I'm starting to get sick of working on GriefPrevention based entirely on comments like this that are well-meaning but hide behind them ridiculously complicated changes to something that took several weeks to complete.
I strongly suggest somehow merging the pvp/creative/claim-true/false configs into one file, so I can specify first which worlds I want, and then to set them up.
I've frozen it. This is an interesting idea that could be implemented if I had a full weekend where I didn't want to do anything else or sleep, I suppose. I'm not 100% on what you mean, but I guess the idea is that there should be one config and each individual config should only have the values that were changed. Not difficult, but not trivial either. And people are already calling for my head on a stick because I had the absolute gall to not release an untested development build as a release, though I'd argue most of those simply aren't able to even read the first paragraph of the main page- in any case, It's certainly something to consider for the future, but I'm wary of adding it before I do an actual release, which will require I document the config settings.
side note: You can set SingleWorldMode (or something similar, I forget the name) in the config so all worlds will use the same configuration file. You can also create a template file.
Actually now that I think about it, the original implementation I had for template files was almost what you mention. If a setting wasn't found in the world's config, the template setting was used. It still is- but the difference is that the setting is written to the world config file as well. The reason I went that route was so it was easier to open a file and change a setting, rather than have to figure out what nodes you need to add to change it.
I can probably cheat a quick fix and make that an option, "WriteBackWorldConfig" which will only write values if they differ from the template value, though I don't think such a change would be particularly trivial either.
-
View User Profile
-
Send Message
Posted Nov 14, 2013@Alshain01
Fixed.
-
View User Profile
-
Send Message
Posted Nov 14, 2013@BC_Programming
Sweet thanks! But it doesn't integrate with GPFlags, it integrates with Flags. GPFlags doesn't have the ability for flags to be registered externally.
-
View User Profile
-
Send Message
Posted Nov 14, 2013@Alshain01
I've added Hardcore Claims to the extensions list.
-
View User Profile
-
Send Message
Posted Nov 14, 2013this is the best plugin to protect land but need updates.
-
View User Profile
-
Send Message
Posted Nov 14, 2013@darkvirusx1987
Would you mind if I took on this idea? I'm kind of looking for something else to do right now.
EDIT: Well I started toying with the idea anyway and because the Grief Prevention API is so awesome, by the time I was done toying with it, it was pretty much finished, so I created a project for it.
-
View User Profile
-
Send Message
Posted Nov 13, 2013@BC_Programming
My fingers hurt. From all the ctrl+c and ctrl+v. Dev build is okay, tomorrow will be the pressure test when everybody logs in. The migration from flat to flat was ok, but to mysql...it failed. It created tables, inserted the correct nextclaimid, set the 5 permission claim blocks, and everything else is empty. 90 claims and 1600 players are not migrated to the SQL db. I reverted back to flatfile storage until I hear some feedback from you. No error logs btw.
As for the configs...daamn. These could be made shorter. I strongly suggest somehow merging the pvp/creative/claim-true/false configs into one file, so I can specify first which worlds I want, and then to set them up. And consider adding a global config for the blocks per hour, I have ranks with different numbers, and as such have disabled the option to grant my users block on an hourly basis. (yeah, someone has to pay the server hosting too...) Thank you for your time btw, we had a nice chat today...looking forward to tomorrow. xD
Edit: Please look at this issue, as of 190, still a bug: http://dev.bukkit.org/bukkit-plugins/grief-prevention/pages/7-8-and-later-grief-prevention-configuration/#c33
-
View User Profile
-
Send Message
Posted Nov 13, 2013@BC_Programming
My players can build whereever they want, except in the world with creative rules. I am using flatfile, but I do have a neat fast dedicated sql server from my hosting provider. Should I switch, because I notice 6sec lag on startup between your plugin and DeathCube, no idea which actually... So, if yes for the db, when would be the best moment? Before, or after going to the dev build?
For the separate world configs, have you considered creating one global, and then every other to just override values if needed? Because I currently have 2 service worlds, 3 main with 2 more for the main-main, nether and end, and perhaps a few more comming soon....
-
View User Profile
-
Send Message
Posted Nov 13, 2013@stgram
The dev version has started to stabilize, IMO. Of note is that no configuration data is brought forward; Of course, Claims and player data are migrated from your 7.7 data, but the configurations are now handled per-world and with a lot more granularity. There are still a few kinks regarding recreating the functionality of "noSurvivalBuildingOutsideClaims" using BlockPlace Overrides, so if you are using that you might want to wait a little bit.
Since you'd have to recreate the configurations if you used 7.7 and updated later, it might make sense to give the development build a shot. When it first starts it will find the 7.7 data and migrate it to the new folder. (the data folder is now called "GriefPrevention" instead of GriefPreventionData). It doesn't delete the old folder, so you can switch back to 7.7 if you are using the flatfile datastore. If you are using a DB though, 7.8/dev makes a few changes to the schema that might cause problems with 7.7.
-
View User Profile
-
Send Message
Posted Nov 13, 2013@darkvirusx1987
You could find a plugin that executes commands on death event for the player. /abandonallclaims and /acb ? Sounds like a much simpler task.
@BC_Programming
Do you reccomend updating then, or should I wait, if you intend to release a milestone version for 1.7? If yes for the dev, which version should I download, the last one or any specific? I am running a starting server, currently 30-ish rushhour players, but soon to scale up massively.
-
View User Profile
-
Send Message
Posted Nov 13, 2013@steviej1801
modification dates are tracked but It looks like it's only half implemented (the database schema doesn't have a column for the modification date, but the flat file datastore uses the file creation time). Another issue is that some operations actually create a new claim entirely, such as resizing, so even if it did work it might not reflect the actual date of original creation.
It might be something to look into for the next version- right now I've decided to freeze it so I can finish it up and write the documentation for all the changes.
@stgram
I seem to recall 7.7 having some issues with cleanups, including one rather long PM thread where a server admin was having massive problems; we traced the issue to the cleanup tasks, and I believe I worked to fixing the underlying issue and he reported success with the dev builds resulting from that change.
@darkvirusx1987
That's a cool idea, and could possibly be implemented as an option. It would also work well as a separate plugin (Hardcore claims or something?).
-
View User Profile
-
Send Message
Posted Nov 13, 2013Hi im looking at running this mod on challenge type servers.
Id like it so when a player dies, not only does it delete their claims, but it would run restore nature on their claims, and reset their claim points. effectively resetting that player back to when they first joined the server.
Or is there a command which will allow me to run restore nature on all of a players claims?
-
View User Profile
-
Send Message
Posted Nov 13, 2013@BC_Programming
Just a question regarding server performance, I am very happy with your plugin, but as it seems, every now and then the me.ryanhamshire.GriefPrevention.tasks.EntityCleanupTask runs for 2 seconds straight, which may be a cause for server lag. I am monitoring the plugins with NoLagg's examine feature. Should I be worried about it dragging the server, and is there any way to modify it?
-
View User Profile
-
Send Message
Posted Nov 13, 2013Thanks stgram. Yeah that is what I usually tell them, that's how I found out some were being dishonest about when they created the claim. However, I'm running a FTB server and I know it doesn't prevent everything so sometimes claims do get griefed(though it is rare). I can still use my rollback plugin to see who griefed to ban them but I can't tell if I should give back their items or not.
-
View User Profile
-
Send Message
Posted Nov 13, 2013@steviej1801
if they have a claim, the claim was not griefed while existed. Tell them that, the claim is impossible to grief. Therefore, the grief is from before that time.
-
View User Profile
-
Send Message
Posted Nov 13, 2013I've tried looking around so sorry if this is in the documentation somewhere. I think this plugin is great! Is there a way to see when a player created a claim? I am having an issue of players getting griefed and I'm pretty sure it was just because they didn't claim an area and I don't want to give them their items back if they're too lazy to protect their area. To get around this I've found that they protect their area after they've been griefed and tell me it was protected the whole time.
Thanks in advance!
-
View User Profile
-
Send Message
Posted Nov 13, 2013@SuperPyroManiac
I've edited the description to include a note and link about the continued development of GP-RealEstate. :)