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).
@bigscary:
one word, amazing, this is exaclty what i have wanted for a long time and its even got extras that i havent thought of but i think are all essential!
Please do consider my suggestions: 1. Players that build with each other can give each other "claim blocks". This could also integrate with the economy allowing people to sell, buy, or trade "claim blocks". 2. Have an AFK timer, if a player hasn't moved for 1hr+, they don't receive blocks.
@bigscary
Height isn't calculated into the claim area at all, huh? So a 10x10 area, regardless of how much vertical space is protected (up OR down) is just a flat 100, no matter what, for the purposes of calculating claim block charges? That's interesting. Totally different from Residence, but different in a good way.
Thanks for the information!
@Dudescast
Yeah sorry Dudes, you're on your own for that. I've got enough on my plate just trying to code this one, let alone figure out the details of Tekkit and work out their differences. :) Good luck!
@ValawynV
Claim blocks required for a claim are length x width (height isn't considered). For example, a PopulationDensity region is 400x400 blocks, so to claim the whole thing, a player would need 160,000 claim blocks available. Or an admin can just claim it outright as an admin claim, since those are free.
@bigscary
Of course I made sure to test while not being admin. But I am running the server with tekkit: http://technicpack.net/?page_id=355
But I can't see how that should make the plugin work fine otherwise but make so that people can place blocks inside an claimed area...
EDIT: Okay just tested with a totally clean regular bukkit server, and it was working just fine. Then I tried the Tekkit without any other plugins, and it was still acting strange, so I am guessing it is the mods somehow cause problems, and I guess isn't really in your interest to figure out what is wrong? I mean since it is not really the purpose of this plugin, that you run mods that is...
@bigscary
That's a very good point, and I can't believe I didn't think of that. Forget I mentioned anything. >.>
On a side note, how does you plugin calculate how many "claim blocks" are in a claim's area? Does it just calculate the volume of the selected cuboid, and then charge that number of claim blocks to your account? Some specifics would be of great help to other administrators that use economy plugins to limit land claims.
@ValawynV
Oh, I get it. I'm trying to avoid "feature creep", and I think I might have to draw the line on this one. I want to stick to features that are entirely rooted in preventing grief, and this one seems more like a "change the game" rather than "fix the grief".
There are other compatible plugins which can help you get it done. Consider using Residence or WorldGuard alongside GriefPrevention. You'd just set Residence or WorldGuard so that only certain knowledgeable players (admins?) could use them, to prevent conflicts and confusion. Then for those few situations where GriefPrevention won't give you the flags you want, you can use the other plugin for that protected area. You can even overlay, for example, a residence over a claim. So when you want to create an area where no monsters spawn, instead of asking for a new flag over here in GriefPrevention, use one of those plugins instead for that special case.
1.4 updates!
Players can now resize their claims by using the shovel on the corner of the claim, then using the shovel again at the new place for that corner. Think of it like "click and drag" without holding down the mouse button.
This rapid development (daily updates) is finally taking its toll. Coding this feature was an ugly, frustrating business because the code has become overly complex. It's time for me to have a good look at it, do some commenting and reorganizing, then test again before adding the next feature (which is the big one, claims subdivision). It may be a week or so before I finally release it. In the meantime, please continue to give me any feedback you have, especially around my plan for subdivision. Thanks all!
@bigscary
Okay, I'll try to elaborate... Uh.. Say, for instance, I'm creating a puzzle-based dungeony-thing. Zelda-esque. I obviously don't want them to be able to break blocks inside the region, which this plugin already handles nicely. However, with subdivisions and the ability to set "public flags" (allow all players entering the region/subdivision to do Action A without having to be given trust for that region) I could allow players to, for instance, build in one section but not in another section of the same "dungeon", use levers in one subdivision, but not another, etc.
It adds complexity, granted, but it's all optional complexity. A person is not required to add public flags, and if they don't, the plugin would behave as it does now.
This is all assuming there is not already some sort of "public flag" system built into the plugin that I have just not seen. If so, you'll have to forgive my ignorance.
@ValawynV
Can you provide a more specific example of something you want to accomplish? I don't quite get it. It sounds to me like you want to allow a player to say, operate some switches but not others?
@bigscary
Yeah, Bookworm enters you into "write mode" which then intercepts all of your chat messages and adds them to the book, not to chat. It's a really convenient feature, if you've got no spam protection. I'll have to warn my players about it, and give permissions nodes as needed.
In regards to your subdivisions implementation, is there a way to set "public flags" so to speak, as of yet? I could, for instance, use subdivisions to allow certain actions in certain sections of dungeons. This would let me create even more complex puzzles for players to solve for their spells, which would mean more fun for everyone.
So FYI, my plan for today is to make the claims resizeable. The major benefit will be that players who have lots of people on their /trust lists for a claim will not have to re-apply those permissions to a new claim. Instead, they can make their existing claim bigger. It should work like this:
Right-clicking with the shovel (or string) on an existing claim will visualize the claim, highlighting its corners with glowstone.
Right-click any corner of a claim to start resizing.
Right-click again in the NEW location where you want that corner to be.
As long as you have enough claim blocks, the claim is more than the minimum size, and you're not overlapping another claim, your claim will grow or shrink to the new size, and your permissions will remain intact.
Please tell me if you think this should work another way.
Now, on to subdivision, because I need that feedback, too. Here's the plan:
Player places a claim. Now he uses /subdivideclaims to switch to subdivision mode, where he uses the same "right click at corners" steps to designate a subdivision within the existing claim. Subdivisions will be visualized in white and silver, to differentiate their boundaries from those of the containing claim.
Subdivisions have no limit on size (minimum or maximum), and cost nothing to create. They can't overlap, and you can't create a subdivision inside another subdivision (subdivisions are limited to ONE level for sake of user and developer sanity).
If a player has permission to do something in the containing claim, he also has that permission in ALL its subdivisions. So for example, if you give a player the permission to open boxes in your claim, he can open boxes in the WHOLE claim, including all subdivisions.
If you use any of the /trust commands within a subdivision, the changes will apply to ONLY that subdivision. This makes it possible for you to give a player more permissions in a specific subdivision than he has in the claim in general. This is useful, for example, if you'd like to make a player a "tenant" in a house or on a plot you've created, while preventing him from accessing other parts of the claim, including others' houses. You can also use this to give a player access to a community chest or workshop without giving him access to everything else in the claim. You could also give a player permission to come in the front door of your claim, but not the back, by placing separate subdivisions around those doors' switches.
Please think carefully about this. Whatever scenario you have in mind - can you accomplish it with this implementation? If you can't, please post here about your scenario so that we can discuss it.
@burtthaman
Right sorry, that explanation was meant to be in reply to Val's post, not yours. Bad mouse aim.
@ValawynV
Hey, does the book thing use raw chat, or does it send a series of slash commands? If it's using a slash command, then you should be safe with the latest version because it only monitors the slash commands you list in the config file.
If the book plugin is expecting all your text to come as plain chat, then that's a bad plan in general. They should be using a slash command because their text is in fact not chat. :) But yeah, there's no way around it - either use permission nodes for specific users, disable spam protection entirely, or tell your users not to use that particular feature of spout for creating books.
Actually, that whole spout feature that allows for players to send much larger blocks of chat is a dangerous one. I'm surprised they implemented it, given that a griefer could use it so easily to spam a ridiculous amount of text. There's good reason for Vanilla client's limit on chat message size.
@Dudescast
Are you an admin on that server? Admins can do whatever they want. De-op yourself.
After testing this on a Tekkit server I found that you could still build block in claimed areas, is that a common bug atm?
@burtthaman
That's what I was afraid of. Looks like I'll be giving out permissions nodes, then. If there's no way around it, there's no way around it. The spam prevention's certainly not getting disabled. >.>
There is no way around this that I know of. Same problem on a dif server with dif spam protection. The thing is it breaks your text up and sends it line by line thus making a wall of text. This is exactly what spam protection is designed to stop.
An idea is to give you and your dungeon creators etc the permission node that ignores spam prevention (griefprevention.spam). Then let it moderate regular users.
Otherwise just turn off spam prevention all together.
@bigscary
Got a potentially tough one for ya, this time. Let's see if I can stump you. :P
Right, so, here's the situation: A player is writing a book via the bookworm plugin, and this player possesses Spoutcraft which, as you may or may not know, enables you to copy and paste text into the chat box, and removes the text limit by automatically splitting your wall of text into multiple messages of the proper size. In order to write in a book, you simply type something in chat while write-mode is active. This player wrote the book in notepad, formatted it, etc., and then attempted to paste it into the chat box and send it through and thus into the book.
They were immediately banned for spam.
This is a bit of a problem. I myself use this same method, as it's the easiest way of writing lengthy books (we use Bookworm and MagicSpells to create riddle and clue-based dungeons that contain new spells in them for new players to find. Gives you something to do other than building) easily and with proper formatting. If there's a way around this, it'd be awesome.
You are correct, I didn't quite understand how the system worked. I either missed where it explained that, or it isn't explained. My confusion was that it wasn't taking money out of their accounts when they claimed a plot of land. Little did I know, that they way it works is that you convert money in your bank account to blocks in your block account, and then you "spend" those blocks on land you claim. Now I know.
@bigscary
Your plugin is shaping up beautifully and your work has allowed us to go live again. You (or anyone curious about this plugin that wants to see it in action) are welcome to pop in any time you like. We're going to remain on 1.0.1 until a stable recommended build of Bukkit comes out. Server information: 96.8.119.99:25631 Bukkit for 1.0.1, newest version of GriefPrevention (as of this post) MagicSpells, Bookworm, Runecraft, Citizens, BOSEconomy, and others that are not worth mentioning.