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 Oct 18, 2014I just wanted to give a big shout-out and thanks to bigscary, Tux2, and BC_Programming. So many plugins aren't receiving updates because of the whole DMCA situation, and yet you haven't given up on us poor server owners who are still running your awesome plugin! Even when it seems thankless - since most of the comments are bug reports/ feature requests/ general trolling - know that there are a lot of us who rely heavily on your plugin and really appreciate your commitment to it! Cheers!
-
View User Profile
-
Send Message
Posted Oct 17, 2014@TJW28
That's a bug, I made a mistake. I'll have it fixed this week.
@Ivanna79
GP does a lot more anti-grief than world guard does - anti grief goes way beyond land claims and stopping fire spread. Also, player made land claims are critical - if players (even little kids who aren't so experienced in gaming) can't claim their land correctly and early in their play experience, then administrators have to do a lot of rollback work and players have to wait for them to do it. WorldGuard is a great administrative tool, but it's not a great overall anti grief solution.
Your point is about as strong as your English. Class dismissed. Homework: Watch the video (the whole thing).
@Turbotailz
You do have that authority, you just don't know it, I guess. You can override claims with /ignoreclaims to do any administrative work, including moving horses with leads or by riding. I will check and ensure the /ignoreclaims advertisement shows up in that error message to save others in your situation a trip to these comments. :)
@Lostwave
Yes, please! Someone seemed ready to share, but I have yet to receive any links from him/her. I don't need your player data, just claim data.
-
View User Profile
-
Send Message
Posted Oct 17, 2014@bigscary
Do you still need a flat file with over 5k? I have 6500 left. (I deleted 12k old ones). I can zip up the folders and send to you.
-
View User Profile
-
Send Message
Posted Oct 17, 2014@Turbotailz
IIRC, I was able to corral other peoples' horses by using /ignoreclaims
-
View User Profile
-
Send Message
Posted Oct 17, 2014@erik1988
I agree, adding groups to claims will make things a lot easier and I'm pretty sure my players would love to be able to make their claims only available to people Level 2 and up.
Anyway, I'm here to say that you really need to do something about horses. I have someone who is building in an area where someone else's horse has wandered in and they can't move it away. They asked for my help but not even I (an Op) could do anything with the horse. The only option would be to kill it but we will wait until the owner gets on to do something about it.
The fact that admins have no authority to move other peoples' horses is quite ridiculous. The whole horse claim thing is stupid and we've had so many troubles with horses :(
Sorry to sound like a whiney bitch, I feel this really needs to looked into.
-
View User Profile
-
Send Message
Posted Oct 17, 2014Worldguard works just fine as a server grief prevention. This only seems good as a made player grief prevention. I really don't see any use of this plugin, no faction support, skyblock support etc.
-
View User Profile
-
Send Message
Posted Oct 17, 2014@bigscary
I was also thinking that upgrading the craftbukkit would help but craftbukkit website is down now and I can't download a new version. If anyone could upload it somewhere, or send me by e-mail that would be wonderful.
EDIT
Okay, I found 1.7.9 version of craftbukkit, installed it and now everything works fine. Thanks for your help :)
-
View User Profile
-
Send Message
Posted Oct 17, 2014@bigscary
Thank you so much for implementing my suggestion so quickly. I notice now the claim outline shows as netherrack and redstoneore. Is this now by design, I didn't see a mention in the change-log.
-
View User Profile
-
Send Message
Posted Oct 16, 2014@bigscary
I would disagree, I think a lot of players will benefit from being able to add groups of people. A big drawback with GP is that it does not work with plugins that makes clans/town/factions. Sure you can use plugins like simpleclans with GP that does not offer land protection in itself, but people does not get a community feeling from this as they do with factions and towny.
I would say that many big survival servers have a form of team plugin. but the problem with plugins like e.g. towny is that it does not offer any protection for players without town, and using both GP and towny together is messy.
If you had a system like what I describe many plugins may with little effort be able to hook into GP and we can therefore get many interesting plugins as a result.I love GP but many of the people I know rather want to use Towny instead, since it offer more community feeling. I really hope you will reconsider, this could give make your plugin a lot more popular.
-
View User Profile
-
Send Message
Posted Oct 16, 20148.4 Updates
@Sinuce
I don't like that doing a little hop to an intermediate version partially solved your problem. There's a bug there somewhere, I'll keep thinking on it.
-
View User Profile
-
Send Message
Posted Oct 16, 2014@bigscary
What's the path to your folder where claims live? Is it GriefPreventionData/ClaimData or GriefPrevention/ClaimData?
Back in build 295 it was GriefPrevention/ClaimData. After converting with 8.3 using TheShadbusher's method (upgrading to 8.1 first -> then to 8.3) it's GriefPreventionData/ClaimData.
Thank you for your time :)
-
View User Profile
-
Send Message
Posted Oct 16, 2014@Noisebound
Hmm... try 1.7.9 R0.2 instead, that's what I tested with and released for. The version mismatch COULD be the reason for the weirdness. Not reproducing this problem on my test server or on my development box - there's gotta be something else going on, here. Also you could try disabling all your other plugins except grief prevention, to see if there's a conflict problem.
-
View User Profile
-
Send Message
Posted Oct 16, 2014@bigscary
Thanks for your reply. I'm using 8.3 GriefPrevention and 1.7.2 r0.3 craftbukkit. Reinstalled both of them, still the problem remains.
-
View User Profile
-
Send Message
Posted Oct 16, 2014@confuser
Sorry I don't have hard numbers on how fast the migration speed is now versus what it was before, because I don't have a suitably large set of test data to measure with. I've heard very positive feedback, though - anecdotally, hours instead of days for very large servers.
@Noisebound
Well that's a very bizarre problem to have. What version of CraftBukkit are you running, and which version of GriefPrevention?
-
View User Profile
-
Send Message
Posted Oct 16, 2014I have a big problem! The claim of a player do not work when the player is offline. Everything can be destroyed and accessed. When you click with a stick on a player's who is offline territory it doesn't say anything. Please help
-
View User Profile
-
Send Message
Posted Oct 16, 2014@bigscary
I've got around 17k ClaimData files and 135k PlayerData files, however we're still on 7.8 as 8.1 took far too long to convert. Looking at the changelog, how much has it sped up?
-
View User Profile
-
Send Message
Posted Oct 16, 2014@erik1988
I have something similar to that for admins, using permission nodes. I probably won't add a feature for players to create groups because it would be a lot of coding and I don't think very many players would use it. If your interest is administrative, do it like /trust [my.permission.node].
@TJW28
Yeah I get where you're coming from on that. I'm planning to just have visualizations disappear on their own after a couple of minutes, and also to have visualizations disappear when something is too far away (so you could right click straight up into the air to make a visualization go away).
@delsolsi213
It would be great if I could get that from you. I don't actually need the player data, just the claims. Maybe upload to one of those nifty file sharing websites? I think onedrive does 5G for free if you don't already have an account somewhere else.
@Sinuce
Glad you got this to "good enough", although I wish you'd had a better overall experience. What's the path to your folder where claims live? Is it GriefPreventionData/ClaimData or GriefPrevention/ClaimData?
@theory18
Sorry to hear that, can you get me a pastebin of your boot logs from when you first switched? There's no repair option, only rollback with a backup and retry (but let me investigate before you retry... for now restore backup and use an older version of GP so your players can continue playing).
@LordDWT
Thanks, made a note, will look into that. :)
-
View User Profile
-
Send Message
Posted Oct 16, 2014@bigscary
Just notice an issue. I can create a claim and then when i try to transfer the claim to "player" the claim is transfered instead to "PLAYER". I can't figure out why this particular player always transferred in caps. I can transfer to others just fine.
-
View User Profile
-
Send Message
Posted Oct 15, 2014I ran into a problem when updating when updating from v7.8 to 8.3,
none of the claims were personal anymore but he converted them all to administrator claims. This is what i get from console
15.10 21:26:16 [Server] INFO GriefPrevention: Converted land claim to administrative @ Location{world=CraftWorld{name=world},x=-6553.0,y=69.0,z=-4445.0,pitch=0.0,yaw=0.0} 15.10 21:26:16 [Server] INFO GriefPrevention: Couldn't resolve this name to a UUID: ComedyGM.
Any way to fix this please? My previous version was v7.8 i'm not using bungeecord
-
View User Profile
-
Send Message
Posted Oct 15, 2014@bigscary
"During boot, does the # of claims loaded match your expectations (see logs)?"
Thank you for replying so fast. No, it's loading 0 claims: http://pastebin.com/Tt4bMaQU
Even though it has converted all claims (screenshot): http://i.imgur.com/5dqaEN0.png
EDIT: Just FYI; Changing from Flat File to MySQL doens't affect the outcome.
@LeeTheENTP
Thanks, I will try that as well :)
UPDATE: At first glance, upgrading from my old GriefPrevention build 295 (??) to 8.1.3 first and then afterwards to 8.3, seems to work, TheShadbusher. My subdivided claims are, however, lost in the process - but that's not the main priority here right now, so that's good enough for me :)