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).
@missemilia06
Spigot does that, edit the merge-radius in spigot.yml
Does this plugin force XP orbs to clump together? Is there a way to turn that off?
@Bobcat00:
I've updated my plugin for people not using dynmap (even if you already have your own program, maybe other will find it useful ;) )
Claim statistics, export to csv file and teleport commands are available without dynmap.
http://www.spigotmc.org/resources/jdynmapgriefprevention.818/
11.6.3 Update
@GodsDead
:)
There is an issue with the configuration reading CommandsRequiringAccessTrust if the command has a parameter, Im trying to deny the commany /crew sethome, Im assuming since its got a space in the middle its being ignored, or there is a special way to format this that isnt documented, how can I deny this command unless the player has trust? This is from my config:
Typo in /trust, "Graants"
@Wavef0rce
In the config Claims.Mode, change the value to Disabled for worlds which you don't want people to claim land.
@bigscary
I want to say a big sorry, it wasn't GP which was causing this strange glowstone glitch, I'll try to find the solution so I'll inform you if even that happens to someone else to know.
how can i deny a group of players to claim land? I have a plots world and a survival world on the same server. and i am able to server permissions for each world. so i would like to deny permission for one world but not the other.
@bigscary
I am 95% sure that it's GP but today I'll confirm it and try to what is possible to fix, If'll do anything I'll inform you :)
@Jikodis
You can find instructions on how to get your own latest spigot.jar file on the spigotmc.org site. It requires a couple of quick downloads, then one command line. No coding.
@Vtownhood
Like Jikodis mentioned, you can fix this by changing your config settings. I have a todo item to make this happen much less often.
@Bobcat00
Placing one block is sufficient. Breaking has no effect.
@robvan
Sorry no, there isn't one. I will add a command for you.
@xDizasterCYx
This seems very odd - no one else has ever reported it to me. Are you certain there's no other plugin doing this to you? If you have only GP enabled, do you still have this problem? :(
@Nentify
Yes, click the "files" link at the top of the page for older versions.
@norsemines
Let me see if I understand - you visualize a claim, and your sign is replaced by a visualization block (glowstone, gold, wool, etc). When the visualization reverts (goes away), your sign is blank? Don't worry, your sign is safe - if you log out and back in, you'll get the server's version of the sign again, complete with your text. It might even work to right-click the sign with an empty hand (without logging out first). I will make a quick tweak to improve this.
@wd40bomber7
That sounds like a bug I fixed recently - are you on a recent version? If not, please update and try again. Regardless, I'll try to reproduce this on the latest and investigate.
@xSnowBlitzz718
Unlikely. I just don't have the free time to convert a project that took me 4 years to build over to another platform. :( Maybe if I had the kind of time I did when I started the project, but now I have a 2 year old and a second kid on the way. I'll keep refining this and possibly take on some small projects, but porting all of GP over to a new platform would be huge.
A smaller job would be convincing the Cauldron guy to uncancel that project. ;)
Not sure if someone did already but I would like to request this to be ported to Sponge. https://forums.spongepowered.org/c/plugins/plugin-requests
@norsemines
Yeah I've heard of this too, it's bad to hear that you have problems with GP, surely it's another plugin that it's not conflicts with it, when I firstly used GP it wasn't working to me because I was using another plugin called "LightningStick" and it was completely destroying GP, I created another server with GP and I was testing my plugins 1 by 1 but luckily I've found the problem really quick. Even the most irrelevant plugin can be the source of the problem.
So, small bug that's been around for a while.
A person with /trust and /permissiontrust on a normal claim who then attemps to /untrust someone else, gets a message telling them they don't have permission to do that. But the person is untrusted anyways.
I would expect to get a success message instead of a failure message since that seems like the desired behavior.
@xDizasterCYx
Fair enough :) I came here because the subclaim borders seems to remove sign-text where the border.blocks are shown :) E.g Place a sign, subclaim around it, and the border blocks will still remove all content of the signs it touches.
I'm hoping this is a block update problem though, and not something stored.
Your 'trailing glowstone' comment made me think, 'oh *noes* that as well?" :D
My advice would still be to see if it happens around claim borders, by shovel or stick clicking. Or if it even drops glowstone dust/lamps.
(the diorite glitch i mentioned would actually drop diorite from blocks that used to be stone, but that was caused by Spigot) :/ It was/seems fixed by a rebuild of the spigot jar however.
@norsemines
Wait, I wasn't blaming the plugin, this plugin is awesome, I was just asking if it's caused by that or not just to know, I've tested it with and without the custom plugin but this still happens.
@xDizasterCYx
My point was, in response to "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."...GP is not causing this lag, and most likely not the apperance of glowstone. The reason The Norsemines even exist, or is not whitelisted, is because of GP, but in no way or how a fanboy server :).
As long as your custom plugin remains closed-source'd, it seems kind of unfair to report bugs here, outside of tickets, without ruling GP out beforehand. Because it makes GP users, (The Norsemines being one), look for faults unlikely to exist in their setup.
@Nentify
http://dev.bukkit.org/bukkit-plugins/grief-prevention/files
and find the 1.7x versions ^_^
@norsemines
Well, it's not skript. This plugin is custom made by a friend who is developer, I can't share it sorry but you can find an alternate plugin like this:
http://dev.bukkit.org/bukkit-plugins/fear-darkness/
It's outdated but it stills works great, I tested it for you so I'll be sure I'll recommend you something good, however there are no other plugin like this :/
@xDizasterCYx
The claim tool is configurable i think.