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, 2012@zathrus_writer
It isn't anywhere near spawn. Even if it were, I'd be able to edit blocks as I am Op. Such is not the case here. As you can see by the torches, it used to be fine. This is problem happened only recently.
-
View User Profile
-
Send Message
Posted Jun 8, 2012@judam
make sure that's not a spawn point area, which is protected automatically
-
View User Profile
-
Send Message
Posted Jun 8, 2012There's an area that overlaps one of my users' claims where neither he or I (admin) can edit blocks. Here is the affected area marked off with cobble stone. There is no prompt saying the area is claimed by anyone, just can't place or break blocks.
Plugins (22): SilkSpawners, Spectate, ProperTime, SpongeRestore, CoreProtect, pvparena, ExternalChat, BKCommonLib, Vault, PermissionsEx, Command er, GriefPrevention, LWC, MyHelpPages, Essentials, dynmap, NoLaggMonitor, MineBackup, CreeperHeal, NoLaggExamine, ChatManager, AuthMe
-
View User Profile
-
Send Message
Posted Jun 8, 2012@hotdogPi
You were spamming the server. You've done this on multiple occasions intentionally, blatantly playing with the anti spam code. You annoyed players with your fake death messages for at least a couple of days - chat is for chatting, not drawing pictures or forging server messages. You knew you were playing with fire, deserved the ban, and it will stand. The anti spam did exactly what it's supposed to do. I would have banned you myself sooner, but I wanted to see if the code would catch you.
If you want to continue to argue, please do it in private messages. This comment area is for feedback on the plugin, not specific issues with the test server.
@zathrus_writer
No kidding? I'll check on that. I had originally tested that case and it was fine, but I may have broken it recently.
@ev3rm0r3
Sorry to hear you're having trouble. I'll stick to making Vanilla work for now.
@zedadiaswick
Removing the world from the list of siege worlds is the only way to disable siege. As long as the server knows there's a block, players will be unable to move through it. Actually, the client starts to get glitchy when its view differs from the server's view, and players can get "stuck".
@stevevbrewer
Pressure plates always working is intentional. By making pressure plates "public", players have a way to make iron doors openable by everyone if that's what they want. The access permission only covers buttons, levers, and beds. If a player wants privacy, he should use a button or switch (button is better, because it auto-closes).
If you have a button or switch which seems to be usable by everyone, check two things - first, the button or switch itself is actually IN the claim, and second, it's not an administrative claim (which allows the public everything except build/break). You can convert an admin claim to a private claim with /transferclaim.
Just stand or fly in the claim and use /deleteclaim (/dc).
I'm very glad to hear that you like GP enough to go through the migration headache. It's always a pain to get people to do something different. :) While it does have some cool not-grief-related features, Towny is overly complicated and too difficult to use, in my opinion. The size of their wiki blows my mind.
-
View User Profile
-
Send Message
Posted Jun 7, 2012Is there something I need to do to prevent outsiders using pressure plates and switches to open iron doors in claims? It seems everyone can use them even if they have no permission in that claim.
I've tried both true and false for 'PreventButtonsSwitches'.
Here's my config.yml http://pastebin.com/7dT2LWVR
Also is there any reason why saplings would stop growing in claimed land?
How do I force delete claims in creative worlds? I don't want to delete all claims for a player, just one that's really in the way.
UPDATE: Also for what it's worth, I've posted your video on our server listing pages. I'm also rigorously forcing the training down my player's throats, they hate change but GP is soooo much better than Towny and it's stupid 16x16 chunk plots that mean you have to dedicate a whole row of giant plots just to have a road in your town.
-
View User Profile
-
Send Message
Posted Jun 7, 2012@bigscary
Mmm, that is a shame. I realise this touches on your issue of being sure blocks don't drop items, but could chests be breakable but not drop their inventory? Or perhaps some kind of method to (and I'm talking without knowing if anything like this could be possible) make the blocks only seem to be breakable client-side, but actually remain untouched server-side, but allow the player to move freely through "broken" blocks?
I disabled siege weeks ago, many server restarts ago. Unfortunately the player who used siege has been banned for the incident, it was a case of three players ganging up on one player in an attempt to make him leave the server. Mostly for talking too much. So I doubt I'd get much co-operation in getting more information. When I taught him how to use siege, i only covered using /siege. I didn't know there was another way to initiate it, so I would assume that's how he did it. I've removed the world from the siege worlds in the config, hoping that would disable siege for me. Not had a server restart since setting that for it to take effect, though.
-
View User Profile
-
Send Message
Posted Jun 7, 2012Actually with Bc and IC2 and Redpower, the machines work because they are fake entity's in the world. Their actual player names are BuildCraft, IndustrialCraft and Redpower and Forestry or whatever the mod is. Those names HAVE to be op'd in order to work with essentials. But your mod locks them down because it doesn't recognized the fact the player is operating those machines, it just recognizes that the machines are another player. So it locks them down completely. The mod's themselves have to be allowed per name as they are titled. It doesn't allow greifing, but it is necessary for plugins to cooperate with them. Its part of the normal issues with a buildcraft server. Everyone has to do it.
-
View User Profile
-
Send Message
Posted Jun 7, 2012interesting bug report - my players report animals can be griefed within claimed areas by shooting at them
-
View User Profile
-
Send Message
Posted Jun 7, 2012I got banned for spam. It seems like 4 comments with a lot of spaces in a row did it, even there were 4 minutes in between. I got a warning after 3, but I didn't know a fourth one typed 2 minutes later would ban me. I was trying to make fake death messages. Can you please unban me? (damn near vanilla) This is the only way I can contact you.
-
View User Profile
-
Send Message
Posted Jun 7, 2012@CharlesWCrete
It sounds like a really great idea, but unfortunately /RNA will wreck the landscape, and /RN will not remove the entire build. So we'd still be leaving a griefing opportunity open.
@SuperSpyTX
Lots have said they don't like the new feature, and I've promised to replace it with something better. Probably this week.
@Possessed45
Set it to -1 to disable those automatic claims entirely. 0 means protect only the chest.
@ev3rm0r3
Maybe eventually. But right now I have enough to do with Vanilla and its patches. Also the correct solution is on the mod end - when machines make world changes, they should make those changes as the owner of the machine. That way an owner who has permission can do work with a machine in an area. If machines are ignored entirely, then griefers can build machines to bypass the claim permissions.
@zathrus_writer
Again... I've said several times now I will replace this feature. :) It's even mentioned in the to-do list above.
@zedadiaswick
I like that idea, but I think it will be much too expensive. Also containers and high value blocks are a problem - trying to restore a container and all its contents sounds like risky business (even one small bug in this area could permanently hurt a lot of players), and making chests not breakable would make them an abuse-able building material to make your house siege-proof because they're so easy to make. Also, it'd be tough to guarantee that blocks destroyed during a siege don't ever drop... otherwise, there would be a duplication bug because the blocks regenerate later. It might be possible to make something like this work, but I don't want to pursue it due to the combination of bug risk and performance cost. Remember, only low-value blocks are breakable by default. It's not a big deal to replace them.
Did you not /reload after updating your config to disable siege? If you did, do you have any idea how the player managed to initiate a siege? The /siege command should only return an error message when siege is disabled. Let me know if you get any more information.
-
View User Profile
-
Send Message
Posted Jun 7, 2012@SuperSpyTX
support how?
-
View User Profile
-
Send Message
Posted Jun 7, 2012@zathrus_writer
Support this PR then https://github.com/ryanhamshire/GriefPrevention/pull/2
-
View User Profile
-
Send Message
Posted Jun 7, 2012I have siege mode disabled in my config; but a player used it today to bully and grief another player along with some other players. So, how could he use it if it was disabled? :/
Also, I forgot to bring this up when i originally tested siege mode: the image I had of siege mode was that destroyed blocks would be replaced once the siege ends - undoing all the grief that had been done inside the claim. But it doesn't do this; any chance it could be made to? I thought that idea was great, as it meant players could still battle and have a chance to break down the walls and get inside - but without ruining their hard-work in designing and creating their build.
-
View User Profile
-
Send Message
Posted Jun 7, 2012hmm, I have to second everyone's opinion on the login/logout messages delay... it seems wierd, as if a lag was present on the server when player chats and only then the join message is shown... I say make the time configurable at least or allow us to disable this completely
-
View User Profile
-
Send Message
Posted Jun 7, 2012@Possessed45
Setting the radius to 0 will create a 1x1 claim at the chest.
-
View User Profile
-
Send Message
Posted Jun 7, 2012Needs a way to add block id's and damage values aka 100 or 100:5, so that this addon can be used with builcraft type mods. Currently it works un paralelled with vanilla but we had to remove it in favor of machine guard and others on our buildcraft server. Was unfortunate as it was the easiest for players to use. Also it would be great if you could add an option in the config to exclude players that will be blocked so that on a buildcraft server like ours the mod's names like [buildcraft] or [industrialcraft] could be overlooked by this plugin as it disabled the use of several machines.
Think about it, having a second implementation of this plugin for techit types servers would get you revered amongst the community of customer minecrafters.
-
View User Profile
-
Send Message
Posted Jun 6, 2012Thanks for responding to my earlier questions, they helped a lot! I just have on more. I have looked and looked through the config but I haven't found an option for setting automatic chest claim off. The only one I see is the radius of the chest claim. Should I set this to 0?
-
View User Profile
-
Send Message
Posted Jun 6, 2012Hey bigscary, I've noticed that in your 4.3 update, it now adds a so called delay for join/leave messages. This is causing conflict with my plugin and so to resolve it, i've modified the plugin so you're given the ability to set the delay on it.
Could you check out my PR on GitHub? https://github.com/ryanhamshire/GriefPrevention/pull/2
-
View User Profile
-
Send Message
Posted Jun 6, 2012@bigscary
Hey ryan! I have a super duper idea for creative! Lets say someone wants to unclaim, he could have a message saying 'This will be deleted if you unclaim, say /unclaimconfirm to confirm'. If he does say /ucc (alias), the claim is deleted and it does /rna on the claim so it get deleted so other user can go claim it! If you ever add this, add a option in the config called 'creative-unclaim' which it defaults to true.
Thanks! Im thinking about adding a creative server to our server line! Check it out! Here!
-
View User Profile
-
Send Message
Posted Jun 6, 2012Hey guys I've heard a lot of "I've been looking for this plugin a long time and didn't find it until recently" lately. You can all help me and the community a lot by taking 10 minutes to go to either the bukkitdev forums or minecraftforums.net and posting about your experience with this plugin.
It's a real shame that bukkit dev doesn't have a ratings system or other helpful thing to help server owners find the best plugins. Please consider taking just a few minutes of your time to tell others how helpful this plugin has been for you, to encourage them to give it a try. Griefers haven't met their match yet, not because this plugin doesn't beat them, but because not enough server owners use it.
Also, I forgot to mention... the last version also includes an update to protect villagers, golems, and squid in claimed areas.