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 Dec 19, 2012@bigscary
You have some valid points about using WE's regen. But regarding regenerating ores or damaging underground structures you don't have to extend the selection down to bedrock, you could simply go from ground level up to sky limit. As far as the world generation code when is the last time that even changed? 1.3 for new ores? I'd guess a majority of servers reset their maps to get the new ores. And did it even change the actual land formation or just inject the new ores? Either way most maps were likely reset and anybody that is using such powerful tools should be competent enough to understand whether or not it's going to work due to these types of things. As far as a change in level seed you aren't supposed to change that once a map is generated, anybody who does so probably doesn't have any business running a server since it will cause strange formations at the borders of generated vs non generated areas after you change it. Also WE's regen doesn't attempt to protect anything when using the command. It IS going to regenerate all blocks in the selected area using the level seed and it's up to the person using the command to make sure a proper area is selected. Again this is a situation where if somebody isn't competent enough to select a region carefully/properly they shouldn't have access to it to begin with.
Don't get me wrong I think your plugin is great (or I wouldn't be using it). And the tools your plugin has are very useful especially for some of the things you mentioned such as fixing some of the ugly natural terrain that happens or filling in smaller holes. But your tool isn't the end all be all of terrain repair tools, and in many situations there are tools that are much faster and more efficient. A good example would be a player who decides to stockpile TNT and create a nice giant sized very ugly crater. Fixing it with your tools would be much slower than using WE's regen or even faster would be using a block logging/rollback plugin. Unless a server admin is trying to get as close to a "set it and forget it" server as possible (which your plugin would certainly help with) they're going to need other plugins to deal with the multitude of scenarios that are encountered. And both WorldEdit and WorldGuard should be on the 10 "must have" plugins for many servers meaning those tools are already available to begin with.
-
View User Profile
-
Send Message
Posted Dec 19, 2012I notice that new players can exit my spawn without doing /acceptrules by doing /trapped. I have verified that new players are not given any GP permissions. Is there any way to remove this permission from a group, with something like "-Claims.Trapped"? Thanks!
-
View User Profile
-
Send Message
Posted Dec 19, 2012Using gp 711 and bukkit version git-Bukkit-1.4.5-R0.2-10-g55e2ef7-b2501jnks (MC: 1.4.5) (Implementing API version 1.4.5-R0.3-SNAPSHOT)
We have recently have had to rebuild the database due to a world removal. Things are working again, but when i add animals to player folds, animals are disappearing after a few minutes. Any clue?
-
View User Profile
-
Send Message
Posted Dec 19, 2012@Stevensaurus
What other plugins do you have installed?
@wicked321
http://dev.bukkit.org/server-mods/grief-prevention/files/91-7-1-2/ (needs approval)
-
View User Profile
-
Send Message
Posted Dec 19, 2012I updated to latest version of CraftBukkit, 1.4.5 R1.0 and I'm using GriefPrevention 7.1.1 (Because I have no clue where 7.1.2 is). Now I'm getting spammed with:
java.lang.NoSuchMethodError: org.bukkit.event.entity.EntityChangeBlockEvent.getEntity()Lorg/bukkit/entity/LivingEntity;
Grief Prevention seems to be working still but not sure what that error means or how to fix it.
-
View User Profile
-
Send Message
Posted Dec 19, 2012Is 7.1.2 save to use with 1.4.5R1.0 Recommended Build?
-
View User Profile
-
Send Message
Posted Dec 18, 2012Great plugin, except for one thing; when I right click with the gold shovel, my Minecraft crashes. Any suggestions?
-
View User Profile
-
Send Message
Posted Dec 18, 2012also, where do i find 7.1.2?
-
View User Profile
-
Send Message
Posted Dec 18, 2012About to switch over to this plugin; here's hoping it's as good as you say it is!
-
View User Profile
-
Send Message
Posted Dec 18, 2012hi guys, i hope someone can help me with this. is it possible to make grief prevention land claims and factions land claims work together? right now, a faction can claim over the land that has been claimed by grief prevention land claim. is it possible to not allow that?
-
View User Profile
-
Send Message
Posted Dec 18, 2012@confuser
Thanks for your input. However I've already used that link to check it and shows output ok, but the changes keep disappearing.
-
View User Profile
-
Send Message
Posted Dec 18, 2012@amojica
Run it through http://yaml-online-parser.appspot.com/ before uploading to make sure it's valid.
-
View User Profile
-
Send Message
Posted Dec 18, 2012Hi, using GP 7.1.2 on Bukkit 1.4.5-R0.2-b2488 I get the following error when using the claims list command with an (offline) username:
In game it only says 'An internal error occurred while attempting to perform this command'
-
View User Profile
-
Send Message
Posted Dec 18, 2012I keep trying to add those tekkit items in v5.5.1 and no errors appear when checked by a yaml parser, but the items get erased anyway after running the server. I'm using notepad ++ to edit file. Any suggestions would be appreciated.
Thanks in advance.
-
View User Profile
-
Send Message
Posted Dec 17, 2012This might seem like a stupid question, but I can't find a way for a player to transfer ownership of their claim to another player. Or even for an admin to give a claim to another player. And it seems /TranferClaim is only for Administrative Claims?
( actually, that wasn't a question but you get the point ;) )
-
View User Profile
-
Send Message
Posted Dec 17, 20127.1.2 Fix
@Esaych
Please confirm you're on at least 7.1. I think I fixed that issue a couple of versions back by disabling teleportation restrictions entirely (you can now add slash commands which are not allowed in combat in the config file instead). Plugin-based automatic teleportation is no longer restricted, because I recognize that other plugins do weird shit and their developers don't care to play nice.
@CompeteToDefeat
I highly recommend against regeneration and content that GP's nature restoration is overall much better than a chunk (or selection) regen. Regens can destroy builds you don't see (like underground player builds), and will often generate an entirely NEW chunk with a different biome from the surrounding area especially if your world was created before Mojang updated world gen code or if you've changed your seed. Also, world edit's approach to protect the nearby area outside the selection is prone to bugs which can result in permanent collateral damage. Finally on lesser notes, it puts the ores back, which some purists don't like, and doesn't do anything to fix world gen problems, like floating islands, noisy terrain, and exposed stone on the surface. As you can probably guess from this pompous lecture (sorry, I got carried away), I very thoroughly investigated this area before setting out to build my own restoration feature. :)
@CompeteToDefeat
No, I try very hard not to build against dev builds, especially when there are non-dev builds compatible with the current Mojang version. Imagine the confusion when everyone who comes here to download gets the "new" version which is incompatible with their server version. Yikes. :\ The source is available if you'd like to get ahead of myself.
-
View User Profile
-
Send Message
Posted Dec 17, 2012@bigscary
Any chance of this plugin getting recompiled against current development builds so it can be used with bukkit versions after they added EntityChangeBlockEvent? I understand you want to hold off for a beta or RB, however from what I understand EntityChangeBlockEvent isn't something that's going to be changing and only requires a plugin be recompiled against the newer version. There have been quite a few fixes in the development branch and I'm sure many people, like myself, would like to be able to update to have implemented on our servers. I'd even be willing to run a not yet "published" development build of your plugin to work around this holdup. The other plugins we have which have issues with EntityChangeBlockEvent (essentials and worldguard) have development builds available that will work, GP is the last thing holding us back at the moment.
-
View User Profile
-
Send Message
Posted Dec 17, 2012@Smac3223
If you really want to restore an area back to being completely 100% natural I'd suggest WorldEdit. To be honest I feel WorldEdit is one of the "must have" plugins on most servers. With WE it's as simple as selecting the area, expanding your selection to cover from bedrock to sky limit with the expand vert command then using the regen command. That will reset the entire selected area back to the way it was before it was ever touched. It uses the level seed to regenerate the selected area, so it will be back to 100% natural. In addition to that function WE does a bazillion other useful things.
-
View User Profile
-
Send Message
Posted Dec 17, 2012Thank you, this is the greatest plugin for anti grief i have seen ever. I will add it to my server flyingblock.com asap. Thank you for considering stupid players.
-
View User Profile
-
Send Message
Posted Dec 17, 2012@diannetea
You mean it logs him back in after he's booted for idling, right? He's not receiving any extra blocks. If he's not actively playing (moving around a lot under his own power), he won't get any blocks.
@FordRacer2007
I'm saying you can tell your players to use /claimslist when they forgot where their claims are. :)
@netherfoam
Thanks, I'm looking into it.
@mazter_redz
No sorry, it's too complicated to make them work together. Even if I fixed my end, the Towny guy would have to do the same giant pile of work on his end.
@flurryknox
The initial blocks setting only applies to brand new players who have never, ever been on your server before you changed the setting. So if players had 100, then you updated the config to 500, those players don't get a bump because they joined when it was at 100.
@flurryknox
Check your file to make sure your message edits are still there. If you make a small formating mistake in a YML file, the YML reader will reset the whole thing back to defaults.
@tttwebsite
I thought about that, but it's complicated because there's no guarantee the player is even online at the time. Anyway he can just punch a block to find out.
@confuser
Easiest way is to use your file search to find all files in the claimsdata folder which contain the old world's name, then delete them all. Do this while your server is turned off. :)
@Esaych
Are you on the latest version? That sounds like a problem I already fixed.
@Simo389
Wow, that is very, very odd. Please look into your other plugins for the reason. You can confirm it isn't GP by temporarily disabling GP and then trying to reproduce the problem.
@Tr33x0rs
I'm very sorry you're facing such a tough problem. I don't have the expertise to help you troubleshoot this database situation. :\
@Smac3223
Okay, so you wanna use /rn to put trees and grass back... it's doable, but complicated because how to decide the tree type? If I expect the user to specify it, then the slash command gets ugly. Let me think on it.
@ManBeastPigDev
Sorry bro, you set up a system where you would have to be a landlord for all the plots. I don't know how I can make that work better for you without turning this into a real estate management plugin.
@amojica
Yep, you have to stick to the 5.5.1 version for Tekkit. The reason your edits disappear is because you've made a minor formatting mistake in your YAML. It's very common, and very big problem with YAML. All I can say is... before you reboot your server, always make a copy of your config file so that if it resets, you don't have to start completely over. The most common mistake is using TAB to indent instead of spaces, and some text editors do that for you when you start a new line.