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 Feb 14, 2013@bigscary
Is there anything we, as a community, can do to make maintaining this plugin worth your while? A minimum goal for donations, say? Can totally understand if the time this takes up is getting in the way of other, more important, things. I'm sure more people would contribute if given the alternative of losing the plugin/you at the helm.
@GumbyDammit
Ah, thanks. Seems to be missing from the documentation (as far as I could see, at least)
-
View User Profile
-
Send Message
Posted Feb 14, 2013@zedadiaswick
griefprevention.spam
-
View User Profile
-
Send Message
Posted Feb 14, 2013Sucks you've lost interest as I just found out about this plugin. lol. Thanks for all your work.
This is a bit of a feature request, I don't know how hard it would be to do but maybe it wouldn't be to bad....
Would you be able to make a script that would convert residences to grief prevention zones?
Don't have to include trusts, just the owner and their coords...I would imagine it'd mainly just be parsing the residence data correctly.
I might have a look at how to make it myself. Claim ID's are a little annoying wonder why you did that instead of a file for each player or just one big file containing all claims.
-
View User Profile
-
Send Message
Posted Feb 14, 2013Was I imagining it, or is there a bypass permission node for the anti-spam protection?
-
View User Profile
-
Send Message
Posted Feb 14, 2013@bigscary
These are the kinds of things I'm talkign about with regard to the over-eager spam filter:
Names have been changed to protect the innocent ;)
-
View User Profile
-
Send Message
Posted Feb 13, 2013@bigscary
@bigscary
Please don't stop developing the plugin, it's the very first time I find a good protection plugin for a 150 player server.
-
View User Profile
-
Send Message
Posted Feb 13, 2013@bigscary
They're NOT getting any error message when trying to build on their own lots, that's never been a problem. AGAIN, the problem is that anyone else can break blocks on a protected lot if they're not opped! In regards to messages, it's not an error that they're receiving when trying to plant a block on a protected block, it's the INTENDED message of, the person not having permission to build here.
Can't help me eh? I did what you asked and followed all your instructions to the T. Anyhow, I see you're giving up and passing this to another dev. Thanks for your time I guess.. I had high hopes for this.
-
View User Profile
-
Send Message
Posted Feb 13, 2013@bigscary
Nope, but working with what we have :p Only reason I asked. Either way, thanks a ton for the plugin :]
-
View User Profile
-
Send Message
Posted Feb 13, 2013To get it to grant claim blocks upon creating Golden Shovels I'd have to create a plugin that makes that happen? So now I have to teach myself how to program in JAVA?
-
View User Profile
-
Send Message
Posted Feb 13, 2013Hey everyone, I'm looking for someone to take over this plugin. Please send me a private message if you're interested. Be warned it's a very big job - daily comment checks, frequent feature requests, lots of bogus bug reports, and recently, lots of people confused about all the new non-CraftBukkits out there. :) So you have to be willing to make a pretty big free time commitment.
7.6.2 Update
@deleted_9935739
For a specific player, /deleteallclaims <player>. For a world, you have to shut down your server and delete the files for those claims (or run a SQL delete statement with appropriate parameters, if you're in database mode).
-
View User Profile
-
Send Message
Posted Feb 13, 2013How can I delete all claims made by a certain player or in a certain world?
-
View User Profile
-
Send Message
Posted Feb 13, 2013@Tomdebeast
Yes you can. /acb [permission.node.here].
@vivalaminecraft
Sorry I don't plan to add that. You could give a permission group a flat amount of bonus blocks using the slash command I mentioned to Tom above.
@xclucky
I'll bet they're using something that doesnt play well with Bukkit. Are you running a modded server, like Tekkit? Or do your players maybe have access to a plugin which lets them change the world like WorldEdit or MagicSpells? When a plugin or mod item changes the world, it doesn't always tell all the plugins about the change - hence the back door for anti grief and nothing in your log block logs.
@imaapseudonym
You have it backward - BukkitForge needs to do a better job of running CraftBukkit plugins. You wouldn't call Nintendo for a new Legend of Zelda to work the the emulator you downloaded from the internet, would you?
@lukasparsons
That's the way it should work. Basically, the deployer can't make changes because it can't be determined who OWNS the deployer. If a deployer could take up water in a claimed area, then griefers could use it to steal water from land claims without permission (when the water is on the edge of the claim).
@suliman101
It sounds to me like ForgottenNature or your plugin platform doesn't correctly ask permission from plugins before placing a block.
@lukasparsons
This is for CraftBukkit servers, not modded servers. If you have an issue you'll have to take that up with your platform developer (ForgeBukkit or MCPC or whatever).
@geekyservers
I'm sorry, but I can't help you unless you can narrow down the problem. You have lots of permissions and you're running lots of plugins. Please follow the instructions I gave you to eliminate the possibility of another plugin undermining Grief Prevention.
You also didn't answer my question about the message players are getting when they're blocked from building when they should have permission.
@GumbyDammit
I can't help you unless you show me the logs between when a player logs in, and when he got banned for spam. Then I can see the reason why he was banned and potentially fix something there. I need details.
@Stevensaurus
That would be cool. But it is not possible, because WorldEdit doesn't ask my plugin for permission before making changes to the world. I would have to change WorldEdit, and that is not my project.
@Nekuroi
Sorry, but your stack trace is incomplete. Please check your logs again and be sure to get the whole thing.
In what way are your players teleporting? Are they using a slash command to do it? If so, go into your config file and add that command to the list of commands which are not allowed during PvP. If that is not the case, players may be cheating - try adding a plugin like NoCheatPlus.
-
View User Profile
-
Send Message
Posted Feb 13, 2013Reporting this
http://pastebin.com/BhGJ4jCQ
Also there is an unknown way to avoid the teleport prevention in pvp. Some users are keep reporting me that someone get instant teleport when they hit them.
-
View User Profile
-
Send Message
Posted Feb 13, 2013It would be really cool if you could prevent using WorldEdit to edit other players' claims.
-
View User Profile
-
Send Message
Posted Feb 13, 2013A minor thing, but I'm finding the spam filter seems to be cranked up to 11 and I can't do much about it. I run a server for small kids aged 8-12, and they are being muted and banned right and left for totally innocuous things. Phrases I have seen give spam and ban warnings:
"ok" "hi!!!" "xD" "lol"
It's now to the point where I exempt everyone in my main Builder group from the spam filter, and proper spammers get moved to the Pest group which has no exemption. As it is, the spam filter is a black box. I have no idea as to exactly what constitutes spam, nor is there any way to adjust it's behaviour.
-
View User Profile
-
Send Message
Posted Feb 12, 2013The Gravigun mod is on my server. And the gravigun moves blocks inside of claims without permission. would anyone have any idea how to make Gravigun compatible with this plugin?...
-
View User Profile
-
Send Message
Posted Feb 12, 2013@xclucky
Lucky, I'm having this SAME issue. Are you using bPermissions? I found out that people that are OPPED cannot break things and the plugin works as intended. However, non-opped players can break EVERYTHING but chests and doors (if specified in the config).
-
View User Profile
-
Send Message
Posted Feb 12, 2013@bigscary
Before I begin, let me say that I am extremely grateful that you have a lot of passion for your plugin and are a pillar of greatness when it comes to your ability to communicate with your plugin users! Thank you! If only all devs were like you. You definitely have a clear understanding of how to keep an open communication with the people that praise your plugin / work.
Alright, so I cleaned out ALL errors in my server.log and updated ALL plugins.
The only people this plugin works on via bPermissions is, OPPED users; well, at least on my server.
There's definitely something wrong. The non-opped players cannot break chests / doors, that's about it. Everything else is a free for all. Also, they can't build in a claimed area. Which is good. But the fact that people that are not opped can break everything else, it very very bad obviously.
Is there a way to have people with issues like mine, be able to manually add blocks that I don't want to break on my server? Please? Emergency update lol... I have 4000 users (not all at the same time thankfully) and this is the last plugin that doesn't work for me. Though it is an EPIC plugin, it just won't work for me and my users with everything properly updated and errors knocked out.
-
View User Profile
-
Send Message
Posted Feb 12, 2013after some careful reading i noticed your section detailing how to add mod blocks to the list prevents a player from interacting with an already placed block. This is good and it seems to work already with most of the forgotten nature blocks. However, after reading closely i noticed that this does not mention the possibility of preventing a player from placing said block in another players claim. Upon testing i notice i can place blocks in another players claim that belong to forgotten nature but i cannot destroy them. Is it possible to prevent a player from placing mod blocks in another players claim ?
-
View User Profile
-
Send Message
Posted Feb 12, 2013hello. i'm running a server with this plugin that has the deployer/filter/receiver machines in it. and one of my players is using a deployer to bucket up water in his claim and use it then filter the empty bucket back through to be used again by the deployer. But, when the deployer and water source are claimed, the deployer wont bucket up the water. when they are unclaimed, the setup works fine. is this something that can be worked out in the config? any ideas?
I dont think its the deployer. i think it is something about the claimed water.