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 13, 2013I have GP and a lot of claims (that belong to more than 100 different players) in nether on my server. I would like to remove all claims in nether and also disable GP so no new claims could be made in it. I can disable GP for world-nether in config, but claims still remain there. Is there a way to remove all those claims?
-
View User Profile
-
Send Message
Posted Aug 13, 2013@BC_Programming
That makes a lot of sense to me. Thanks! :-)
-
View User Profile
-
Send Message
Posted Aug 13, 2013@Cattasraafe
This is due to the fact that if someone had access to edit in a claim they could easily destroy the and get take all the items anyway. The trust permissions inheritage each other, so trust inheritage chesttrust, and chesttrust inheritage accesstrust.
-
View User Profile
-
Send Message
Posted Aug 13, 2013Hello!!!!!! you awesome people and Thank you for this fantastic plugin. I have a question for you. Recently some of my server members were actually griefed in a way. They were letting someone help them build and forgot to remove the trust later on, so that "trusted" player stole a few things form the chests of the person he was helping. So at the moment I am using LWC to cover that little issue, but I was wondering am I over looking something or is there not yet a way to give someone trust to build and them not access containers at the same time? All I can see reguarding containers is trust to use chests but not actually edit in the claim. Hope this makes sense :-). Thanks again for the awesome plugin.
(edit) One other thing also how do I deny a permissions group access to the /trapped command. I've had a couple of people log in and just /trapped to get out of my spawn room. Can't say it is a bad thing though when they get pissed and leave because they can't promote themselves in the spawn room lol.
-
View User Profile
-
Send Message
Posted Aug 12, 2013@BC_Programming
Thanks for clearing that up. I suspected something along those lines after reviewing the errors in the log file.
The permission that stopped working was that I no longer have build privileges in admin claims, but I was able to use the ignoreclaims command to work around that. The trend I've noticed that seems to work well with permissions is to have them grouped, so that pluginname.player and pluginname.admin give the standard sets, with finer grained control available with the specific nodes for those that need them.
Thanks again and keep up the good work!
-
View User Profile
-
Send Message
Posted Aug 12, 2013@hovercatz
The player data is used primarily for spam protection and for claim cleanup by tracking last login times.
@timsavage
Yes. a field was made private and needs to be accessed with an accessor now. This was actually changed a few builds previously. This is primarily a result of GriefPreventions original "API" really just being a result of everything being made public.
GriefPrevention.TransferClaim requires griefprevention.transferclaims permission. The reason this isn't documented anywhere is the same reason half of the changes in the dev build aren't documented anywhere, and is pretty much why there hasn't been a beta release.
As a side note, I'm trying to redo permissions anyway. ALL commands will require GriefPrevention.Commands.<command> permission to use, in addition to any applicable other permission; eg. the trust command will require both GriefPrevention.Claims permission as well as GriefPrevention.Commands.Trust. They will default to reasonable values (ideally). Existing permissions will be restructured to better allow for the addition of new ones in a heirachal setup; eg. GriefPrevention.claims.create, GriefPrevention.claims.ignore, GriefPrevention.claims.delete, etc.
-
View User Profile
-
Send Message
Posted Aug 12, 2013@timsavage
About permissions: My Supervisor group has the nodes griefprevention.adminclaims and griefprevention.adjustclaimblocks, but if they want to transfer a claim using /transferclaim a message tells them they don't have permission to perform the command =/
-
View User Profile
-
Send Message
Posted Aug 12, 2013I want to thank the dev of this plugin SO much right now! While I was on, some guy with a major spambot attacked my server with 816 alt accounts. (freeze0n) Either way this plugin took care of ALL of them.
2013-08-10 18:08:20 [INFO] [GriefPrevention] Auto-banned CallicoBanks because that account is using an IP address very recently used by banned player Drypod (/24.119.92.204).
2013-08-10 18:08:23 [INFO] [GriefPrevention] Auto-banned batista2045 because that account is using an IP address very recently used by banned player Drypod (/24.119.92.204).
2013-08-10 18:08:27 [INFO] [GriefPrevention] Auto-banned awesomees because that account is using an IP address very recently used by banned player Drypod (/24.119.92.204).
2013-08-10 18:08:33 [INFO] [GriefPrevention] Auto-banned hoops9 because that account is using an IP address very recently used by banned player Drypod (/24.119.92.204).
So forth
-
View User Profile
-
Send Message
Posted Aug 12, 2013suggestion: just like there is a warning on /abandonclaim , can you also add a warning on /abandonallclaims
-
View User Profile
-
Send Message
Posted Aug 12, 2013The latest dev build (155) seems to have broken the Real Estate plugin. Also, have the permissions strings changed? I no longer have administrator privileges.
-
View User Profile
-
Send Message
Posted Aug 12, 2013@alfun5432
Yes sir, it does
-
View User Profile
-
Send Message
Posted Aug 12, 2013Hey. Please remove the code where the plugin creates a new file for every new player, even if they dont protect anything. We got a spambot attack, and its taking forever to delete all of the user files. Essentials only had 45% of the files.
-
View User Profile
-
Send Message
Posted Aug 11, 2013Did anyone test if this works with 1.6.2 ?
-
View User Profile
-
Send Message
Posted Aug 11, 2013Hi,
How/where di i find out how to change how many blocks each rank (PEX) can protect? And, how do i enable buying/selling claim blocks?
Thanks!
-
View User Profile
-
Send Message
Posted Aug 10, 2013@RustyDagger
Yes, you're right. That's wrong. The default is:
this.addDefault(defaults, Messages.ResizeNeedMoreBlocks, "You don't have enough blocks for this size. You need {0} more.", "0: how many needed");
Messages.yml entries are not recreated in newer builds. If the entry is already in messages.yml it overrides any changes to the defaults; so if you were to have a message entry generated erroneously in a one-off build, unless you delete messages.yml you may erroneously continue to report the problem.
@Dynamite_Dez
I believe that is how it works; it would disable PvP within all claims between any two players. I am not 100% on this but it certainly appears to be the way it functions.
-
View User Profile
-
Send Message
Posted Aug 10, 2013Hi, I have a question:
In the config theres an option under PvP, protect players in land claims. Does this protect the claim owner from PvP only or anybody trusted to the claim aswell or any player in that claim?
I started using GP flags to stop players from pvping in claims, but if GP does this anyway I can remove this plugin.
Any help would be appreciated :)
-
View User Profile
-
Send Message
Posted Aug 9, 2013@Eelviny
my worlds.yml did not reset they had some bits added to them tho. I fear that downgrading from 154 to 150 Is going to leave my config broken :(
@einer2002
No it don't Why Would it? plotme is its own protection system and world gen. why on earth would you have GP and that running on the same map...
Feature Request:
Could we please have another Option for claim Control in the rules Called Siege. So that we can only enable TNT damage inside claims During a Siege.
Bug report:
In build 150 and higher ( maybe even lower )
In the messages.yml This message is Wrong.
It in fact should be something along the lines of:
I worked out this was the error because the message in chat was confusing and every time I moved the point the minimum would change. The changed message makes a lot more sense to me and is correct.
-
View User Profile
-
Send Message
Posted Aug 9, 2013GREAT PLUGIN! 1 problem... Needs Compatibility With PlotMe
-
View User Profile
-
Send Message
Posted Aug 9, 2013@ljprevo
I came to report this very issue, ie: people can't mount their horses inside a claim they do not own. I also believe that people are prevented from untying a horse inside other claims; this has been a problem in my town when people tie their horse to a lamp post which is protected by an admin claim. I was planning to experiment with the different trust permissions, to see if I can fix this by granting public trust in my admin claims that are roads and have lamp posts along them. But mounting inside other people's claims is a serious issue that players are having.I am unable to reproduce this behavior. I will investigate issue and report back. Running dev build 150.
-
View User Profile
-
Send Message
Posted Aug 9, 2013Tested 154, the config file generates correctly, but that error spam really does fill the logs. The plugin still functions, but the world.ymls reset.