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 Jan 15, 2013I have a player that is trusted in a subdivision of a claim however they cannot build there. yes they have the main /trust not /accesstrust, etc. i have tried untrusting then then retrusting them ... still no also i really need help FAST EDIT: I have figured it out there was a worldguard region also there preventing players from building
-
View User Profile
-
Send Message
Posted Jan 15, 2013Is it somehow possible to only use the "Restore Nature" part of the plugin. The server I'm running is not really big enough to justify land claiming, but never have I seen a better tool for removing ugly structures (both player made and generated). So if possible I would like to use that part of the plugin only
-
View User Profile
-
Send Message
Posted Jan 15, 2013@ViciousCircleMC
The problem is that your connection is dying of boredom. Once it's dead, it stays dead. I'll look into fixing it, but I'm not making any promises. I don't want to risk breaking it for everyone (the inherent risk in making changes) to save headache of a few who insist on using SQL for a low-pop server.
Also, look into your documentation. It might be possible for you to increase the timeout either in your database settings or your driver settings.
@notif
I'm very glad you figured it out. :)
@panade
Yes, you can customize messages.yml. But be careful, if you make a formatting mistake you will end up with defaults again.
There's no option to configure claim blocks per world. A player gets X number of claim blocks, and he can decide where he wants to spend them. You could potentially grant claim blocks by a permission, and set your permission plugin so that players only have that permission in a specific world. So then only when in that world, they'd have bonus claim blocks.
@ManBeastPigDev
If you're running Tekkit, maybe there are some items you need to ban because they bypass plugins. If not, then check your logs, looking especially for logins around the time of the problem. It could be that someone "cracked" your password using a password guesser, or that of another one of your moderators. Or maybe the griefer is one of your moderators.
@ridddle
Thanks, it looks like I need to double check a few places to make sure the blocks from permission groups are being considered everywhere.
-
View User Profile
-
Send Message
Posted Jan 15, 2013I wanna give this System a Kick and I already like it.
But there are some issues i dont found anything about. 1. Is it possible to Customize the messages.yml? I would like to use a selfmade Translation of it. But GP seems to ignore it generaly. I temporarely removed the write permissions and its still using the english Version. Im a bit confused why this file is even generated.
2. I just miss a function to make Claim Blocks per World active. So 1 World has a amount and the other Worlds have differnt amounts of available Claim Blocks. Its not that big Issue, just wondering if it wouldnt be usefull for a usual Multiworld Server.
-
View User Profile
-
Send Message
Posted Jan 15, 2013FYI - My spawn was griefed last night.
Complete right off.
It's protected by GP "and" worldguard.
No idea how they did it.
MOD EDIT: There is no force op. Personal information removed.
-
View User Profile
-
Send Message
Posted Jan 15, 2013@bigscary I updated and the 60001000 bug isn’t there, but difference between /claimslist and message while holding a bone (we use it instead of golden shovel) is still there – and it’s a difference of 1000, which is exactly how much I assigned to a higher rank. Low ranks don’t have that permission, I triple checked. Also, those 1000 blocks aren’t really there. Players can’t claim more, and their actual limit is that displayed by holding a GP tool.
-
View User Profile
-
Send Message
Posted Jan 14, 2013I figured out what was causing the driver issues. .
It doesn't like the "localhost" part of the address:
URL: jdbc:mysql://localhost:3306/mcd_48
So changing it to the IP resolved that:
URL: jdbc:mysql://127.0.0.1:3306/mcd_48
-
View User Profile
-
Send Message
Posted Jan 14, 2013Great plugin. Truly awesome job! I love the checking the chat for the trapped/stuck word. One issue is it should ignore the case of the words. It currently does not. Not a big deal, however, it is a real easy fix.
Example: Player says, "HELP IM STUCK"
The plugin won't notify the player of the /trapped command.
-
View User Profile
-
Send Message
Posted Jan 14, 20132013-01-14 21:48:33 [INFO] GriefPrevention: Unable to save data for player Legit_Monkey_28. Details: 2013-01-14 21:48:33 [INFO] GriefPrevention: No operations allowed after connection closed.Connection was implicitly closed by the driver.
I'm having the same issue as notif. This is not a problem with the MySQL server or the connection to it. When this is happening with GP logblock continues functioning normally. For that matter even when the MySQL connection is temporarily severed logblock is able to start communicating with it again once connectivity is restored. I'm not sure how we are supposed to investigate and fix something that clearly isn't within our control to either investigate or fix. I understand that using a database is optional but if you are going to just disregard reports of it being broken then the option should be removed entirely. If this issue can't be resolved I'm going to end up having to stop using database storage for the plugin, which means every claim will be lost along with the number of blocks people have accumulated from playing. At that point I'd seriously debate just going back to letting people rely solely on their Factions claims as a means of protection and ditching GP entirely.
-
View User Profile
-
Send Message
Posted Jan 14, 2013@KStorm1
Hmm, I might just disable zombie door breaking in admin claims. Let me think on it. The other solutions you recommend are doable but very difficult to code up and test.
You can use /subdivideclaims to make a subclaim around the chest or group of chests, and give a player or permission group the option to use them with /containertrust.
Adding regeneration is just too hard for the small payoff (griefers are already stopped from griefing with the current code). You could consider the CreeperHeal plugin in addition to Grief Prevention if you want that very badly, but that will only help for outside of land claims where it's possible to disable GP's explosion protections.
@Jackalmen
Please double check the delete all claims thing, and make sure you're typing the player's name exactly right, and then right-click the area which should have been unclaimed with a stick to verify it was correctly unclaimed. When I tried it just now, it worked for me. If you still see the problem on your end, please try to provide me some more details, if you can think of any.
I will try with the anvil to see if I can reproduce it as well.
@GeoChargerGaming
Please review the configuration page. Radius = -1. But I recommend against it, because in many cases players will have unprotected stuff which will be stolen and/or destroyed.
Not in game, only one player at a time. If you want a mass delete, shut down the server and use the file system (or SQL if that's what you have set up). You can do a file search or SQL query to find exactly the claims you want deleted, and delete only those.
@myCraftServer
Yes, add the timer ID to your containertrust list. See configuration page, Mods section.
@TD751
I use PermissionsBukkit because it's simple.
@codiaz
Database is an option. The ram footprint is very efficient.
@notif
Driver error? Are you talking about database something? Sorry, but that's up to you to investigate and fix.
@ridddle
You need to update to a later version. That bug is already fixed (I think), and players now have /claimslist (without a parameter) to get their own data.
-
View User Profile
-
Send Message
Posted Jan 14, 2013@riddle
This is hard for me to test on my server. If I disable GP, chaos and mayhem would ensue. It is an issue that is seldom seen, but is fixed easy.
-
View User Profile
-
Send Message
Posted Jan 14, 2013@giggaflop Just assign them a huge number via:
Brackets are necessary.
And then add a permission to their user or group:
claimblocks.over9000Didn’t test huge numbers like that, it might break.
-
View User Profile
-
Send Message
Posted Jan 14, 2013Hello, would it be possible to add a permissions node to ignore the number of claim blocks someone has so they can claim as big as they like?
-
View User Profile
-
Send Message
Posted Jan 14, 2013Hello again! I have a bug report to file: it seems that /claimslist adds bonus blocks wrong, because when a player has 6000 bonus blocks adjusted manually and 1000 blocks from permission node, it shows (60001000). Without passing judgement, I think you need to convert those to integers. :-D
Also, sometimes my players report different amount of blocks in /claimslist (I’ve given them out a permission using CommandHelper’s alias (/blocks) which points to /claimslist <their-name>). Like, /claimslist will show 1500 while bone only 500.
The additional 1000 is for a permission node, but it’s for a higher group then they are. Is it possible that the code fails to check the group properly?
@Jackalmen
I have the same problem on my server! Have you tested this without GP? I think it’s Minecraft’s problem where you need more levels server-side than it shows client-side.
-
View User Profile
-
Send Message
Posted Jan 13, 2013@bigscary
The server has eight people on right now, and it's still spamming the driver error to the console. This happens when there's more people on, too.
-
View User Profile
-
Send Message
Posted Jan 13, 2013how i can create a pvp area
-
View User Profile
-
Send Message
Posted Jan 13, 2013Nice plugin but i am sure that because it uses no database it uses more ram than necessarily need to be used
-
View User Profile
-
Send Message
Posted Jan 13, 2013Just what i need oh yeah whats the best permission system for this plugin?
-
View User Profile
-
Send Message
Posted Jan 13, 2013Can you add it so timers from Tekkit can not be changed when claimed?
-
View User Profile
-
Send Message
Posted Jan 12, 2013Ok 2 questions. First how do you disable auto claim with the chest. Next is their a way to delete all player claims at the same time without deleting admin ones.