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 Mar 28, 2014Finally figured it!
Large pull request submitted.
-
View User Profile
-
Send Message
Posted Mar 28, 2014I want majority of my players to have a limited ammount of claime blocks they can build up to unless they buy permission to be able to buyclaimblocks but it appears that buyclaimblocks does not go above the max set
-
View User Profile
-
Send Message
Posted Mar 28, 2014When i was trying to test my creative world for anti-grief i bumped into something:
TNT Carts still do explode even when TNT is disabled.
-
View User Profile
-
Send Message
Posted Mar 28, 2014I really appreciate this plugin and find it very useful, the only issues I have are that many things are disabled by default. For example, villager trading and creating iron golems are all disabled in the wilderness. Why would any of that be considered griefing?
-
View User Profile
-
Send Message
Posted Mar 28, 2014@3sM
Oh man, IntelliJ is soooooo much better for Github and Maven. Though if your accustomed to eclipse, you have to do just a little configuration to get things you will miss and aren't on by default (like Javadocs popups).
-
View User Profile
-
Send Message
Posted Mar 28, 2014I'll look into how I can do this after work. Currently using eclipse to make my changes....so gotta figure out that extra layer of complexity!
-
View User Profile
-
Send Message
Posted Mar 28, 2014@3sM
It might be, I did not check all directions. If you can rebase, go ahead and send in your pull.
-
View User Profile
-
Send Message
Posted Mar 28, 2014OK I get why you only changed that. I was being selfish and making changes I wanted.
Wrt making sure it works...did u test dispensing south into other claims...the vector clacs for me seemed to evaluate southern movement as northern movement thus checking the wrong block for claim data.
-
View User Profile
-
Send Message
Posted Mar 28, 2014@3sM
Not sure what happened to the maven encoding, it was in there before. Looks like the vau;lt repo is wrong too, it's pointing at WorldGuard's repo.
-
View User Profile
-
Send Message
Posted Mar 28, 2014@3sM
It is possible there was more than one bug. My changes purposely did not change dispensing from a claim to the wilderness because I wasn't sure that was what it was supposed to do. It's pretty obvious it shouldn't let you dispense into the claim, but is that a grief putting lava in the wilderness?
To fix your pull request, stash your changes and rebase from the master. Or if you haven't made a lot of changes, you can rebase and just re-do the changes rather than doing the Stash.
https://blogs.atlassian.com/2013/07/git-upstreams-forks/
-
View User Profile
-
Send Message
Posted Mar 28, 2014Try dispensing south on a claim edge.
See what happens
Also I'd really reccomend adding some encoding to stop pissing off everyone on Linux Lol.
Oh BTW I'm smc87 but my phone seems to have its own account!
-
View User Profile
-
Send Message
Posted Mar 28, 2014Bah! You beat me.
Haaha
Good to see a new build though...wish I could figure out github so I could make pull requests.
Also are you sure what you did fixed it? Did u test in every direction. North east south west? My tests showed that the vector calculations were wrong and I had to rewrite all of that. Its wasn't just the logic.
Also what about claim to no claim and claim to claim but if claim owner is the same etc.
-
View User Profile
-
Send Message
Posted Mar 27, 2014@smc87
Oh I like the local repo, I didn't know you could do that. I'm afraid the old way was my doing, I'm not super experienced with Maven. I'll have to steal that idea for Flags.
As for the water/lava issue, if this is the issue of being able to create an adjacent claim and dispense water into another claim, it's been fixed and pulled.
-
View User Profile
-
Send Message
Posted Mar 27, 2014I wish i was better at github :(
ive fixed the lava/water dispensers problem...although i may have broken some config options for dispensing potions etc.... i also think i've fixed the issue with case sensitivity on linux by setting some encoding in the POM file. The negative claims issue was a BIG problem for me!
I cant send a pull request though as i've managed to do something on git that prevents me from doing so :/
Also i restructured the dependencies completely so the is a local repo now, instead of referencing external jars.
If anyone wants to test my build, or has any idea how i can push the changes back into GP let me know.
Sorry for being rubbish at gitHub! :(
-
View User Profile
-
Send Message
Posted Mar 27, 2014@GodsDead
I'm not abandoning it, that's for sure :P but I'm useless at programming (I can manage Python and bash scripting :P ) I'll try to get back to tickets and assign them to whoever they need to go to.
@lucasbuck2
I'm afraid that's not entirely possible - You can specify individual worlds to require claims, but not specific areas.
@Tigergruppe
There's a section in each WorldConfig where you can set the thresholds.
@zombiex227
This sounds like either the WorldConfigs section is set up incorrectly, another plugin is interfering with the block breaking method, or you're running a modded server. Post a ticket with more information.
@Smac3223
I'm afraid we're all human beings here :/ I try to do my part, and while this plugin has not been receiving updates for a while, I hope that someone will be able to pick it up again. I personally have not found updating to be an issue like this - do claim blocks get set like this on each playerfile or is it the "duplicate claims" bug that's been around? Ask users to relog and try again, is all I can say.
-
View User Profile
-
Send Message
Posted Mar 27, 2014@GodsDead
Well I know BC mentioned he had a new job (you know, one that actually pays), so he may just not have the time right now. I sent in a pull request for one of your tickets.
-
View User Profile
-
Send Message
Posted Mar 27, 2014I have reported a few bugs in the tickets section, I can see this is a dry spell for development, no recent releases, I hope this plugin hasn't been abandoned!
-
View User Profile
-
Send Message
Posted Mar 27, 2014Although I'm only a moderator on a server, I was wondering.
Is there any way to make a public claim but DENY certain players from it.. On the server I play on, we have a public sheep/cow/pig farm (actually its another players claim made 'public' & we have rules put in place to say 'Breed the mobs and only kill the same amount of grownups as babies born'
Some players, regardless of warnings, kicks etc (I don't like banning) keep 'forgetting'.
I'd like to prevent those players from killing the mobs but still allow the other players access. Only way I can see is to un-PUBLICize the farms & only add all the other players.. but that's a LOT of players to add.. easier to have 'public' and Deny just those players as punishment
-
View User Profile
-
Send Message
Posted Mar 27, 2014Does anyone know, is it possible to setup and area (like a town) where people cannot build UNLESS the claim land. Like, will GP override worldguard build deny? I'd like to have my town area set to not build anywhere unless you claim it. But haven't figured out a way yet. Thanks for any information!
-
View User Profile
-
Send Message
Posted Mar 26, 2014Is there a way to edit the threshhold for automatic chat spam banning? I ask because a few of my users are experiencing issues in regards to posting one message....saying several other things, then posting the same message again minutes later and then receiving an autoban.