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 Jun 10, 2013Just to make this clear:
DEV BUILDS ARE NOT RELEASE BUILDS.
DEV BUILD=DEVELOPMENT build. so it has WHATEVER we happened to have in it while testing, including ANY AND ALL debug messages. if this is a problem DO NOT USE DEV BUILDS!
-
View User Profile
-
Send Message
Posted Jun 10, 2013@BC_Programming
Ah alright. Thanks for the replies. I appreciate it.
-
View User Profile
-
Send Message
Posted Jun 10, 2013I love grief prevention, but it is spamming my console to the point of feeling like a ddos attack. it has made using my console to communicate with players literally impossible. for this reason i may be searching for a new plugin to replace it. the config file is poorly documented so i have no idea how to stop the ridiculous spam in the console. i would like to disable all console spam but this plugin simple insists on being in your face with useless information.
[Info] ClaimBehaviour [Info] ClaimBehaviour [Info] ClaimBehaviour [Info] ClaimBehaviour [Info] ClaimBehaviour [Info] GriefPrevention: Enderman pickup has been disabled for this area [Info] ClaimBehaviour [Info] ClaimBehaviour
about 5 times per second.
-
View User Profile
-
Send Message
Posted Jun 10, 2013@BC_Programming
I was under the impression the block bank was the economy account where all money from players buying/selling claim blocks comes from, but the usage string in the plugin.yml indicates an 'amount' argument, maybe that's a mistake?
-
View User Profile
-
Send Message
Posted Jun 10, 2013@GamersSynergy
I haven't implemented SetClaimBlocks yet. SetBlockBank doesn't even seem have an implementation so I have no clue what it's even supposed to do, since I didn't add that.
-
View User Profile
-
Send Message
Posted Jun 9, 2013will this work with 1.5.2?
-
View User Profile
-
Send Message
Posted Jun 9, 2013@BC_Programming
I forgot to mention that while in game, and typing /setclaimblocks name blocks, it doesn't work. It actually just outputs the "/SetClaimBlocks <player> <amount>" command each time I try to type it. /SetBlockBank <player> <amount> does the same thing.
-
View User Profile
-
Send Message
Posted Jun 9, 2013Hi, awesome plugin. We're using it for a PvP server, and had a couple of requests for some additional config flags.
1. A flag that disables the automatic item transfer in siege mode, because this interferes with some other plugins and it also doesn't seem to take the armor slots into account.
2. Lots of players are using siege mode to grief the nature around bases instead of breaking and entering. Would it be possible to restore the damaged blocks after the siege has ended, when the player gets ejected from the claim?
Thanks!
-
View User Profile
-
Send Message
Posted Jun 9, 2013Quick question. Is it possible to allow players to break only certain blocks outside of their claim areas? Such as just Dirt, grass, stone , logs & leaves. Been trying to accomplish this for a day now figured it was time to ask. Thanks
-
View User Profile
-
Send Message
Posted Jun 9, 2013@GamersSynergy
A few builds ago, I fixed a rather large logic error in how configurations were saved, which was causing the 'core' config.yml file to get overwritten with the contents of a world configuration every time that world configuration got saved. That's probably why the setting appeared to be missing, since it the config.yml would be constantly overwritten with world configurations.
-
View User Profile
-
Send Message
Posted Jun 9, 2013@BC_Programming
Neither of those were in the version I had previously. I installed one of the latest dev builds and I now see those settings properly. Thanks.
-
View User Profile
-
Send Message
Posted Jun 9, 2013@GamersSynergy
GriefPrevention.Economy.ClaimBlocksPurchaseCost or GriefPrevention.Economy.ClaimBlocksSellValue must be larger than 0, and a compatible Economy plugin must be installed. The above two values are found in config.yml.
-
View User Profile
-
Send Message
Posted Jun 9, 2013@Firdausfazil
If you have fiven people permission to use the command, then you need to make sure you have a price set for the claim blocks
-
View User Profile
-
Send Message
Posted Jun 9, 2013@Firdausfazil
This. I can't find anything in the config or the world specific configs regarding this.
-
View User Profile
-
Send Message
Posted Jun 9, 2013How to enable /buyclaimblocks
-
View User Profile
-
Send Message
Posted Jun 9, 2013Either when I get around to it personally
Just read this back and it sounds a bit wrong- When I said this I wasn't saying "that Tux2, he's so lazy he won't do it so it will have to wait until I do it", just that since I made a lot of the changes that would be documented, it would likely be best if I documented those changes.
@deleted_9101167
I don't know what could be causing that, but from reading it seems like BloodMoon uses some bukkit internals, so it might be changing things in some way that causes Bukkit events to fire strangely.
-
View User Profile
-
Send Message
Posted Jun 8, 2013@BC_Programming
@Tux2
Derp. That makes sense. Keep up the awesome work, guys!
-
View User Profile
-
Send Message
Posted Jun 8, 2013I just wanted to stop in and say myself, my staff, and my players LOVE your plugin, keep up the good work guys!
-
View User Profile
-
Send Message
Posted Jun 8, 2013So I've got this plugin called BloodMoon, which makes zombies break blocks in some nights. Grief prevention of course blocks that, even outside of claims. Now my question is: Is there a way to toggle this? Bloodmoon has the feature of automatically executing a command when it turns to a night when zombies can break blocks, and when it ends. Thanks a lot!
-
View User Profile
-
Send Message
Posted Jun 8, 2013@keytastic
Dev builds are our way of getting feedback and to work out bugs. They are undocumented because then people using the bukkit dev page would be expecting the release build to work the same way (which it clearly does not at this point). If you want to know what exactly has changed in the builds just take a look at the project on github and look at the commits. We've been diligent to document what has changed in every commit.