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).
@Tux2
you mean a sort of land thats marked as claimed so no one else will claim it, aka a NULL Claim?
@bigscary
Thanks! I appreciate that. Also, since you don't have tickets enabled for this plugin I would like to suggest something: I would like to have a way to have an "admin claim" that would basically claim land but not apply any sort of protection to it, that way I could apply protection via residence or another protection plugin while still not having users plopping chests in it and calling it theirs. (aka: put a chest in their store). I'm sure the chest thing would be extremely rare (who would have a shop without a chest somewhere else), and would be preventable (just make sure they already have a residence), but having to make 4 narrow admin residences around the mall so that players couldn't accidentally claim part of the mall while making their claim is kind of a pain.
@mrcheesete0
i think all the areas remain admin claims until you assign them an owner
@bigscary
are you sure? doesn't it say "the block is apart of <player> claim? :P
If I were to go /adminclaims and claim a HUGE (say 500X500) area, then /subdivideclaims and make small plots in the huge area with pathways between the plots NOT subdivided, and leaving some plots NOT subdivided,
would it make it so any of the smaller plots, are private claims that need /trust to do anything? Or would it make the smaller areas also admin claimed areas?
@Tux2
You'll have to use residence or another plugin, because grief prevention's claims always reach all the way to the sky. I made that design choice because it reduces slash commands and eliminates griefing by overtopping, and also makes the visualization nicer. But it does mean that you can't stack two claims on top of each other.
Question, I have a mall area with several stories where residents can have stores in. Is there any way to do cuboid protection within a small confined area at the moment with this plugin or will I have to continue using Residence for that?
@bigscary
+1 to that...
i was eaxplaininh this yesterday, griefers are indeed lazy, if griefing costs them something, they just dont bother
also its even more simple with ur chunk restore, so now u can regen chunks and no destroy calims (which would be injured anyways :P)
@Kane_Hart
If you don't want players to get the free chst claim, you can disable it by setting its size to a negative number. Again read admin details link.
Also, limiting players to exactly one claim is trouble. There are many situations where non-griefing players will benefit from having multiple claims. Consider oddly shaped claims around houses which try to include pastures or fields, claims to protect nearby wildlife areas like streams, claims to protect roads they build, and claims to protect house/field/pasture when those areas aren't adjacent.
I think you're over-thinking. I've been running this plugin on a public (and advertised) server for weeks now, and nobody has tried to grief by amassing blocks and making multiple claims. You may be imagining problems that are very unlikely to manifest - griefers are lazy, and there are plenty of servers out there where they can grief without having to play on the server for many hours as a prerequisite. Consider just adding an AFK kick plugin, so nobody can idle to get blocks.
The griefing strategies you're concerned about are possible, but not even close to practical. Griefers like to log in somewhere they haven't invested, wreck house, and post it on YouTube. They lack the patience to wait it out, and with the /deleteallclaims <player> and /ban <player> commands, you can instantly undo any claim-based grief which would have taken many hours to prepare. If a griefer is smart enough to figure out how to use claims to grief, he's also smart enough to realize it's a complete waste of his time because hours of his hard work are seconds to you.
@Kane_Hart
Claims are on for all worlds, or off for all worlds. I am planning to add world-specific configuration, but I just haven't yet.
Without user interaction, there's no way to know where to place the claim. You can make all claims deeper via a configuration variable. Check out the admin details link above. The depth is relative to where the player placed the claim, though, rather than set at a specific world depth. Consider the fairness of the current system - by making claims shallow, you're preventing new players from claiming the valuables in an area they haven't even explored yet by simply placing a chest.
No, there's no way to limit the number of claims. The small minimum size for claims makes micro claim griefing difficult to pull off because one has to amass lots of claim blocks, then go about patiently creating those claims. Consider that to surround even a newbie claim with other claims, you'd need four times the claim blocks the newbie has, and it's not much of an achievement to temporarily block a newbie. The difficulty grows (non-linearly) as the claim gets larger.
You can't do an up-front charge when a new player joins the server, but you could just configure iCon so that they have less initial money, OR you could configure grief prevention so that they start with zero claim blocks. If you want players to ONLY gain claim blocks through the economy, then just disable claim block accrual (see admin details link). The claimed blocks limit applies only to accrued blocks, not purchased or admin-gifted blocks.
@cvxx7q
tested the cases, if i break a claimed 97 no silverfish will spawn,
if i use silk touch i get regular stone
so in a Survival server the silverfish are no problem really :D
i dont know how the hell i got ID 97 but in future im checking wat i get from the creative menu!
thanks for your effort bigscary, hopefully wont send u on a wild chase again :S
bigscary the silverfish are no problem for me now, somehow i was getting ID97 from the creativ emenu (possible bukkit bug back in R1) the only think i can see as an issue is if someone uses say silk touch (untested) and takes the 97 from a strnghold, makes a house and then if a silverfish was bashe dnearby the house wud rip apart, or perhaps if the block was broken (while protected) mc may catch this and spawn the silverfish, i will test that soon 9unless u beat me to it)
sorry if i have sent u on a wild goose chase :S
@Kane_Hart
if you want them to make 1 claim thats 20*20 and they have to move this claim around (abandon and reclaim) use this config
the Radius is ten but the claim will be 20*20 (i think 21*21 to be exact)
have a tinker with that if its 21*21, change the 400 to 441
@cvxx7q
Oh crap I mean 20x20 but I assume same thing but 20 and 400 :P Thanks, I will play around with it but I'm going have to disable the chest placement hehe.
Okay so whatever settings I put and with (AutomaticNewPlayerClaimsRadius: -1) I can't get a user to claim around 20x20 area. They can claim 10x10 3 times maybe 4 not sure 100% think they be off a couple blocks but they can make 3 claims and that I really don't want.
This a example: 2012.02.09.04.20.15 400 0 build;-55;53;-64;;build;-45;54;-64;;build;-35;54;-64
@Kane_Hart
easy
set initial to 400
and accrued to 160000
and set the hourly accrue to 0
they will always only get 400*400 claim and nothing more, id they abandon they can claim 400*400 somewhere else ;)
@cvxx7q
Thanks for the info. Yeah I guess the part I wanted is not the new player radius for chest but forced one period. I wanted to make players claim 400x400 nothing else and no more. I really don't want idiots grabbing bunch small plots and such. That alone would be a wicked grief haha.
But thanks for the info anyways.
What I will do is prevent chest placement and then I think it could be set to one world only.
@Kane_Hart
well only give them 32 blocks of depth, this way the ONLY way your noobies could interfere with the underground is if they dug right down to level 34 then claimed (its not impossible but unlikely) or give them 16, i think the 128 is fine, but if u let ur players claim upto 100K at a time u may find HUGE claims in and this can be an issue,
a clever sort of "limit" u can impose is set the max accrued from 80000 to say 100(maybe 1000) or something, and the depth to 16/32/64128, there is certainly a point where any claim extension is higher than this and therefore is not possible to make larger so evne if they claimed with 128 depth they cant make huge claims, just lots of small ones
you CAN alter the default 10*10 to a 20*20 claim here.
per world activation is probably going to be considered, although with the 1.2 Update around the corner Bigscary is going to bug fix and add little bits here and there, major updates will be after 1.2 bugs and issues are cleared
damn BBCode sucks on here.. XD
@cvxx7q
See I would love to set mine to 128.. BUT cap it at say 25 depth so that people can mine 25 and down without any issues at all. Maybe that is wishful thinking :P
Also I really wish there was a config for the 10x10 and such to make it 20x20 but not only that I wish there was permissions for chest placement for the system..
I only want this feature enabled in my PVE world that is for guest players. But now when a player places a chest in the main world it activates. I guess I could remove it but then the plugin would not be so newbie friendly in the pve world ;)
@Kane_Hart
claim depth is in the config file...
however u cant limit claims to a range height, for example u cant sotp claims being made under level 63 etc
i have my claim depth set to 128 (overkill i know)
but thtas just because i have special admin claims which run ver deep underground and i do not wish to have to do them again XD
@Kane_Hart
1) I second this and hope it gets implemented.
2) This would be useful as well.
Thanks.