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 Feb 4, 2014@BC_Programming
Regarding those subdivison ID's, I noticed they get "reused". If I create a claim and create a subdivision then abandon that subdivision and create a new one, it has the same ID as the first one. That's a bit problematic for extension plugins like mine that are storing data for those subIDs, especially since the ClaimDeletedEvent doesn't seem to fire for subdivisions either as far as I can tell. EDIT: I take that back, the event not working may be my problem.
I set flags in my subdivision and then abandon the claim and the next subdivision I create already has those flags set, whether I wanted them or not. There is no way for me to tell from within my plugin that it's not the same subclaim short of tracking it's boundaries.
-
View User Profile
-
Send Message
Posted Feb 3, 2014Are there any notes somewhere about how to properly use the GriefPrevention.Rules.BreakOverrides/PlaceOverrides nodes in a world's config.yml? I did not see these nodes discussed in the 7.8 configuration document on this site.
-
View User Profile
-
Send Message
Posted Feb 3, 2014What is the update process from 7.8-beta-b197 to the lastest dev build (268). Every time i try to update i get loaded with error. I most certainly am doing something wrong. If someone could help me out or point me in the right direction this would greatly be appreciated :)
-
View User Profile
-
Send Message
Posted Feb 2, 2014@ColeWiand
Currently there is no way to "reassign" claims from one world to another. I'm not sure how difficult it would be to provide such a capability (/moveworldclaims perhaps) But I will look into it.
@MinerAccident
I appear to have been incorrect. For some reason, the CreatureDamage rule is never used internally, I'd bet I added it back when I first added rules but never actually got around to changing the current implementation (which is still hard-coded, rather than using the rule). Thanks for your investigation into this, and sorry for misleading you with my previous comment, I was sure it was being used!
Currently the hard coded logic will protect all creatures in claims from damage by players without container trust., except for villagers, which can be damaged by zombies.
I'lll try to figure out if the 'hard-coded' logic can be approximated reasonably with a rule or two.
@Turqmelon
subclaims don't have a unique ID among all claims, but they do have a getSubClaimID() method that will retrieve a 'unique ID' that is unique amongst it's subclaim siblings.
-
View User Profile
-
Send Message
Posted Feb 2, 2014@newfization Yes they do. 7.7 and 7.8 have a different location in which its disabled and enabled. But both do it well. :)
-
View User Profile
-
Send Message
Posted Feb 1, 2014I may have missed this but will this overprotect World Guard claims? Like say, the spawn is using World Guard (So it can use flags), if some random player just claims spawn with grief prevention, will it claim or will it leave it rest as a world guard protection, unless admin claim.
-
View User Profile
-
Send Message
Posted Feb 1, 2014Will this plugin lock doors, fence gates etc?
-
View User Profile
-
Send Message
Posted Feb 1, 2014Ok, ignore my assumption that it was an admin vs player claim issue. What happened is I changed the CreatureDamage claim rule from ClaimControl: RequireContainer (Default) to ClaimControl: RequireBuild and expected to see a different behavior, but I did not. I did further testing, and it looks like the problem is that it just ignores this setting. I even changed it to ClaimControl: Disabled, and I could still kill animals, the only requisite being that I had at least containertrust in the claim. So, do I need to see if this is in the reported bugs list or something? I want my players to be able to trade with villagers (containertrust) without being able to kill them (thus trying to set CreatureDamage to a higher level of trust).
-
View User Profile
-
Send Message
Posted Feb 1, 2014How do you change the name of the world? I recently changed my servers worldname from "world.zip" to "world" for compatability with another plugin, and i changed the name of the worlds in the plugin folder, but all of my players' claims have disappeared. How do I fix this?
-
View User Profile
-
Send Message
Posted Feb 1, 2014Okay, I've set it up and tested the CreatureDamage rule. It works as expected in player claims, but not in admin claims. No matter what I set the rule to, I can always damage villagers and animals in an admin claim. Anyone else seen this behavior or know how to fix it?
Thanks.
-
View User Profile
-
Send Message
Posted Jan 31, 2014guys 3 words:best plugin ever!!!!!! you are awesome Ive started a server and have been looking for a anti griefing plugin for ages and then i find this thank you!!!!
-
View User Profile
-
Send Message
Posted Jan 31, 2014Do subclaims have their own unique ID? I seem to get a NPE whenever trying to reference it. If it doesn't, adding this would be awesome. :)
-
View User Profile
-
Send Message
Posted Jan 31, 2014Is It Possible To Add A Feature That Allows Admins To Prevent Claims From Being To Close To Other Claimed Land. To Help Keep A Build Server Look More Tidy They People Claiming Side By Side. And Add A Changeable Number To This. Prevented Claimed Land In All Areas Including Diagonally.
-
View User Profile
-
Send Message
Posted Jan 31, 2014@BC_Programming
Well that makes sense! I am still in the process of setting up my server and hadn't actually tried it with a non-op account. You guys are awesome! Thanks for the reply.
-
View User Profile
-
Send Message
Posted Jan 31, 2014@anfereon
will there still be problems with claims disapearing and other bugs like claims not showing up right?
I don't know. People have the darndest issues sometimes. The PlayerData issue should be fixed though.
@MinerAccident
Monsters should always be attackable within a claim. Villagers and animals should be protected by the ProtectCreatures rule.
-
View User Profile
-
Send Message
Posted Jan 30, 2014First I want to say this is a GREAT plugin! Well done. That said, I have an issue. I want players to be able to damage 'monsters' inside claims, but not kill villagers or farm animals in those same claims. Is there a way to do this with just GP? I've looked into using Flags as well, but still can't see a way to accomplish this.
Thanks!
-
View User Profile
-
Send Message
Posted Jan 30, 2014So I wan't to stara a new server (on linux) and use latest dev build of gp, will there still be problems with claims disapearing and other bugs like claims not showing up right?
I had huge problems and many unsatisfied players because I updated to dev builds (claims and clam blocks disapearing...)
-
View User Profile
-
Send Message
Posted Jan 30, 2014Is there a way to disable making claims in a certain world guarded region?
-
View User Profile
-
Send Message
Posted Jan 30, 2014@erik1988
@damndummie
This can be done in using Flags with GriefPrevention.
-
View User Profile
-
Send Message
Posted Jan 30, 2014How you change the default claim blocks space when a new player joins the server? My players all get 0 blocks and I want them to start with 100.