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 Aug 20, 2013In the dev builds, where in the config is the setting to protect animals in claims?
-
View User Profile
-
Send Message
Posted Aug 20, 2013@BC_Programming
oh, my bad.. i thought plugin.yml was up-to-date ;-)
Also: What is the difference between /giveclaim and /transferclaim?
(in my experience /giveclaim doesn't always seem to work whereas /transferclaim does)
-
View User Profile
-
Send Message
Posted Aug 20, 2013@ThisUsernameIsMine
GriefPrevention.adminclaims is the previous perm.
It is now "griefprevention.admin.claims"
-
View User Profile
-
Send Message
Posted Aug 20, 2013Is it possible to disable teleports to claims? If not could it be a future feature? I've had issues with players setting homes in others claims and pestering them because of the PvP protection.
Also, spawn eggs and throwing egg hits aren't disabled in claims.
-
View User Profile
-
Send Message
Posted Aug 20, 2013@BC_Programming
I still experience problems with GP build 157:
Despite having the nodes griefprevention.adminclaims and griefprevention.ignoreclaims, Grief Prevention still tells me i don't have permission =/
(using bPermissions 2.10.7 and Vault 1.2.26)
-
View User Profile
-
Send Message
Posted Aug 20, 2013@LeeTheENTP
The Explosions are enabled but the Block damage is not. This is so Creepers exploding don't do nothing to players, since that sorta makes Creepers rather non-threatening.
Firespread and Firedestroys will probably be replaces with some rules; eg FireSpreadSource and FireSpreadTarget behaviours, referring to the place the fire is and the place the fire is trying to spread respectively. Currently, Firespread and firedestroys are both false by default.
Re: multiple worlds, You can create a "template" file, by changing a single world config and renaming it to "_template.cfg". You can change the specific template file in the config.yml.
You can also enable a "singleconfiguration" mode where it will use the same "world" configuration for any world, by changing GriefPrevention.World.SingleWorld to the name of the "world" configuration you want to use for all worlds.
@BryanChung
"Plugin GriefPrevention v7.7"
7.8 and the latest dev builds have included changes that cover nearly every facet of GriefPrevention including numerous bugfixes. Whether the specific issue you had is one of them, I couldn't say. I do know that Tux2 issued a fix to 7.7 without changing the version number shortly after it was released, with the message "fixed ArrayIndexOutOfBoundsException" which may be related to the problem you had.
@RustyDagger
you need adminclaims permission to deal with admin claims.
-
View User Profile
-
Send Message
Posted Aug 19, 2013@LeeTheENTP
If you look more closely at the config you would notice that the explosions are enabled but the block damage is NOT. Its really not that hard to copy / paste the config either.
Onto why im here to post.
i am using build 150 atm ( not yet upgraded due to chat message issue's ) it seems that as an admin with the admin node i now have to ignoreclaims to edit an admins claim so I now have to ignore claims to edit my own claim Da fuck? ignoreclaims needs to be renamed at this point its more like ClaimGod mode or edit mode. its not really ignoring them its ignoring any and all permission requirement. I honestly think that having to have ignoreclaims enabled to change any thing on an admin claim is utterly stupid annoying and frustrating.
One more thing in build 150 siege block revert does NOTHING it allows drops and does not restore. That really sucks its a cool feature.
-
View User Profile
-
Send Message
Posted Aug 19, 2013After a month past, is there a fix for this yet?
-
View User Profile
-
Send Message
Posted Aug 19, 2013Chicken eggs aren't blocked by the anti PvP inside claims and it would be nice is spawn eggs were too. I have issues on my server with players abusing them to bypass Anti PvP.
-
View User Profile
-
Send Message
Posted Aug 19, 2013@BC_Programming
Will we still be able to have a server-wide configuration? I tried out 7.8 and I think it's annoying to have a separate config for each world, and I find that the new defaults for those configs don't really keep to the heart of Grief Prevention. Above-ground explosions and firespread are now enabled by default? D: I needed to go through each config, find that, and disable it. I like the better control but it's too monotonous even for me.
-
View User Profile
-
Send Message
Posted Aug 19, 2013@maski
There is currently no simple way to transform GriefPrevention Claims to WorldGuard regions or vice versa.
Fundamentally I think that would be ideal as a separate plugin. Not because it doesn't fit- it would be a useful feature, but rather because it would mean either GP referencing WorldGuard, or WorldGuard referencing GP. Neither of those is really super ideal. I could see perhaps a 'soft' dependency being made on WG for this purpose, but then that's extra stuff that would only really have a transitive purpose.
Even so, it sounds like it might be very useful, despite the protestations by both myself and other GP devs previously. As long as GP still works <without> WorldGuard and there aren't any problems it might be something we could look into.
@oppositeZERO
Actually, this is already implemented in the latest dev build- before you get too excited about it though, I've not yet gotten around to properly testing it or documenting it yet. iirc it even includes the distance from a claim feature. I think it's only implemented for Items (purpose being originally to try to deal with Mining Lasers and stuff)
I've been trying to figure out the best way to add Block-specific controls, but would ideally make sure the current Item stuff works too :P
-
View User Profile
-
Send Message
Posted Aug 19, 2013@maski
Thanks for showing your interest in Grief Prevention. I'm no coder of it, but I know it like the back of my hand.
Grief Prevention gives players a claim block allowance. New players spawn with the ability to claim 100 blocks, 81 of which are taken to create a 9x9 area around the first chest they place. Each hour players receive an additional 100 claim blocks, given in small increments every few minutes. So, player claims are limited by both time and size. The more a player plays on the server, the more room they'll need, and Grief Prevention provides it. You can also let people buy/sell claim blocks if you have an economy plugin like Essentials, iConomy, BOSEconomy, etc. All of this is configurable if you feel the need to change it.
There is no way to transform Grief Prevention claims to WorldGuard claims or vice versa, but this probably won't be an issue as this plugin is so widely used that even if the current maintainers do drop it, someone will want to keep it going. Bigscary, the original coder, had to move on and left it in the capable hands of the current coders/maintainers.
-
View User Profile
-
Send Message
Posted Aug 19, 2013Not sure how feasible this is, but I have a possibly feature request.
This is mainly aimed at server running mod packs such as Feed the Beast.
It would be great if there would be a way to block users either placing certain blocks , right and right and left clicking with certain items, within a configurable radius from a claim.
For example this is how it might work.
Say you don't want land marks placed around a claim, you could set in a config the item id and the radius you want it block for, and the same could go for right/left clicking items, as you could set it to their respective ranges.
Someone has already made something similar. here but although it somewhat works (A few things don't) it would be great to see something similar implemented into grief prevention.
-
View User Profile
-
Send Message
Posted Aug 19, 2013Hi all! First of all, this is a great plugin, but I have a problem.
In my server we offer free lands up to 25x25 blocks definited with WG. We let users to change their claim (if they want, obviously) twice a month. My question is: I haven't found any way to limit claims by time instead of block size, is there any manner to limit it by time?
I'm thinking in using this plugin instead of making WorldGuard protections, but if this plugin becomes inactive, is there a way to "transform" lands from this plugin to WorldGuard protections?
Thanks in advance.
-
View User Profile
-
Send Message
Posted Aug 19, 2013How does prevent lighter / set fire work at version 7.7 vs. latest beta?? In 7.7 i cannot control it. Players can use the lighter all the time, and anywhere.
-
View User Profile
-
Send Message
Posted Aug 18, 2013I really like this but i need some way to see who can do what in a claim. Is there any way to do this already and i am just missing it?
EDIT: Nevermind, i found it, it is /trustlist
-
View User Profile
-
Send Message
Posted Aug 18, 2013@2coolforu22
If you (or perhaps somebody else, if they are having the same problem) doesn't start actually describing the problem in some detail, I'm going to start deleting these informationless and unactionable comments.
-
View User Profile
-
Send Message
Posted Aug 18, 2013It also adds optional configuration elements to each Rule that allows for overriding of permissions for Attackers and Defenders during a Siege, as well as for players still in PVP combat.
Additional Permission node granularity will likely be added. Non-command permissions may be changed and added to only apply to features that are not command-related (whereas they currently are checked for some commands as well).
-
View User Profile
-
Send Message
Posted Aug 18, 2013Does anybody know how to fix the claims randomly disappearing Build #155 ?
-
View User Profile
-
Send Message
Posted Aug 18, 2013@RiviakEnderman
Well i've tried dev build 156 and opened the jar's plugin.yml to see what the permission nodes were like. I added them to our groups but they didn't have permission to do anything.
It must either be something i've overlooked (changing settings in config.yml) or its something they still have to change/fix in a later build (build 155 still works best for me).
The changes of build 156 are as followed:
- changed permissions, added set of permissions specific to each command.