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).
@burtthaman
You don't pay when you claim land. You just pay when you use /buyclaimblocks <amount> to get MORE blocks. Using the blocks you have in your "block bank" doesn't cost you anything. But it costs to add blocks to that bank.
Since you're using economy, you probably want to disable the "claim blocks accrual" which awards blocks based on play time. You can do that by setting that config variable to zero. If you don't want to disable it entirely, maybe you can set the max accrued claim blocks to a relatively low number, to encourage players to spend money when they want large claims.
@ValawynV
This may be a silly answer but I don't see in your post what economy plugin you are using? Vault is just the backbone API that lets plugin creators make a standardized economy plugin as well as offering the other plugins an ability to hook into these newly created economy plugins. Think of it like a translator that also writes the rules for how translation works. So you would need BOSEconomy or iconomy etc
Also what you are describing in the last part of the comment sounds like charging to place blocks already owned. Why? Just charge them to get blocks then let them do what they want after receiving the blocks
@bigscary
Awesome news again. The visualization is brilliant, and really helps work with the regions. Thanks!
On a side note, I may be doing something silly here, but I'm trying to set this plugin up to charge money for blocks, as you're already aware. Vault is up to date, so is your plugin. From what I see that you've stated about the economy integration, it should be active so long as the values for block prices are set to anything but 0. I have done so, and my testers are not receiving any fees associated with purchasing blocks.
I guess what I'm trying to say/ask is: How do I convince the plugin to ignore block limits and only limit claims based upon the cash the player possesses, and then actually charge them?
Version 1.3 is compatible with clients 1.1. I tested it briefly with the latest CraftBukkit build - please tell me if you notice any issues, as there's no "recommended" craft bukkit build yet.
HELLSYAH visualization is in, and it looks AWESOME. Sorry, got a little excited there. You guys gotta check it out - use your string on a claim!
I also updated the spam code. If you want commands to be monitored for spam, you have to list the commands you want monitored. The default is only /local and /global, the most common "chat" slash commands.
Also fixed my mistake where decimal values for the buy/sell amounts for claim blocks would be ignored or rounded down.
@ValawynV
Burt was right on both counts. Yes, I made a msitake which ignored your decimal values, and I'm fixing it right now. :) Also, some economy plugins (like EconXP) don't deal in decimal amounts.
@ValawynV
Big can probably answer this better but it is my understanding that vault allows it and your economy plugin of choice is what enables decimals or not. Big just hooked his plugin into vault api for added functionality so it should work just like everything else though this may be wrong...
Big if it is on your end... maybe the config variable you are storing for block price needs to be a double where you placed an int?
@bigscary
Are decimal prices supported? Trying to do .025 per block, and it seems to be ignoring my edits to the config file in regards to economy. Any ideas?
@bigscary
I'm gonna PM you... We are starting to get more technical than these comments need :). WALL OF TEXT for the loss :).
Okay, I see. :) You're right about the block counting, it wouldn't be too hard to figure out how many blocks overlap and do that math correctly.
The reason for blocking overlapping claims is because right now is the expense in determining whether or not someone is in a claim - doing that involves searching existing claims, which could be very many (several per player, including offline players). Currently, when I ask "is there a claim here?", I can stop when I find a claim. If I allow for overlapping claims, then I ALWAYS have to search all claims, even after I find one claim the player is in, because there may be more. That's the major reason for that limitation on claim placement.
Also, other experiences for players get more complicated, not just for me, but for those players and admins, as well. When two claims overlap, should BOTH of the claims get a permission update when the player uses /trust? If so, how do I make it clear to the player so that he understands about that special case without making him read a manual? Similarly for the administrative /deleteclaim.
Well that would be nice. But I'm more talking about staying rectangle or square and just overlaying one on top of a part of another. And only subtracting the needed claim blocks for the "extra area" outside of a claim. For simplicity. Let's say you have a 2x2 claim (4 blocks). Then you make another claim of 2x2 however one block of claim two is inside one block of claim one. Now three blocks are subtracted from your claimblocks because you already owned one and you have an odd shape now made of two squares. We could possibly be describing the same thing in very different words. But that is the simplest way I can think to picture it.
I'm not a java coder but I am pretty good at the ideas behind programming in general. How exactly are you storing data points for claims? As two coordinates? If so it seems you could just take away the check for isThisLandClaimed for property the user owns but keep it for others. Then use some sort of mathematical x,z - x,z coord formula to figure out remaining blocks and subtract only those blocks. You still can keep your data system by just having all 4 points logged as claimed by said user. This keeping rectangular shapes method in tact.
@burtthaman
I'm not sure, but I think you're talking about sort of "glueing" two rectangles together into one claim to make an L, U, or donut shape, right? Damn, that's a big ask. The entire data strategy thus far has been based on the assumption that claims will always be rectangular, and I'm not sure it's even possible to maintain performance, elegance of implementation, and my own sanity without that tenet.
It's possible that after finishing aaaaaall those other features on the todo list, I might just wake up one morning with brass balls the size of boulders and decide to take on that design change. If I do it now, I risk complicating the code so much that I get buried in bugs and never move on to finish the other features. :) But I will definitely keep that in the back of my mind, in case the sun ever rises on that fateful day of unbounded confidence.
@bigscary
I still think you should add appending as well as resize. being able to move corners in and out is great but for odd shapes clicking on spot th making a square at other point without worrying about boubdaries is intuitive letting the plugin give you the extra blocks needed while keeping original plot in tact and only using amount of claim blocks needed all done in background.
Also Vault FTW. Much better than register
@ValawynV
Also, giving credit where credit is due... this "miracle" as you put it was brought to you in large part by the letter V. Thanks to the Vault team's coding and documentation efforts, I was able to add support for several economies in just a few hours. That feat would have been impossible without Vault (it probably would have taken a weekend otherwise, or I would have had to settle for supporting only one economy).
@TylerIsTooPro
What a crappy update too. They break bukkit for this junk? So pointless. Get some real content wait a few more months then release something mojang. Dumb.
@burtthaman
I understand your frustration. Last night, I was using temporary dirt or cobblestone blocks on Tyler's server to remind myself about the extents of my claim.
The next item on my todo list is claims visualization. The plan is for your claim boundary to be highlighted when you right click with the string, specifically I'll show glowstone at the corners, and a glass block every 5 blocks or so along the boundary lines. The visualization will last one minute(?), unless you use the string to turn it back off, or start another visualization.
Next will be claim resize. Plan is to use the shovel at one of the corners of your existing claim, then use the shovel again elsewhere, and that corner will move to the new location (assuming you have enough claim blocks for the new size). This is important because players get new claim blocks each time they play (under the default config), and this will eliminate the tedious re-adding of permissions each time you want to resize your claim.
And now 1.1 is out. fml :/
Well here is my server info if any one cares: mc.globoid.beastnode.net:25601 I will post the number ip later. If anyone cares it is 24/7, try out this sexy plugin.
@bigscary
I will gladly share my server's information with everyone here once I've got your plugin set up and running properly for the server. We're looking for new players, since we've just gone live (prior to Residence shutting us down again) and would welcome anyone that wants to give this plugin a try (and might also decide to stay. :P).
tested adminclaims a bit today. Two things:
1) Since there is no leave/enter message it is nearly impossible to tell where one claim ends so that you can "append" onto it, when making multiple claims near by without spamming right click on your string. And if you leave the area and come back and didn't mark it with something ugly to let you know the boundary... good luck figuring out the exact corner. Granted i can delete the claim and redo it making 1 HUGE rectangle but this means it is nearly impossible to do the "odd shapes" you are talking about.
2) When appending I can't overlap my claim which is understandable, but by default I think it should just add the blocks to the previous claim if I already own it. Possibly alerting me with a message telling me it did that. This would solve problem number one for the time being.
Very glad to have helped! If it's not a private server, please post your connection info here so others reading about the plugin will have a server to try it out on. :) Or if it is private, please consider sending me the connection info via private message so that I may come and visit. Thanks!