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 23, 2013Think this great plugin, donation on its way! Hope more joins in and donate.
-
View User Profile
-
Send Message
Posted Nov 22, 2013I'm having problems with the annoying Spam bot on your plugin.
In the config under Spam i have set it to "Enabled: false" but non-op players still get a warning and a kick for spam.
When they return they lose their PermissionsEx prefix and I'm not even sure if it was your plugin conflicting with it but it was the only plugin I was fixated on at the time.
Anyway, does "Enabled: false" DISABLE the spam bot? Otherwise what is it there for?
Thanks, -superzyr
-
View User Profile
-
Send Message
Posted Nov 21, 2013@BC_Programming
Ok no problem. I was just curious because I just converted to my first to maven. It worked pretty well for most, except one that required shading, ended up abandoning that and doing it the old way.
-
View User Profile
-
Send Message
Posted Nov 21, 2013@Alshain01
It was working with the 1.5 builds but I removed it when I switched it over to 1.6, since I spent over an hour trying to figure out why it failed to build and just switched it back because it was defeating the purpose.
-
View User Profile
-
Send Message
Posted Nov 21, 2013Is this commpatible with towny? will people be able to claim land in other peoples towns?
-
View User Profile
-
Send Message
Posted Nov 20, 2013BC, Did you ever get Maven working or did you give up on it?
-
View User Profile
-
Send Message
Posted Nov 19, 2013Is it possible to add a /lockallclaims <user> [time]
I like the feature where you can lock a claim to prevent it from expiring, but for players going on vacation that have several claims, it can become really tedious to go through each of their claims and locking it.
Basically it'll work the same as lock claim except it'll lock all claims under the <user>'s name possible for a specified amount of [time], which if omitted can be indefinately.
There can also be a buffer when it's for a specified amount of time. For instance, if the claims are locked for next 20 days, once that lock expires, the user has the next .... say 24 hours to log in so that the system recognises them as active again.
EDIT: PS: Great Plugin by the way. The only complaint I have is it's torturous to dig through the documentation, but I do it cos it's a great plugin xD
-
View User Profile
-
Send Message
Posted Nov 19, 2013I cannot use /trust while op in admin claims, and cannot /trustlist others claims with 190 build. Is this a known issue?
@D496580
You know, you can simply delete the comments. ;)
-
View User Profile
-
Send Message
Posted Nov 19, 2013@AbuRom
The exception is thrown from the server implementation itself that should not occur.
Nothing in the stack trace points to GriefPrevention, either.
-
View User Profile
-
Send Message
Posted Nov 18, 2013Hey hey, having some issues with GP...
I have a Tekkit Server, and as it goes with Tekkit servers, GP stops people from breaking and taking things out of machines, however... It does not stop users from opening the GUI in someone else's claimed land.
Here's the issue... When someone goes on another user's claim (one he is not trusted on) and they open up the MK2 Crafting Table, the empti GUI of the table will come up. If a player puts an item inside it... The server restarts itself. It does it the proper way... Saves world, sends message that the world is restarting... I can only see this coming from griefprevention... Any chance someone knows a fix for this?
Here's a log of the error (it may contain other crap) http://pastebin.com/cLwGrB1e
-
View User Profile
-
Send Message
Posted Nov 18, 2013@knivesstryfe
It's listed in the config as "AutomaticNewPlayerClaimsRadius." Set that to 0 or -1 (I forget which). I'm sorry about the ambiguity in my last comment; I thought the feature was listed in the config as something like "AutomaticChestClaim," so it wouldn't require a lot of directing to get to it.
-
View User Profile
-
Send Message
Posted Nov 18, 2013Here's a comment just saying hi and that I'm really happy to see continued activity on this plugin. It's the best and my players and I (now playing 1.7 vanilla) really miss it.
That is all. Please keep up the good work and thank you!
-
View User Profile
-
Send Message
Posted Nov 18, 2013@stgram
Using SQL is only particularly useful if you have several other plugins that use it and want to keep all your data in SQL, or if you want to keep that data out of the file system itself for whatever reason.
Otherwise, it doesn't really make GP work better with more players.
-
View User Profile
-
Send Message
Posted Nov 18, 2013@BC_Programming
A bug found is a bug 50% resolved, right? :D
In general, do you recommend using SQL database? Concerning a large(ish)-scale server, 50+ players in rush hour?
Oh, and, I think I mentioned this, /ic doesnt give access to /trustlist, is this a real issue?
-
View User Profile
-
Send Message
Posted Nov 17, 2013@stgram
in the words of Q-bert, !@#!#@!.
Looks like the migration code is busted. I get the same results. This is a lot of fun having stuff that worked perfectly suddenly break for no obvious reason. Let me have a look see.
OK, pretty easy fix.
Basically it was migrating, but at the time it tried to migrate, no claims were loaded so nothing really got migrated. The issue was in the method that attempts to force load the claims so that they <do> get saved to the other dataStore, whereby it basically wasn't doing what it's name implied.
It appears to be fixed now, in the next dropped build it should work better.
Ideally, in terms of migration, the long-term idea is that there are going to be numerous DataStore implementations that provide the logic to save to any number of things- eg we have flat file and MySQL, but there could be dataStore's made for PostGres, SQLLite, etc. And migration should work between any two of them.
Right now it is pretty much one way still. It is using the "generic" routine so theoretically it could migrate the other way if a way to cause that to occur was added, but right now if the datastore is a database, it's set to look for the flat file data files, if the data exists it migrates it and renames the folders.
I'm also not a fan of the dataconfig itself. The goal for that is to centralize all the configs for any future datastores that are added. The downside is that the basic info for each is only really added once that datastore is used- eg. the MySQL section isn't added until you run the plugin with MySQL.
At least with incorrect settings (like the defaults) it doesn't try to migrate and doesn't rename the data folders, so it's just a case of getting the right information in. This might be the best trade-off in the long-term.
General Note: Yes I have started writing new doc pages. I plan on a core set describing the Rules and the standard Permissions, then something describing the different areas in the config as well as configs in general (eg, creating and using templates, setting singleworld mode, and whatnot)
-
View User Profile
-
Send Message
Posted Nov 17, 2013@Ricowan
Awesome! Thanks a bunch bro ^_^
-
View User Profile
-
Send Message
Posted Nov 17, 2013@BC_Programming
I meant no disrespect, your plugin is wonderful and I understand that its support is not an easy task, so keep up the good work. :)
"If you have data on the file system already, they will be migrated to the database." As for the sql problem...well, I am on flat storage with 7.8, and was wondering if SQL is better, tried to switch the storage mode, on startup it says "migrating the data to database", but it transfers absolutely nothing and thus 80 claims get lost. Well not lost, they remain in their folder. Am I doing something wrong?
-
View User Profile
-
Send Message
Posted Nov 17, 2013@knivesstryfe
Make this change in your config file: Claims.AutomaticNewPlayerClaimsRadius: -1
-
View User Profile
-
Send Message
Posted Nov 16, 2013@LeeTheENTP
Yeah thanks... that was really.... helpful. I guess i'll figure out what to manipulate by my self. Thanks for trying though.
-
View User Profile
-
Send Message
Posted Nov 16, 2013@knivesstryfe
It's in the config.
. . .
I think this got buried, but players can shear mooshrooms inside claims. I'm running 7.7, so this may have already been patched.