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 Oct 5, 2012@bigscary
Thanks for the update! I thought your plugin was the only one I updated. Guess not. Thank you for your time!
-
View User Profile
-
Send Message
Posted Oct 5, 2012@mspaulding86
Thanks, I must of missed that!
-
View User Profile
-
Send Message
Posted Oct 5, 2012Hey, @BigScary, I need some help. It has to do with INDIVIDUAL BLOCK permissions. I use a "slot machine" that has a "noteblock" as the switch. The only way someone can use the noteblock is if they have /trust. Can you make it so "noteblocks" work with "/accesstrust" or "/containertrust" instead?
You would really save me a lot of "GRIEF"... haha, bad pun. Or possibly add a permission node like griefprevention.usetrust.noteblock
Thanks.
@coolo1 - You can just add yourself to someone's trust list if you want. Or read this:
"Overriding
Permission: griefprevention.ignoreclaims
Any player with this permission may gain access to any non-administrative claim using the /IgnoreClaims command. Admin claims still require the adminclaims permission. Use /IgnoreClaims again to go back into "respecting claims" mode, to prevent accidental changes to others' builds."
-
View User Profile
-
Send Message
Posted Oct 4, 2012I have a problem, ops cannot do anything in protected areas, which makes this impossible to use properly. Please add a permission node to bypass protections.
-
View User Profile
-
Send Message
Posted Oct 4, 2012Is it possible to give the enchanting table its own trust group? you can't actually store stuff in it, and i might like to give a person access to my enchantment table but nothing else.
-
View User Profile
-
Send Message
Posted Oct 4, 2012@bigscary
Haha thanks, cant believe i missed that :P
-
View User Profile
-
Send Message
Posted Oct 4, 2012Hey,
I still really am happy with this plugin. Our Creative world is alot cleaner then it has ever been since i turned creative world mode on :) This plugin is amazing however, i am running into an issue with the automatic restorenature feature. Whenever i remove a claim that has nothing in it, in our creative world, for some reason it spawns a huge block of stone and grass in the sky? am i doing something wrong? >.< (im still secretly hoping you can somehow make a switch to disable this entire feature cus its not really wanted... i dont like things to be done to the world which i cannot rollback its the only bad thing in your furthermore fantastic peace of code please provide a feature to disable this! youd make my day xD
-
View User Profile
-
Send Message
Posted Oct 4, 2012@bigscary
Thanks, hopefully I don't have such an experience again but it would probably be helpful to all who do. A lot of peoples houses burned down. Luckily I was able to roll it all back with my trusty logging plugin so no harm done =)
-
View User Profile
-
Send Message
Posted Oct 4, 2012Nice plugin, however, what I'm working on currently is not what is posted on that page, sorry about that, I'm adding a documentator later.
-
View User Profile
-
Send Message
Posted Oct 4, 2012Join my server :D heres the ip 216.108.185.254:25565
-
View User Profile
-
Send Message
Posted Oct 4, 2012hey, is it possible to get restorenaturefill to work through/under water, i have some pretty ugly shore lines due to admins copying and pasting areas, and i want to tidy them up a bit.
also a customisable time/block place between building outside of a claim warnings,
i find it causing a lot of spam when i am purposely building outside of a claim
-
View User Profile
-
Send Message
Posted Oct 4, 2012I could stick my neck out here and say you'd be stupid to run a bukkit server without Grief Prevention... but I wouldn't be sticking my neck out because you really would be stupid to run a bukkit server without Grief Prevention. :D
@FordRacer2007
Are you running any other plugins that may be controlling the spread of fire? Or is there a config option anywhere that says fire can spread? I've been using GP for many months and I haven't had a problem with fire what-so-ever. The upgrade from 6.5.1 to 6.6 was as smooth as ever for me and it killed a few demons. (not daemons - LOL!)
-
View User Profile
-
Send Message
Posted Oct 4, 2012@bigscary
Sorry, let me start over, I think you misunderstood me. I'm using the latest version of your GP plugin and ever since I updated to 6.6 from 6.5.1 fire has been spreading even though the feature is disabled in the configuration.
-
View User Profile
-
Send Message
Posted Oct 4, 2012@mdcollins05
That's not my plugin doing that. Maybe you also updated something else lately?
@diannetea
Actually I'm already propping-up sand to a large extent, it was much worse before (I'm assuming you're using one of the later versions?). I don't think it's possible to perfect this, because I also want to avoid putting sandstone up in the air when players have built big sand constructions, which may make the problem worse rather than better. In general, sand is very difficult to deal with because it's a natural block, which means I have to try and determine based on nearby blocks whether it's in a natural formation or likely placed by players.
For floating islands, use /rna.
I could make the /rn brush size adjustable, but it would be a lot of work for me to save only a few user clicks, and it may surprise you to hear that I get more complaints that the brush is too big rather than too small.
Ignoring water isn't in the cards. Unfortunately, water is the most popular griefing tool. :\ Waterfalls are usually started with one source block, so they're easy to replace. I understand your complaint about the above-sea-level ponds, but it's impossible for me to separate world generated ponds from player-built messes. Fortunately, most world generated water formations are at sea level (oceans, big lakes, and streams).
Use /rna to remove floating grass and ores when they're problematic. Basic /rn doesn't remove those because I don't want to throw out blocks which are most likely world generated (players place them only very rarely).
Sometimes this will happen when you have a desert biome next to a field biome, for example, and I've noticed it myself. I think it would be very complicated to fix, and the result wouldn't be as nice as you'd like. I'll think on it, though. :)
@zSwayz
Permissions node are in the admin details page. You could turn off the "place water only inside land claims" option, but that will cost you performance. If a player can't abandon his own claim, then update to the latest version and set the config option to allow players to resize their creative mode claims. If you mean deleting another player's claim, that node is documented in the admin details page.
@FordRacer2007
If you're not on a Tekkit server, don't downgrade to 5.5.1. Is fire spreading on its own, or only from lava? You should expected lava to catch nearby blocks on fire, but that fire shouldn't spread further. If you can determine the original source of the fire and post a screenshot, it might help me understand what's happening.
Did you change anything about other plugins lately? Maybe you updated another plugin, or changed configuration for another plugin?
@bman01
Use /RestoreNature to remove his builds. See the admin details page for a video on how /restorenature works. If you want to be very thorough, you can use /claimslist to get coordinates for all his land claims so you can see what he built at each location. Otherwise, /deleteallclaims will remove all of his claims without you having to visit each.
As long as the neighbors have their builds correctly claimed, /restorenature will not change any of their blocks.
@Draylynn
There was a related bug in the last version, be sure you're on the latest. Also be sure you're not actually putting xxx in the config file (just making sure, no offense intended), you need to put the actual number of blocks players should get per hour. Players get blocks every 5 minutes or so, and only when they're moving around.
@ryvix
Hmm, sorry the error message wasn't more helpful. I'll see if I can make that experience a little better.
-
View User Profile
-
Send Message
Posted Oct 4, 2012Somethings definitely wrong somewhere. I am using MySQL and in the latest version a few things went a bit wonky. Now on startup I get these messages:
http://pastebin.com/1WqadFfk
I never changed the config and I can access my database just fine. GP just suddenly doesn't seem to be working for no particular reason.
EDIT: Alright, what's happened is I deleted a world and it still had an admin claim in it.
-
View User Profile
-
Send Message
Posted Oct 4, 2012BlocksAccruedPerHour: xxx
Having issues actually getting this function to work on GriefPrevention, no one on my server is seeing any increase in blocks over time, any ideas why?
-
View User Profile
-
Send Message
Posted Oct 4, 2012Nice work on this plugin and thanks for taking your own time to do this for everyone. I have a question / request. On my survival map I have banned my first player (yes pretty new at this) and I have all his claims all over the place. I see the deleteclaims will remove his claim, but will it remove the blocks he put there? Some of the buildings were offensive and I keep getting requests to remove his work. If deleteclaims leaves his blocks for everyone else is it possible to do a deleteclaimsrestorenature sort of command? Some of his work is jammed up against other user's claims so it would have to just stay exactly within their claim locations.
Thoughts on this? Thanks again for your help with question and for the awesome plugin.
-
View User Profile
-
Send Message
Posted Oct 4, 2012@bigscary
What do you mean get GP 5.5.1? Do you mean 6.5.1? And if so, Why should I downgrade? Oh and I'm not on a Tekkit server. The plugin was fine until I updated to latest version.
-
View User Profile
-
Send Message
Posted Oct 3, 2012Hey, i cant seem to find the permission nodes anywhere for this, and i would like some of my player to have the ability to bypass placing water, and have the ability to abandon claims.
-
View User Profile
-
Send Message
Posted Oct 3, 2012I just would like to request a few changes/fixes to restore nature
The problems I have come across so far are:
1. If there is something like a flower on top of a block it ignores it.
2. Sand. Sand sand. Sand falls when you use RN, making the mess much worse. Is there a way it could check for vacant blocks below the sand and replace them with a layer of sandstone to prevent them from falling?
3. Bigger scale cleanups - I would like the option to restore say, 4 chunks at a time instead of one.
4. Floating islands. Is there a way to perhaps check the height of the block to determine whether or not it should be floating? Combined with 3 it would make screwy world gen easier to clean.
5. Water!! I would like an option to ignore water, this has a tendency to remove natural waterfalls and ponds. I don't like that. Honestly I'd be okay with it leaving lava falls too. Toggleable would probably be best though if this were implemented.
6. Ores. Ugh. Ugly ores stick out when you RN some of those nasty world gen scrapes. Could it check for any ores on the surface and replace with the appropriate grass/sand/whatnot?
7. Biome smoothing. I don't know how possible this is, but I've come across a few spots between biomes where RN will leave sand in one chunk but then fill the one next to it with grass. Very jarring.
I think that's all...