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).
Added spam protection. Note new config variables. Details coming soon (probably tonight).
You'll need to delete your GriefPreventionData folder before starting this update, because I updated the file format for player data.
Hi scary I will probably be opening tonight or tomorrow. Thanks for your continued development :D
@burtthaman
Yeah I've already done some homework on that problem and I'll do some more before I release any code in that area. In some cases, the source is available so I can see what others tried and where they might have gone wrong.
I think you misunderstand about PvP limits. PvP will be either on or off for a world. When it's off, no PvP damage. When it's on, it's on everywhere. However if you want to be safe even before siege is implemented, all you have to do is build an iron door with a button. Because others can't use your button (because it's on your claim), no one will be able to get into your house to kill you (unless you leave other entrances open).
I'll consider a new player PvP-free time. I saw that on another server and liked it.
Awesomeness. One thing I forgot to mention. NoCheat and lumberjack ran into some issues. I believe nocheat fixed it on their end but not sure about total solution. May want to look into that before creating implementation of tree top spam part.
Also in the pvp limits part. Does this mean I can have pvp on for the world but off for claims? This would be great. At least till seige is implemented. And when that time comes I have no idea how you would do this withour people abusing the system but some way to have pvp off till they are done building. Possibly a simple time limit from when you first start building property to give them a chance to get up walls etc.
0.8 Updates!
Fixed wool thievery.
Tweaked permissions required to create, modify, and delete administrative ("public") claims. Note especially that /trust and family no longer apply to those claims, since modifying them is already regulated via the griefprevention.adminclaims permission.
Newbies finally get their automatic claims! :) If a player doesn't have a claim yet and places a chest, a claim will automatically be created around it. There's a config variable to control the RADIUS around the chest which will be protected (it's a square shape, but you get the idea - variable set at 4 = 9 x 9 blocks, including the chest itself). If the entire claim can't fit because there's another claim nearby, it will automatically shrink to fit. At the very least, the chest itself will be protected. To protect ONLY the chest for newbies, set this value to 0. To DISABLE newbie protection, set this value less than zero.
Yes, I know the docs still aren't complete. They need config variable updates and a complete permissions reference. I promise to deliver this weekend. :)
@burtthaman
Okay Burt, you got it. Priorities rearranged. :)
I think the order is nice, my server should be good to go soon especially with the upcoming updates!
@bigscary
I think fix 1 and 2 and call it done for now on claims. I am the loudest about the other claim features but seeing them on the list is enough for me :-). I think then 6,7,8,9, then 3,4,5 then 10. 10 will be the hardest and longest tweaking. 3,4,5 don't have to be done right away for near full functionality of anti grief with easy to use claims system. But get the advanced claims done before siege warfare heh.
Hi all, just some details on the to-do list priority. Feedback welcome.
@ubuntu10
Very glad you like it. :) The claims protection is pretty solid as far as I can tell, with only a very few known bugs right now. For example, it's still possible to shear sheep and thereby steal wool. And I'm on the fence on the subject of eggs, since they don't stay on the ground long before disappearing. Probably won't try to do anything there. There's also a weakass piston exploit that could, in very limited situations, get you into somebody's house. I need to see whether it can be used to break chests or not.
@deleted_7036002
Chest claim is still on the to-do list. Will be in this weekend. If claim subdivision coding goes smoothly (that's a big if), then it will probably be available this weekend, too.
Working on updating the project docs today. Will be moving administrative details to a separate page, keeping the main page for overview and player usage.
love this plugin all the gritting stop on my server with the new update 0.7 :)
@bigscary
Great work :D is the chest claim implemented or not?
This plugin is coming along nicely :D
Edit: can we have a list of permissions?
0.7 changes are in! Admins get some luv!
/adjustbonusclaimblocks now requires permission.
/deleteclaim to delete the claim you're standing in, even if it's not yours.
/deleteallclaims <player> to clear a player's claims.
/adminclaims to switch to administrative claims mode. Use administrative claims to protect public areas. Admin claims don't use up any of the creator's personal claim blocks, and are accessible by everyone (buttons, switches, containers, etc). Admin claims can only be deleted or edited (build/break) by admins who can create them. When PvP is implemented, they'll be immune to siege.
/basicclaims to switch back to "standard" or "basic" claims mode.
Admins now ignore claims, meaning access privilege constraints don't apply to them. They can open any boxes, build and break anywhere, etc.
Added an option to restrict claim creation to specific players (it makes the "griefprevention.createclaims" permission required to create a claim with the shovel).
Hey bigscary just wanted to say thanks for the daily updates you have been doing we are much closer to release so far, and my friends love the plugin.
@burtthaman
No plans for spout right now, especially since I'm not planning to use anything spout-specific. Wanna keep it simple so that admins can download this and JUST this.
I think 100 per hour is still a bit much but again that is just for my server and play style and economy etc. a non economy server 75 to 100 would be fine as default I'm sure. I don't care what default is honestly as long as its configurable :-)
I'm wondering if you have any plans to port these over to spout as they are breaking off soon from bukkit. I may be going spout only since I use a lot of things from it.
@burtthaman
Yep, 100 blocks is big enough for a very compact, efficient house, but not enough for a library and fields and pastures, unless you engineer a very vertical home (ugh, square cobblestone towers!).
100 blocks per hour might be reasonable. I'm just guessing though - I don't have any experience to go on, yet. I'm happy to take suggestions for a better default, provided those suggestions are built on experience. :) I hesitate to provide much more than that as a default, though, because I don't want griefers to be able to wall people in. Under the current defaults, a griefer would have to play 3 hours on the server before he'd have enough claim blocks available to wall in a newbie claim. Three hours of work to grief one newbie hut and then catch a ban probably isn't worth the effort, or at least that's the way I'd hope griefers would see it.
The 80,000 block upper limit is almost unreachable given the current accrual rate of only 100 blocks per hour (you'd have to play 800 hours to get there). It's also very large - 90,000 would be 300 x 300 blocks.
Anyway, all of this is up to opinion, hence flexibility via configuration variables.
Real quick. 100 blocks is 10x10 square right (or 20x5)? I guess 500 isn't as big as I had originally thought. 22x23 block square. Just wondering what I would set the hourly gain to in order to make gaining land from time only a long task. Sorry thinking out loud lol.
This is awesome... you are really doing a lot of work and I appreciate that so much. I will put credits to you and this plugin as well as population density in my spawn area as well. I really love the idea of switching from basic to advanced mode. This enables much more configuration etc as you said AND for new players you don't have to worry about any of that mess. I totally understand it taking more time for the advanced features... all we want right now is a fully working "basic" version of claims with n00b protection and all the config/perm files/system in place. I'm speaking for everyone when I probably shouldn't but I think that would go a long way to getting us all up and running on our individual servers. Keep up the great work and as always THANKS!
0.6 Changes:
Added /adjustbonusclaimblocks, claims blocks accrual with play time, and associated config options. Note that /adjustbonusclaimblocks can be used to add a negative amount, to inhibit a player's claims or to undo an accidentally too-large bonus.
Fixed a bug with /abandonallclaims which left some claims standing.
Added config options to disable claims altogether, only theft protection, or only access protection.
Added a config option to adjust the number of blocks into the ground a newly created claim will extend. If desired, use a very high number to guarantee all claims reach to bedrock.
Sample config, illustrating default values:
GriefPrevention:
Claims:
Enabled: true
PreventTheft: true
PreventButtonsSwitches: true
InitialBlocks: 100
BlocksAccruedPerHour: 100
MaxAccruedBlocks: 80000
AutomaticNewPlayerClaims: true
ExtendIntoGroundDistance: 5
Next changes will be mostly adminstrative, including permissions and some admin-specific commands like /deleteclaim and /deleteallclaims <player>. I also hope to include the automatic new player protection in the next release (the config variable appears above, but that feature is not yet implemented).