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 Sep 6, 2013Are the Claims created by a chest everytime protected from bedrock to sky?
-
View User Profile
-
Send Message
Posted Sep 6, 2013@BC_Programming
RustyDagger sits back in chair and looks at BC with evil eyes. And Yells Dam you!!!
-
View User Profile
-
Send Message
Posted Sep 5, 2013@BC_Programming
well i watch like a crazy woman and its big enough to be safe. Likely this is the issue. We'll get if worked through.
-
View User Profile
-
Send Message
Posted Sep 5, 2013@Awsmpossum1313
For the claims disappearing thing I'm thinking it might be /abandonclaim since I believe as it is currently, any trusted player can use /abandonclaim. I'll still give it a go since the repro steps are pretty simple once I get a chance to do so.
@RustyDagger
This is not necessary >:( Best I can tell if it's not working would be an issue from reference equality. The override logic is considered only when the location for the rule being tested is determined to be within a claim that is under siege. It then sets the override based on whether the player is the attacker or defender. I compare the references directly so I think that might be messing things up. I'll change it to compare the Names of the Players instead (which is used pretty much everywhere else anyway).
I already changed that to configure through config.yml in my current working copy :P I guess you have that to look forward to at least, heh.
I'll probably spend a few hours on GP now. I have a bunch of "real" work piling up (not sure what else to call it) so I'll probably end up working over the weekend. Hopefully I can get enough time to try the offline suggestion, which should make working on the Siege and PVP related additions easier to test.
-
View User Profile
-
Send Message
Posted Sep 5, 2013@BC_Programming
Hey BC? Is there a donor link. I dont have a lot but figured i could send you enough for some beer and a pizza for the hard work.
-
View User Profile
-
Send Message
Posted Sep 5, 2013@BC_Programming
Was adding those bits to my config meant to make things happen or just look cool?
Im unable to get any of them to do any thing I added siegeDefender Allow to the containers section and the defender can't open chests or other containers during a siege.
build 169 also seems to of broken the breakables list all the destructible blocks are unbreakable saying that the area cant be built in because the defender is in a siege ( derp i know that i'm attacking... ) I suspect the breaking issue is related to the new rules your working on so that's fine.
I also tried allowing both attackers and defenders filling and emptying water buckets Neither worked.. a rule for dropping items during pvp would be handy also I hate that rule. Pointless what am I going to do fill his inventory with cobble? if I screw up and drop my sword sucked in on me.
Also I have a way that you can do some better testing. Offline mode will allow you to login with 2 players with different names just run both the server and both clients in offline mode. ( I Bet you get real sick of that Hour long cool down real fast it slows my testing down So much :(
-
View User Profile
-
Send Message
Posted Sep 5, 2013@BC_Programming
As A defender i was able to break blocks in my claim yes. ( keep in mind i was using 150 ) I don't fully agree with blocking the claim owner from building or breaking at any time its their claim after all. if a player is attacking me and i need to break a wall to run away i should be able to do that if i need to place a block to slow an attacker down I should be able to do that.
This seems to all be coming down to personal taste. I think the config rules are a step in the right direction and the building / placing rules should let me control the siege a whole lot more can't wait :D
I will be updating to 169 later today and will have some good testing done in the coming days. always welcome to stop by my server and see GP Siege pushed to its limits.
And regarding the whole config to complex and people complaining honestly not adding all the siege stuff to the file makes it a ton more complex than having it I honestly don't see how people find it complex it could not be any more clear is the same block of settings for each event its like you can be playing and notice TNT is not doing what you would like oh easy fix just find TNT in the rules and change a few allow and deny around. The only people complaining are the ones that are too lazy to spend 10 min reading the new documentation page yes that page could be a little less uh how to say this uh Jumbled an actual copy of the file and comments explaining each setting/line might help idk. my point is hidden settings are far more complicated than settings sitting in a file and not knowing what they do. Its just a huge change from the old file and its opend many many doors. essentials config is still worse.
The PVP setting is a little confusing at first I was thinking like why would you stop some one pvp with a lever ... then I realized its using the lever during pvp and that makes a lot more sense. Maybe PVP is a little misleading as the name. i think it needs extending to duringpvp or something.
-
View User Profile
-
Send Message
Posted Sep 5, 2013@BC_Programming
It appears to be pretty simple.
1. Create adminclaim larger than 100x100. Lock it. I have always /accesstrust public (no idea if that makes a difference)
2. Create a player claim that is touching its border. Reboot.
3. The admin claim is then gone.
I've worked around this by putting a 1 block wall around the boundary and then putting the claim inside that wall hoping a player doesnt get cute and claim the wall itself. I have had a lot off issues with my adminclaims vanishing. I have a question can players abandon any claim they stand int or ONLY ones they are trusted in. If its any then this may way be the issue completely because i am trusting public any player that types abandonclaim while standing in the spawn claim removes the spawn claim. I will test; this would make the border thig a read herring.
-
View User Profile
-
Send Message
Posted Sep 4, 2013@Awsmpossum1313
Hmm... I'm pretty sure I thought of this requirement while considering how trash blocks could be reworked. They act different in a few different situations. I know "CreativeRules" toggles a behaviour. It's name is misleading (in fact the name "Trash blocks" is
misleading, really). You can enable "creativerules" Which sort of toggles.some of the behaviour, such that <only> trash blocks can be broken outside of claims, which would prevent mining outside claims if Ore is not a trash block.
Right now there isn't. a way to prevent trusted players from using /abandonclaim. Seems reasonable though, I'll try to work something in for that.
The bold part is more interesting. And seems fairly serious. Do you have any steps to reproduce? @RustyDagger
Yes. They are not added automatically because people were complaining the configuration was too complicated, so some nodes/info is only actually placed in the configuration if they aren't set to the defaults.
It doesn't. I never said it did. Right now Block Placement and Breaking have already been changed into their own Rules, they just aren't exposed in the configuration yet. Once they are you can use the Siege override nodes/values to change what players can do on a claim during a siege.
Yeah that was on purpose. Reading the code however it should not be letting anybody but the attacker actually break blocks anyway, is that what you are seeing? The Siege stuff is the trickiest part because I don't have a good way of testing it. I disable the check to prevent a player from seiging themselves which acts a bit weird but seems to work for basic testing.
-
View User Profile
-
Send Message
Posted Sep 4, 2013Is there a way to do /giveclaim for a player that is offline?
-
View User Profile
-
Send Message
Posted Sep 4, 2013@BC_Programming
Ok I see the new rule parts for siege now.
I take it I need to manually add them where I need them Like the require permission?
I still cant see how this lets me enable building during a siege. Unless I was to maybe use the trash blocks settings? that way i could limit what was place able as well. One more bug I did find any damage to the fort by the defender was not restored. Intended?
-
View User Profile
-
Send Message
Posted Sep 4, 2013Hello!
Yes me again ..:-| Is there a way to lock down what players can or can not break outside of their claims. I have looked and searched and most of the the things i find are about trash block placement not about breaking. It would be great if you could disable break all ore types so people are forced to mine in their claims or in another world.
This may be available but i can not find it. I am also having some trouble with claims being abandoned by trusted players. Is there a way to make this available ONLY to the owner? Otherwise it also seems that if someones claim touches the border of an admin claim it makes the admin claim disappear.
You all are great and I appreciate all the hard work. Thank you yet again for all the hard work.
-
View User Profile
-
Send Message
Posted Sep 4, 2013@xOMutleyOx
If you are using the development build, GriefPreventions permissions have been changed. The perms should be documented near the end of this Page.
If memory serves GriefPrevention.Claims was changed to "GriefPrevention.Claims.Allow", and players must have "GriefPrevention.Commands.<commandname> permission to use any command <commandname>. The defaults are still being worked out.
-
View User Profile
-
Send Message
Posted Sep 4, 2013Is anyone reporting issues with /trust command ?
All permission nodes are correct and am using bPermissions.
Yet no-one can do /trust on there own landclaims.
-
View User Profile
-
Send Message
Posted Sep 4, 2013@RustyDagger
I know because its a dev build its not well documented
The dev docs cover this already. In the documentation for the Rules.
-
View User Profile
-
Send Message
Posted Sep 3, 2013My FortWars server is running this plugin as its Core Plugin the things I am able to do with it are Awesome I can't begin to thank you enough.
I am still using build 150 I Like some of the changes like the permissions and the Moving of Siege to the new rules system But I'm yet to have time to really test out and find a really stable build that don't have any thing major broke any idea's ?
I just downloaded 169 and went looking in the per world files and i cant see any changes. iv even deleted them and let the plugin make them again. one of the changes listed was moved siege to new rules system so where are the settings for that located I also cant find any referance to the building during siege in the config at all help? I know because its a dev build its not well documented Help :(. Id much like to use the newer features.
My players are building floating platforms so they can't be siege because the attackers cant get up...
I was expecting to find:
in my config :( had me all excited
Atl east some config for that hour long cool down would be super handy too and allow me to increase the pace of my server a little when low players are online in 20 min you could of attacked every one online then run out of stuff to do not so great.
-
View User Profile
-
Send Message
Posted Sep 3, 2013@Raginshunter
GriefPrevention doesn't work with BukkitForge, and it won't until BukkitForge is fixed. The preferred alternative for running Bukkit Plugins with a Forge server is to use MCPC+.
-
View User Profile
-
Send Message
Posted Sep 3, 2013ok im having severe issues with GP and cant seem to resolve them.....
i have tried the following to resolve this issue..
1) Removing the plugin and all files 2) reviewing my code and replacing it 3) restarted the server
I am running a FTB Forge server am using the correct version for my software and my players cant create calims i have given them perms it allows them the use of the golden shovel and when they click in 1 corner it says claim created or that the claim overlaps another when there are no claims in the server. Or it just says they dont have enough blocks for a 30x30 area when they have over 100k claim blocks available. also when setting a claim it says "claim block set" then under that msg it says Claim created but we only set the first block and havent set another one any help ?
-
View User Profile
-
Send Message
Posted Sep 3, 2013Thanks _Snoogles_ and BC_Programming :)
-
View User Profile
-
Send Message
Posted Sep 2, 2013@Awsmpossum1313
I believe you told me as long as they were locked they should remain.
They should. GriefPrevention does not delete them through claim cleanup if they are locked.
@vinilly
The players were happy and the one day the spawn are admin claim disappeared and it was reduced in size griefprevention said it some how still had it there but when I would fly around it wasn't physically there.
The only time I've ever seen this was in an early dev build. I believe somebody posted a video on the behaviour which I looked into and to the best of my knowledge fixed. I suppose it could be a bug in 7.7 or earlier but nearly everything has been changed in 7.8 to the point of eliminating or moving older bugs or at least replacing them with new ones, meaning that issues with 7.7 and earlier are obsolete in terms of the current codebase.
Doesn't sound like a very thorough investigation. If it was in 7.7 it was probably claim cleanup. claim cleanup is a giant mess, but it was a lot worse then, too.
Removed griefprevention now I keep looing at this site to see if it will update
There is a dev build mentioned in the first paragraph of the overview. There is no Beta or Release because I do not have the time to support and watch the comments/tickets 'explosion' that will result from updating either one to the current development build, nor do I currently have the time or inclination to go through all the existing documentation and update it, which I would have to do at pretty much the same time.
@thedragoness
Multiple-world configurations and more granular control over what is allowed and denied inside and outside of claims can be found in the newer development builds, the config info is linked by _Snoogles_. There are rules that can be changed for Lava and Water placement.