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 8, 2013@keytastic
Don't worry, you didn't miss the memo. We don't send out memos. :P
but I am wondering when this page will be updated to explain the new config files?
Either when I get around to it personally, or shortly after it's no longer a dev build. For the moment it seems that I'm the most active contributor, since Tux2 is busy on his various other projects and other work. Main issue is that if I was to document it as it is now, Dev builds can change pretty quickly over just a few builds, and that can quickly make any documentation that was written obsolete.
For what it's worth, the reason I changed the name of the folder was two reasons. One was that it was requested, and the second was to make it so upgrading to the latest version of the plugin wouldn't obliterate the configurations of the previous versions (which it would do otherwise). It was mostly the second reason, so people's carefully crafted 7.7 config.yml's didn't get obliterated by simply running the newer version.
The primary world-based configuration changed simply moved some config.yml options to each world configuration. After the initial move, I expanded some of the options and added more granular control for some options, which shows up as the various segments for different behaviours. Every possible value isn't implemented yet and I'd prefer to document how the software actually works, not how I hope it's going to work, which seems sensible to me, at least. :)
-
View User Profile
-
Send Message
Posted Jun 8, 2013I must have missed the memo that says the dev builds are changing the name of the folder where claims are stored. Not to mention the config files themselves. I am pleased to see per world support for the configs, but I am wondering when this page will be updated to explain the new config files?
-
View User Profile
-
Send Message
Posted Jun 7, 2013People on my server don't get claim blocks per hour like they should.
-
View User Profile
-
Send Message
Posted Jun 7, 2013@rawrlehel
"GriefPrevention.Claims.AllowUnclaimingLand"
-
View User Profile
-
Send Message
Posted Jun 7, 2013@rsod Thanks didn't think of that.
@Alshain01 I have nosurvivalbuildingoutsideclaims: true so people don't grief the entire world. If they can remove their claims and make a new one after griefing the area then what's the point?
-
View User Profile
-
Send Message
Posted Jun 7, 2013Can you make more than one claim as a player?
-
View User Profile
-
Send Message
Posted Jun 7, 2013@rawrlehel Well, there is different situations...
WorldGuard
execute in each world
-
View User Profile
-
Send Message
Posted Jun 6, 2013@rawrlehel
It's tied to griefprevention.claims
There would be no real reason to allow creation of claims and not allow deleting them.
-
View User Profile
-
Send Message
Posted Jun 6, 2013Is there any way to disable /abandonclaim and /abandonallclaims? Just wondering since the permission nodes are not listed for them, would it be griefprevention.abandonclaim and griefprevention.abandonallclaims?
Thanks
-
View User Profile
-
Send Message
Posted Jun 5, 2013My players cannot light nether portals inside their own claims. How can I change this?
-
View User Profile
-
Send Message
Posted Jun 5, 2013So i have admin claim on a building for the public that has items like enchantment tables and such. Is there any way i can allow public access to certain items such as these within claims without giving container trust to everything?
-
View User Profile
-
Send Message
Posted Jun 5, 2013@ArtBorax
I like your terse, context free comments.
-
View User Profile
-
Send Message
Posted Jun 5, 2013Flood
-
View User Profile
-
Send Message
Posted Jun 4, 2013@GaminglikeaMAN
/accesstrust public
-
View User Profile
-
Send Message
Posted Jun 4, 2013@BC_Programming
You my dear sir are a hero no less.
And while i'm here i might as well continue being a problem: http://pastebin.com/MnLrBdNH
-
View User Profile
-
Send Message
Posted Jun 4, 2013@BC_Programming
Hi! I love GriefProtection, but I want the players to be able to open chests, use crafting tables, use furnaces and destroy certain blocks. Is there a way to toggle this somehow? Thanks!
-
View User Profile
-
Send Message
Posted Jun 4, 2013@BC_Programming
Thanks!
-
View User Profile
-
Send Message
Posted Jun 4, 2013BlocksAccruedPerHour: 100
limit does not increase in the last version had a problem with small values started to work on the 15.
-
View User Profile
-
Send Message
Posted Jun 4, 2013@zlepper
Very well, if you say the database isn't removed, then when can we access it again, i now
have a completely unprotected 1.5.2 server, since i can't access my database any longer.
So again, when do you think you have a fix for that little problem?
You can add GriefPrevention.Database.URL,GriefPrevention.Database.UserName, and GriefPrevention.Database.UserName options into config.yml to fix it. It will only be active for a single server load since the config file is rewritten and the database settings are not stored again.
As for when it will be fixed, Next Version means "next Dev Build" which Jenkins will build whenever I decide to commit my current working copy.
EDIT: Build #67 should fix this issue. Turns out that not only were the Database settings not getting written back, but every World Configuration load would also overwrite the main config file with that world configuration.
-
View User Profile
-
Send Message
Posted Jun 4, 2013How do I get rid of GriefPreventionData...I can't delete it.