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 Oct 18, 2012@bigscary
I wanted to disable claiming in the world, but the only way I can think of allowing people to build is to grant them "griefprevention.ignoreclaims" for the world, which still requires them to enter a command. Maybe a permission we could add to a group for a world that functions like Mods.PlayersIgnoringAllClaims?
On second thought, though, I rather like the claim system, so that people are forced to fight someone if they want to steal and grief. Is there a way to let people wreck everything in a claim whenever they want, without using /siege, as long as the owner is inside their claim, or been in the claim recently?
I know this is kind of against what GriefPrevention was made for, but it has potential to make for a good Factions-like plugin for grief allowed worlds. I want the world to have a sense of anarchy, and formal organization kind of spoils it... but at the same time, people wrecking stuff with nobody around to stop them is no fun either.
-
View User Profile
-
Send Message
Posted Oct 18, 2012ok, i must be a derp, lol. So how does the math really work on this, with the rad of 4 ? Lets say i make it 8, will it then be 18x18 = 324?
Guess i would like to make it, so normal players can only get a one time , 20x20 area, then maybe my donaters , can expand but only up to like maybe a 100x100 block area? Dont want them overtaking the map, lol. Guess i cant figure out the math on it, since it goes by rad, not actual block size.
Also when we try to expand it say's must be larger then 10X10. So is it really meaning 100x100? Like 10X10=100 Blocks? That you need to expand? Sorry guess i just cant figure it out, and watching the vids, this is a really nice plugin, i want to use it. Thanks in advance.
-
View User Profile
-
Send Message
Posted Oct 18, 2012@Marenwynn
What specifically are you unable to disable for a world? I can probably help you configure for that.
-
View User Profile
-
Send Message
Posted Oct 18, 2012@bigscary
By any chance, would you be willing to put in an option to disable GriefPrevention for select worlds completely?
-
View User Profile
-
Send Message
Posted Oct 18, 2012Hey guys I've got an update in my pocket (on my test servers). Because it includes some changes to claim cleanup, I'm going to check logs later today to make sure I didn't wreck something, then let you guys have it. Here's the preview:
1. Options to change the expiration period for claims where nothing is built and which are free chest claims, separately from expiration for all claims.
2. Options to toggle automatic /restorenature those expired claims, even for survival worlds.
3. Updated /trust commands will accept permissions like abc.def.ghi without requiring brackets, so folks won't have to come read the documentation to figure it out.
4. A player who has permission to use /ignoreclaims will be told about /ignoreclaims when he tries to change something belonging to another player, again to stop folks from having to read the documentation (and post questions) here.
5. Lava will not light nearby blocks on fire anymore when fire spread is off.
6. Memory management improvement to eliminate out of memory errors on servers with lots of claims and few active players.
-
View User Profile
-
Send Message
Posted Oct 18, 2012@SyncCraft
There would be workarounds that I couldn't fix - for example leading an animal over to trigger a pressure plate for you, or tossing an item on a wooden plate. If I went a step farther to disable plates being activated by items and animals/monsters, then players would then complain that their redstone gadgets designed to be triggered by animals, items, or monsters don't work. :\ Since neither option will be good for all of your players, I choose to keep the player experience which is closest to what players expect from single player. Ask your players to use buttons or switches instead, OR add another layer of security using a button or switch before the player gets to the touchplate.
@ChilleCharlie
The next version, which I expect to release today, will have an option to not automatically restore land when claims expire.
Yes, it's true that an admin that doesn't know what he's doing can be far worse than a any griefer. The only reason to administratively delete a player's creative mode claim is to restore the land, since that's the only thing you can't do while the claim is in place. Therefore, I restore it for you when you delete the claim to save you time. If you want to resize, then resize. Players are given a grace period to change their minds, because they may not be aware of the risks in leaving a part of their area unclaimed. Admins are expected to understand the implications of removing a land claim, and it saves time to instantly restore the land rather than getting out the shovel, issuing another slash command, and then right-clicking each chunk individually.
You're right, I should somehow stop people who don't understand the nuances of the design from shooting themselves in the feet by changing the code. Unfortunately, I haven't figured out how to tell bad developers apart from good developers, at a glance. :) So I leave it up to the developer to decide whether he's doing the right thing or not. Although I don't agree that the change you're making would be best for everyone, you get major props from me for having the fortitude to step up and fix the problems in front of you, even when the task seems difficult.
@EnergyCraft
Damage values are not supported in GP versions which are compatible with Tekkit. When Tekkit moves up to 1.3.2, then you can update GP and then damage values will be accepted in your config file.
@matt531320
It's not possible to do this. Due to TNT physics, it's impossible for me to know that when TNT blows up inside a land claim, it was actually placed there by someone with build permission. See for reference: "tnt cannon".
@EnergyCraft
Very glad it works for you. :) But don't thank me, I didn't code the YAML file format. It's just lucky for me that it works.
@AuntieBeast
Please provide more information, for example detailed steps of what you do, what you expect to happen, and what actually happens. I don't quite understand your meaning in "trip wires don't work". :)
-
View User Profile
-
Send Message
Posted Oct 17, 2012Greetings again, BigScary,
We can't seem to get trip-wires to work right in claims. Any idea what setting we need to have for it? Or has this already been addressed?
-
View User Profile
-
Send Message
Posted Oct 17, 2012@bigscary
im referring to the danish language With the AE and A with a dot on the top and a O with a line over from the right top to the left button and thanks for the support i will try.
EDIT:
I tried and it's working!.
-
View User Profile
-
Send Message
Posted Oct 17, 2012@Sp33d3h
Yeah - delete the line in the messages.yml
-
View User Profile
-
Send Message
Posted Oct 17, 2012Could you make it possible to blow TNT up (on and above the surface) in your own claim? Along with TNT making TNT next to it go off - But so that if someone launches TNT out of their claim, it doesn't damage the ground? It would make a creative world a lot more fun for players who like to create cannons or other similar things.
-
View User Profile
-
Send Message
Posted Oct 17, 2012BlockIdsRequiringAccessTrust: [181, 181:1, 181:2, 181:3, 181:4, 181:5, 128:1, 128, 178] I tried to do blockid's but it wont work and spit out errors and reset the config. (sorry for my bad english)
-
View User Profile
-
Send Message
Posted Oct 17, 2012Ok,
I decided to proceed and continue cus this was bugging my brain for long enough. I managed to compile it and it works, no longer deletes anything inside a removed claim. It no longer checks for the size of the claim to be above 10.000 but above 1, and every claim is above 1 :) so voilla now your plugin is perfect :) though i still think many people have this problem and alot of sad faces happen because of it.. you should fix this it is not a feature it is a problem, a serious one. and now that i fixed it for myself, but you should do this for anyone using this thing, dude this thing is ANTI grief, not GRIEF... on top of that this is using up valuable resources and causing more overhead then is needed. Let me explain.
Who can remove creative claims? ;) right... an admin can nobody else ;) Is it so much work for the admin to first do /deleteclaim and afterwards do /rn or /rnf or use worldedit so at least they can undo it? and click a few times that it HAS TO BE automatically done instantly? no questions asked? without confirmation or undo? i say no, ive seen this do more damage then the worst case scenario a griefer can do to your server...
Oh well, im done i learned how to work with Eclipse, i have succesfully compiled my first thingy in java, even though it is offcourse your code :) by the way, anyone who is doing the same (and i guess many people will want this), dont forget to import Vault.jar the same as you do with craftbukkit.jar, or it wont compile, you can forget it ;)
Ill look into your code abit more the upcomming days, and i think im not giong to create a second .jar, instead ill make a new class for the flags and provide it to you, its up to you to either give your users it or decide not to implement it at all
Best regards, Charlie Teeuwen
-
View User Profile
-
Send Message
Posted Oct 17, 2012Hey bigscary,
I found your source -.- should have found it way earlier though lol... im quite new to all this. I found also a solution for the pvp issue with the plugins, though it is a very nice feature which i would love to leave enabled in certain worlds but thats a later thing, i have set the pvp timer to 0, which according your code should work, and it does. So anyone having this issue, just change this to 0 in the config: CombatTimeoutSeconds: 15
I have also found how to remove the auto rollbacks of the creative world :) however im a n00b with java XD and i cant seem to get it to compile in any way... so... i think i am importing wrong or something, i am adding the bukkit jar file, thats not what im doing wrong.. oh well ill figure it out when i have some spare time. Our host decided we had to migrate to a faster server and stuff was a little stressy today :) so havent had much time to investigate, tommorow i have sollicitation, so tommorow no time either :) But basically i just commented out the creative part in the part of the code that does the deleteclaim xD and i bet it should work once compiled... although in my oppinion this is not something a developer should let its users do via the source code >.< especially not a developer with your skills, you are a really good programmer and i admire your quality, your code is nice and clean, very good documented with comments :) i learned alot from just looking at it :)
I will, when i have the time, figure out how to compile this, and after that my next step is flags :) the flags will be in a seperated jar though as you have requested, and i will send it to you when im done, (if i manage to get it working without issues that is) i must say im not even close to your skills so... :) oh well i think ill get it working :) will let you know, but i seriously state this will take some time for a beginner like me :) this is my first ever java attempt ;)
-
View User Profile
-
Send Message
Posted Oct 17, 2012@SyncCraft
Cool idea SyncCraft. Pressure plates would fall under the catagory of buttons and switches, no doubt. :)
-
View User Profile
-
Send Message
Posted Oct 17, 2012Hi, is there a way to stop players using pressure plates inside claimed land? If so, please tell me :D and if not, would it be possible to add it?
Thanks.
-
View User Profile
-
Send Message
Posted Oct 17, 2012@RasCas
I get where you're coming from regarding attracting zombies. But stopping players from exploiting game mechanics for their personal gain (as opposed to ruining the fun for other players) isn't a job for an anti-grief plugin. You might want to look into the "Extra Hard Mode" plugin, which has an option to stop players from using monster grinders. You'd probably want to disable a lot of the other features, though.
@WartyWarlock
It would be a lot of work for me to add what you're describing. Let me try to give you some tips which could save your time.
1. You can use /acb while players are offline, so you can use it before the club starts for the week.
2. If you want to give claim blocks to ALL players at once, assign a permission to all players using your permissions plugin's config file, then use /acb [permission.node] amount.
3. There's a "grief prevention real estate" plugin which may or may not help you with your "players transfering claims to other players" problem. May be worth looking into.
@JAG100
I'm sorry to hear you had a bad experience. Since I'm not doing anything with respawning, the problem is likely in the survival games plugin. Good luck!
@rjad
Check two options - first, claims should not be required in survival worlds. Second, ensure your survival worlds are NOT listed under "creative rules worlds".
@ChilleCharlie
Hi Charlie, thanks for the detailed report. The fix for this is for the survival games/capture the flag plugins to actually allow the players to die properly rather than just teleporting them somewhere else. Their dropping items can even be stopped and put back into their inventory after they respawn, if that's needed. The reason for this rule is to prevent PvP players from using commands like /home to avoid losing a fight, which can be a real problem where pvp campers are concerned.
About the claims resize, do you really want a fix which will enable you to spend all your time babysitting kids? If they can't follow what they saw in a very short video when it involves no slash commands and only mouse clicks, then maybe they have no business playing Minecraft on the internet, which is full of jerks who will ruin their fun. Anyway, I will reconsider - your detailed description of the issue helped me understand your view. :)
@LeChuuck
Yeah, what RasCas said. But... it only pops up once per 25 placements I think, and common blocks like torches, dirt, and cobble don't pop the message. Is it really annoying you?
@RasCas
I haven't heard of that from anyone yet...?
@freakyy85
/IgnoreClaims. But beware, they will also be able to change anything anywhere, so don't give the permission to anyone you don't fully trust. The next version will have a help message appear to tell folks with the permission about the /IgnoreClaims command.
@EnergyCraft
Sorry, I can't read that. Whatever language you're referring to, you can edit messages.yml to give it a try. There's probably a list somewhere of all the languages supported by the YAML file format.
-
View User Profile
-
Send Message
Posted Oct 17, 2012Is there any way to give moderators etc. the possibility to look inside chests?
-
View User Profile
-
Send Message
Posted Oct 17, 2012Regarding Shopkeepers Plugin and Griefprevention, anyone here having Problems with walking away or vanishing Shopkeepers?
-
View User Profile
-
Send Message
Posted Oct 17, 2012@LeChuuck
sure take a look in the config. ;-) WarnWhenBuildingOutsideClaims: false
-
View User Profile
-
Send Message
Posted Oct 17, 2012Hey
Got a question, is there any way to disable that message when you build in unclaimed land?