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 Apr 21, 2012You should be able to reload the config in-game, if you added that in, it'd be great :)
-
View User Profile
-
Send Message
Posted Apr 21, 2012@shutka
not going to happen, you can only run GP and WorldGuard side-by-side
FAQ:
"How do I make monsters stop spawning, or allow PvP in a claim?
You can't. This plugin is about preventing grief, and neither of these is about player grief. However, GriefPrevention is entirely compatible with WorldGuard and Residence, so you can use those with it. Do the following:
1. Restrict the other plugin so that only administrators can use it. GriefPrevention is the solution for your players, but you'll be using the other plugin for a few special cases.
2. Use the other plugin to mark off special administrative areas where you'll be allowing PvP, stopping monsters from spawning, or whatever.
3. Optionally, use /adminclaims and possibly /trust public to add a grief prevention claim on top of your protected area. That will prevent players from making personal claims there.
Now you have the effectiveness and ease of use for your players through GriefPrevention, with the special "flags" offered by the other, more complicated plugin. :)"
-
View User Profile
-
Send Message
Posted Apr 21, 2012@bigscary
In the griefprevention folder inside my plugins folder there is the config file. Whenever i make changes to it (like the amount of block accured per hour) then start my server it changes back to default. Really really frustrating, plz help
-
View User Profile
-
Send Message
Posted Apr 21, 2012@bigscary
No Problem Bigscary, Sorry post was so big, but I wanted to be detailed and not make a bunch of separate posts. Thanks for taking the time to consider them all and look into #3 and SimpleClan integration.
Thanks Saintcrime.
-
View User Profile
-
Send Message
Posted Apr 21, 2012I LOVE the transferclaims!
SO now anyone with the admin all-giving node can /adminclaim then /transferclaim bob to make a claim for bob, and adds it to his bonusclaimblocks?
-
View User Profile
-
Send Message
Posted Apr 21, 20123.4 Updates!
-
View User Profile
-
Send Message
Posted Apr 21, 2012@krisdestruction
None of the commands work in console. Maybe some of them, like this one, should. :)
@DrFusion
No, you can use /containertrust public to allow for everyone to use the chests, but there would be norestriction on what they can put it or take out.
@RustyDagger
Okay thanks, I'll try to imagine a way to fix this. I didn't consider that another plugin might be doing something non standard for stopping pvp.
@Sollo360
Which config option are you changing? It's possible you might be changing one of the options that isn't used anymore. Also after editing the config file, you need to either /reload or shut down and restart your server (which I think you're doing, but I just want to make sure I understand you correctly).
@saintcrime
He won't be able to claim because there's an existing claim above him, and that would create an overlapping claim situation (which isn't allowed). He'd get an error message, and he might be confused because it's possible the claim visualization blocks placed to help him are hidden by cavern walls.
@dabomb665m
That doesn't sound like expected behavior, no. Are you sure this is the case for brand new claims? Remember that claims automatically extend downward as players build or break blocks underneath them. So generally claims start shallow, but eventually end up deep. Can you check a little more and see if this is the case for your server? Try making a new admin claim at the surface and testing its depth with a piece of string (don't dig INSIDE the claim though to test, dig beside it, because digging inside will sink it as you go).
@DrFusion
Use /containertrust public in the claim or subdivision containing the chest.
@Foltax
"Siege is disabled here" means siege is disabled in your world. Check your config settings, you need to list each world where you want to enable siege.
@saintcrime
On (1) I understand where you're coming from, but /trust is by claim, not by person. There's no record of you trusting anyone universally, it's just by each claim. Nonetheless maybe I can do something about this. I've noticed it myself, but I think it's a small annoyance at worst.
Unfortunately, I think (2) would be a giant performance problem. Searching for claims within an area would be very, very expensive. I agree it would be nice though, if I could do it affordably.
(3) is a really big feature ask. :) Let me look into the details of SimpleClans to see what it would take for me to integrate.
Thank you VERY much for your thoughtful feedback and for taking the time to play on my test server!
-
View User Profile
-
Send Message
Posted Apr 21, 2012@Sollo360
make it read-only for now
@saintcrime
wasn't a complaint, was just a shock :P
-
View User Profile
-
Send Message
Posted Apr 21, 2012@cvxx7q
Yeah, I know but it was better than making 3 separate posts.
-
View User Profile
-
Send Message
Posted Apr 21, 2012Heyy guys how do i stop the config file changing back to its default state everytime i open my server??
-
View User Profile
-
Send Message
Posted Apr 21, 2012@saintcrime
TL;DR
damn that's a big post lol
big scary is going to be reading a small novel..
-
View User Profile
-
Send Message
Posted Apr 20, 2012Having a hard time getting siege to work.
Just testing with two players for now, but unable to siege the other player while he is inside his claim. I get the message "Siege is disabled here". I could only imagine because it's his newbie chest claim that it may be protected from siege somehow? Just guessing for now. Any ideas?
Cheers.
(I'm willing to be a test case. :P)
-
View User Profile
-
Send Message
Posted Apr 20, 2012@DrFusion standing
in
the
claim
type:
/containertrust Public
problemsolved
-
View User Profile
-
Send Message
Posted Apr 20, 2012I do like your point three!! Have a simplelan intergratation would be awsome!
-
View User Profile
-
Send Message
Posted Apr 20, 2012Hello Bigscary, I have a few things I would like to request/open discussion/throw at you. I have been testing your PVP/Siege and GriefPrevention in general on your test server. I have come across a few details that I found that either hamper game play or could be modified.
1. PVP enabled even for trusted people: I and my Bro have found that this can get in the way a lot. When we are working together and are building we hit each other sometime by accident, then have to wait to get out of combat to continue building. Also, when we are out fighting monsters we sometimes hit each other. It would be logical that if you /trust someone that you and those trusted would become non-PVP to each other. Basically, becoming a team of sorts. You would still be PVP enabled for all other non trusted people on the server but would not be able to hurt each other. Think of this as a "Friendly Fire". Maybe even have an option to turn "FF" on or off. This could also be done with SimpleClans as it has this "FF" feature built in see part 3.
2. Warn on claim to close to another claim: I have come across situations where I find a nice spot. No visible buildings by others. I then claim my land. Everything is fine. I build something and then during build I decide I need a little more land claimed, or the design needed access or something on one side (Say for stairs or door etc..). I go to adjust this side of claim or build there and find that I made my claim right up to or within a few blocks of another person's claim. I did not know I did this because even when I used the string to check originally their claim was just on block farther or more away when I checked. Would be nice to have a configurable or preset config option. Maybe WarnMinimumClaimDistance. All it would do is warn you in chat that you are within the minimum distance of another person's claim. Possibly like this- WarnMinimumClaimDistance is set to 10 in the GP config. You go to claim and claim within 10 or less from another claim. GP warns you in chat similar to other warnings with "This claim is within minimum distance(or have it use the minimum number such as "10" from config in place of "minimum distance" like "within 10 blocks") of another players claim. Consider this before claiming this land!!!"
3. Possible Clan/Faction Tag integration: There are plugins for PVP that I believe would enhance GP. I will use SimpleClans SC Link Here as an example plus it's my choice plugin for clans :). Currently SimpleClans uses the PreciousStones PS Link Here for claims of land for PVP/Clans. I really like GP's Claiming of land and it's user friendliness, and would hate to have to use another plugin for Clan land claiming etc or cause players to have to learn and use a second plugin. SimpleClans does state that "Any Protection plugin can hook into their API" for both Protection SC Prot Link Here and War SC War Link Here It would be awesome if GP could use SimpleClans. This would/could allow Clans in SimpleClans to have access/permissions on Clan Claims and also be able to Siege(GP) each other clan to clan.
Here's an example- I make a claim. I am a clan leader and my clan is called Friends of Bigscary and the clan tag is FoB. After claiming the land I can use GP permissions such as /accesstrust {clantag} /containertrust {clantag} etc... so /accesstrust FoB or something similar, I do not know how GP and Simple clans would need to be connected as I cannot program yet but i would assume you would use the same command structure that you are already using, just adding the {clan}. Also SimpleClans states that with using PreciousStones "If you are in a clan, every field that you place will automatically have your clan in the allowed list." Maybe that can also happen with GP. When you or a clan leader make a claim their clan is automatically on the /accesstrust as a minimum and allow the owner to add other /"trusts" as they see fit. Now, let's also say that another player has made a claim and connected their clan to it. Using SimpleClans "War" feature these clans could attack each other's claims. Maybe even using GP's Siege feature. So, Clan A goes to War (using SimpleClans) with Clan B. A is now automatically able to destroy clan B's claims and vice versa. Or when the clans go to war using SimpleClans they are in Siege (GP)mode with all their "at war" rival clans claims.
These are just my Opinions and Ideas. Please discuss or pick apart as needed. I would like to see these implemented or something similar directly through GP or SimpleClans integration. If they can or won't be that is cool to. Just offering my thoughts to help make GP more awesome than it's already awesome level of awesomeness! Thanks Saintcrime
-
View User Profile
-
Send Message
Posted Apr 20, 2012@Europia79
like everyone open chest on ONE claim not all the claims there is in my server
-
View User Profile
-
Send Message
Posted Apr 20, 2012@bigscary
Hi. I just found out that claims on my server extend from bedrock to the sky (highest point). Is this correct behavior? I have "extend into ground" setting in config.yml set to 5... but for some reason it goes all the way down to bedrock (making it tedious for miners). There's also a group of people trying to build a skyrail that have run into people's claims at 100+ elevation when the homes are built at around 60.
Is this a bug? is there a way to adjust it or maybe I missed a config somewhere?
-
View User Profile
-
Send Message
Posted Apr 20, 2012Hey All / Bigscary, Quick question. "What happens if player A has a claim, and that claim goes down into surface default 5 blocks. Now player B comes along underground at a level below that 5 units, lets say 25 more units below the player A's claim. Now player B is beneath player A's claim. What happens if player B tries to claim while under player A's claim?" I have not tested this just curious.
-
View User Profile
-
Send Message
Posted Apr 20, 2012@DrFusion
"/trust public"
that command there makes everyone trusted
"/trust public"
"/containertrust public"
"/accesstrust public"
-
View User Profile
-
Send Message
Posted Apr 20, 2012Heyy again When I change the config file and then start the server up he resest it back to the original settings. I change the config while the server is down then open it. When the server opens thats when it changes. I tried changing while the server is up but the changes wont occur until you restart the server so when i restart it the config file changes again. please please help