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).
I'm pondering if I should check out the code and compile a private version that does some debugging to help out, if possible =)
Anyone else experiencing the 'lost claimblocks at login'-issue? Seems to be happning some players when they connect after the server has been idle for a while. Looks like lost mysql connection.
Sorry if I've missed anything =S
How do you give all players access to accesstrust or containertrust. I tried ALL as the playername, is there a way?
@bigscary
I don't get how its always me that's always reporting major issues, thanks for getting on top of this, thankfully I can quickly disable siege and run /gpreload, Its a massive shame that there isn't a permissions for /claimexplosions otherwise I could have just removed that.
We have over 4500+ claims, Starting to mess with conversions again only worries me, I have never once had a working conversion with databases and GP.
For the AllowedIpAddresses accepting URLS, here is what I have:
Ah! If you don't filter URL's in your spam filter, then it must be another plugin that is doing it! I will have a hunt through my plugins to see if I can find what is filtering urls, for some reason I always thought it was GP! It must be essentials.
@ExDomino
I really hate to say no, but I just have to. It sucks that you have to choose between losing subdivisions randomly and that anti-mod-damage feature, but you're asking me to support an obsolete version I made almost a year ago. It's too much to ask for a free time project, at least from a guy with less than two hours of free time per day. I'm sorry. :(
@GodsDead
I'll get back the TNT thing down to only cannons in the next update.
Yes, wolf protection is determined by GP config pvp worlds setting. I will try to come up with something better.
You have me stumped on the URL whitelist. Please give me an example of a message containing a URL which won't send so I can try it out. I don't have any code which intentionally mutes URLs.
Everyone can run claimexplosions? Will get to that straight away. For today, I say step back to the previous version. I'm feeling pretty good about the beta release, so I may just do a forward fix. More than 300 downloads over two days, and no complaints yet about data problems.
@Blanidur
Yes, there's a config option for that - "deliver manual", I think.
@HolyPsychWard
I need the internal error - you can find it in your server logs. It'll be big, ugly, and around the time that you tried to run that command.
@Sorky
Hmm... you say the fluid stays even after the claim is removed? I will check into this. For creative mode worlds, it should still be removed when the claim goes away. The config option you mention doesn't exist because it's ALWAYS on.
ABSOLUTELY MAJOR BUG.
In one of your last updates for siege, you have now allowed ANYONE to toggle explosions when they siege a player, people can siege a base and /claimexplosions when they are attacking it, thereby making anything and everything get blown up, making GriefPrevetnion useless, put this with the modification to allow TNT to be laid IN claims during siege, you have utter disaster. This needs to be patched separate from this new "beta" development version that converts claims in the database or we will have many more problems on our hands. Please act fast no this major bug.
I'm having trouble with GP 12.3 and Spigot 1.8.8 in my creative world where water and lava somehow ignore claim borders when going from inside to outside. The fluid will also not be removed when claim is removed. I tried changing the config to add CreativeWorlds under AutomaticNatureRestoration but every time i restart the server the plugin seems to erase the line as if it is invalid.
This makes it very easy for people to claim a small patch, dump a bunch of fluid and then remove the claim. The fluid stays put and has to be cleaned up manually. Repeat this a 100 times and I have a massive cleanup on my hands. Is this perhaps due to changes from 1.8.3 > 1.8.8 ?
Hey there! I'm loving the plugin, but for some reason I can't the buy/sell commands to work. I have Vault with CraftConomy3 all for 1.7 server. When I do /sellclaimblocks it gives me the prompt and everything, but when I try to type in a number it says "An internal error has occured". The same things happens when I do /buyclaimblocks, except I don't even get a prompt for that one. Any suggestion would be greatly appreciated! :)
Can I prevent new players get the ClaimBook?
@bigscary
Hey bigscary, having them place TNT has just been a disaster so far, it would be fine if they could cannon it in, either with existing Minecraft TNT cannons or a plugin, Being able to lay blocks in siege just creates a whole new dimension of exploits! Creating a cannon takes effort, where as running in spamming TNT and blowing up grass around a base just to piss of a player is very easy to do.
We just tested the Wolf situation, and they are still invincible. You can storm in with Wolfs that start attacking the player and they are invincible to the Victim, is this reliant on having PVP enabled in GP? Mine is disabled as I use PVPmanager, and didn't want any conflicts.
As for the URL whitelist, does this have a new variable I need to set them to? Or is there a different format? I put urls in the IP white-list variable and they still cannot be used by players.
When you resize a claim with more than one subclaim, only few of them are preserved. It's apprently random, like if your mod cannot read them all. I you want to check out the problem by yourself, I uploaded the claim file before and after a resize, you will see that some subclaims was removed but not all of them, despite the main claim has grown.
Before : http://pastebin.com/DfVgyeJz After : http://pastebin.com/qL10zgJg
We cannot downgrade because we need something added in 9.1 : « Non-Vanilla items are now treated with suspicion - trying to right-click with them while pointing at a claimed block requires build trust. » That's because we have mods on our server!
@ExDomino
Hmm, please double-check on that. I've been recommending that build as the best for 1.7.10 since 1.8 was released almost a year ago, and you're the first to report that problem. I don't work on 1.7.10 anymore, so if you do consistently have that problem, you might try a different version of GP made for 1.7.10. If you do that and find one which works better for you, please tell me and I'll consider changing my recommended 1.7.10 build.
On the latest version for 1.7.10, when I resize a claim, all subclaims are removed. So we're unable to use GriefPrevention to create cities, because if the city grows, all resident territories are removed. Can you fix that bug please?
@GodsDead
I fixed the wolf thing a couple of versions back? I remember testing it to be sure. :\
URLs are already allowed - only IP addresses are blocked. If you've noticed otherwise, please grab the details from your server logs so I can see the exact messages and investigate on my end.
@bigboone11
I'm sorry, I can't help without any details. It just isn't working? Check your boot logs for error messages.
@LordKainzo
Per hour per group no. Per group yes - /acb [permission.node]. The brackets are required.
@GodsDead
Yep. You don't want it placeable, then? Only cannoned in?
@marubal21
I'm working on a scary rework of the way claims are stored to get a performance boost and make sure subclaims have unique IDs. Then I'll re-triage the rest of my todo list. :)
EDIT: That didn't answer your question. In my mind, the smart claim depth on creation feature is #2 on my todo list after my current item, behind an optional profanity filter to proactively shut down players who join servers just to troll the chat. I'm uncertain about the restore nature feature - the more I think about it, the less it sounds worth the effort to me. If only there weren't fat trees to consider!
@SatansDaughter66
I'll fix that. It's /separate <player 1> <player 2>.
i dont think the /separate command works....i do it in chat and it just says /Separate in chat :/
is there another argument that im forgetting? because nothing was specified
Any ETA on when the "coming soon" features will be added?
I can't use my Grief Prevention! It's been working fine for a very long time and all of a sudden we just can't make any claim.. It's been like this for a long time now and we have tried just about anything... Please help.
Siege laying TNT -> Players can now nerd pole into bases, they can create stairs too, or bridges to avoid moats.
Is there no way set these things?
Per-player(permission node or group) allotment?
SupporterRank1 > 20000
SupporterRank2 > 30000
SupporterRank3 > 40000
Per node/group allotment per hour increases
SupporterRank1 > 200
SupporterRank2 > 300
SupporterRank3 > 400
Without this, I feel really restricted based on the configurations...
I can't use my Grief Prevention! It's been working fine for a very long time and all of a sudden we just can't make any claim.. It's been like this for a long time now and we have tried just about anything... Please help.