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 1, 2014Hi, everyone! I hate that the 1.8 update came out while I was out of town and unable to work on this project. Of course the one week of the whole year I'm away, this happens - sigh. :) But it's good news overall, I'm excited! I will be working feverishly to investigate all the bug reports and close any gaps created by the core game changes.
If I have not responded to your request or bug report, don't worry - I've taken careful notes and will address all issues. Keep them coming!
Thank you for your patience!
@diskman2000
Sorry DM, but I need your complete boot logs, not just the bits you shared in your message. You can use something like pastebin to get them into a comment here.
@CKGAR
Yep will work on it.
@diskman2000
Is there more to that error message? It seems like there should be a stack trace or other helpful information.
@diskman2000
I will look into animals - but I tested very recently with the CB beta build and it was working great. Please check again - be sure you're not in /ic mode, you don't have permission to the land claim, and that the animals are actually inside the land claim. As for wooden buttons, that is intentional.
@Willcomputerguy799
I don't understand the "stop spam so it goes <playername: msg>" question? What exactly do you want, there? As for caps spam, there's no option to disable caps spam blocker - can you give an example of a message which you think should not have been lower cased so I can understand the problem?
@Praqoon
I'm working to get GP fully updated to 1.8 as soon as possible. Good to hear from you again! You can get spigot (and craftbukkit) for 1.8 on spigotmc.org.
@Bubbbaaa
What do you mean they wont work unless claimed? Do you mean activating a button which is not claimed does not actually power the block it's attached to? If your problem is specifically with pistons, that is by design - there is a config option to allow pistons outside of land claims to function, but your server could potentially be griefed (lagged to stoppage) by a redstone clock + piston combination if you enable that.
@joshuat3500
Which GP version and CB/Spigot version are you on? This was recently tested with the builds I released for and was working then.
@thedi1ceman
Will check on it, players should definitely not get any blocks if set to zero.
@LordDWT
Thanks for telling me, I will add them to the protected list.
@raum
I'd rather update GP so that it's as-good or better than your current solution. Can you tell me why you prefer your current solution over GP's version? Sorry there's not an option, I will add it to the todo list but expect some wait because right now the 1.8 update has me backlogged on bug reports.
@mcly
Sure, I will try to do that but right now I'm backlogged on bug reports, give me some time to catch up. :)
@pr4xt3roy
Yes, add brackets like /trust [my.permission.node] .
-
View User Profile
-
Send Message
Posted Nov 30, 2014Can I trust a whole "group" (like my staff or a builder rank) ??
-
View User Profile
-
Send Message
Posted Nov 30, 2014I often hear complaints from players that there are others who sethome in their claims. If there's a function to ban players from your claim, that'd be great!
-
View User Profile
-
Send Message
Posted Nov 30, 2014Not seeing anything to block sign logging. We have a custom plugin that watches this, so the double spam is .. well, spammy. I don't see anything in the config, or a perm to prevent it .. am I just missing it, or does it not exist?
-
View User Profile
-
Send Message
Posted Nov 30, 2014Apparently I can't see my Administrators sending PMs with eavesdrop turned on. Can this be fixed? I'd like to make sense of conversations they have with players without having to check the logs.
-
View User Profile
-
Send Message
Posted Nov 29, 2014@BigScary In the new 1.8 update GP does not handle the new doors and fence gates. I'm sure there are other items that are not handled/restored but haven't noticed yet. I use LWC (mostly because I like it closing the doors) so this is my backup to this for the moment.
Edit: armor_stand are not handled by GP or LWC. (I know you have nothing to do with LWC, just mentioning it)
-
View User Profile
-
Send Message
Posted Nov 29, 2014Since upgrading we're seeing players getting 8 extra blocks every few minutes, even when the config is set to 0.
We were using an older version for quite a while and didn't have this issue before.
Any ideas?
-
View User Profile
-
Send Message
Posted Nov 29, 2014@joshuat3500
I don't have any issue with this, it seems to block it perfectly fine. Are you using an up to date version? I can't imagine it was implemented recently though.
-
View User Profile
-
Send Message
Posted Nov 29, 2014Has anybody figured out a way to stop players from removing items from item frames on other players' claims? This is a huge problem on my server, and it's making people close up their shops so that people won't take their itemframe items.
-
View User Profile
-
Send Message
Posted Nov 28, 2014using 9.1 now
found no option for buttons/switches outside of claims. They will not work unless claimed. All my world guard claims have to be adminclaimed then public trusted to get the buttons/switches to work.
was using 8.8 with no problems on that aspect.
-
View User Profile
-
Send Message
Posted Nov 28, 2014Just letting you know, spigot has been updated to 1.8 :)
-
View User Profile
-
Send Message
Posted Nov 28, 2014Greetings grief preventers! Grief prevention always was, and always will be, THE definitive no.1 plugin for CraftBukkit, and you can quote me on that. ;)
@Bigscary, it's good to see you're back! Very good news indeed. :D
It's a crying shame CraftBukkit is no more. Since its demise I have switched to vanilla Minecraft 1.8 and, even though it features command blocks and the scoreboard (and a lot of other complicated things only you would understand), I am missing Grief Prevention badly. I remember the times when griefers would complain or tell me the server was broken because they couldn't dump lava or destroy another players house and I still laugh at those moments. Good times.
I've been advised by more than a few people to start using Spigot. I've also heard about the new Sponge-Powered project which looks promising. I don't know much about Spigot but if it's anything like CraftBukkit then grief prevention is a MUST-HAVE.
I can't believe Mojang, or Microsoft, haven't incorporated something like grief prevention into the official game yet. It's the best logical and most sensible solution all round. Plus, there's nothing else quite like it for ease-of-use, user-friendliness, and functionality.
-
View User Profile
-
Send Message
Posted Nov 27, 2014Is there a way to keep the spam feature enabled, and stop spam so it goes <playername: msg>, but disable the caps filter? It seems to filter out capitals.
-
View User Profile
-
Send Message
Posted Nov 27, 2014Hello,
Just a crash, seems to be related to GP. Happened only once, here's the stack trace: http://pastebin.com/Ay5MfBsw
Thanks for taking a look!
-
View User Profile
-
Send Message
Posted Nov 27, 2014@diskman2000
I'm using GP 9.1 and see that arrows can activate wooden buttons, but I am unable to hurt animals in a claim (tested by shooting a cow).
-
View User Profile
-
Send Message
Posted Nov 26, 2014Animals in claims can be killed with arrows. Wood buttons can be activated with arrows also.
-
View User Profile
-
Send Message
Posted Nov 26, 2014@bigscary
unfortunately the log was deleted when I did the restore from backup. I can work on setting up a test box and trying the conversion again there.
The server is on bungee, but its not on the same box as the bungee and the call to mojang shouldn't be affected by that. I can't say whether my host was having network issues or not that morning, I did have players on all my other servers which were up. It was running for 3 hours before I got to it, as it started at 2am when the server does a normal restart/backup cycle. I found it still going at 5am and only doing about 4 uuid lookups a minute.
Is there an updated github? :) (Pop density too?) pwease? =^..^=
-
View User Profile
-
Send Message
Posted Nov 25, 2014FIXED.. Updated vault to current version.. Sorry.
Getting the following error when players do /buyclaimblocks
issued server command: /buyclaimblocks 10 2014-11-25 18:21:22 [ERROR] null org.bukkit.command.CommandException: Unhandled exception executing command 'buyclaimblocks' in plugin GriefPrevention v9.1
-
View User Profile
-
Send Message
Posted Nov 25, 2014Admin claim's subclaims got abandoned randomly. I have 57 plots in my admin claim :/
-
View User Profile
-
Send Message
Posted Nov 24, 2014@bigscary
I believe I was using the 1.8 vanilla client on the 1.7.10 Spigot with the protocol hack. I half-suspected that to be partly the issue, but couldn't think of a way that would be caused unless the fake block change packets are misinterpreted on 1.8 clients. If it's not exclusively the client issue, then I suppose you'd need to be handling chunk loading somewhere in order for it to keep generating those blocks on the loaded chunk borders.