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).
@cvxx7q
Well, it seems that everything related to ic2 can be used to grief :) Too bad that even after 2 years of modding it' is still a mess...
Another idea from my moderators... again you will probably say no because it might not be in the spririt of your plugin. But what about having a different type of claim, where I can setup a group claim that only certain groups can build/claim in. Like a giant 1000x1000 area that is limited to Citizens, and a 1000x1000 area that is limited to Guests. Then the guests can do what they want in their area, it behaves just like wilderness, except only that group (or higher) can build / claim land in it. This would keep the guests out of the citizen area and keep things a little more tidy.
BTW, I told all my moderators that I am planning to change to this plug in and they are ecstatic.
Thanks again, Lostwave.
@cvxx7q
Yes, I will be getting rid of both Towny and Residence, and probably big brother too.
I know its not a socal plugin, but the beauty of the map is I can follow people around without logging on, and see where they are, and more importantly see whos claim (residence) they are in. Its great to see the claims on the map... plus its very convenient to see an overview of what is where. It would be nice to have this plugin work there.
Thanks again guys for your quick responses and information.
Also, did you see Jebs announcement this morning... new world format, height limit 256 in 1.2... AWESOME!
Lostwave!
@Lostwave
yes exactly, with grief prevention you can let grief run wild and it wont hurt your players (so long as they smart enuff to claim) and any grief in the world can be fixed with the restore chunk function
you use a gold spade in restore mode to fix chunks, its a regen not a block log
per world has been added in 1.8 it hasnt appeared on the file list yet but it has been released (subscribers get early "access")
for your museum just make one big bad ass admin claim, no problem ;)
griefprevention is grief blocker not really a social/town plugin therefore you will want the author of dynmap to add the ability to "label towns" etc, i don't believe this in bigscary's interests
and im in the same boat brother. 1.2 = total rebuild of my server (alot was built into the terrain, but not this time!, at this current time i am rebuilding in a 1.2 snapshot with my friend, for what its worth our rebuilds are much much more detailed and elaborate, since we get a chance to rework alot of things and work on "flawed" ideas ;)
as far as i can say, you can get rid of residence, im not sure about towny maybe even that too, but for me this is all i use to manage ownership its the EXACT plugin i always wished for :)
@bigscary
Interesting. I didn't even think about that... allow griefing basically, if you don't want to be griefed, then protect your stuff. Our mods are getting really tired of dealing with grief. If we just allow it, then we don't have to do anything.
About your /restorenature command, how does that work? You don't save all block changes right (this is a problem with towny and the datafiles get huge)? Just regen's the chunk? How big/small of an area gets restored with that command?
Also, what are the chances of getting per-world settings? I am going to have to use Residence on my Museum world to set allow build to false. (its just for looking, no touching). It would be great if I didn't have to do that. The museum world is 20k by 20k blocks and creating a protected zone in there seems like overkill. Unless you could make a setting about which world has which permissions, including build. Then I could get rid of Residence all together.
Okay, maybe I will try this plugin, I love all your features. I have to wait until 1.2 comes out because that is when we are creating a new world, but we will give it a try.
On another note, you should talk to mikeprimm from dynmap and see if he can add a plugin for this. Its great to be able to see the residences/towns on the map. see:http://lostwave.com:8123 to see what I am talking about. All residences/towns show up on the map and its pretty cool.
@deseven
test 'em and report back ;)
@bigscary
Thanks for the info. Okay, i think i'll just disable nukes and dynamites, not so sure about lasers, terraformers, etc...
@bigscary
Thanks for the update! I've been eagerly awaiting it. You forgot to mention the end fix which works perfectly. :) VERY low priority enhancement: have the blocks that fall off the edge appear near the height the player is at instead of at the 0 y index. (like level 64 or something so they can actually see that block.)
EDIT: Just saw that you put in the minimum claim size variable in. Thanks a million! When I get some money to spend I'll definitely send you a small donation for your awesome plugin!
@bigscary
lol i understand what caching is :Pi was asking how how you have implemented it because as far as i could tell grief prevention caused me no loss in performance at all, so i was wonder [/s[s]]what the heck you would be caching? (i assume in memory?)im surely not asking for code lol, just what is it your caching and why is it important to cache iti see you edited your post (lucky i checked back) thanks for the Elaboration ;)
@rmh4209
Also just to clarify, it's not possible to determine reliably WHO owns fire, once it starts spreading. Besides, even a well meaning player could accidentally burn down the server. It's better not to allow it in any case.
@deseven
Sorry deseven, plugins like industrialcraft and tekkit change all the rules. For example, I know that tekkit's machines all change blocks under a fake player account, so that entirely dodges my protection mechanisms, which depend on having a way to reliably determine WHO is making the edit. You should take up your issue with industrialcraft, because there's nothing I can do on my end - those game changing plugins need to respect the platform rather than ignore it, so that other plugins will work well with them.
@Lostwave
I think you're wrong about that. Anyone who's been griefed before will happily use an anti grief plugin, and GriefPrevention is by far the easiest to use. As a bonus, even players who don't know how it works get a basic level of protection from the automatic first-chest claim. That's not true of Precious Stones, World Guard, or Residence.
On my server, all I do is have a message that appears once per hour that says "Protect your builds from grief! Watch the "Grief Prevention Basics" video on YouTube". For the vast majority of my players (I have a 20 slot, public, advertised server, so I get all types), that's sufficient. For the few who refuse to take the advice, they learn the hard way by catching a grief, and I tell them to fail less by claiming their land.
I don't have a problem with a mess in the wilderness. But if I did, the /restorenature command makes any cleanup in the wilderness insanely fast and easy.
@cvxx7q
Performance caching is something I do in the background, where you don't see it. It eliminates searching ALL claims EVERY time someone places or breaks a block, which can get expensive as the number of claims on the server increases.
Basically, I'm noting which claim each player was LAST seen in. The next time I ask which claim that player is in, I first check that claim to see if he's still there. If he's not, THEN I search all claims. Most of the time, a player hangs out in one claim, so this adjustment saves a lot of CPU cycles.
@bigscary, what is this caching your update list speaks of?
@Lostwave
its not really something they can complain about, if they are too damn uneducated (or stupid to google residence help files) if they get griefed then you should flat out tell them "you should have protected your land" sometimes u gotta tell em they did something stupid, its how they will learn, i'm all for helping players dont get me wrong, but geeze some people need a disaster before they learn :S
@bigscary
Oh man, that's too bad, I guess I will stick with residence. Unfortunately residence and towny (both of which I am using now in different worlds) are too complicated for new users. But I don't like the mess that happens when I allow people to build anywhere. At any given time during the day we have 20+ users and half of them are new, and they have a hard time figuring out residence... And even harder with towny. But I love with both that I can block building in wilderness. I allow giant claims right off the bat, but people can't figure out residence so I have to allow them to build in the wilderness, and they never protect their land. I would have the same issues I have now with your plug in. Even if your plugin allows for easier protection, they won't use it unless they are forced to, and therefore we will still have griefing. At least with residence I can block all wilderness building. Makes me sad, I was really excited when I saw your plugin. Regardless, keep up the great work. I love how responsive you are on here! Take care
Lostwave
@cvxx7q
Understandable. Thanks.
@rmh4209
this request goes against the foundations of this plugin, its not going to be implemented, you can see the reasoning here> Quote: Big scary: Fire is extremely dangerous to allow to spread in any case, and doesn't spread predictably (like lava), which means I can never be totally sure my code is right.
Could you add a permission node to allow users with it to create fire?
@bigscary
Sorry about the minimum claim size, that's just a want, not a need, as players get really confused when they want to resize their small claim (all set at default) and find out that "it doesn't meet the minimum size?!?!" It's really frustrating as an admin to have to go around and tell them that it isn't broken, they just need to expand in both directions, not just one. As far as the end thing goes, yeah, I have some builders that build in really interesting locations, and stuff, and it also seems they like creating connected houses below the minimum size as well quite often (if needed I can disable grief prevention in the end until you get that fixed if not included in 1.8). I understand about you not wanting to include it and I can definitely tell the builders that they need to start building stuff in sizes bigger than 10x10.
Also, another feature request (low priority):
Have the ability for admins to resize any claim.
Not sure if i should call it a bug, but... I'm using Industrial Craft 2 with bukkit and there are many different ways of griefing (nukes, dynamites, lasers). Grief Prevention just ignores it and allows anyone to destroy protected areas with ic2-specific methods. Can you please solve it somehow?
Feature Suggestion:
Would it be possible to add a way to just regenerate land above sea level with the restore nature function? I'd like to be able to use it to restore natural features, but not regenerate the ores and such below ground.
Planning to release 1.8 today.
New features:
Both the golden shovel and the string work from a distance! Up to 100 blocks away. This means:
When a player can't create a claim or restore nature due to a conflict with another claim, that other claim will be highlighted in red so that the player can see it.
When a player builds or breaks beneath his claim, the claim will be automatically extended downward. So as a player explores, his claim goes deeper with him, eliminating the need for tedious resizing or reclaiming to claim areas like basements, cave constructions, and mineshafts.
The claims.enabled config can now be a list of specific worlds, "true" for all worlds, or "false" for no worlds.
Optimizations:
If a player places a chest outside his claim, now he gets a warning message.
Increased the pretty level in visualizations.
Performance caching is in. Less load on the server.
RestoreNature highlights the restored area when successful, instead of displaying a message.
Bug Fixes:
"/untrust all" works without displaying an error message (it was working before, but also showing an error message).
/deleteallclaims and /untrust will now work when the player is offline, provided you type the name with the correct casing. The player must have played on the server previously, though (so no /trusting your friends before they join the server).
RestoreNature can't kill players be suffocating them. It just doesn't work when there's a player in the chunk.
RestoreNature now requires the restorenature permission rather than the ignoreclaims permission.
Players and explosions can no longer destroy minecarts and boats in your claim.
Treetopper code got a major fix. Now tree tops are even harder to leave, while stacks of logs placed by players as part of a construction are MUCH safer (your non-log blocks have always been perfectly safe, and still are).