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 Jul 22, 2013hello can anyone tell me how to disable the ingame chat <player>(sign):<text> ? in the console it shows me "GriefPrevention: [Sign Placement]:<text>"
-
View User Profile
-
Send Message
Posted Jul 22, 2013@ttiffom2016
It already does. You can use Vault to hook in Grief Prevention for buying and selling claim blocks, and you can use Real Estate to buy and sell claims
-
View User Profile
-
Send Message
Posted Jul 22, 2013is it possible to get this plugin to work with iConomy?
-
View User Profile
-
Send Message
Posted Jul 22, 2013@BC_Programming
I have 2 questions for either you or tux2;
1) on a server we opened using grief prevention we never looked into modifying the plugin at all until a week or so later, we now realized we would like everyone to start with 10,000 claim blocks to start which is a 100x100 claim which works perfect for any newly joining member they do get the 10k blocks fine. But for anyone who had played before we changed it we can't figure out how to give everyone the 10k blocks so they aren't all in the negatives. Do you know how to give everyone in the current files 10k blocks or is it needed to be reset completely?
2. This one is much easier: I have read everywhere but can't seem to find an answer.. Is there anyone to make this plugin somehow work with world guard flags, for instance every time someone walks into a claim it tells them who's claim it is. Another thing we are trying to let this work with is PvP everywhere in the wilderness except inside claims, and spawn; would be nice if we could have message for members every time they leave a claim and re-enter into the wilderness (PvP)
-
View User Profile
-
Send Message
Posted Jul 22, 2013when My friend issues /deleteallclaims on my server, the console displays this.
JakeXJake issued server command: /deleteallclaims 2013-07-22 16:05:48 [SEVERE] null org.bukkit.command.CommandException: Unhandled exception executing command 'deleteallclaims' in plugin GriefPrevention v7.7 at org.bukkit.command.PluginCommand.execute(PluginCommand.java:46) at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:189) at org.bukkit.craftbukkit.v1_6_R2.CraftServer.dispatchCommand(CraftServer.java:523) at net.minecraft.server.v1_6_R2.PlayerConnection.handleCommand(PlayerConnection.java:964) at net.minecraft.server.v1_6_R2.PlayerConnection.chat(PlayerConnection.java:882) at net.minecraft.server.v1_6_R2.PlayerConnection.a(PlayerConnection.java:839) at net.minecraft.server.v1_6_R2.Packet3Chat.handle(SourceFile:49) at net.minecraft.server.v1_6_R2.NetworkManager.b(NetworkManager.java:296) at net.minecraft.server.v1_6_R2.PlayerConnection.e(PlayerConnection.java:118) at net.minecraft.server.v1_6_R2.ServerConnection.b(SourceFile:37) at net.minecraft.server.v1_6_R2.DedicatedServerConnection.b(SourceFile:30) at net.minecraft.server.v1_6_R2.MinecraftServer.t(MinecraftServer.java:590) at net.minecraft.server.v1_6_R2.DedicatedServer.t(DedicatedServer.java:226) at net.minecraft.server.v1_6_R2.MinecraftServer.s(MinecraftServer.java:486) at net.minecraft.server.v1_6_R2.MinecraftServer.run(MinecraftServer.java:419) at net.minecraft.server.v1_6_R2.ThreadServerApplication.run(SourceFile:582) Caused by: java.lang.ArrayIndexOutOfBoundsException: 0 at me.ryanhamshire.GriefPrevention.GriefPrevention.onCommand(GriefPrevention.java:1535) at org.bukkit.command.PluginCommand.execute(PluginCommand.java:44) ... 15 more
Is this normal? It looks an awful lot like a traceback...
-
View User Profile
-
Send Message
Posted Jul 22, 2013@RustyDagger
Thanks :) I've never been able to test the changes I made to siege so I didn't even know if they would work :)
Regarding your two issues, hopefully they will be fixed in the next dev build. I changed the "tweak" rules for blocks to only be considered when right-clicking a block, which should allow the logic to proceed to the 'block break' which is where the logic for storing blocks to revert and allowing/disallowing break during a siege.
The duping issue should be partially addressed as well. When the Revert option is enabled, attackers breaking blocks shouldn't allow any drops.
Not sure if the door one can be addressed very well, since when you break a door you 'break' one block which get's recorded, but two blocks break. And when the revert occurs only one piece of the door would re-appear, which probably breaks instantly :/
-
View User Profile
-
Send Message
Posted Jul 22, 2013@newfization
Using the dev builds you can there are settings for just about every thing you could imagine even arrows hitting buttons and plates. you can control what happens outside claims and inside claims takes a little while to build up each worlds file but well worth is when you realize the cool stuff you can actually do if you get a bit creative.
@tux2
I have ran into some issues with siege Duping items using build #142 Also some issues with comparators and repeaters being sieges it seems their tamper protection stops them being broken even when they are on the Siege break list.
The duping is a result of the restore system i think in this case it would be best to just not drop the blocks as they are broken instead of letting the player that's attacking steal them then create copies when it restores. also my iron door dropped on the ground when restored however i doubt there's much you can do about that that's only minor lol.
If you need any help testing any fixes just hit me up In a Pm and ill send you my skype or steam info. Spent the good part of an afternoon playing around with siege FYI its not listed on the player commands section :o
-
View User Profile
-
Send Message
Posted Jul 21, 2013Hi. Do you know how to import other's world claims? I want to add new-existing world with claim to my main server. Do i have to just copy Claims folder ?
EDIT. I noticed that claims ids are similiar so my idea is: Change claim ids of imported world, change names of world in all files from Claims to new name (theres alread world called world). And change _nextid to highier than existing. Will it work?
-
View User Profile
-
Send Message
Posted Jul 21, 2013Can you change the amount of blocks that are protected under the claim for only AdminClaims?
-
View User Profile
-
Send Message
Posted Jul 21, 2013Can you lock doors, trapdoors and fence gates with this?
-
View User Profile
-
Send Message
Posted Jul 21, 2013@Kahenraz reported for Build #141 in ticket 255. confirmed fixed for build #142.
Ticket 255.
The details of the stack trace you note is impossible with #142, where any NPE possible on the given line would have occurred a few lines earlier.
-
View User Profile
-
Send Message
Posted Jul 21, 2013Null pointer exception with the latest jenkins build (Build #142):
Exception is triggered when the player tries to right click on a block to select the second point of a claim using the golden shovel.
This is when using GriefPrevention with the latest Bukkit 1.6.2 snapshot.
Rolling back to Build #137 fixes the problem.
-
View User Profile
-
Send Message
Posted Jul 21, 2013@P2Neo
hi i have your plugin installed and even tho i have nosurvivalbuildoutsideclaims to false its not letting me build anything at all and tells me "You can't build here unless you claim some land first". :/
-
View User Profile
-
Send Message
Posted Jul 21, 2013@BC_Programming
Sry, but that doesent work.
I've set it in my city.yml file:
GriefPrevention:
Claims:
Enabled: false
But it does not work :(
InGame it says "You can't build here unless you claim some land first"
Another Question:
In the config.yml file:
WorldConfig:
SingleWorld: '[NONE]'
TemplateFile: plugins/GriefPrevention/WorldConfigs/_template.cfg
What does this two lines do?
Thx for your reply and the great plugin
-
View User Profile
-
Send Message
Posted Jul 21, 2013This plugin is great! The only thing that I would like to be changed is the message that pops up to players when they build in non-claimed areas. Please change this!
-
View User Profile
-
Send Message
Posted Jul 21, 2013@marco1095
Changing The different trust levels to a set of "flags" rather than tiered access levels has it's advantages- and in fact could probably be accomplished by a rather trivial change. The issue however is that there is also overlap; having build trust a player can use hoppers to take items from a chest by connecting them to a dispenser, and open doors and activate circuitry by breaking buttons or placing redstone torches, so the trust levels acting as a "flag" would be rather full of 'security holes', so the real issue would be trying to intelligently block such actions only in some cases, like preventing the placing of certain blocks based on specific trust levels and whatnot, which would make things rather tricky.
That said, while I'm not an expert on what features it provides, I would hazard a guess that whatever functionality you are aiming for is probably accomplished/added in the excellent 'GriefPrevention Flags' plugin.
-
View User Profile
-
Send Message
Posted Jul 21, 2013@P2Neo
You should be able to set GriefPrevention.Claims.Enabled in a World Configuration to false to disable GP Logic in a world.
-
View User Profile
-
Send Message
Posted Jul 21, 2013How can i disable a map from the config? GP should only work with two maps and i want to use worldguard on another map. Since this dev build it wont work like in 7.7 Unfortunately, I find nothing in the documentation. I've tried a lot of settings. I use the GP dev Build #141 and craftbukkit dev build #2815 Thanks
-
View User Profile
-
Send Message
Posted Jul 21, 2013Hello!
It would help a lot if you can change the trust permissions, so users can build, but have not access to containers, kindda /buildtrust only gives permissions to modify construction blocks but not containers. Thanks and sorry for my bad english hope you can understand me.
PD: I speak spanish, and i translated all grief prevention plugin to spanish, so if you want to translate you're plugin(the new version for 1.6) i could help :)
-
View User Profile
-
Send Message
Posted Jul 21, 2013We have an admin claim over our and we have a worldguard region also protecting our spawn. Now we want to make it so that people can't use doors but players still can. Is there a way to fix this?
An admin may have done /trust public but I have already did /untrust all.
Also, is there a way to see info about a protection like in worldguard?