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 31, 2012Why aren't admins able to override protected zones? (ie: open chests, and doors)
Admins should be able to take priority over these things.
-
View User Profile
-
Send Message
Posted May 31, 2012Hi Great work! One question, it's possible to enable this plugin only for OPs ?
I would like to use it to protect the spawn and safezone, but the wildness in my server is with no rules so I don't want the other player to use this.. It's possible?! Thank u
-
View User Profile
-
Send Message
Posted May 31, 2012how do u allow someone else to make a subdivision on ur claim?
-
View User Profile
-
Send Message
Posted May 31, 2012Also, you probably need to change the function of string to another item. In the upcoming minecraft 1.3 you will be able to place string on the ground for tripwires.
-
View User Profile
-
Send Message
Posted May 31, 2012@cvxx7q
Hehe, yea.. the thing is that i'm not running it on a live server just yet. :P Still testing it out.
I want to know for sure though that people won't get auto banned when i start using this on my live server. For me, only getting the information "a player who tries to log in and seems to very likely be another account belonging to a player who has already been banned will be automatically banned as well." isn't really comforting for me. It would be nice to know what it actually looks at for deciding if someone is the same person. xD
-
View User Profile
-
Send Message
Posted May 31, 2012@zathrus_writer
well i cant send too many to heaven now can i? ;)
there is a balance to be kept! XD
-
View User Profile
-
Send Message
Posted May 31, 2012I like how our current moods are being reflected in this thread... sometimes the same guy who helped a lot yesterday will send people to hell just like that :D
-
View User Profile
-
Send Message
Posted May 31, 2012@snowy007
if your friends aren't getting banned then there should be no problem
-
View User Profile
-
Send Message
Posted May 31, 2012@bigscary
Can you give some more information about that auto-ban feature? I have a lot of players that are real-live friends and are often located at each others houses. When exactly do you ban? When a player with the same IP as a banned player logs in?
-
View User Profile
-
Send Message
Posted May 30, 2012@Hoot215
Thanks, please do. If we're still having this problem a little later, I'll try to do something on my end.
@Simo389
You can do this yourself. For the regions you've created with WG, put an admin claim on top. If you're talking about WG regions created by your players, then that won't be manageable for you. I recommend either switching entirely to GP claims and preventing your standard players (non admins) from creating WG claims, OR disabling GP claims entirely and telling them to just use WG for claiming everything. I usually recommend the former - limit WG to admins and use it for only what you must (like making an area pvp, or stopping monster spawns in your city), and using GP for everything else, including all player claims. I recommend it that way because in my opinion, GP claims are easier for players to use and manage (fewer slash commands, with less params which are easier to remember, and good boundary visualization, plus automatic claiming for newbies).
@mbaxter
Thanks! That sounded like a good idea to me at first, but then I thought about how being invisible doesn't necessarily mean the login message shouldn't be shown. I know that for both SV and VNP, it's possible to be invisible and still notify players when you log in and out, based on permissions and/or config options. Also, this fix would assume that all plugins use the Bukkit API. I know that's true for SV, but I'm not sure if VNP has changed over to use the new API, and there may be more notification message stopping plugins out there (like simply turning off all notifications) that don't actually use the Bukkit invis API to pull that off.
I guess there are no perfect solutions. :) But we can engineer for the common cases (the most popular potentially conflicting plugins).
Edit: Sorry, SV = SimplyVanish.
-
View User Profile
-
Send Message
Posted May 30, 2012@bigscary
A better solution for all parties would be having this plugin's login message check the Bukkit vanish API to see if the player receiving the message can see the player the message is about. No plugin dependencies, it's a Bukkit feature.
I'm open to chatting about implementing this on IRC, which is quicker than comments back and forth. Hanging out on esper, gamesurge, and freenode under this name.
-
View User Profile
-
Send Message
Posted May 30, 2012Hi, can you please disallow players from claiming areas inside WorldGuard regions. It's causing some major issues on our servers. :-(
-
View User Profile
-
Send Message
Posted May 30, 2012@bigscary
I can understand if you don't want to add that feature; I'll see if I can convince mbaxter to change the priority, or just submit a pull request.
Also, yes, I am sure about the permissions. "vanish.currentlyVanished" is the permission given to a player only when they are actually vanished (and therefore should not be modified manually), and "vanish.silentjoin" is the permission that allows a player to login silently.
-
View User Profile
-
Send Message
Posted May 30, 20124.2 Updates!
@Hoot215
I know how simple it is. It takes me like 5 mins. But after coding and testing for hours, I'm usually like UUUUGGHHH. Anyway, I just updated to 4.2. I'll try to do better in the future.
I'd like to avoid taking a dependency just to quiet login messages, I'm sure you understand. The problem is that his code to set the login message to null executes after mine. If he reduces his priority to high instead of highest, we'll be compat. Maybe I can check those permissions... are you sure they indicate current status, rather than permission to change to that status??
-
View User Profile
-
Send Message
Posted May 30, 2012@Feaelin I would have a fork, except that the source is almost always out of date, and I prefer to always use the latest source when forking, because otherwise things could possibly get "messy".
@bigscary I can understand why you order your priorities that way, but updating a GitHub repository is literally as simple as typing a few commands in a terminal. Heck, if you're using GNU/Linux, I could even make you a script that you would simply click on, and it updates your repository for you (It's possible with Windows too, but I'd have to look up how to do it). Anyway, I'm sure that you are doing a lot of coding work, and maybe I don't give you enough credit for that. Sorry.
Enough ranting, here's a bug report that you might be interested in. The new login delay feature seems to be incompatible with VanishNoPacket's login hiding. In case you weren't aware, VanishNoPacket has a feature where you can login without it announcing it to the server, but with the new login delay feature of this plugin, your login will still be announced to the server regardless of whether or not you have login hiding enabled. If you decide to fix this, I might suggest checking for the permission "vanish.currentlyVanished" (which is true when a player is vanished) or "vanish.silentjoin" (permission to join silently), but you might be able to think of a better solution. Again, thanks for all of the work that you do.
-
View User Profile
-
Send Message
Posted May 30, 2012@Hoot215
I'm also not coding as much as I could be, or sleeping as little as I could be. Give me a break guys. :) What's more important - a new feature or source for yesterday's? Answer: for most, the new feature. That's why my prioritization of coding over source releases.
Anyway I'll try to remember to update after today's release.
-
View User Profile
-
Send Message
Posted May 30, 2012@Hoot215: Do you have a private fork of GP? In what ways does it differ? :)
@Sexy_Glenn: For starter kits, there's also StarterKit, and a couple of other plugins (in addition to the kits built into Essentials and CommandsEx)
------One thing I like about Essentials is its help filtering based on permission (you only see commands you have permission for). Is there a stand alone plugin that provides the same feature? I've thought about extracting that and any other (very few) features I actually want out of Essentials. :)
-
View User Profile
-
Send Message
Posted May 30, 2012I do not know compile the plugin too. I want translate one phrase.
-
View User Profile
-
Send Message
Posted May 30, 2012Would you mind updating your GitHub repository a little bit more frequently, please? It can get repetitive having to ask you this after every update. Thanks in advance. (Note: Sorry if I sound pushy at all, it's just that I don't think you're updating the repository as often as you could be)
-
View User Profile
-
Send Message
Posted May 30, 2012Hey guys I'll probably get some fixes and the new hybrid ban out today. I want to run it a little longer on my test server to make sure it's correct first, because any mistake involving bans is a big one. :)
@Sexy_Glenn
I recommend against making it easier to get. Part of the design is to make players work for custom claims, otherwise griefers might get creative. But if you're going to do it, starter kits are a good solution. Don't get essentials just for this - that plugin is ludicrously bloated, especially for a plugin named "essentials".
@re4397
Sorry, smallest cooldown is 1 minute. With the recent feature add to inhibit login spam, you might be okay with turning the cooldown off entirely.