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 May 20, 2012other suggestion: if possible make the protection lost effect after 20 days of player offline.
-
View User Profile
-
Send Message
Posted May 20, 2012I've installed the plugin, and it appears to be working perfectly for the protections I need within city limits, however I've disallowed generic users from claiming plots while my server is currently in pre-launch as I don't want a bunch of claims made in the wilderness before we launch, unfortunately this mod is not allowing anyone (except op) to build in the wilderness without having first set up a claim, which can be problematic since I want to allow my friends to help prepare the map for players, but I don't want to give them full access to my admin commands.
My question is: how can I change this behaviour? I'd like to allow them to build freely in the wilderness without having to first claim a piece of land.
-
View User Profile
-
Send Message
Posted May 20, 2012other suggestion: I want disable pvp in my claims. And a reload command to reload config.yml.
-
View User Profile
-
Send Message
Posted May 20, 2012Suggestion: make some thing to block the sethome from others players on my land.
-
View User Profile
-
Send Message
Posted May 20, 2012I am getting more of this erros http://pastebin.com/gn1wSTMe Maybe are conflict with other plugin.
-
View User Profile
-
Send Message
Posted May 20, 2012I have an enhancement idea for initial protection creation. Most of the time on my server people do not place chests until they actually need to store what they have in their inventories. It takes time to fill the inventory though, and in between they start building houses from planks and get griefed.
I would like to suggest that the actual first placed block that is not a dirt block would create initial protection instead for the abovementioned reasons ;)
-
View User Profile
-
Send Message
Posted May 20, 2012Lava is not working properly on my server.
I have very few addons (Essentials, GriefPrevention, NoCheat, Orebfuscator)
Nobody can place lava inside their own claims no matter how old they are. As admin, I have no trouble doing so, but I've confirmed that it is not allowing lava placement after one hour like it's supposed to.
Anyone else having this problem or can shed light on a solution?
[EDIT] - Also, no error message is displayed. The lava just disappears instantly when placed, even in ones own claim, even if it's over an hour old.
-
View User Profile
-
Send Message
Posted May 20, 2012Sadly, I have had to disable this plugin because TPS fell to 10 every time we used it (or sometimes as bad as 3). I having the timings if you need them, but it has been 20 ever since I removed it from NoobCraft. It is an awesome idea, but I can't run it in its current condition. I am pretty sure I posted the timings here before, but I can do it again if you need. Also, I am sure this plugin wasn't designed the way my moderators were using it (claiming entire continents and giving out trusted claims to users to build in their cities). If you have any ideas as to why this plugin would be causing terrible server performance, please let me know. I tried it on windows 7, Ubuntu, open source java, java 7, with and without GPrs, turned off all our ore obfuscation plugins, changed nocheat plugins, disabled magic carpet, tried different versions of essentials, different versions of multiverse, disabled our skylands map, etc.... I am out of ideas.
-
View User Profile
-
Send Message
Posted May 20, 2012Does anyone know to use this together with chestshop?
I want them to be able to use the shops but not open the chests or anything else (levers, beds...)
Never mind it works fine, my mistake...
-
View User Profile
-
Send Message
Posted May 20, 2012@mailtomomo
You can just download the sources from github and edit the messages you want. Most of them located inside of the "GriefPrevention.java".
-
View User Profile
-
Send Message
Posted May 20, 2012Is there a way to customize the various messages? ( beyond the spam/ban warning )
I've tried it on my little server, but since not everyone speak english, i find myself having to explain how it work each time...
-
View User Profile
-
Send Message
Posted May 20, 2012@bigscary
Just tried the creative mode and I like the way that you have to have a claim to be able to build, but this still seems to apply to me as an OP and with the griefprevention.admin.* permission. Is there a different permission to let me build everywhere in a creative world?
Edit: Just discovered that I just have to use /ignoreclaims or /ic :)
-
View User Profile
-
Send Message
Posted May 19, 2012I have see a error on my console: http://pastebin.com/HmugrisJ
-
View User Profile
-
Send Message
Posted May 19, 2012Can you add a way to define the maximum block limits and the max size of a region for different permission groups?
So defaults can only set up to a 20x20 and have a lower claim limit compared to a donator. And higher groups can set regions larger than 20x20 and get larger claim amounts.
-
View User Profile
-
Send Message
Posted May 19, 2012We are switching from Towny to this plugin currently and ran into an issue we are unable to resolve.
On a subclaim we want a person to have build and chest access. Some want to do all three. But when we do any of the trust commands it removes them from the other trusts.
Is there a way to add one person to multiple trusts in one subclaim?
Thanks for any help!
-
View User Profile
-
Send Message
Posted May 19, 2012@bigscary
That's not about some mods or plugins which are breaking the rules. That's about data handling. I do not know java and i don't want to, but when i'm writing something, i prefer to think that my code must be ready for anything if i'm working with user input or other data. However i appreciate your point of view and if you really don't want to do it just tell me.
-
View User Profile
-
Send Message
Posted May 19, 20123.7 Update!
Now you can protect your creative worlds!!! =D You need to set an option in your config file, though, so GP knows which worlds to treat as "creative rules" worlds. Because these features are new, they probably need improvement. Please submit any feedback you have here in the comments!
With this update, some of your most active players may suddenly notice they have negative claim blocks. This is because I corrected a bug which was not correctly "charging" claim blocks for some claims, so now some players in in "debt". I suggest that you use /acb to go ahead and put these players back in the black so that they can continue to build new stuff and protect it. Sorry about that guys. :)
I'm planning to create a short demo video specifically for creative mode players, after the feature set matures a little.
@deseven
I disagree. Sounds like he's breaking the rules and expecting everybody else to work around him. Anyway I'll see if I can do something for the short term.
@Hoot215
The best solution is to ask the nocheatplus guy to try his best to reduce false positives. In the short term, you can either configure GP to not punish combat logouts, or configure nc+ to have a higher warning level before kicking for that offense, OR to disable kicks entirely for that offense.
@judam
Okay. I don't even know what maximum character limit means. Good luck, please tell me if you figure it out. :)
-
View User Profile
-
Send Message
Posted May 18, 2012When one of my users tries to use a gold shovel they get disconnected with an error saying they've reached maximum character limit. Also getting disconnected with a socketerror after creating a claim. My whole server has been acting up lately (disconnecting, lag) and this is the best lead I've gotten toward the issue. I'm going to run it without your plugin for awhile and see how it goes.
-
View User Profile
-
Send Message
Posted May 18, 2012There seems to be an issue with kicking players who are in PvP combat and them dying and losing all of their items. This wouldn't be an issue if the player deserved to be kicked, except that we have NoCheatPlus on our server, which sometimes has false positives. Sometimes players get kicked for hacking when they aren't actually. This happened today during our Hunger Games event, and the player died unfairly. I know this is technically NoCheatPlus' fault for having false positives (and maybe also partially my fault), but it would be great if you could fix this issue. Thanks again for all of your work on this plugin.
-
View User Profile
-
Send Message
Posted May 18, 2012@bigscary
It's a null pointer exception.
A man who ported this mod told me that "plugins are expecting the interact event to contain something (a block?) but the event from this mod does not have it. Could be fixed by having these plugins check for null in their event handler, or changing the mod to not send events like this. Hard to say which is best, but I'm leaning towards asking the plugins to change – ideally, they should be able to gracefully handle any kind of event, even those generated by other mods or plugins".
So what i'm asking is to filter such cases. Something like that should help: