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 4, 2012@bigscary
got a 1.3.1 dev for grief prevention? :3
-
View User Profile
-
Send Message
Posted Aug 4, 2012@Rawker its worldguard
-
View User Profile
-
Send Message
Posted Aug 4, 2012@bigscary
if you nee help with the data values take a look at this XD
http://pastebin.com/Rdv9M1vL
this shows many ways to grab that extra number as i like to call it some for items like health of an item and some for block ids like 14:1 i hope this helps works grate on tekkit and im sure you would get many people that would donate to you that run tekkit servers (getting very popular)
-
View User Profile
-
Send Message
Posted Aug 4, 2012@Sinistralis777
i was gona hook in to his plugin again to solve this issue but im shure he will get around to it if not ill probly hook in to the plugin (or if easier decompile the plugin) and just add the proper function to grab on to the data values :D i run a tekkit server and have made a banning plugin that any tekkit server would die for LOL but its nto for public use XD but i might add it to this plugin im very busy but if you would like it hit me up some time :D i need the money XD
-
View User Profile
-
Send Message
Posted Aug 3, 2012@bigscary
Essentials does it with a comma, but I commonly see it with a semicolon as well. For example, there are 16 types of wool. White Wool is 35, and then it goes 35:1, 35:2, 35:3, etc.
This is called metadata. I believe it uses the damage value field IIRC.
Blocking commands during pvp. Do it. (I'll throw money your way if you show me a donate button and make this happen. Just got my paycheck ;D)
-
View User Profile
-
Send Message
Posted Aug 3, 2012@bigscary
yeah, scenario: 2 players find a chest, the fight no one can get in the chests, and at spawn when the grace periods ends, we all pvp but now we cant access chests to "hit and run" ;)
-
View User Profile
-
Send Message
Posted Aug 3, 2012I'm always trying to tell people not to use dev builds because they're risky. This bug in particular will open your server to grief if you run the current dev build:
https://bukkit.atlassian.net/browse/BUKKIT-2002
See also this bug, which is less severe, but serves to illustrate that dev builds are NOT to be trusted with your live servers:
https://bukkit.atlassian.net/browse/BUKKIT-1999
Only plugin developers who are running code on temporary (test) servers should use the dev builds. Please do not put your players' builds at risk by running on a dev build!
-
View User Profile
-
Send Message
Posted Aug 3, 2012@bigscary
It's what I normally do, but I'm running tekkit: CONSOLE: [INFO] Reload not allowed on a forge bukkit server.
Plugin works great with Tekkit btw, just 2 blocks so far I can't protect with your plugin. It's because parts of the mod doesn't go through bukkit or something.
-
View User Profile
-
Send Message
Posted Aug 3, 2012@Rawker31994
The default is now stick. If you don't like that, you can configure it in your config.yml. I recommend against using a dev build on a live server. Dev builds are usually full of bugs, and who knows how badly those bugs could interfere with anti grief.
@08havoc
I may go ahead and separate creeper from other types of explosions. Let me see what I can do.
@roggbart
Just /reload.
@Sinistralis777
I will see what I can do about this, but I'm not familiar with the format. Does 35:3 mean material ID 35 with data value 3?
@Lostwave
Wow, I have never heard of this before. I will look into the code to see if I can guess why something like this would happen. Are you running any other plugins? Is it possible one of those plugins might be doing something "odd" which allows players to break blocks by setting them to air instead of sending along a block break event? Do you remember if you had this problem with 3.4? That may help me narrow my code search.
Also, just in case - could you share a pastebin of your 5.5.1 config file?
-For the curious, my plan is to wait for the first beta build, then do a quick test of the most important features (anti grief for claimed areas) before releasing a version for you all to use. I have no reasons to expect that there will be a problem, but because even beta builds of bukkit can have serious bugs (it's unlikely, but it has happened before), I recommend that you back up all your server data (not via plugins! zip your files and store them, and/or backup your database content). This way if there is a Mojang or CraftBukkit bug which prevents grief prevention from doing its job, you will have insurance. If your server is hosted, your hosting provider probably has a process by which you can have them zip your files for easy download, so you can look into that now.
The first 1.3-compatible release of GP will include a minor bug fix (details witheld until later, sorry), and a new optional feature which will warn players when they're placing non-trash blocks in an unclaimed area. More details on that feature will come with the release.
-
View User Profile
-
Send Message
Posted Aug 3, 2012Hey all. I haven't upgraded for a long time because I seem to keep having an issue with new builds. The last build that worked correctly for me is 3.3 and I have been running that for a long time. I tried to read the forum posts, but there are just too many for me to read through.
Here is my problem. When I run a new build of GP users can break in any claim. It still gives the error message that You don't have xxx's permission to build here, but the block breaks. They however cannot build in the claim and also get the correct message.
Anyone have any idea why people can break blocks anywhere?
Thanks.
-
View User Profile
-
Send Message
Posted Aug 3, 2012@bigscary
It plays by bukkit rules, the mod isn't the issue. Your config isnt accepting metadata values like 35.1/35:1/35;1/35,1. None of these variations work so either you use a different syntax for metadata for it just doesn't support it.
The main metadata items in vanilla are Potions and Wool, obviously. In Tekkit however, MANY items conserve ID space by having metadata values assigned.
I can protect everything for a short time before the ID is casted back to a whole number except Computers (I'm not sure wtf Computers are classified as. They aren't a container though like everything else. Maybe access?).
Eitherway, the config file keeps changing values like 35.3 into 35, which is causing a lot of issues banning specific items.
Also, you really should extend the combat pvp thing to block specified commands as well.
-
View User Profile
-
Send Message
Posted Aug 2, 2012Any command to reload the plugin config?
-
View User Profile
-
Send Message
Posted Aug 2, 2012@bigscary
BlockSurfaceExplosions: true
Allows for creeper explosions also. We don't need/want this - Just TNT explosions.
Mods.BlockIdsExplodable: [7, 8, 9]
This may work.
-
View User Profile
-
Send Message
Posted Aug 2, 2012Currently usiung a dev. build of latest 1.3 craftbukkit. Ran into conflict when using string, not sure if its with worldguard or this plugin but I casnnot use strings for tripwires because of strings use for checking claims, anyway we could change the item for claim checking?
-
View User Profile
-
Send Message
Posted Aug 2, 2012@Sinistralis777
I don't quite understand what you're asking for. You want to put a specific player into ignore claims mode? If so, then the way to do that is in your config file. Just list the player's name in the "always ignores claims" list under mod settings.
I'm totally at a loss to what you mean by number of blocks. Ignore claims is either on or off, there's no number associated with that functionality.
@DrFusion
No, many of the pvp functions are server wide. But remember, it's on a timeout - after the 15 seconds are up (or shorter if you configure), you can access containers again. It should be a small problem - is it very often that your players try to build or access boxes immediately after pvp combat in your survival games world?
@Sinistralis777
What do you mean by computer items? I might have opened a giant can of worms by adding this modding support. Chances are that if you're still able to interact with a block after putting it into one of the protection lists, it's because your mod (tekkit or whatever) isn't playing by bukkit rules (like firing cancellable events so plugins can see what's happening).
@schmidtbochum
Okay do you need to drop items as an admin, or do you mean you want all players to have the option to drop items?
@08havoc
Yep, there's a config option to enable explosions above sea level. See admin details page.
@ryvix
Yeah, it's y = 2 because in the normal world, bedrock varies between those two Y values. I may be able to adjust it down to 1 safely, let me just review and make sure there wasn't another reason for y = 2.
@Impiryo
I'd think you would be granting players permission to build in admin claims fairly rarely, right? Is it really so much trouble to teleport over and do a /trust? Adding remote control for specific claims would be a big deal on my end, and I really think it isn't useful all that often. At best, you'd be forced to write down or remember ID numbers for claims, which is awkward, it wouldn't work for specific subdivisions, and there would be a lot of error handling for me to worry about (is it your claim, etc).
Here's an idea to smooth out your experience. Do /trust [permission] where the permission is something you're using only for those claims where you commonly give specific players permission to build. Now use your permission plugin's slash command to grant the permission. No matter where you are, you can effectively grant and revoke permission for that specific claim (or a group of claims where you've trusted that permission node).
I expect to have this ready for 1.3 the day of or the day after the first beta build release. I plan to test the most critical functionality (ensuring claimed areas can't be griefed), then give it to you guys. I don't expect there will be any big problems. The only real concern I have is about the new "use dispensers to pour lava or water" mechanic.
@schmidtbochum
Thanks for the info, but I'm not supporting dev builds. I'll be sure to test that against the beta build before I release a GP version for 1.3.
@roggbart
Thanks so much. :) PLEASE go to your favorite server administration forums and spread the word!
@blizzard158
Pressure plates are never protected. Players have lots of other options to work with, if they want control over who can access their stuffs. I do not plan to add this as an option. Consider that for lots of machines (especially monster grinders) to work, touchplates always have to work when monsters or animals step on them. Because a player can lead a monster or animal (with wheat) anywhere he wants, there would always be an easy workaround to a locked pressure plate.
-
View User Profile
-
Send Message
Posted Aug 2, 2012Hello I'm using Build 5.5 for CB 1.2.5-R4.0 and i was wondering if Pressure Plates are protected in Claims. I looked through the config and saw some options for "PreventButtonsSwitches" and "LockAllDoors", i enabled them both but they didn't stop people from using pressure plates. Are pressure lockable and i'm just missing it? or is it not added yet? if it's not, Do you think you could possibly add an option please?
-
View User Profile
-
Send Message
Posted Aug 2, 2012How does this work with Tekkit, do you know? Will it be able to protect peoples machines and tekkit chests? Edit: sorry, read your text.
Amazing plugin, never been so impressed by a plugin in my life.
-
View User Profile
-
Send Message
Posted Aug 2, 2012Critical Bug in Bukkit 1.3 (Dev Build): Players can place water/lava outside of claims, or in other player's claims
-
View User Profile
-
Send Message
Posted Aug 2, 2012@Sinistralis777
Yeah it would be really cool - would save a lot time at explaining users to type for example "/t [BuildCraft]"
But form other hand buildcraft would be exploited to grief...
-
View User Profile
-
Send Message
Posted Aug 2, 2012@Impiryo
The main reason I want to set people to ignoreclaims is because this is how tekkit works. It registers mods as "people" because some of the mods build things themselves, which causes a lot of issues with protection plugins without a bypass permission.