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 Jan 26, 2013Too many files open and too many claims. One high quality server with minimum plugins, 20k claims, server's laggy and too many files open. Please have the option to limit how many claims a player can make. Thanks
-
View User Profile
-
Send Message
Posted Jan 26, 2013Could u make it possible to disable /trapped command? I don't want players to be able to leave certain regions.
-
View User Profile
-
Send Message
Posted Jan 26, 2013@bigscary - I saw your note about certain mods using fake players to update their components and the risk of adding these player names to PlayersIgnoringAllClaims: in config.
What if Grief Prevention were to assume a 1 block buffer, basically the claim border, where these "fake" players were not allowed to make changes? This would theoretically allow these mods to function normally in most of the claimed space without the risk of abuse by griefers.
Basically make it so the owner of a 9x9 claim could build functional machines within the interior 7x7 area of said claim.
I think this could currently be done manually by subdividing a claim and granting the fake users permissions to the subdivided claim. It would, however, be nice to have an automatic option.
-
View User Profile
-
Send Message
Posted Jan 26, 2013@bigscary
Not just walking around in, but getting into places they shouldn't be. What's the point of locked doors if players can easily bypass them with ender pearls? You might argue that they can make it ender pearl proof but that wouldn't look very nice on most builds like huge castle walls.
-
View User Profile
-
Send Message
Posted Jan 26, 2013@Absolutionmc
It runned my 350 player server like a charm. Its really not CPU power taking.
-
View User Profile
-
Send Message
Posted Jan 26, 2013Is this plugin cpu efficient enough to hold a 200 player server? Another thing that I wanted to ask, I'm thinking to move from world guard and protection stones, I don't know but there I had about 15,000 protections, and I just wanted to know if it would be more efficient to have those 15,000 protections on grief prevention. The plugin looks really easy to use and learn, but if the performance gain isn't that big from lwc/w.g/protection stones (those are the ones i'm using) then it's not that helpful.
Thanks
-
View User Profile
-
Send Message
Posted Jan 25, 2013Where are the permissions? I need them for my server. Please respond back as soon as possible, thanks :)
-
View User Profile
-
Send Message
Posted Jan 25, 2013@deleted_9935739
My plugin is about preventing griefing. How is walking around in a player's area griefing?
@Hoot215
Oh sure, thanks for that. I wasn't aware of the problem. :)
@Tr33x0rs
I warned you it would wreck house, man. Basically, old claims will now disappear as new claims are added.
@RemyPas
I'll consider it. Please explain how getting into somebody's area is griefing them, though?
@fungreenfox
Please update. It looks like a bug I fixed in 7.2.1. Also, please use pastebin when you want to share a stack trace. :) Thanks!
@deleted_9935739
You could get my population density plugin, which will fix that. But it also has other features you may or may not want. There are definitely plugins available to remove entities (animals, monsters, items, etc) when there are too many too close together.
@Haaaaanzz
Which version are you on?
@DetectiveButler
I'm not sure. Do you mean that in ANOTHER player's claim, you're able to place but not break while in /ignoreclaims mode?
@colomnon
Dunno, you tell me. I build plugins for CraftBukkit. Does TekkitLite include CraftBukkit? You could try what ooarashi suggested.
@Krankbait1
That's not accurate - their player slots are assuming you have a Vanilla server, not a CraftBukkit server. CraftBukkit recommends 1GB per 20 player slots. I'm glad you like them, though. :)
-
View User Profile
-
Send Message
Posted Jan 25, 2013Beastnode.com For the win! and their prices are lower now than what you say in your description just to let you know. Its $10 for a 24 slot server
-
View User Profile
-
Send Message
Posted Jan 25, 2013@colomnon
You may be able to use BukkitForge to use Grief Prevention with a Tekkit server. I am using it with a FTB Direwolf20 modpack server.
Also, be aware of the notes about Tekkit in the main page for this plugin.
-
View User Profile
-
Send Message
Posted Jan 25, 2013does this work with tekkit lite yet?
-
View User Profile
-
Send Message
Posted Jan 24, 2013@diannetea I agree the current spam detection seems a little oversensitive. So far I've seen someone only has to "fail" once in order to get muted, even if it's as harmless as not being joined to a chat channel or repeating a line a single time.
-
View User Profile
-
Send Message
Posted Jan 24, 2013On tablet so this is gonna be short, what determines spam?
2013-01-25 00:43:35 [INFO] [HomeSpawnPlus] New player asdf detected. 2013-01-25 00:45:53 [INFO] GriefPrevention: Muted spam from asdf: heroo! 2013-01-25 00:46:22 [INFO] GriefPrevention: Muted spam from asdf: herro!
-
View User Profile
-
Send Message
Posted Jan 24, 2013I can place red-power devices such as timers inside a player claim, but can not break them as expected. I have added them to the config, is this just a glitch?
Thanks again for making an admin's life allot easier.
-
View User Profile
-
Send Message
Posted Jan 24, 2013Hi! I have a problem on my server, once in a while a player will ask for help because (s)he has a negative amount of claim blocks. This happens pretty often and I always have ot give them claim blocks. You know the cause of this issue and how to fix it?
-
View User Profile
-
Send Message
Posted Jan 24, 2013So it turns out all the lag on my server comes from players having farms with 300 or more animals in their claim. Is there a way you could limit the amount of animals a player can have in their claims? I don't want to get rid of creature protection altogether.
-
View User Profile
-
Send Message
Posted Jan 24, 2013im getting this error very often:
bukkit 1.4.6
16:34:44 [SEVERE] Exception in thread "pool-1-thread-65" 16:34:44 [SEVERE] Exception in thread "pool-1-thread-63" 16:34:44 [SEVERE] org.apache.commons.lang.UnhandledException: Plugin GriefPrevention v7.2 generated an exception while executing task 417614 at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.removeSandstone(RestoreNatureProcessingTask.java:204) at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.run(RestoreNatureProcessingTask.java:112) at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53) at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) ... 3 more
16:34:44 [SEVERE] org.apache.commons.lang.UnhandledException: Plugin GriefPrevention v7.2 generated an exception while executing task 417618 at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.removeSandstone(RestoreNatureProcessingTask.java:204) at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.run(RestoreNatureProcessingTask.java:112) at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53) at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) ... 3 more
16:34:44 [SEVERE] Exception in thread "pool-1-thread-66" 16:34:44 [SEVERE] org.apache.commons.lang.UnhandledException: Plugin GriefPrevention v7.2 generated an exception while executing task 417617 at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.removeSandstone(RestoreNatureProcessingTask.java:204) at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.run(RestoreNatureProcessingTask.java:112) at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53) at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) ... 3 more
16:34:44 [SEVERE] Exception in thread "pool-1-thread-67" 16:34:44 [SEVERE] org.apache.commons.lang.UnhandledException: Plugin GriefPrevention v7.2 generated an exception while executing task 417615 at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.removeSandstone(RestoreNatureProcessingTask.java:204) at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.run(RestoreNatureProcessingTask.java:112) at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53) at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) ... 3 more
-
View User Profile
-
Send Message
Posted Jan 24, 2013@deleted_9935739
@bigscary
I would like to adress this as well. I have no issues with people 'pearling' into claims that have insufficient protection against it. But as of recently. Players have found a glitch to abuse Enderpearls to get through solid walls and enter claims that way.
It is explained here: Youtube of EP abuse
-
View User Profile
-
Send Message
Posted Jan 23, 2013@bigscary
Well I'm not sure what deleting the "griefprevention_nextclaimid" table did, but all my claims are still there. I am just opening the server back to the public, so we'll see if they complain that their claim blocks are missing, or if when they make a new claim it'll delete other claims, or what.. Do you know what this table stores?
-
View User Profile
-
Send Message
Posted Jan 23, 2013I've been using this for a long time. It has never failed me.
Keep up the great work!