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 Aug 18, 2013@Narzerus
the jenkins build use Java 7.
-
View User Profile
-
Send Message
Posted Aug 18, 2013For the new permission system, is there one to use the stick to see claims?
-
View User Profile
-
Send Message
Posted Aug 18, 2013Help! Last night one of our admins updated the greifprevention. None of the players are allowed to /trust or /abandonclaim and I'm unable to find anything in the config files to change this.
P.S. I've already confirmed the right permissions in the right places but even our moderators aren't able to use these commands.
-
View User Profile
-
Send Message
Posted Aug 18, 2013I'm getting a crash on load. I'm using CraftBukkit's Beta Build for 1.6.2 and GP's latest development build (156).
Could this have something to do with my server not running on Java 7?
Thanks, great work guys
Caused by: java.lang.UnsupportedClassVersionError me/ryanhamshire/GriefPrevention/GriefPrevention : Unsupported major.minor version 51.0
-
View User Profile
-
Send Message
Posted Aug 18, 2013@Awsmpossum1313
It's GriefPrevention.Economy, in config.yml.
-
View User Profile
-
Send Message
Posted Aug 18, 2013Hi. I want to make a command that lets players save schems of their claims. How do I check if a block is in their claim?
Also can you add 108.61.53.218:25578 to the official servers? Thanks :)
-
View User Profile
-
Send Message
Posted Aug 18, 2013Economy section missing from my config:
It appears the economy section is missing completely from my NEW config files on my fresh installation of Grief Prevention. I have confirmed this in 150 and 156. I have removed the entire folder and let it rebuild from scratch and the economy lines are still not there.
-
View User Profile
-
Send Message
Posted Aug 17, 2013@cpcool3
First, say what dev build you have. saying "newer dev build" tells me nothing. Changes are made in every single build- it's not automated and builds are only created when new changes are made.
Second, if you are using the current latest dev build, read the Comment immediately before yours where I describe the issues with permissions that others are having as well.
Also, Permissions were changed almost entirely, so if you are using the same permissions as you were with 7.7 they won't work.
-
View User Profile
-
Send Message
Posted Aug 17, 2013Okay, Griefprevention was working fine, right? Soon after I updated it to a newer dev build my admins can no longer build in admin claims even though they have permissions for it. What is the deal here?
-
View User Profile
-
Send Message
Posted Aug 17, 2013Looking at it, I think it might be a simple typo on my part. I used "griefprevention.commands.{0}" as a String format pattern; erroneously using the C# Style for formatting (to be fair GP also seems to use it internally elsewhere). As such all commands test for a Permission "griefprevention.commands.{0}" instead of the specific command name.
If you grant "griefprevention.commands.{0}" permission, it should fix it. This won't give access to all the commands; the plugin.yml also specifies command permissions, which will/are still enforced. the commands simply double-check the permission and do so in an erroneous fashion.
-
View User Profile
-
Send Message
Posted Aug 17, 2013Comments form is not being my friend here.
Anyway, thought I'm mention this here. I've never really dealt with permissions, and the idea to have command-specific permissions was a suggestion. I'm going to try to look into this Today and Tomorrow and hopefully get a working build with those changes available by Monday. :)
-
View User Profile
-
Send Message
Posted Aug 17, 2013Hi all, I have a problem with messages.yml file! when i try to costumize my messages.yml file (for translate it to Turkish), it returns the original messages.yml file (English one) when i reload. Have any ideas about it?
-
View User Profile
-
Send Message
Posted Aug 17, 2013having a problem with it also, permissions Trust, AbandonClaim...
not including the other problem I've been happy with claims discipline
-
View User Profile
-
Send Message
Posted Aug 17, 2013@deleted_9935739
Second to this comment. I'm assuming I missed something and will try again later. We reverted to #155, working fine.
-
View User Profile
-
Send Message
Posted Aug 17, 2013I gave the new permissions found in plugin.yml but it doesn't seem to give them the commands. Nobody can do anything except create claims even though it's supposed to be default.
Edit: Reverted back to #150. Permissions work fine in this version.
-
View User Profile
-
Send Message
Posted Aug 17, 2013Cant spawncampers trap the person in a room. Throw a block down then attack you?
-
View User Profile
-
Send Message
Posted Aug 17, 2013@BC_Programming
On a second look I didn't miss that one.
I mean for all GP management to be removed. Rules and etc still apply if griefprevention.claims.enabled is off. Most plugins have a list of worlds that they manage in their main config. This way GP could just ignore those worlds instead of having rules that do nothing for each.
This is handy for other worlds like games worlds, foyer worlds, and so on.
-
View User Profile
-
Send Message
Posted Aug 17, 2013@BC_Programming
Thank you I missed that one.
-
View User Profile
-
Send Message
Posted Aug 16, 2013Will build #156 claim all blocks below the selected area in 1.6.2? Right now, griefprevention is only claiming at and above the claimed area.
-
View User Profile
-
Send Message
Posted Aug 16, 2013@Slind14
Just to clarify, the dev build, and subsequently, 7.8, loads claims differently than 7.7. 7.7 and earlier load all claims at once when the plugin loads. If a Claim is in a world that isn't available, the claim is deleted. This causes problems with mystcraft worlds.
7.8 eg. the dev builds, now load and unload claims from the list of loaded claims as worlds load and unload; when a world loads, all that world's claims are added to the claims listing. When a world unloads, all that worlds claims are removed from that listing.
@mbl111
Dev builds make this possible by changing the FireSetting Rule configuration. I might have added a option to allow for chest access during PvP but I cannot actually remember. Since containers are now also a rule, this could probably be added by adding an optional setting to each rule to allow or deny while in PvP as well as Siege (the latter being something specifically requested by iirc RustyDagger)