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 Dec 15, 2015I imagine this has been answered somehwere but I can't find it. Is there any way to disable piston protection outside of land claims? I need pistons enabled without claiming land but cannot find any configuration nodes regarding pistons...
-
View User Profile
-
Send Message
Posted Dec 15, 2015@Bobcat00
Yeah, there is. You need to define the book's text in book.txt, then you can specify that book ID in a kit.
books.txt
config.yml
kits: book: items: - 387 1 title:Example_Book author:&4Server book:ExampleFinding the actual book data to use isn't hard, it's all in GriefPrevention's messages.yml
BookAuthor: Text: BigScary BookTitle: Text: How to Claim Land BookIntro: Text: Claim land to protect your stuff! Click the link above to learn land claims in 3 minutes or less. :) BookDisabledChestClaims: Text: ' On this server, placing a chest will NOT claim land for you.' BookUsefulCommands: Text: 'Useful Commands:' BookLink: Text: 'Click: {0}' Notes: '{0}: video URL' BookTools: Text: Our claim tools are {0} and {1}. Notes: '0: claim modification tool name; 1:claim information tool name'Naturally, stuff like useful commands you'll have to keep up to date yourself, but there's no easy way around that.
-
View User Profile
-
Send Message
Posted Dec 14, 2015"Added a config option to protect pets outside of land claims even in PvP worlds. Note that pet wolves are NEVER protected in PvP worlds because they have the potential to attack players, who should be able to defend themselves."
Hey! This is AWESOME! Thanks for adding this and listening to me! :D Here's a suggestion to add to this idea if you want. If pet protection is enabled then hitting wolves will not damage them, but it will cause them to sit and not be able to move. The owner would have to make them stand every time they got hit so it would be a big setback during a fight. Just an idea.
-
View User Profile
-
Send Message
Posted Dec 14, 2015@bigscary
Some of my players are gone in 2 minutes, or they've gone through a portal to the non-GP plotworld. They never get a book in that case. So I'd want it to work like an Essentials first-join kit. Which brings up a good question: Is there a way to add the book to an essentials kit?
-
View User Profile
-
Send Message
Posted Dec 14, 2015@GodsDead
"Crappy" is a human decision and I won't try to automate it. If you don't have the time or don't want to spend it, then get some staff volunteer to do the job for you. I won't introduce a feature (deleting claims in an area) that requires WorldGuard. I'll think about adding a slash command which takes two sets of coordinates instead, but even then I think you'll be disappointed that you sometimes delete non-problem land claims you didn't realize were there, like underground work.
On preventing land claims in an area, you already have two ways to get it done, one with WG and one without. I get that you think typing /ac and /trust public is a hassle, but I disagree and think you've set your expectations way too high for free software. Maybe have someone make you a private version of GP if you want that level of control over features. If it were a small ask, I'd do it anyway, but I don't see a way to get it done without a lot of work to add some new design concepts to the plugin, which would then probably be used by very few.
@Bobcat00
Because players are usually too busy oggling the spawn or struggling to read a mountain of other on-join messages to notice the important "how to not get griefed" information. Sure, I can do that config option.
@maclarenss
In your config, you have both lava dumping near other players AND flint/steel near other players turned off. Are you saying that players are still burning each other anyway? If so, please describe how they are doing it so that I can find the problem.
I'm especially interested in how fire charges are being used to burn other players. Is there a method which doesn't involve placing a dispenser?
Limiting water buckets to land claims is a bad idea because players often want to farm in early game before they have a golden shovel (or the necessary claim blocks) to create a separate land claim for a farm and they wouldn't be able to place water for their crops.
Anyway, this wouldn't fix the problem because if a player is outside of land claims, a griefer could create a land claim around him and then dump the lava, OR lure players into his claimed area for grief. This is why the fire/lava protections are based on proximity to other players rather than whether or not there's a land claim.
If you have other suggestions around the "griefers dump water buckets everywhere" problem, I'm listening! I'd prefer a solution that doesn't ever require an admin to get involved. However limiting bucket usage for all players creates a bigger (farming complaints from honest players) problem than it fixes. I know this because the solution you describe used to be the one GP used.
-
View User Profile
-
Send Message
Posted Dec 14, 2015@The_PC_Tech_Guy
yep. i mean burning people.deception!.but /restorenature the server only because of the poured lava or water it isn't reasonable.
-
View User Profile
-
Send Message
Posted Dec 14, 2015@Bobcat00
Perhaps. I rather prefer a longer delay because (most) players aren't going to be thinking about claiming within the first minute of joining... two minutes or so seems about right, where they start to gather resources, but not deeply engrossed in their activities/have fairly-filled inventory.
@maclarenss
Use /restorenature. And... what do you mean by "burning" peaceful players? Your server is PvP, why don't they just attack them...? Do you have something else managing PvP?
-
View User Profile
-
Send Message
Posted Dec 13, 2015@bigscary
this my config http://pastebin.com/3TPnYHgr. I simply wish that what: fire_charge,lava_bucket,water_bucket,FlintAndSteel,worked only in my land claim,because out of a privat people spoil a landscape with lava and water_bucket, and also burn peaceful players.
-
View User Profile
-
Send Message
Posted Dec 12, 2015Why did you delay the book delivery to 2 minutes? Maybe this should be a config parameter.
-
View User Profile
-
Send Message
Posted Dec 11, 2015@GodsDead
What flag should GP check for then? By default there's a global region in WorldGuard, and some might want to use WorldGuard as it integrates right now - perhaps allowing claims in area players can build, but also want to set special flags for that area. Seems to me that you're an isolated case :S
-
View User Profile
-
Send Message
Posted Dec 11, 2015@The_PC_Tech_Guy
Obviously this is how I've been having to do it for, this is extremely obvious as I explained already, this is also a terrible method having to double claim an area, when it shouldn't be at all, the setting just need to be adjusted on how it works in the config. Double claiming is NOT a fix for the current way WorldGuard claims are treated. This isnt something recent this is just extremely irritating design that hasn't been fixed.
-
View User Profile
-
Send Message
Posted Dec 11, 2015@bigscary
No idea. "Crappy" as in half build cobble boxes, Im having to manually delete all inactive claims, There not large at all, im guessing most are under 10x10, either expanded from the initial chest drop or their first building, then they got board and left the server. Im fining claims that the player hasnt been on for 100+ days and its just a crappy cobble house/mess they have left. These are the majority of claims around spawn, its a mess and there needs to be a fast way to clear them up.
-
View User Profile
-
Send Message
Posted Dec 10, 2015Update 13.2.1 is here!
@maclarenss
I'll check on it. Please share (pastebin) your config and tell me which world you're having the problem in. And also, what's the problem with fire charges? Please tell me what players are doing that you want to stop.
I won't tell players they're muted. That will just make them act out more (outside of chat). If you don't want players auto-muted, reduce your banned words list. I also won't auto-unmute a chat troll. The only auto mute is for brand new players who start with racism and anti-homosexual hate speech right away. There's no way players who do that can be assumed to improve their behavior the next day. If you disagree about which terms are acceptable in your chat, update your banned words list.
@GodsDead
Why would the "crappy" claims not be targeted by the auto delete tool? Are the players still active? Are the claims too large, or does the player have additional claims? Please explain.
You can get the 'allow build but not claim' done with admin claims in GP.
-
View User Profile
-
Send Message
Posted Dec 10, 2015@The_PC_Tech_Guy
i mean minecraft:fire_charge. ok then add pls autounmute after 1 day or somthing else
-
View User Profile
-
Send Message
Posted Dec 9, 2015@GodsDead
Just make an /adminclaim and /trust public, then use WorldGuard for whatever you please.
@maclarenss
Fiery sphere? What do you mean?
Regarding muting, the intent is to not let the player know they've been muted, as this would defeat the purpose of softmuting. If you want to notify the player they've been muted - there's numerous censor plugins (some of which are far better than the one included with GP), and many include notifying the player when they've been muted.
-
View User Profile
-
Send Message
Posted Dec 9, 2015@The_PC_Tech_Guy
yep in pvp world...and more add pls fiery sphere too.and add when mute(when he wrote bad words) the player that it was written to a chat you are mutted up.I will test about a bucket of a lava and I will tell precisely
-
View User Profile
-
Send Message
Posted Dec 8, 2015@The_PC_Tech_Guy
Both, a force-run command to tidy up and a selection. I see a ton of really really crappy 1/8 built cobble/wood square houses that can die a death that are claimed that would not be targeted by the auto-delete tool. Its as if the auto cleanup never happens, I have over 6000 claims now.
Another Request: Add a custom flag for worldguard to set if in that region only if people can claim land with GriefPrevention. I want to create WorldGuard regions that allow people to build in and CAN NOT claim land using griefprevention, at present CreationRequiresWorldGuardBuildPermission when false allows anyone to put a griefprevention claim inside a god damn admin owned Worldguard region, WG regions need to be created by an admin, this is silly behaviour, so the only option is to set it to true, which then makes it so you have to have build permission in that WG claim, makes sense, until you want an Admin Wordguard region that allows people to people but NOT claim land with griefprevention (y u no create admin claim...) Worldguard has a lot of flags & supported plugins that are not supported by GP.
There is a library already to do most of the legwork http://dev.bukkit.org/bukkit-plugins/worldguard-custom-flags/
-
View User Profile
-
Send Message
Posted Dec 7, 2015@GodsDead
A better idea is just a command to force-run the claim removal task.
@maclarenss
We're going to need more details than that. Is this a PvP world? Can you show us a video of it?
@propilot2
Yes to the first - I use it this way as well. As for the second, I'd just use another plugin and permissions to prevent building/destroying. You can restrict claiming, however, and coupled with the SurvivalRequiresClaims mode, you could "restrict" whatever permission groups you want from making claims, and thus "blocking" the ability to build/destroy.
-
View User Profile
-
Send Message
Posted Dec 6, 2015Wow, what a plugin.
Now, I have a question. I have World Guard, can I use that as well? I love using World Guard along side of World Edit.
Also how do I prevent guests accounts from building anywhere?
-
View User Profile
-
Send Message
Posted Dec 6, 2015AllowLavaDumpingNearOtherPlayers: false = not work AllowFlintAndSteelNearOtherPlayers: false = work