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 7, 2012So I updated to the latest RB of bukkit, and my old version of GP doesn't work. So I really need to figure out why I can't use a new version of GP.
As I mentioned before bigscary, version 3.8 works, 3.9 and above does not... it allows users to break blocks in claims... even though it gives the you don't have permission error. It still doesn't let you build, but you can break.
Any progress figuring this out?
-
View User Profile
-
Send Message
Posted Aug 7, 2012I use this plugin to protect the spawn, but there is only 1 issue, no1 but me can make claims, but when you place a cehst, there is a small 1*1 area of protection made, I don't want this, but I dont know how to disable that?
Thanks in advance + keep up the good work :)
-
View User Profile
-
Send Message
Posted Aug 7, 2012@VietNg
Not so fast! They're having issues. Uploading their own RB. To their own services...
Wat.
-
View User Profile
-
Send Message
Posted Aug 7, 2012Good thing Craftbukkit Recommended Build is released :) I wish you good luck :)
-
View User Profile
-
Send Message
Posted Aug 7, 2012@bigscary: THANKS! I'll do some playing around with the beta on a 1.3.1 test server. :)
-
View User Profile
-
Send Message
Posted Aug 6, 2012@n33dy1
http://dev.bukkit.org/server-mods/grief-prevention/files/73-5-8/
I've been playing with it for the last 30 minutes. Working fine so far on a fresh world - will load it up on my exisiting server (4 worlds) after mowing the lawn. Thanks Scary!!
I copy of my existing worlds... LOL I'm not that silly.-
View User Profile
-
Send Message
Posted Aug 6, 2012Thanks Bigscary!
The dev build is running without any issues so far. I'll keep an eye on it!
-
View User Profile
-
Send Message
Posted Aug 6, 20125.8 Released for Dev 2311!
I recommend very strongly against running ANY dev build on a live server. However the Bukkit guys have told us that they will no longer guarantee any level of quality, even for the builds they label "recommended". Since there's no way for us to tell, then, which builds are good except by trying them ourselves, I understand if you feel you want to go ahead and update. IF YOU DO, BE SURE TO BACK UP YOUR WORLD.
Okay I'm off my soap box. See my changes below. I tested the protection for claimed areas, and it seems solid. Good luck, please tell me if you have difficulty - however be advised that unless you're on 2311, I reserve the option to not investigate your issue. 2311 is the build I'm "officially" supporting.
@n33dy1
This is not an accurate statement. It would be more accurate to say that if you run a GriefPrevention build which was created for 1.2.5 on some specific 1.3.1 dev builds, then you will have a problem. The problem is not grief prevention, it's that you've gone and plugged an American-style appliance into a European-style outlet, and now you're getting electrocuted. Serves you right for going cowboy against common sense and my explicit warnings. Now stop screaming in my comments about how your unsupported config doesn't work, or you'll be banned from commenting.
@Jadedwolfs
The harm is that even basic testing takes a lot of my time, so I can't afford to test every dev build that comes out (they're about one per day, right?). So that means I can't say "I support" each build, and the end result is that server owners have to either run their server on my supported build and run cowboy with their other plugins, or vice versa. It's a very bad situation to have a platform changing so rapidly that the community can't keep up, so I was hoping to wait for a recommended build so that at least everybody would be on the same page.
But like I said above, the bukkit guys have said that their first recommended build won't be tested AT ALL, so I figure... might as well release a dev build now, since quality is a crapshoot anyway. However you'll notice that I'm only offering to help server owners with issues if they run dev 2311, which will keep this manageable for me.
Given that even basic testing took my whole evening, I probably won't release another 1.3.1 build until Bukkit releases their first RB.
-
View User Profile
-
Send Message
Posted Aug 6, 2012i hope that they do have a RB soon i really need a fix for this addon. It was working right up till they changed the chat stuff. once they changed that it then stoped working. i know you want to wait till a RB build so i hope one comes out soon.Keep up the great work on this addon
-
View User Profile
-
Send Message
Posted Aug 6, 2012Grief prevention has been a liable and 110% effective method of not only preventing inevitable griefing on my server-to-come, but also replacing any other potentially effective anti-griefing mechanics implemented by World Guard, Redstone protect, Towny, etc. etc.
Simplicity is a trait that many people overlook, but funny enough, simplicity in itself can forge and generate the best plugins, servers, and whatever else one might be constructing. My personal experience with servers? If I log in for the first time and it takes me more than 5 minutes to figure out how to get out of the spawn point and build or interact with the sever in it's entirety, there is no way I'll be playing on that server. Thus, grief prevention in my eyes is a very prodigious plugin. Insanely better than world guard, or any other mention able protection plugins.
Very big props, bigscary!
-
View User Profile
-
Send Message
Posted Aug 6, 2012This is a free service - give the guy a break! He'll release when it's time and not before. Sheesh.
-
View User Profile
-
Send Message
Posted Aug 6, 2012@bigscary
I understand, I really do, however it was said in irc by amaerath. However it could be a day away, who knows.
What harm are you doing by releasing early? People stuck on 1.2.5 are not affected. People who are on 1.3.1 are however, plus you would get more feedback before an official build was released. build have the version they are compatible with, right beside each download.
I'm not trying to be all "this plugin does it you should too"
But it does make sense, no?
-
View User Profile
-
Send Message
Posted Aug 6, 2012@Jadedwolfs
Last time we went through this process, they did use the beta build system. What they said was that this time, they'd release a recommended build as soon as they could do some very minimal testing. So then, if an RB comes, of course I will treat it just as I was planning to treat a beta build.
Where did you read about "could take weeks"? I've not seen any timeframe given by any of the bukkit guys. Please link me to that announcement.
@tentonaxe
I think you've been misinformed. Caps is not considered spam (players don't get banned for that). Please check your logs to see what actually happened - I find that players sometimes tell a different story.
If you disable the ban, they will be muted until they stop spamming.
@Sinistralis777
I'll try to get this fixed for you, but it may not be in the next version (the first one for MC 1.3.1). I say that because the more I read about patch notes and hear about breaking chat API changes, the more work I expect for me to get an update out.
@spacedestroy
I might do that - a custom slash command to run in case of spam sounds doable.
@Sinistralis777
Ouch, a "trust everybody except this guy" type of command would be very hard for me to do, actually. And I think it would be used very rarely. I'll say no for now, and might reconsider if others ask for the same.
@Esaych
Like I've been telling everybody - you're out of your mind for running a dev build. This is the kind of thing that happens when you run a server on code which was released only for plugin developers to use. Good luck, I hope your world isn't corrupted.
-
View User Profile
-
Send Message
Posted Aug 6, 2012@bigscary
Evilseph said there won't be a beta build, they are waiting to get a RB build, which could take weeks.... They added the whole beta build status to the system, yet it's rarely been used. Please do not use that as a guideline for when you're going to update or we will not be able to go live with our servers for a very long time.
-
View User Profile
-
Send Message
Posted Aug 6, 2012Thanks for the headsup bigscary. Just what I needed to know. Sticking to 2284 untill a Beta is released and you update.
Thanks for shining some light on this. And thanks for the awesome plugin!
-
View User Profile
-
Send Message
Posted Aug 6, 2012There's nothing I can do about dev build bugs. When the first beta build comes out, I will publish an updated grief prevention build (assuming there are no severe bugs in the beta build).
-
View User Profile
-
Send Message
Posted Aug 6, 2012Up to dev build 2284, it's working. But newer one, it won't work. Dev build less than 2284 sucks, and laggy. I hope you can update so my server can run properly :)
-
View User Profile
-
Send Message
Posted Aug 6, 2012@bigscary
I narrowed it down some. 3.9 and above doesn't work (the blocks break and stay broken while giving the you don't have permission error). 3.8 does work correctly as far as protecting blocks.
I have a lot of plugins: MessageChangerLite, WorldEdit, VoxelSniper, TakeaNumber, BeardStat, mcbans, DiscoSheepPlus, Vault, PermissionsEx, Multiv erse-Core, GriefPrevention, AutoAnnouncer, dynmap, Essentials, MagicCarpet, EssentialsProtect, BeardAch, ProperTime, EssentialsSpawn, HawkEye, Essenti alsGeoIP, EssentialsChat, Residence
My GP Config: http://pastebin.com/HFeCEqEg
Thanks for lookin into this.
-
View User Profile
-
Send Message
Posted Aug 6, 2012I have a test server on which I installed the latest 1.3.1 dev build to find GP isn't working... so I rolled back the dev build from 2302 to 2283... and GP is working. This allows me to sample 1.3.1 a little and try things out. It's not by any means the latest dev build but it works with GP 5.5.1. I'm not planning to run 1.3.1 on a live server until GP is updated and working... which will take time.
Eventually I hope all the existing plugins which I use will be updated soon after Bukkit release 1.3.1. Until then I'll run dev build 2283.
-
View User Profile
-
Send Message
Posted Aug 5, 2012Another good idea for this, if you get the time, is a Container/Access/Build Deny command that you could utilize on AdminClaim areas when making them public.
This is a very specalized use and is more of a personal request so feel free to disregard it, but it would be nice when doing shopkeeper claims to make the adminclaim public and then being able to ban users from shops should they upset the shopkeeper in some way.