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 Mar 2, 2012The only things preventing me from using this plugin is the fact that you cant allow players to buy/sell Subdivided claims / Claims and that you dont seem to be able to create 3D Subdivided claims to limit the height a player can use(so that I can have houses etc on top of eachother).
If these features were added I would consider this as the best protection plugin yet :) (Its certainly on the top 3 acording to me tho! =] )
Massen
-
View User Profile
-
Send Message
Posted Mar 2, 2012@skullriderltu
no, and i don't think there is any intention to do implement this, especially since the 1.2 stuff is happening
-
View User Profile
-
Send Message
Posted Mar 2, 2012Can you add buy/sell regions?
-
View User Profile
-
Send Message
Posted Mar 1, 2012@Jayyx2
it was a tip just to keep up to date on the dev builds, you will get a message on login saying to update ur bukkit ;)
EDIT: its not a "fix" at all lol
-
View User Profile
-
Send Message
Posted Mar 1, 2012@cvxx7q I just changed it despite not being sure what that will do for me. The error still spams randomly after the change.
-
View User Profile
-
Send Message
Posted Mar 1, 2012@Jayyx2
dont forget to set your server to the 'dev' channel in Bukkit.yml
-
View User Profile
-
Send Message
Posted Mar 1, 2012@bigscary I actually am using 1.2.2-R0.1 build #2006 now (http://dl.bukkit.org/downloads/craftbukkit/view/00814_1.2.2-R0.1/) and the error still spams. It appears to be random, nothing specific aside from someone needs to be connected to the server in order for it to spam. I would say it's nothing to worry about and most likely related to the 1.2 update and dev build of CB. I will patiently wait for the next stable release of CB before making any more complaint. I absolutely LOVE your plugin. My server would be a scary place without it!
Most recently: 22:38:25 [SEVERE] Could not pass event PlayerItemHeldEvent to GriefPrevention org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:303) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:441) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:736) at net.minecraft.server.Packet16BlockItemSwitch.handle(SourceFile:24) at net.minecraft.server.NetworkManager.b(NetworkManager.java:229) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:112) at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78) at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:549) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:447) at net.minecraft.server.ThreadServerApplication.run(SourceFile:490) Caused by: java.lang.NullPointerException at me.ryanhamshire.GriefPrevention.PlayerEventHandler.onItemHeldChange(PlayerEventHandler.java:307) at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:301)
-
View User Profile
-
Send Message
Posted Mar 1, 2012@bigscary
they only problems ive had was some console spam (using 1.2, this is expected)
but it seems to be working, i used resotrenature and the diamond blocks appear and nothing happens (console spammed) but if i DC then reconnect that chunk is regenerated, so its working at least XD
EDIT: and yes i see your plugin for grief is the best in class, not because you brought new ideas, you cut back being fancy, you learned from where other ideas sucked, and more importantly u implemented your ideas with ease of use for both the player and the administrator, its just simple in every way, for everyone, your plugin flat out says (by its design) "why should the players play and the admins baby sit? they are players too!"
and when this whole storm of shit with servers cleans up and the new vanilla is out, my first thought will be to check out GP ;)
-
View User Profile
-
Send Message
Posted Mar 1, 2012Hi everyone, yes I know the client update is out, but Bukkit has not released a recommended 1.2 build yet. When that comes out, I will udpate and release a compatible GP version. If you use the current version with 1.2, you do it at your own risk AND DO NOT POST YOUR PROBLEMS HERE. Thanks.
@EroOu
As I understand it, because /t is an alias, if there's another plugin which has /t as a command, that plugin will win. So you will always have the full command /trust when there's a conflict. So if you're running another plugin which has a conflict with the abbreviation, you'll just have to use the long form to disambiguate.
@Jayyx2
Having trouble reproducing your bug. Are you on 1.1-R4? Are you or one of your players doing something specific at the time this error appears, which always makes it appear?
@cvxx7q
Yes, grief is a very important problem to solve, and nobody seems to be doing anything comparable in both effectiveness and usability right now, so I feel like I need to keep going with this. I hope the transition will be easy.
-
View User Profile
-
Send Message
Posted Mar 1, 2012Oh, I see, you are using /t as an alias. Please do not, as this conflicts with /tell. And /toggle for citizens. (WHY on earth would citizens make /t alias for toggle? Thats rarely used command replacing ALOT used command. Well, kinda same as happened here.)
Generally using 1 letter aliases is a majorly bad idea. 2 letter aliases are on the kinda gray zone too... As we can see from the /pt. gargh...
Its not like those commands will be used so often that they would require such short aliases. Could you make them atleast 3 or 4 letter long? Like add GP for GriefPrevention in front of them or something?
-
View User Profile
-
Send Message
Posted Mar 1, 2012I am using 1.2.2-R0.1 build #2000 and there is an error randomly spamming in console:
15:49:36 [SEVERE] Could not pass event PlayerItemHeldEvent to GriefPrevention org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.ja va:303) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav a:62) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j ava:441) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:736) at net.minecraft.server.Packet16BlockItemSwitch.handle(SourceFile:24) at net.minecraft.server.NetworkManager.b(NetworkManager.java:229) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:112) at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:7 8) at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:549) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:447) at net.minecraft.server.ThreadServerApplication.run(SourceFile:490) Caused by: java.lang.NullPointerException at me.ryanhamshire.GriefPrevention.PlayerEventHandler.onItemHeldChange(P layerEventHandler.java:307) at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.ja va:301)
-
View User Profile
-
Send Message
Posted Mar 1, 2012@bigscary
your one of the good dev's i see (sticking out through platform changes) , alot are pissed and saying they will migrate to spout or one of the other OS Servers.
from the little details i have seen around, it seems the vanilla will be what bukkit is but closed source, i guess that's kind of a good thing wrapped in shit (mojang do it so well :S, no offense to them but seriously)
-
View User Profile
-
Send Message
Posted Feb 29, 2012I will continue to support GP until either Mojang puts something in the Vanilla server to stop griefers, or I stop playing Minecraft entirely. In the event I stop playing Miencraft, I will publish the source.
There are no details about the specific changes coming in that announcement, but I'll do what I have to to ensure GriefPrevention's feature set is available. I didn't do all this work to just quit and throw it all away because a new platform is coming out.
-
View User Profile
-
Send Message
Posted Feb 29, 2012http://forums.bukkit.org/threads/bukkit-the-next-chapter.62489/
will this make or break GP Development, i mean if there new Server API is successful will GP be "rebuilt" or are you hoping for a community bukkit continuation? (Like whats happened with MCEdit)
-
View User Profile
-
Send Message
Posted Feb 29, 2012@bigscary
ok but it is now some what working now players can break blocks in some spots but not in others spots in a claim I think this is weird
go to robertserver.weebly.com to get on I will send you a email asp
-
View User Profile
-
Send Message
Posted Feb 29, 2012@spblat
Did you check his claim to ensure it's exactly 10x10? It's very easy to accidentally create a claim that's one or two blocks wider than you intended. The player data file should have two lines, one depicting the number of blocks the player has accrued on his own, and one which is the adjustment (gifted by admins, or purchased by the player).
He can also check his claim blocks by just equipping his shovel. And you can investigate this yourself by using the commands on your personal account.
-
View User Profile
-
Send Message
Posted Feb 29, 2012I'm experiencing a problem with claim blocks accounting. Players are told in the chat interface that they have a negative number of available blocks. But their file in PlayerData seems to show something else, and while I've tried to make sense of the discrepancy I'm not sure where to begin. But check this out and see if you agree something is goofed up somewhere.
EDIT: haven't checked into 2.0 yet. Bravo for all these great releases!
-
View User Profile
-
Send Message
Posted Feb 29, 20122.0 Updates!
This is not a major version update, just an incremental update from 1.9, which rolled us over to 2.0.
@xBladeM6x
Sorry to have confused you. The refilling chest thing I mentioned in the video was from another plugin. It was one example of a gadget you might use administrative claims to protect, but is not implemented in grief prevention itself.
@ubuntu10
Sorry, I couldn't get that bug to reproduce on 1.9. If you send me your server info via private message, I can meet you on your server and maybe we can figure it out there.
@Matoyoshi
Yes, you need to make each room a subdivision. ContainerTrust will grant access to everything except building, while accesstrust grants only bed and buttons/levers.
You can't set different permissions for different Y levels, so you can't do multiple floors with different permissions.
@briankdk
If you don't want an automatic claim created when a player places his first chest, set the automatic claim radius to -1. This is mentioned on the administrative details page.
If you just want to enable stealing, then set allow theft to true.
@Gamemasher
No, there's no way to list the people who have access to a claim. You can imagine where it would just scroll out of your chat box, anyway. If you think someone has been given access that shouldn't have it (for example, by a friend who you gave /permissiontrust to), then use "/untrust all" to clear permissions and start over.
As an administrator with access to the server, you can open the claim's data file to read the list of players who have various levels of permission there. Claims are listed by their location. You can get a list of claim locations for a player by opening his player data file.
@Confuzzled77
Only one name at a time.
@MrFancypantsy
That's an old bug, it's fixed now. Update to the latest version.
-
View User Profile
-
Send Message
Posted Feb 29, 2012Creepers always explode and destroys logs even if you have another (WorldGuard) plugin that is supposed to prevent that.
-
View User Profile
-
Send Message
Posted Feb 28, 2012I also would like to know if there is a way to see who has permission for each claim, if there is a way. Also, is there a way to trust more than 1 person in a command? so "/trust confuzzled77 bigscary"?
Im running it on a test server so I cant try more than 1 name. :P