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).
@xDizasterCYx
I cant see any other possible cause than this being from a plugin detecting what biome/block type player's are walking on. Most likely a skript, or something else, trying to detect either the block below you, or the biome player's are in. And this will cause lag if not made properly.
If it's not a skript, please let me know what plugin it is, because i'd love to make The Norsemines players more focused on survival. A plugin that makes it scary in darkness is "hard+" material :)
(With skript, or most likely any plugin, detecting each players surrounding at EVERY MOVE, would cause strain on the server.)
Other than that, i guess you would need to check with a 'stick-click' if these glowstones are actually even from claim borders/corners.
As a sidenote, 14 versions of Spigot behind (from the one that was was current yesterday, 24.05.15), i had a problem where blocks would turn to dirt and diorite whenever they got updated.
Are there any 1.7 forks or versions of the plugin?
@robvan
Tried this already, even when I don't have a golden shovel in my hand it still appears, but you know why that is bad for me? because i am using custom plugins that makes minecraft more scary when you are in dark areas, for example voices using nbs and more. Also it causes so much lag when moving.
@Jikodis
Building and using the latest Spigot JAR file fixed the issue. I wish you could just download the JAR files, but I guess building them works too...Thanks!
@xDizasterCYx
I believe that is from showing you the edges of your claim. If you put away your claim tool (e.g. Golden Shovel) then those should disappear. It may take a minute or two. Someone with more experience with this plugin may know more.
Hello I want to ask something,
When I just walk glowstone appears under my feet, it's fake but I don't like it, here's a screenshot:
http://prntscr.com/794cyn
Is there any way to get rid off from this?
Hello. Does anyone know how to get a list of admin claims? I've tried /claimslist, but it always returns personal claims for the adminstrator. I've also tried switching to /adminclaims first, but the /claimslist still returns the personal claims. I've also tried "/claimslist admin" and "/claimslist administrator".
Thank You.
@Vtownhood
The plugin works best when people claim the ground, then start building. The claim depth will automatically be adjusted as they build. If they build first, then do something like claiming the roof of the building, the claim won't necessarily go down to the ground.
One possible fix is to place and break a block on the lowest level within the claim. That should adjust the claim depth. But I'm not sure if placing+breaking a single block is sufficient.
@Vtownhood
There is a config parameter for this. By default, claims only go a few blocks down. The following is from the documentation:
Claims.ExtendIntoGroundDistance: 5
How far into the ground a new claim should extend from the golden shovel location. If the golden shovel is used at two different heights, the lower value will be used in conjunction with this variable. To guarantee all claims run all the way to bedrock, use a very large number. The default doesn't sink to bedrock because that would effectively claim valuable ore that the player placing them claim hasn't discovered yet. Please note! As a player digs or builds underneath his claim, his claim automatically sinks lower with him. Thus, mine shafts and basements are safe from grief even if you set this variable at a small value.
There is a sort of glitch I'm experiencing because my players have complained about this when their stuff gets robbed. I am running the latest Spigot and griefprevention (even the one posted 12 hours ago). It seems as though when players claim their land, the protection only goes a certain distance when a block is covered. What I'm saying is, that everything above ground is protected, however, things like caves can be exploited to go under someone's claim because they seem to be unprotected. The unprotected zone in the ground usually runs about 4 to more blocks down. This also affects houses sometimes when it counts the roof or they are underground. I've gone over it with the claim stick and it proved that the above layer is protected as normal but under it stays unprotected. There maybe an issue with some players unclaiming other people's land, but I have to proof of that so I consider it a rumor. Thank you for any feedback.
@dutcholdskool
I am now using the latest version of the plugin (11.6.2) I am still on build 373 of Spigot. People are still able to kill horses and explosions do damage. They can't destroy blocks through other means though...My config file is fine since it worked before. I will contact my hosting and ask them to update the Spigot JAR files. Otherwise I will have to figure out how to make my own builds of Spigot. It looks a little daunting and I am a web developer even...Thank you!
@bigscary Fixed. Thank you!
11.6.2 Updates
@keytastic
I'm not saying it can't be done, just that I haven't bothered to code it. You can probably do it - one thing to watch out for is that there has to be a special file (I think _lastClaim or something like that) which has an integer in it which will be the next claim number (or maybe its the last claim number?). Try file mode on a test server to see an example.
@MotheMan
So /ignoreclaims doesn't let you override? Sounds like an oops on my part. I'll get it fixed.
@Kepler_
You don't want them crafting the required tool? Help me understand the motivation. Maybe we can come up with a good solution together.
Do you think it would be possible to add a feature to disable using gold shovels (or whatever the claim item is set to be), so players can't craft/use gold shovels normally, and can get them by typing a command?
@bigscary
You're a champion. Thanks for adding the pvp override. Slight problem with it is that when respecting claims i get the message that i'm in a pvp free zone, however when i do /ignoreclaims i get the message that the other player is in a pvp safe zone. Any idea why? do i need to add another permission node or change the config?
Are you 100% positive there's no way to convert a database back to flat files? I'm tempted to do it by hand, if that will work. My host recently stopped being able to maintain a database connection to save its life. In fact, when I submitted a ticket they actually blamed your plugin >:( wth
11.6.1 Updates
@Jikodis
See dutch's comment below. If that doesn't help, you can eliminate other plugins interfering as a possibility by temporarily disabling everything except grief prevention. If even that doesn't solve your problem, please share your config file's content, and explain exactly what you're seeing that you don't want (inside/outside claims? sea level or beneath sea level? tnt or creepers?).
@TJW28
You mispelled it, and I forgot to add an alias for that common mispelling. I will add an alias. It's /separate.
@Jikodis
The latest build is 421, try using the latest build.
http://www.spigotmc.org/resources/griefprevention.1884/updates
PLEASE be sure you're on a VERY recent 1.8.3 server version. Earlier versions of Spigot/CraftBukkit will not work with latest versions of GriefPrevention, due to breaking changes the Spigot team made somewhere along the way in 1.8.3 development. Symptoms of an outdated server build include errors logged during boot, explosions destroying blocks they shouldn't, and entities like item frames, animals, and armor stands not being protected.
Loving the updates bigscary, though cant seem to get the new /seperate command to work, I have the Permission, griefprevention.separate, though just get unknown command in game.