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 18, 2014Are there any new perms for the /givepet command, Im getting unknown command when trying to use it as admin;)
-
View User Profile
-
Send Message
Posted Dec 18, 2014People being able to claim too many areas. I’m not happy how automatic abandoning works and when I had it enabled it led to unhappy playerbase (my rules allow anyone to grief/steal from unclaimed territory). On top of that capping claim number means that people start being conscious what they claim and how they do it. Lastly, their /claimslist screen isn’t a mess. We did a 3rd party “modification” and redesigned that list and split it into two but it would still be a mess for a player with 200 claims: http://imgur.com/a/IYIdJ
Hehe, we are in different time zones it seems. Thanks for the fix.
On top of the algorithm that looks for an air pocket (which is the hardest thing, I realize), we are also checking what the floor is made out (ignoring liquids, fire, cactus, bedrock) of and giving player 10s of Resistance V, giving them immortality (so they don’t instadie when get ported into a hostile mob).
Well crap, I thought that
BuildingOutsideClaimsmessage would be displaying every 10 blocks like in 7.x branch. I placed a few hundred of them now and can’t get it to display. Oh well.My tone definitely needs improvement. Truth be told, what happened with Grief Prevention during last year caused a few grey hairs to appear on my scalp. I think I don’t have to tell you exactly what was wrong but if a staple plugin changes major features or breaks basic functionality every 2 months, players get unhappy and leave.
I’ve had so many issues with GP and I had to change so many design decisions around it changing that I think I may simply be burnt out in regard of my goodwill. I thought everything was rather stable and then 9.x branch comes in and introduces major changes that I have to try to relay to my community, without them burning me at the stake. :)
That said, you are maintaining this page in an exemplary way so I’ll try my best to be an exemplary administrator, working with you for a better plugin. I saw your future plans and I may have some experience to share regarding blocking portals from cutting into claims – we fixed it with 3rd party code on our server, it’s been working fine for last year. Once again, I’m sorry for my tone.
-
View User Profile
-
Send Message
Posted Dec 17, 2014@bigscary
Thanks for the response. If I have surface explosions enabled players shouldn't be able to explode TNT inside players claims should they?
-
View User Profile
-
Send Message
Posted Dec 17, 20149.6 Updates
-
View User Profile
-
Send Message
Posted Dec 17, 2014@ridddle
About water - because giving someone permission to build in a subdivision shouldn't mean he can also build in the top level claim via water bucket dumping. On the inverse situation, why not? Because now we're splitting hairs and I don't want to write special purpose code and risk bugs over a difference I think few will care about. My usual policy applies here - if more complain I will revisit. Just wouldn't be responsible of me to implement asks on a first come first serve basis instead of prioritizing based on how many want it or would likely benefit from the change.
I'm already planning to run the per player limit on number of land claims, if that's what you're referring to. Why is the total number of land claims important to you, anyway? Just curious - your answer might push the priority on this up. Also, can you recommend a default for this setting?
About horse trading, I know how Minecraft works and what players to with horses. If you had waited another 24 hours, you would have had a fix for this. I already promised it and I will deliver it, and suggested two different workarounds, one of which doesn't involve killing the horse (and which you conveniently ignored).
Yes horses are pets. However you can specifically exclude horses from GP's rules in the config, if you want to. I recognize they're more than a little different from other types of pets.
Sheep are protected, ender pearls require access trust on the destination end. Cattle require container trust, so I don't understand your question about villagers. Why not try some of this yourself and then tell me if you don't like it the way it is? Trying it yourself will get you answers in a few minutes rather than waiting hours or a day for my responses.
Don't know what you mean about "sensible defaults", please be more specific.
I'm open to suggestions about /trapped in the nether. I haven't come up with anything that feels "safe" for as you said, less technical users. I worry they'll shoot through the bedrock ceiling or end up in some lava.
About the spam thing - can you describe a situation which produces this type of spam so that I can improve the feature?
As long as you've been commenting here, your tone has always sounded lecturing to me. You'll get better results from plugin devs everywhere if you sound more understanding and patient, instead of judgmental and condescending. For example, a compliment "insightful tester" vs. an insult "combative nitpicker" both work in this context, but the tone is entirely different and the response would be very different. If the idea of "being nice" makes you uncomfortable, think of it as skillful manipulation of inferior beings. :)
@Cammo009
Not sure I fully understand what you want from towns. You want players to not break blocks there unless they claim first? It's not really a solution - players could claim, break, then unclaim to work around the protection you're asking for.
@alhamli99
Make sure you're on spigot or bukkit for 1.8. That's the most likely reason for everything not working. You have to have Minecraft 1.8 for the latest versions of grief prevention to work.
@Duffa13
Not explicitly. The surface explosion protection only applies to worlds where land claims are enabled, though. Does that help?
@modzmarvin
I think that's fixed in 9.5.
-
View User Profile
-
Send Message
Posted Dec 17, 2014I used to be able to control settings such as surface explosions etc per world, can this no longer be done in the config? Thanks :)
-
View User Profile
-
Send Message
Posted Dec 17, 2014Hello, got a issue in the latest version (same for all the versions.) No one can get more claim blocks when they vote so i tried to typing the adjustclaimblocks bla bla bla and it always gives out the same error. Using the version from 7 hours ago.
http://pastebin.com/DmyArBnR
Kind regards
-
View User Profile
-
Send Message
Posted Dec 17, 2014The problem when i do a right click holding the shovel or the stick nothing happen even when i put the chest nothing happen
-
View User Profile
-
Send Message
Posted Dec 17, 2014Thank you Big!
-
View User Profile
-
Send Message
Posted Dec 17, 2014Thanks grief provention to the Pet tamer. love you guy, so happy to get that issue fixed. Cheers
By the way, is there a way to protect a full town region so players cant brake towns unless players place land claims? if town region can be added this be a perfect plugin. we can set admin claims to protect buildings that dont want areas for players to claim in the town regions
-
View User Profile
-
Send Message
Posted Dec 17, 2014hello this plugin dosn't work in my server i don't know what is the problem answer me on skype ID: ii_alhamli
-
View User Profile
-
Send Message
Posted Dec 16, 2014@bigscary
PerPlayerLimit. Having this set in 8.x builds dropped the global number of claims from 19,000 to 4,000 in the same lifespan of two maps. Nobody complained.WarnWhenBuildingOutsideClaimsorWildernessWarningBlockCount. GP defaults are annoying and spamming chat. Having this is similar to whispering useful tips to player instead of scolding them all the time.As for more detailed config options from
Rulessection of 8.x builds, I guess that’s just too granular for your taste. Did you at least move sensible defauls to 9.x branch? Do Villagers require ContainerTrust to be traded with or are they still like cattle? Can I shear sheep in someone’s claim without some level of trust (I shouldn’t be able to)? Can I set specific rules for Ender Pearls? I don’t want people teleporting into claims but once they’re inside, they should be able to use them to escape (we overwrote GP’s /trapped to make it work in Nether and not be a death trap but for non-technical users this kind of 3rd party modification it’s out of the question).Why? Do you know how confusing it will be for players? Subdivisions extend indefinitely too so having dead zones for liquid in your base will be super confusing and/or infuriating.
Are horses pets?
Again, horses aren’t cows. They have unique and many times hard-earned stats. It’s pretty much impossible for your normal admin to know how to clone a horse with their full stats. You should provide a tool to remove tamer tag from a horse, not ask admins to slay those valuable mounts.
-
View User Profile
-
Send Message
Posted Dec 16, 20149.5 Updates
@MrARCO
Inside the admin claim, do /accesstrust public.
If you also want them to access containers and interact with / damage animals and farm, do /containertrust public instead.
-
View User Profile
-
Send Message
Posted Dec 16, 2014Hello Big,
how can i make a spawn in my server, without people claiming my spawn area wich i claimed? They are allowed to press buttons, open doors, etc. new players in the spawn are in my admin claim, but they cant press buttons, etc
-
View User Profile
-
Send Message
Posted Dec 16, 2014@LordDWT
I think GP's anti spawn camping will fix that situation, assuming the player who's being camped doesn't actually want to fight.
Nope, there's no colorful fun stuff and messaging going on with GP's pvp stuff. Just measures to prevent grief.
@snowfox12
Yep, all and public do the same thing.
@dutcholdskool
Elithelion's explanation is correct. You gave them bonus blocks - that doesn't stop them from accruing blocks over time, up to the limit you've set in your config. You could either remove the bonus blocks later after they've accrued their block limit, let them keep the bonus blocks as a "thank you" for sticking with the server, or directly run SQL in your database to give them accrued blocks instead of bonus blocks.
@modzmarvin
Yep I have a fix for the sending message thing coming today.
About the legend - are you saying it's not working for you? You need both the new GP AND the new spigot/craftbukkit. This is because the spigot guys changed how things work, so I had to change how GP works, and now the latest GP doesn't work with older spigot/craftbukkit.
Sorry, I know it's confusing and unfuriating... I've been struggling with the armor stand issue on my server as well. I've already complained and logged bugs - the spigot team isn't as good at this as the Bukkit team was. I guess they just need practice. Other plugins are having the same problem - there's a lot of confusion in the spigot forums around this topic.
-
View User Profile
-
Send Message
Posted Dec 16, 2014@modzmarvin
p.s armorstand protection, what a legend :P
-
View User Profile
-
Send Message
Posted Dec 16, 2014@bigscary
Useing this version of build tools:
Build #17 (Dec 14, 2014 12:29:06 AM)
Using this version of grief provention:
9.4.1 (you put out today)
and here are the errors i am getting now:
http://pastebin.com/9VFsuUFb
There is a lot less errors and can do commands now with the update you just put out but its still going glitchy.
-
View User Profile
-
Send Message
Posted Dec 16, 2014Unless you tell GP not to, the default is 100 blocks per hour of accrued blocks. They won't accrue blocks unles they are doing something so just being logged in and afk won't add blocks to their total. Also, adjusting their claim blocks the way you did gives them BONUS blocks...not ACCRUED blocks. From my understanding GP tracks those totals separately.
-
View User Profile
-
Send Message
Posted Dec 16, 2014@Bigscary:
I'm a little confused here, and I was hoping if you could tell me if I am doing something wrong or that it works as designed.
I recently started a new 1.8 server and we started with a fresh config/database. Because we have a fairly stable player-base I manually adjusted the claimblocks (/acb) of our veteran players to the amount they had on the old server. However, I noticed that the claimblocks keep growing depending on the playtime of the player. I was not expecting this, because the amount of bonusblocks given is larger than the maxAccrueddBlocks setting in the config.
maxAccrueddBlocks: 10000
Console snip: [09:21:38 INFO]: GriefPrevention: e 3780(+13500)=17280 [09:21:38 INFO]: GriefPrevention: e (-2700) towny4(292,5,156) [09:21:38 INFO]: GriefPrevention: e (-1584) towny4(352,21,173) [09:21:38 INFO]: GriefPrevention: e (-209) towny4(273,35,170) [09:21:38 INFO]: GriefPrevention: e =12787
5 minutes later...
[09:26:16 INFO]: GriefPrevention: e 3788(+13500)=17288 [09:26:16 INFO]: GriefPrevention: e (-2700) towny4(292,5,156) [09:26:16 INFO]: GriefPrevention: e (-1584) towny4(352,21,173) [09:26:16 INFO]: GriefPrevention: e (-209) towny4(273,35,170) [09:26:16 INFO]: GriefPrevention: e =12795
-
View User Profile
-
Send Message
Posted Dec 15, 2014@bigscary
I did /containertrust all, So Just now I did /containertrust public, It printed the same message curiously. Dunno if its supposed to be that way.