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 May 19, 2013I'm new to Grief Prevention, and as far as I've seen, the only TNT protection possible allows players to place TNT everywhere, but they will only destroy blocks below sea level.
I'd like to know if it's somehow possible to allow players to use TNT only inside their own claims, at any altitude.
-
View User Profile
-
Send Message
Posted May 19, 2013@JerryFord
Thanks!
-
View User Profile
-
Send Message
Posted May 19, 2013@JerryFord
it protects villagers (since they are a Creature) except on admin claims, in which case villagers can take damage from monsters.
-
View User Profile
-
Send Message
Posted May 19, 2013BC-
ProtectCreatures = true will protect the claim livestock, but I think it is protecting villagers residing on the claim also. Is there a current setting that will allow villagers to be turned or killed by zombies, yet protect them from being harmed by players?
Dutch_Boy-
That config will award the player 100 blocks of online hour.
-
View User Profile
-
Send Message
Posted May 19, 2013Hello,
BlocksAccruedPerHour: 100
This is for give players 100 blocks every hour?
Kind regards,
Dutch_Boy.
-
View User Profile
-
Send Message
Posted May 18, 2013@saintcrime
Claims cannot overlap in the X/Z coordinates, and the resize logic prevents claims from being extended down past the maximum.
If you do file a ticket, give a precise list of steps to reproduce. (as opposed to a narrative of them)
-
View User Profile
-
Send Message
Posted May 18, 2013@BC_Programming
Ok, Just did some testing, not as admin BTW just in BasicClaim mode. Here's what I found.
With MaximumDepth: 60 ExtendIntoGroundDistance:0
Claimed at 64, claim was only at level 64. Dug down, claim did not extend down at all. claim stayed at 64.
Made another claim same settings as above, but one corner at 58, other at 64. claim was made, still did not extend down with digging. but created beyond the MaximumDepth: 60.
Changed settings- MaximumDepth: 60 ExtendIntoGroundDistance:1
Claimed at 64, claim was at 64 and 63, so initial level and 1 block down into ground. Dug down, beyond level 60, claim extended down, stopped at 60. So, it worked. in that case.
Same setting as last test.
Went into a hole. claimed at 54 and 58. GP says claim made, charges blocks, shows markers etc. When I click the ground with a stick, it makes the markers disappear and says, No-one has claimed. I get out a Diamond Pick dig down, still no extending stick shows No one has claimed. So, i get out shovel and try to claim in the same spot, it says I already claimed this spot and it will overlap and to re-size. So, i go to re-size, and the golden shovel when clicking inside claim shows markers again, stick get rid of them, i click with the shovel to show marker, find a corner re size a couple of blocks. Now it's a real claim, stick works etc. Other char can not place blocks etc... Claim owner with everything working, dug down....claim does not extend down, stick says, no one has claimed. I go but up click with stick No-one has claimed. I use other char, and their stick now says No-one has claimed. and can place chests, blocks break, etc.. but Shovel says I can not build here because it would overlap Claim of the Owner.
So, definitely something complicatedly wrong here lol. I would post a bug/ticket, but Not sure how to word it. What would you want me to do?
-
View User Profile
-
Send Message
Posted May 18, 2013I would have to look at the source to figure out exactly what those are doing.
It looks like it's only used for setting the maximum depth a player can create their first claim by placing a chest, as well as the maximum depth a claim can go to.
It looks like ExtendinfoGround let's claims go below the specified maximum depth, and the way it's written it looks like that was the intention. Why that is the case, I don't know.
-
View User Profile
-
Send Message
Posted May 18, 2013Ok, another quick question :)
I understand the usage of these in the config:
ExtendIntoGroundDistance: 5
MaximumDepth: 0
Yet it did not work as I thought it would. What I tried or was planning was to have the bottom levels say from 0-20 not be claimable to allow the very bottom area of the worlds underground be traveled/mined beneath all claims. So, I set the MaximumDepth: to 20... Assuming that claims would not go below that point. Then I set the ExtendIntoGroundDistance: to 200 just as a test. At level 64 I claimed land. Yet the claim went beyond the MaximumDepth setting all the way to bedrock. I expected the claims to always NOT go below the MaximumDepth. Is MaximumDepth only a setting for the actual use of the Shovel, like what levels the shovel works at only? From what I've seen, even if I set MaximumDepth at say 64, then claim at 65 with an extend into ground distance of 5, then the claim would go below 64.
With that said, If I was to have the ExtendIntoGroundDistance: set at 0 or 1, and the MaximumDepth: set at say 20, Would the following happen, "If claimed at level 20 claim goes no further down even if you dig, if you claim at say 64, your claim would be 1 block into ground, then when you dig down your claim would extend as you go down but stop at MaximumDepth: 20?"
I guess I expected MaximumDepth: to always be a check for claim depth even with a setting of ExtendIntoGroundDistance: set at a value that would go beyond, but MaximumDepth; would stop the claim from the initial depth at the MaximumDepth value. The reason for the Higher ExtendIntoGroundDistance: would be so if someone was on a mountain top and claimed, the claim would go down to the MaximumDepth: but not farther down into the lower level that I wanted unclaimable.
I hope I explained this well.
-
View User Profile
-
Send Message
Posted May 18, 2013@BC_Programming
Thanks BC_Programming, Now I know and Knowing is half the Battle!
:)
-
View User Profile
-
Send Message
Posted May 18, 2013@saintcrime
There is logic to automatically abandon claims after they reach a certain age, and the players haven't done enough in them, etc. the AutomaticNatureRestoration setting determines if, when those claims are automatically abandoned, whether they will automatically be 'Nature restored' as well.
"AllowUnclaimingCreativeModeLand" determines whether players are allowed to abandon or shrink their claims in creative worlds. "AutoRestoreUnclaimedCreativeLand" determines whether that unclaiming will restore nature.
Hope this helps :)
-
View User Profile
-
Send Message
Posted May 18, 2013Hi a couple of Questions...
Can you please explain a bit more on these config settings, I am unable to find documentation. Thanks :)
AutomaticNatureRestoration: SurvivalWorlds: false CreativeWorlds: true
AllowUnclaimingCreativeModeLand: true
AutoRestoreUnclaimedCreativeLand: true
-
View User Profile
-
Send Message
Posted May 17, 2013@BC_Programming
Ah, thanks for the quick answer. Guess now I just have to wait for the next release then wait for the server admin to up date the plugin.
-
View User Profile
-
Send Message
Posted May 17, 2013@fuzyfeet
That was made an option in a dev build, the details and the appropriate ticket can be found here:
http://dev.bukkit.org/server-mods/grief-prevention/tickets/74-cacti-not-breaking-minecarts-inside-a-claim/
-
View User Profile
-
Send Message
Posted May 17, 2013Anyone know of a way to make minecarts breakable. I'm trying to make minecart stations but cati and lave don't break minecarts (though lava does break rails).
-
View User Profile
-
Send Message
Posted May 17, 2013@LandmineGT
What do you mean? I dont really get it. We dont have turtles on the server. And you cant destroy anything with a normal block of stone. Tried it with a normal member.
-
View User Profile
-
Send Message
Posted May 16, 2013BEST PLUGIN EVER(AND THE EASIEST).
-
View User Profile
-
Send Message
Posted May 16, 2013BC_Programming; First of all, props man! Have been using this since way back and have loves every minute!
When I made a new seed generation for my server and transferred the config and .jar only: my players as well as myself have stopped gaining accrued claim blocks. How can I fix this?
-
View User Profile
-
Send Message
Posted May 16, 2013@Dutch if your sever allows turtles or other blocks to break blocks then they can use the turtles to destroy any block they want.
-
View User Profile
-
Send Message
Posted May 16, 2013Oke hmm sucks. Because someone destroyed allot of the railway we made + stole allot of dia and emerald :(
Normal member permissions. So i dont know how he did it.