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 7, 2012@bigscary
mcmmo activates abilities for tools using right-click, so this can be confusing for players using a golden shovel to dig (although why the hell would you? its crappier than wood and is way more effort to find)
i'm not sure if a work around/configurable claim item is required
i wouldn't need it myself but maybe if i ran into some simpleton's.. XD
POST-MASH: hey bigscray GP is pissed off again XD
git-Bukkit-1.1-R6-35-g2d7e8a7-b2037jnks (MC: 1.2.3) (Implementing API version 1.2.3-R0.2-SNAPSHOT)
10:51:26 [SEVERE] Could not pass event PlayerInteractEvent 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 org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:168)
at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:138)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:886)
at net.minecraft.server.Packet18ArmAnimation.handle(SourceFile:38)
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:554)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:452)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:490)
Caused by: java.lang.IllegalStateException: Start block missed in BlockIterator
at org.bukkit.util.BlockIterator.<init>(BlockIterator.java:169)
at org.bukkit.util.BlockIterator.<init>(BlockIterator.java:256)
at org.bukkit.util.BlockIterator.<init>(BlockIterator.java:289)
at org.bukkit.craftbukkit.entity.CraftLivingEntity.getLineOfSight(CraftLivingEntity.java:92)
at org.bukkit.craftbukkit.entity.CraftLivingEntity.getTargetBlock(CraftLivingEntity.java:118)
at me.ryanhamshire.GriefPrevention.PlayerEventHandler.onPlayerInteract(PlayerEventHandler.java:406)
at sun.reflect.GeneratedMethodAccessor4.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)
... 12 more
-
View User Profile
-
Send Message
Posted Mar 7, 2012@bigscary
Thanks, that was my problem silly me I was changing tools.
-
View User Profile
-
Send Message
Posted Mar 7, 2012@coletam
No SQL. See FAQ.
@farmatyr
Make sure you type /adminclaims before you try to create the claim. If you put your shovel away, then you have to /adminclaims again.
@Sacredox
Cvxx's solution won't work unless you restrict either Towny or GriefPrevention to only admins. The problem is that all players have access to both, and most players don't have the depth of knowledge to understand how the two interact.
I will not try to integrate the two, sorry. Consider either removing Towny or disabling GriefPrevention's claims (you'll still have the other anti-grief features, like spam, treetopping, and fire protection), or restricting GP to only administrators for administrative claims. You can't reasonably run both if they're both available to all your players.
A standard isn't needed because it's an unreasonable expectation for two player-claim plugins to work side by side. Why would you even want to? If one gets the job done, you don't need the other. Considering only non-admin scenarios, if you can claim with GP, you don't need to make a town. If you can make a town to claim your area, then you don't need to claim it with GP. When it comes to admin scenarios, it's reasonable to expect an administrator to be smart enough and invested enough to figure out how to make them work together for his special cases (like using Residence to prevent monsters from spawning in your GriefPrevention administrative claim).
@treesquid
Thanks for reporting that, I hadn't considered it. I won't try to fix it, I think it's not a big deal to "steal" some sand blocks, and it's very situational. Even in Vanilla, building your house on sand is a dumb idea anyway, since it likes to crumble.
Use /adminclaims to make an administrative area. Players can do anything there except build and break. Admins will be able to build/break. See administrative details page.
-
View User Profile
-
Send Message
Posted Mar 7, 2012Small Bug: I noticed that when digging underneath a players protected area, if they dig any block that's unprotected underneath a sand or gravel block, the gravel/sand block will fall down to the unprotected area and be diggable.
That said, I really do love the ease of your system and am slowly setting up it up on my server for my players to use.
Forgive me if this was answered elsewhere, but is there a Admin or non-player owned plot system? I'd like to plot some main areas as "admin" and set it globally that anyone i trust as the admin can have access to these plots, while still retaining my player characters own plots and permissions seperately. It would be nice to cutdown the time spent in each new area I create, entrusting all the players to that area when I could just step outside the plot and do something like /admintrust playerA and they have access to all admin locales.
Keep up the good work!
-
View User Profile
-
Send Message
Posted Mar 7, 2012@cvxx7q
Thank you for the reply!
I'm not sure I understand your solution to the problem I am having. Are you saying to make my entire world an admin claim? Or just towns? Either way I don't see this as being automatic or simple for people to use if they have to constantly adjust both Towny and Grief Prevention to match. It also doesn't solve the problem of towns being able to encroach on existing claims.
So it sounds like there is currently no way to automatically prevent them from intersecting with each other and that it would be necessary to code a way and I'm guessing that would take a lot of time and effort. Here are some thoughts I have about this.
If the land belongs to a town, don't allow to put a claim there.
I thought Towny used flat files to store the location of towns just like Grief Prevention does so I thought maybe it would be a fairly simple thing to check the file it stores towns in and see if there is a town there before allowing a claim on those blocks. It doesn't sound hard anyway.
If the land belongs to a claim don't allow a town to be there.
Maybe towns taking over claims could be stopped by having Grief Prevention also place its claims into the Towny towns file for a non-existing town called Land Claims or something so people can't build towns there.
A standard.
Alternatively, why isn't/couldn't there be some sort of standard way for plugins to share this sort of data so things like this don't happen? With so many different land ownership plugins there should be a standard method of seeing which other plugins own a block or area before allowing another one to own it. I know in many cases people would only have one running but maybe that's because there is no standard way of checking to see if the land conflicts. I think people might use multiple types of plugins like this because some users don't want to belong to a town and Grief Prevention is perfect for them. Someone should develop such a thing which is extremely simple so that plugins can tell which blocks and areas are occupied by another plugin before they touch it.
I know it would be some work if it doesn't exist already but it doesn't really sound all that complex to me. But sometimes things are easier said than done.
So what/how much would it take to make something work?
-
View User Profile
-
Send Message
Posted Mar 7, 2012Admin claims doesn't work for me! It says I don't have enough claim blocks. Running the Buckit 1.2.3 build.
-
View User Profile
-
Send Message
Posted Mar 7, 2012@Sacredox
make a big admin claim then they cant claim, simple
if u need places for ppl to build with in that town i think thats where u subdivide, also version of server and plugin if u still cant get it working
-
View User Profile
-
Send Message
Posted Mar 7, 2012Is there some automatic way to prevent people from claiming land within a Towny plot/town/nation land and visa versa?
It's nice to have border greetings and many other features of Towny but it seems to allow people to sometimes claim land which isn't actually theirs and I can't figure any way other than to just delete the claim within the Town since it isn't really necessary in my case. Unless of course the town was built over the claim after the claim was put in place.
Some players just prefer not to build in a town and would get griefed if it was not for this wonderful plugin.
Thanks!
-
View User Profile
-
Send Message
Posted Mar 6, 2012@Tux2
a few more suitable names come to mind when your labeling them... *censored* *censored* *censored* :P
-
View User Profile
-
Send Message
Posted Mar 6, 2012@bigscary
lol, those guys are so pathetic... I had a few kiddies on my server about 2 weeks ago... Even if team AVO did come through my server I doubt they could do any lasting damage...
-
View User Profile
-
Send Message
Posted Mar 6, 2012@bigscary
yeah, the threat of "i'll DDoS you" or some bullshit, such kiddies...
-
View User Profile
-
Send Message
Posted Mar 6, 2012@coletam
its not going to be added, simple as that, the author has issued 2 Largely explained posts on why, there is no need for SQL since the "flat files" are written very little and the claim stuff is handled in memory for the majority of the time, so other than better persistence, SQL will not be much faster if at all, not to mention bloat.. :S
EDIT: also if you took a look at the data, its not 1 flat file its many, so u will not have an I/O Queue for the same file in any case
-
View User Profile
-
Send Message
Posted Mar 6, 2012Can you please add MySQL, some people may not know how to use MySQL but some do. At least add an option for people who wants to use MySQL (and who knows how to use it). If people don't know how to use it, they can always use a Flatfile...
It would be so much helpful if there was MySQL to it. Thanks!
-
View User Profile
-
Send Message
Posted Mar 5, 2012@lbb601
There's no offline claim selling yet. You can lease a subdivision or claim to another player by using your economy plugin's slash commands to transfer money, then using GriefPrevention's /trust commands to grant that player permission in the claim. You can't actually transfer ownership of a claim, so the player would be more like a "tenant" than a "new owner".
You can subdivide your claim to make permissions different on one chest versus the other.
Hey guys check out how well the spam banner works. I think this guy must have been botting with multiple accounts. Not only is he wrong about our server being "done" because he didn't even manage to lag it, he got all those accounts banned in a space of less than 5 seconds. He later came back on a new account and threatened to "report" us to team avolition (as if we were bad guys, and they were good guys), and caught another ban for being annoying. :)
-
View User Profile
-
Send Message
Posted Mar 5, 2012Is there a way to set predefined claims that users can buy via maybe a sign or something? I'd really like to integrate this plugin with my plotted server.
-
View User Profile
-
Send Message
Posted Mar 5, 2012Hi there, I am VERY interested in this plugin but I have a slight problem with it. The problem is that we already have lwc (and world guard but we can get rid of this one) and with lwc, it lets players protect their chests while we can keep them on their world guard protection. (Trust issues)
Edit: So lets say they want them on their wood chest but not their diamond chest, theres no way to decide what chest protections they are on :/
-
View User Profile
-
Send Message
Posted Mar 5, 2012@mynameismonkey
The week removal isn't editable, but it only impacts players who haven't expanded their claims. So most players won't be impacted, only those who played for only a few hours before disappearing for a full week.
-
View User Profile
-
Send Message
Posted Mar 5, 20122.2 is for 1.2.3? ty ty
-
View User Profile
-
Send Message
Posted Mar 5, 2012Blargle, I just now figured out the comments are upside down and have been reading your copious replies, so sorry to ask something already answered. I am old and easily confused.
In other news, yay! This looks like an awesome plugin, I run a server for kids and I think this will do wonders for them. Seeing as how you are all attentive and answery :) would you recommend I dive in now with 1.2.3 as some are reporting it works fine, or should I wait? My server is still at 1.1 while I wait on RB, but if this works good enough I'd like to get started. Seems like no, but thought I'd ask.
One final question, is the one week removal editable? Kids get grounded for longer...
-
View User Profile
-
Send Message
Posted Mar 5, 2012@mynameismonkey
Yes.