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 9, 2013@bigscary
Assuming Claim ID's are unique always, unless the GriefPreventionData folder is tampered with (Including if Claim 6 is deleted, then another claim is created, the new claim will NEVER be claim 6)....
How can I fetch a claim by ID?
Also... How can I retrieve a list of allowed users from a claim and remove them all?
-
View User Profile
-
Send Message
Posted Jan 8, 20137.2.1 Fixes
Those last two of bugs were breakages introduced by the Bukkit team. I apologize on their behalf for the inconvenience, and thank you all very much for bringing all of these problems to my attention. :)
-
View User Profile
-
Send Message
Posted Jan 8, 2013@iBeCreeping
No sorry, it's a one way street. If you go back to file mode, you will lose any data which was added or changed after you switched to database mode. If you're okay with that, then look at the setup/config page for instructions on how you can restore your "pre-database" data, which was backed-up on your hard drive when you switched to database mode.
@voodoo12334
Gotcha. I understand, and I'm sorry you're having that problem. It really would be a mess for me to add that command, though, and honestly you're the first to ever ask for it (even though the plugin has been available for more than a year). :\ Claiming on the surface where you can move around more easily, then climbing underground and breaking or placing a block is a relatively quick workaround, although I admit it's awkward.
@confuser
Sorry guy, I did what I could and couldn't reproduce the issue on my end to investigate it. I just made my best guess at what would fix it. I think you're the only person having this problem - I wish I could tell you how to fix it on your end, but I just don't know the cause. If you come up with anything that you think might be relevant to this investigation (anything "odd" about your server that would make it different from most?), then please post again. :)
@VietNg
Because you're running CB 1.4.6, you need to update to Grief Prevention 7.2, which was made for that version of CraftBukkit.
@ircopdd
Are you actually seeing noticeable lag in game, or are you just alarmed at the statistics there? BlockFromTo is known to run a lot - but if you are actually having a lag problem you're a rare specimen - make sure you have limitsurfacewaterbuckets = true in your config. If that doesn't help, please tell me your RAM, player slots, and list of plugins.
@ManBeastPigDev
Already done. Use /untrust all (two words).
@AuntieBeast
Maybe one day, if Bukkit dies and Forge replaces it (unlikely). I don't have enough free time to build and then maintain two versions of Grief Prevention simultaneously.
@Pixiyo
/acb works perfectly when run by someone with permission. Please check your logs at the time of the purchase to see if there's anything there about a permissions problem, or a confirmation that the blocks were added (not just a message to the player, but a log message from Grief Prevention).
@zSwayz
Yeah, just turn on the SQL. But don't do it, you'll just be created a headache for yourself. I only added that so people who refuse to believe me when I say flat file is better will be able to shoot themselves in the feet.
@zedadiaswick
Thanks for sending along a stack trace, I see valuable information there. I'll get to work on a fix.
@justicets
Use another plugin to ban the use of that egg. Or better yet, just turn off monsters if you have creative mode on for your players. They're invincible anyway so there's no point in having monsters, right?
@ManBeastPigDev
Only because you disabled "limit surface water buckets" in your config. Turn it back on, and you'll be safe.
@ManBeastPigDev
/claimslist to check, /acb to adjust.
@Pixiyo
Trading with villagers is griefing?
@orkun1675
Workin on a fix. Have a plan.
@shirt100
Give me the list of your world names, please. Any weird ones?
@ryvix
Thanks, I'll get it fixed in the next version.
@soopageek
Thanks, let me know if you have more information on that issue you're noticing.
Group permissions are already done. For example, /trust [my.permission.node]
@Chaett
Thanks, I'll check that. It was working before, maybe something has broken over time. :) Bukkit is always breaking stuff (although they always say they're not when the release a build).
@ridddle
Sorry! Hours. I've considered changing it, but if I change it now, everybody will suddenly have their cooldowns divided by 60 OR they'll have two different settings in their config file and become confused (and lose their customizations on that setting). So I decided to leave it as-is rather than cause users to suffer either of those ugly situations.
@fungreenfox
Have a fix, testing now.
-
View User Profile
-
Send Message
Posted Jan 8, 2013@Tulonsae
I am running it on a multiworld server. One PVP and the other creative. Works great!
-
View User Profile
-
Send Message
Posted Jan 8, 2013Im getting a strange error, and restorenature both are set to false:
22:13:54 [SEVERE] Exception in thread "pool-1-thread-67" 22:13:54 [SEVERE] org.apache.commons.lang.UnhandledException: Plugin GriefPrevention v7.2 generated an exception while executing task 457439 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 8, 2013Does this support multi-world servers?
-
View User Profile
-
Send Message
Posted Jan 8, 2013Is there a way to set /trapped cooldown in minutes, not hours? I want to do 10 minutes, and currently the time format is 1 (hour).
-
View User Profile
-
Send Message
Posted Jan 7, 2013I noticed the tree regrowth from floating trees not planting the same tree type. This intended?
-
View User Profile
-
Send Message
Posted Jan 7, 2013@soapageek
For group: I believe that you could do: /containtrust [myemployees]
-
View User Profile
-
Send Message
Posted Jan 7, 2013@ManBeastPigDev
I believe GriefPrevention v7.2 is the latest version isnt it? I am running ver 1.4.6-R0.3... could this be the problem? Its a beta build I believe....
-
View User Profile
-
Send Message
Posted Jan 7, 2013BigScary:
First of all, great plugin. We're in the early stages of implementation on our server, but I anticipate it being a great success.
Possible bug report: As I understand it, subdivisions work as "bottom-up" permissions and over ride the top-level claims permissions (example: a player could have containertrust on the entire claim, but have full trust in a subdivision within that claim). I've experienced some problems with permissions in a top-level claim (in this case, an admin claim) interfering with subdivision trusts, sometimes granting users trusts they have in the top-level claim to subdivisions they don't have that trust. I'm still in the early stages of trying to figure out when/how these cases apply to offer you more information, but I thought I'd give you a heads up in case anyone else has mentioned it.
Feature request: Are there any plans for group level permissions besides the blanket "public" one? In my own experience, I can think of lots of ways this would be useful. Example: I create a group with Joe, Sally, and Jim called "myemployees" and set /containertrust for them on 10 different properties (bot not all of my properties) throughout the world they need access to. Weeks later, I fire Joe and hire Bob. Rather than run around to 10 different properties and remove Joe and add Bob, I could just change the people in the group, by removing Joe and adding Bob.
-
View User Profile
-
Send Message
Posted Jan 7, 2013@shirt100
probably not the latest version
-
View User Profile
-
Send Message
Posted Jan 7, 2013@Pixiyo
I checked and yes i had just one set wrong. They must have changed the spec since i set it up. Thanks, it works now.
-
View User Profile
-
Send Message
Posted Jan 6, 2013Getting a strange error which seems to correspond to people shrinking claims: http://pastebin.com/raw.php?i=XxuN2RxB
-
View User Profile
-
Send Message
Posted Jan 6, 2013I am getting this error on server start... can you tell me why? thx!
22:14:50 [SEVERE] Error occurred while enabling GriefPrevention v7.2 (Is it up t
o date?)
java.lang.IllegalArgumentException Cannot set to an empty path
at org.apache.commons.lang.Validate.notEmpty(Validate.java:363)
at org.bukkit.configuration.MemorySection.set(MemorySection.java:159)
at org.bukkit.configuration.MemorySection.set(MemorySection.java:189)
at me.ryanhamshire.GriefPrevention.GriefPrevention.onEnable(GriefPrevention.java:283)
at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:217)
at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:457)
at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:381)
at org.bukkit.craftbukkit.v1_4_6.CraftServer.loadPlugin(CraftServer.java:282)
at org.bukkit.craftbukkit.v1_4_6.CraftServer.enablePlugins(CraftServer.java:264)
at net.minecraft.server.v1_4_6.MinecraftServer.j(MinecraftServer.java:321)
at net.minecraft.server.v1_4_6.MinecraftServer.e(MinecraftServer.java:300)
at net.minecraft.server.v1_4_6.MinecraftServer.a(MinecraftServer.java:259)
at net.minecraft.server.v1_4_6.DedicatedServer.init(DedicatedServer.java:149)
at net.minecraft.server.v1_4_6.MinecraftServer.run(MinecraftServer.java:399)
at net.minecraft.server.v1_4_6.ThreadServerApplication.run(SourceFile:849)
-
View User Profile
-
Send Message
Posted Jan 6, 2013was looking through my log file and found this message thrown a couple of times. http://pastebin.com/DnV6VJ9G
-
View User Profile
-
Send Message
Posted Jan 6, 2013@Praqoon
I did the same thing. But still the same. However its random, like every 2hours...
-
View User Profile
-
Send Message
Posted Jan 6, 2013@orkun1675
I had something similar. I stopped the server, deleted my currrent GriefPrevention.jar file, uploaded the new GriefPrevention.jar file, and restarted the server. It solved the errors.
-
View User Profile
-
Send Message
Posted Jan 6, 2013This error is spamming my console with latest builds: http://pastebin.com/RuV4zAyK
-
View User Profile
-
Send Message
Posted Jan 6, 2013@ManBeastPigDev
Fixed the BuyCraft thing! Change {user} to {name}