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 Dec 20, 2013I'm having trouble with my server. Some of my players don't gain claim blocks with time. Others do. Is there some persmission I'm missing. I'm using latest dev-build.
-
View User Profile
-
Send Message
Posted Dec 19, 2013I already know this is a dumb question BUT! I just can't figure out what i'm doing wrong. I am adjusting /plugins/GriefPrevention/WorldConfigs/world.yml
ProtectPlayersInLandClaims: PlayerOwnedClaims: false AdministrativeClaims: false
This above is the default setting. I stop the server, change both of these to true, save file and restart the server.... it changes back to false again..... what am i doing wrong? Please help Oh Wise One!
-
View User Profile
-
Send Message
Posted Dec 19, 2013@ultra1108
I believe the "CreativeRules" setting causes this. If it is true, you must build in your own claim. I believe this part of the rules applies to survival mode too.
@BC_Programming
Ah, I see there is much more to a siege and PvP with this plugin than I previously understood. Thanks for taking the time to explain it, I believe you made the right choice regarding it. Having reviewed my configuration though, it all was coincidence to the fact that I added a new world at around the same time I updated to 206 or 213 and I missed turning siege to false on that one world's config and it was false in all the other world configs. Yet, PvP protection was getting turned off on all worlds.
-
View User Profile
-
Send Message
Posted Dec 19, 2013Hi, my players have to claim land to build in survival and creative! Can someone please tell me how to make it so my players don't have to claim land to build in survival and creative! Thank you! - Ultra
-
View User Profile
-
Send Message
Posted Dec 19, 2013@malfalas
Or you could read the existing documentation page, 7.8 and Later GriefPrevention Configuration
@Haaaaanzz
Horses are protected separate from standard creatures.
@Sargewood
If you are not performing a siege, they should still be protected from PvP with the setting if it is true.
Implementation would not be trivial. It seems reasonably simple, but it's ripe for exploitation by enterprising PvP-ers. Also, I'm not keen on having settings that magically don't apply. In this case having PVP disabled in a claim (admin or land) with siege enabled has to either disable siege or disable PVP, because sieges aren't possible. Of course it could somehow allow PVP only in the very specific circumstance that the player being attacked and the player attacking are the attacker and defender in a siege, or if they are inside a sieged claim, or any number of other special cases, but there WILL be workarounds and people WILL find a way to exploit the setting to protect players from PVP. off the top of my head, a player could make a nearby claim to the claim they want to attack. if they siege that other claim they can go back into their claim and be protected if PVP protection in a claim is on. They could then build a sniping tower and harass the player they are 'attacking', or just sit in their claim, since they would be invincible. The only way such a siege would end is by the defender killing themselves, which gives that "attacker" all their items. The alternative is to have players in sieges always allowed to be damaged, but that won't help if there are multiple players. (eg. Player sieges other player, runs to their claim. They can still take damage, but their 10 friends cannot take any damage at all since they are inside a claim and protected from PVP. So you think "ahh, easy, just make it so if a player is on a claim owned by a player who is currently an attacker in a siege, they can be damaged. Except then some other player can simply create the claim, and now the attacker is invisible again.
Basically, after considering all those problems, I decided it was best to not even try to write that special case logic because it doesn't seem like there is a easy or even difficult way to keep players from taking advantage of it to effectively cause players grief, which I think we ought to try to prevent.
-
View User Profile
-
Send Message
Posted Dec 19, 2013Please update the documentation to explain the new options and how they impact permissions, each other, etc.
-
View User Profile
-
Send Message
Posted Dec 19, 2013I have no idea why, but even though I have enabled the CreatureDamage I still can't kill people's animals in their claims. This is how it looks: <<code CreatureDamage: Wilderness: AboveSeaLevel: Allow BelowSeaLevel: Allow SeaLevel: '-1' Claims: AboveSeaLevel: Allow BelowSeaLevel: Allow SeaLevel: '-1' ClaimControl: RequireNone>>
<</code>> Kind of annoying since killing a player's horses has become a tradition.
-
View User Profile
-
Send Message
Posted Dec 19, 2013Subclaims continue to dissapear. This is a major issue. Please look into it, I will provide full support.
-
View User Profile
-
Send Message
Posted Dec 19, 2013@BC_Programming
That seems like an odd combination of settings. If you are not performing a siege, they should still be protected from PvP with the setting if it is true. You should only not be protected during the siege. If you can siege or not should not change protection in admin lands (assuming no one in their right mind would allow a siege on admin claims). Unfortunately I really don't know anything how sieges work as PvP is handled on my server without the aid of this plugin and I never had to research or try it.
I redid the configuration from scratch when I updated to 206 and used that same config for 213. However, looking at my file it clearly states that siege is enabled. I am going to blame too many hours in the config files during the push to update to 1.7.2 (all plugins not just this one) for that oversight. I'm an options guy and appreciate all the possible settings and am glad at the customization choices, but sometimes I seem to overlook stuff. I hope I didn't waste your time and thanks for the quick response.
-
View User Profile
-
Send Message
Posted Dec 19, 2013Claim protection values are set to false if Siege is enabled, I believe. There is no special logic such that players can attack or take damage while a siege is taking place, so if siege is enabled, the protection settings are set to false. At least that's the best I can determine before my laptop force-restarted for updates and I basically decided to give it a rest until some later time before I smash my laptop to pieces or something. (I could rant about forced updates for a looong time, hah)
There were originally rules for Spawn Eggs. They were removed by request... or something. I know they were one of the first rules I added, don't know where they are now.
-
View User Profile
-
Send Message
Posted Dec 19, 2013@Sargewood
I tested 213 and 214, I am now certain that GP is setting PvP claim protection back to false each time on restart. Most likely started with 205 and the changes to the config file rule ordering.
I have encountered a new issue while testing the above, using gpreload with new correct config files to turn PvP protection in claims to true causes block accrual to stop. It seems I have one issue or another with gpreload with every version I've used since 7.7, full restarts are what I need to fix things. Only this time restarting causes a problem too!
I have resolved my problems (and am now hearing less horse related complaints) now that I have reverted back to 201 despite the item frame issues. They are easier to handle then players attacking players in claims when I set the rules to be PvP off in claims. Or explaining to players why they only have 150 blocks to claim with with no chance to ever get more.
As to my issue with eggs and spawn eggs I mentioned in my last post, I see now that the rules for that is under dispensers. I suppose I just didn't read correctly. I guess then I request rules for normal eggs and spawn eggs so that I can finally be free of the rampant "egging" of player and admin claims. (I have had to adjust about 50 command blocks to no longer use @p without a range check due to chickens walking on pressure plates)
-
View User Profile
-
Send Message
Posted Dec 18, 2013@Titanaswarrior
/accesstrust public
Basically it turns off Grief Prevention door control for the claim, leaving Signshop-Hotel to do it's own thing.
-
View User Profile
-
Send Message
Posted Dec 18, 2013I'm trying to use http://dev.bukkit.org/bukkit-plugins/signshop-hotel/ SignshopHotel with GriefPrevention and I'm having some issues with GP overriding door permissions. I have an Admin area (an Inn) where I want players to be able to rent a room if they can't afford to buy land yet. How can I get SignshopHotel to sit on top of /containeraccess so in this "Inn" I have people can have private rooms.
-
View User Profile
-
Send Message
Posted Dec 18, 2013@Nentify
You can grant bonus claim blocks to a permission node, rather than just a player. So if your ranks are governed by a permission plugin, then yes.
-
View User Profile
-
Send Message
Posted Dec 18, 2013@BC_Programming
Some subclaims in admin claims are "Admin Claim", which have empty owner fields, and some are "an administrator's claim", which have "
subdivision" as owner in the SQL table. I seem to spot a serious flaw in the mechanics of subclaims. Please take a look. I've disabled the cleanup, lets see if they remain.-
View User Profile
-
Send Message
Posted Dec 18, 2013Since build #206 to #213, every time my server restarts GP world configs turn protection of players in administrative claims to false from true. I have to recopy my offsite files and /gpreload to fix it. (I updated CraftBukkit a couple of times since using GP build #206 and McMyAdmin too. I have noticed a couple of other server oddities so this may not be GP related. I thought I would mention it though, in case it was.)
I am also having issues of being unable to get the rules for eggs or spawn eggs to be enforced.
-
View User Profile
-
Send Message
Posted Dec 17, 2013Anyway to make it that GP is only active on one of my worlds? I'm using the Tardis plugin so when players create a tardis they get their own little world it's created in. I don't want GP active on ANY of those. Just the default world.
-
View User Profile
-
Send Message
Posted Dec 17, 2013Not sure if you missed my message. Is it possible to her per-rank claimblock caps? o.o
-
View User Profile
-
Send Message
Posted Dec 17, 2013@Hourn01
Item frame issues have been addressed in dev builds of both bukkit and GP. Be sure you're running the latest GP build from Jenkins (currently 213) and things should be better. Only remaining issue is "creepers blow stuff out of protected frames" which isn't as bad as what you're experiencing.
-
View User Profile
-
Send Message
Posted Dec 16, 2013@stgram
Every single time I've had a missing claim it has been due to Claim Cleanup. For example I will sometimes leave the Test server running on my laptop, then go to test again and find claims missing.
Looking at the Console output however (which I run with verbose on) every single missing claim was removed by the claim cleanup logic.