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 25, 2013Is there a way to toggle the blocks that show up when you place a chest down? Because I don't want them showing up unless someone needs to make the area bigger.
-
View User Profile
-
Send Message
Posted Jul 25, 2013Hi. I checked several sources - not found a solution.
GriefPrevention does not safe Logistic-Pipes from access to it by untrusted users. I made all ID-s to the config (accesstrust and container-trust).
So how to manage that only permitted users can manipulate those pipes with wrench ...
Thanks for help :)
Pyramidalist
-
View User Profile
-
Send Message
Posted Jul 25, 2013@BC_Programming
I tested build 145 Tonight relating to the siege stuff.
I have a feeling your not going to like this.
1. The PvE death = end of siege and restore has been fixed it works now. 2. All Blocks are dropping items again even with restore enabled :( 3, some message saying you can't teleport out of a besiged area came up when i was hit by a spider my spiders are modded with ubermobs so likely it was trying to tp for some effect.. Not a big deal but it was a little spammy until i punched the spider away only to be ninja by a creeper so FUN :D need to secure my test site it seems.
-
View User Profile
-
Send Message
Posted Jul 25, 2013@Alshain01
i dont see where i can change the blocks players start with, nor an economy section for buying/selling claim blocks, also whenever i restart the server all claims get unclaimed.
Sorry i did not see the GriefPrevention folder all i saw was the old folder, i had to disconnect from ftp as refreshing it wasnt working, after reconnecting i finally saw the folder.
-
View User Profile
-
Send Message
Posted Jul 24, 2013@BC_Programming
Thank you very much! I couldn't find the gpreload in the documentation, maybe I just missed it. I liked that explanation for the spam control. I will have to consider something like that for my server. Thank you for your time!
-
View User Profile
-
Send Message
Posted Jul 24, 2013@Azurago
spam configuration is done per world. When I originally reworked the configuration to being world-specific, it was 'global'.
However, then I got to thinking that many servers have a "teired" approach; where players "earn" their way into successive worlds. This is a common technique to prevent grief, since when a player spends more time on a server they are more likely to be a productive and helpful player. In that vein I made the spam configuration world specific to help facilitate the ability to have for example stricter spam controls in beginner worlds and more lax controls and restrictions in worlds that contain more trusted players.
the /gpreload command can be used to reinitialize GriefPrevention without restarting the server.
-
View User Profile
-
Send Message
Posted Jul 24, 2013Does Spam filtering need to be on the world configs? For me this seems like you would enable/disable this server wide more than per world. Also, will there be a reload feature added? Unless I missed it I would like to suggest it so I don't have to reload/restart the whole server.
Nothing critical, just my two cents. I love this plugin, keep up the good work!
-
View User Profile
-
Send Message
Posted Jul 24, 2013@delsolsi213
Dev builds use GriefPrevention folder, not GriefPreventionData.
@deleted_9935739
I think you will have to delete your messages.yml file. That should be fixed now.
@RustyDagger
there was a new dev build yesterday that attempted to rework the Siege guff.
-
View User Profile
-
Send Message
Posted Jul 24, 2013hello can anyone tell me how to disable the ingame chat <player>(sign):<text> ? in the console it shows me "GriefPrevention: [Sign Placement]:<text>" I get that only in the skyblock world
-
View User Profile
-
Send Message
Posted Jul 24, 2013@delsolsi213
Moved not removed. It's per-world now, so check the files for that world.
-
View User Profile
-
Send Message
Posted Jul 24, 2013hi i noticed you removed in the configs where we could edit how many blocks players start with? or is it bugged for me,im using build 145 and all i see in the griefpreventiondata folder is config.yml nothing else
-
View User Profile
-
Send Message
Posted Jul 24, 2013Some more info on the "Missing message! ID: ResizeTooFewBlocks. Please contact a server admin" error. It only happens when you try to make an 8x8 claim (default size limit).
-
View User Profile
-
Send Message
Posted Jul 24, 2013@Ablinn1
Id have to say its a bad MCPC+ build or even try downgrading Gp if your server is 1.4.7
I was ninja by a whole hour.. Dam I need to read more recent comments before back scrolling and typing.
@BC
Any progress on those issues? Not a big rush its just holding me back a little. I also need to solve that whole trusted players in claims issue they can hide in there as you know for now I think i will just remove permissions for the trust commands until some system to allow me to config that issue is added. keep up the good work man if i had spare change I would toss it your way :(
-
View User Profile
-
Send Message
Posted Jul 24, 2013Ablinn1: you need to be running at least Minecraft 1.5. Looks like it's erroring out where GP tries to access some 1.5 elements.
-
View User Profile
-
Send Message
Posted Jul 24, 2013@Max_Coffeebreath
You mean unextendable (No API events), tricky to configure and limited in many ways in that fashion, because all configuration was done in a single file and only a few simple options provided any sort of world-specific settings. Also, MCPC+ and modded servers were completely unsupported and it was claimed that "MystCraft support could never be added without rewriting the plugin" which was evidently not the case since I was able to add exactly that capability.
He did some bloody fine work creating the plugin and laying down a groundwork of features and particularly pushing the simple to use functionality that was as "commandless" as possible through the use of the now ubiquitous golden shovel. However I think it's fair to say that him and I would probably not see eye to eye on many things. Arguably I think many of the items that were part of the To Don't list was simply ideas he didn't have the development time to entertain.
Even so, additions I make either address specific requests for a feature or address 'implicit' requests for features, as well as adding generally useful features. World-specific configurations were added for the simple reason that people have been asking for the ability to configure GP on a world-specific basis for a very long time. The response was often that the plugin would need a complete rewrite. It certainly needed a non-trivial refactor, but it was doable. the way Claims were indexed was changed by Tux2 from a naive sequential lookup through every single loaded claim to a indexed HashMap lookup that indexed Claims by the chunk they were in. Various lookup keys were changed from Bukkit API interface types to Strings in order to allow those Interface references to be garbage collected as well as prevent issues when there were two separate instances of a interface that actually represented the same thing (eg. "World" instances could be distinct but represent the same world). I changed the loading algorithm so that claims would be loaded into the central claim map as a result of bukkit world load and unload events, which improved capability and compatibility with plugins that load and unload worlds, including MystCraft and other forge mods on MCPC+ servers. This was a requested feature by virtue of the number of bug reports it got.
support for searching Forge configs was added because of the number of issues people had with GP on Forge servers; GP, as far as they noted, was the best they could find for Forge servers. So I improved it. I don't even use GP for Forge. I don't even play modded Minecraft. I didn't add it because I really "liked" the idea- I added it because it empowered administrators and made administrating their servers simpler.
Sure, I/we could have "kept it simple"; but that would mean a sequential search through every claims (which is indisputably simpler than the Claimmap that it uses now); it would mean loading all claims all at once when the server loads and then crashing if a world unloads or failing to save and load claims properly for worlds other than the Overworld, because that would be simpler.
However, What is simpler and easier to design and implement is not what makes it simpler to administrate, configure, and run a server.
And yet, the plugin already had sieges anyway. I'm just making them more configurable- in addition to trying to address the fact that sieges otherwise completely circumvent Grief Prevention by virtue of allowing the breaking of blocks in other people's claims. The revert capability is/was designed to address this by allowing only temporary "griefing" in that way. And I'm making changes to address the needs of somebody that uses that feature. That's how it works :D refactoring the logic to a separate plugin might make a few academics swoon about the purity of the project, but it doesn't make the task of administering and preventing grief on a server any easier.
IMO the "I'm not adding that because it's not grief related" could have simply been excuse to not add features, and allow for more dismissive handling of tickets requesting such features. At the very least that reasoning went straight out the window once he added Sieges himself anyway. (or perhaps that was another maintainer; it was certainly added before Tux2 was made the main author and it was certainly added before I had any involvement).
Some have already forked GriefPrevention to their own repositories and removed the siege logic. I don't think they run faster as a result.
When it is disabled, however, it doesn't affect performance. Tux2's revision to how claims are accessed and indexed improved performance about a bajillion times anyway. Pretty much the only difference is in terms of the size of the plugin .jar.
It would be possible of course to make it a separate plugin but as I documented on the indev doc page such an effort would be non-trivial and there wouldn't be any gain except for some specious concept of academic purity- but that isn't the goal.
-
View User Profile
-
Send Message
Posted Jul 24, 201323:56:30 [SEVERE] Could not pass event PlayerInteractEvent to GriefPrevention v7.7 org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:363) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462) at org.bukkit.craftbukkit.v1_4_R1.event.CraftEventFactory.call PlayerInteractEvent(CraftEventFactory.java:162) at ir.a(ItemInWorldManager.java:539) at iv.a(NetServerHandler.java:906) at fk.a(Packet15Place.java:79) at cg.b(TcpConnection.java:467) at iv.d(NetServerHandler.java:220) at iw.b(NetworkListenThread.java:57) at ht.b(DedicatedServerListenThread.java:34) at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:870) at ho.r(DedicatedServer.java:309) at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:746) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:633) at fy.run(ThreadMinecraftServer.java:16) Caused by: java.lang.NoSuchFieldError: HOPPER_MINECART at me.ryanhamshire.GriefPrevention.PlayerEventHandler.on PlayerInteract(PlayerEventHandler.java:1189) at sun.reflect.GeneratedMethodAccessor59.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:361) ... 16 more
Finally found a console error; if anyone can help this is what happens when we right click with either the golden shovel OR the stick.
-
View User Profile
-
Send Message
Posted Jul 23, 2013Rusty, I dont see a max claims at all in the confg, but I have just stated its not only claims.. its everything that involves a right click period.. we are using MCPC+ and used the bukkit name as well.. idk what else to try
-
View User Profile
-
Send Message
Posted Jul 23, 2013Regarding build #143, does it have it's own permission that doesn't need the admin permission?
-
View User Profile
-
Send Message
Posted Jul 23, 2013@Ablinn1
I tried to help you before but you have not answered my question. Also make sure you have no used the ID for the tool but instead used the Bukkit Name. one more thing are you running a buykkit jar or bukkitforge or Mcpc+ I had issues before with clicking with bukkitforge We need more info to help you we are not mind readers.
@Max_Coffeebreath I honestly think you Are WRONG very VERY WRONG. doing every thing siege dose from anohter plugin would require More Listeners listening for movement event. As you should well know That is one of the most CPU intensive things you can do in a plugin. Not to mention the amount of code that would be same / shared prioritors between the plugins listeners would come into play because the siege plugin would have to stop GP canceling the block break event in Claims it just makes it all that much more complex and tricky to code and maintain. I bet you have never even used siege.
-
View User Profile
-
Send Message
Posted Jul 23, 2013Okay I really don't understand what is going on...
We have the plugin installed and placing chests works fine we get protections based on the radius we have set up, everyone gains the correct blocks an hour EVERYTHING works perfectly except ONE thing...
The one thing that doesn't work is editing claims, resizing them, adminclaims, naturerestore anything where we need to right click with the shovel it does NOT work... we have tried changing the item to multiple things it gives no error messages nothing at all.. Just does absolutely nothing.. If anyone can help on this problem would be greatly appreciated.