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 Feb 26, 2015@erik1988
Don't give it to your players - it's an administrative command that will change the owner of ANY land claim, even of those land claims you don't own yourself. Even if it were restricted to only the claims you own, it would still be a bad idea to give to players because by giving claims away to others, players could cooperate to claim an unlimited amount of land.
@danf21
Either upgrade your server to 1.8, or use a version of GriefPrevention made for your server version.
@switorik
Thanks, I'll investigate both. :)
-
View User Profile
-
Send Message
Posted Feb 26, 2015How to fix this Error? http://pastebin.com/2Xu8bSC3
-
View User Profile
-
Send Message
Posted Feb 25, 2015@bigscary
How does this "transferclaim" cmd work? (missing from the docs). Is this something that is safe to give to players? My interpritation is that you can send players your claimblock, is this correct?
-
View User Profile
-
Send Message
Posted Feb 25, 2015Running the latest griefprevention and spigot builds I think I have come across two bugs. I still have the bug where zombeis can not attack villagers in someones claim and also players with permission trust in a subclaim can not trust other people to that sub claim (unless they have that trust level on the parent claim).
-
View User Profile
-
Send Message
Posted Feb 25, 2015Hey everyone, I updated the docs. :) If you notice anything missing, please tell me. Thanks! Sorry I took so long to get around to it.
@zedadiaswick
In modern versions, it only changes the recipient list. It used to do the other thing.
@daycraft
You say your players can use slash commands, but not right click? I don't believe it. Anyway, they should watch the demonstration video which actually shows them how to do everything, and which is linked to them directly in the game. I don't see how it could possibly be made any easier - maybe your players would be interested in an in-home tutoring service for land claims?
@MoldySpore
You shouldn't expect any issues running GP on an old map. GP no longer removes water when claims are removed, except for in creative mode worlds.
About collecting the border items, I think either you're thinking of another plugin, or maybe you grabbed a very bad version from when I wasn't working on the project. This comment is the only time I've ever heard of anyone being able to collect the border blocks, so I'm sure you're safe there. Also, they do disappear automatically after an amount of time now.
@groovyloopylou
You can use a negative number to remove blocks with /acb. Note that if a player actually has land claims which add up to more than his current block total, his block total will automatically increase so that he doesn't have less than 0 total blocks. So you may have to actually delete some land claims in that case.
@MrsWaterhouse
I think you should ask the MCProHost staff for instructions on how to install plugins on their servers. On every server I've ever used, just uploading GriefPrevention.jar to the "plugins" folder worked great.
-
View User Profile
-
Send Message
Posted Feb 24, 2015@groovyloopylou
/adjustbonusclaimblocks <player> -600
just use negative numbers, rather than positive :)
-
View User Profile
-
Send Message
Posted Feb 24, 2015I am having real trouble adding this to my MCProHost server. Any suggestions please? I have changed my server type to Spigot version 1.8 - Downloaded the GP.Jar - renamed it to custom.jar Still nothing. Also I have not idea where to look for all the custom options? Please help Many thanks
-
View User Profile
-
Send Message
Posted Feb 24, 2015@groovyloopylou
@groovyloopylou: with a minus /acb player -10
-
View User Profile
-
Send Message
Posted Feb 24, 2015Quick Q, how do you remove bonus blocks from a player? /acb just keeps adding and adding them on...
thanks
-
View User Profile
-
Send Message
Posted Feb 24, 2015@MoldySpore
Hey MoldySpore: I run GP on my Tekkit Lite (MC 1.4.7, GP 7.6.2) server and have no issues.
So if you decide to install a plugin you do not have it on the server so far. So it always starts on an 'used' map. You don't have GP so you don't have any claims. You install GP and you still don't have any claims and data in GriefPrevention. You claim a land area and a player file (yours) and a claim is being created. So 2 files.In the player file the last login of the player is stored and how many claim points he has. In the claim file the player name/uuid (yours) is stored together with the claim coordinates and world, who is trusted and so on.
So nothing which depends on your world or map. If you delete a world which is still in the config you get a warning message only.
I don't know which version you did use (maybe that had some bugs or did not fit to your craftbukkit version) but I guess you got these issues because any other plugin was interfering with GriefPrevention at this time handling events in a wrong way or something.
And if you try GP together with dynmap (as you wrote), try out my little plugin which shows GP claims on the dynmap ,)
http://www.spigotmc.org/resources/jdynmapgriefprevention.818/
-
View User Profile
-
Send Message
Posted Feb 24, 2015Hello i was wanting to know if this would work on a realm of mianite server? if someone could get back to me that would be great
-
View User Profile
-
Send Message
Posted Feb 24, 2015I tried GriefPrevention out about a year ago on our existing SMP server, but ran into a lot of strange issues, such as flowing water disappearing even inside claimed land and land claim borders that never disappeared (the blocks at the corners of the claim areas never disappeared, and actually became part of the landscape, you could even mine them out and collect them although they turned back into what block was supposed to be there after it was in your inventory)
This all took place on an existing map that has been around since 1.6.x (several years). Is there an issue with implementing GriefPrevention on an existing map that has been around for as long as ours? Were the issues I ran into known issues that have since been fixed? I didn't see anything in the change logs about those specifically.
We are currently running Spigot 1.8 w/ Dynmap, Essentials, and GroupManager. No other plugins. I really want to implement GriefPrevention so I can open my server up to some additional people who aren't friends and family, but have had little luck in the past. Any advice users of the plugin have for preparing to implement it on an old world/map would be much appreciated!
-
View User Profile
-
Send Message
Posted Feb 24, 2015@daycraft
@daycraft:
Yes, that's really complicated. You just take a golden shovel and click on 2 points...and everywhere in the area the 2 points span up another player cannot do anything anymore.
Maybe an easier way would be if every player on your server just remembers where his claim is located on his mind, so you need no plugin. And if someone else wants to build/destroy/grief anything at this place the player could just say: 'Stop, that's already my claim!' ,)
There are a lot of videos showing how the basics work.
-
View User Profile
-
Send Message
Posted Feb 23, 2015@bigscary
I'm just after some clarification as to how GP's anti-spam works. Does it just modify the recipients of the messages, or does it replace the messages with it's own when sending the players' own message back to them?
-
View User Profile
-
Send Message
Posted Feb 23, 2015Good Day!pls tell me ,u fix restorenature when claim expire?
-
View User Profile
-
Send Message
Posted Feb 23, 201510.8 Updates
Please take a few moments to vote for Grief Prevention! :) We're only 35 total 5-star reviews away from being the top plugin on the spigot site, which is absolutely a reachable goal. Thanks for your support! http://www.spigotmc.org/resources/griefprevention.1884/
-
View User Profile
-
Send Message
Posted Feb 23, 2015@The_PC_Tech_Guy
You can change the message shown in your messages.yml file. Try changing it to give instructions on how to use your preferred land claim plugin.
@bikerider123
Resetting your position...? To what?
@Duning
PvP rules will still apply when a world is set to "disabled" in the claims section of the config file.
@GodsDead
Hmm.. I looked into your issues regarding claims/subdivisoins and invincibility.
I made a small change to invincibility by checking inventory at the time of respawn. Are there any ways your players can get items into their inventories aside from either picking them up off the ground or from a container like a chest? For example, slash commands or other plugins' features?
About land claims changing, I couldn't reproduce it over here. When you create a subclaim or resize a claim, GP immediately tries to save your changes to the DB. WIll you please check for any logs messages at the time you do either of these things? If you don't see any, consider database logs or database settings. Let me know if you come up with any hints!
@Jikoo_K
I could, but someone would immediately complain that it should be containertrust because people are "stealing" their wool. Even if I made it a config option, some players on the same server would be happy while others would be not. :\
@Phreag
Thanks for the logs! No, you can't disable caching, it's very important. Maybe I can shift it to another thread, since it doesn't have to be done immediately at boot.
@keytastic
There's a delay by design - I think it's 5 minutes, to give the player a chance to change his mind. Does that help?
The revert after siege feature is gone.
@zedadiaswick
I have no idea... maybe someone more familiar with Skript can help you?
@CyberDrifter
Thanks, will look into it.
-
View User Profile
-
Send Message
Posted Feb 22, 2015It looks like cake is no longer protected (again) Spigot 1.8.1 latest GP build.
-
View User Profile
-
Send Message
Posted Feb 22, 2015I'm trying to create an alternate chat using Skript and fancy json messages, but am having trouble making it compatible with Grief Prevention's anti-spam. I tried combing GP's source but I don't really follow java all that well.
In my skript I am removing all chat recipients from messages and replacing it with my own json message, this allows logging plugins to log the message (as opposed to cancelling it), I assume GP is doing the same but recipients is always set to be all players, not just the spammer being blocked. Is skript just firing before GP? Should I be trying to do something else?
-
View User Profile
-
Send Message
Posted Feb 22, 2015I'm experiencing 2 problems: