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 Aug 9, 2013hello.. i am runing my own server and i am having an issue.. when i do /buyclaim 1 it says that buying and selling is disabled.. there a reason for that? i have checked the config file for anything of the sort and have found nothing that helps
-
View User Profile
-
Send Message
Posted Aug 9, 2013@RustyDagger
Can confirm this. http://pastebin.com/Pa19XSCC
Went back to #150.
-
View User Profile
-
Send Message
Posted Aug 9, 2013There is a problem with horses. If a person rides their horse on protected land and get off their own horse they can't get back on it.
Anything to reemdy this?
We have our town protected and people ride into town to buy stuff, they get off their horse then they can't get back on it.
-
View User Profile
-
Send Message
Posted Aug 9, 2013@RustyDagger
Same here, and because of that i've downgraded to Build 150.
Another problem that is bugging me even more is the massive 'onBlockFromTo' spam which floods the server-console:
- 13:57:04 [INFO] onBlockFromTo:Location{world=CraftWorld{name=world},x=10649.0,y=8.0,z=-4678.0,pitch=0.0,yaw=0.0} Type:STATIONARY_LAVA
It doesn't seem to occur in all world areas but someone was flying to a random location and then i noticed the console-flooding.
All Builds starting from 151 (up-to and including) 154 suffer from it / seem to be affected.
-
View User Profile
-
Send Message
Posted Aug 8, 2013Using Build 154 This started happening As soon as the server turned on. its related to the sea level and I know you have been making changes to that of late.
http://pastebin.com/C4rUJSjR
I also won't mention the fact that just about every message into chat is broken. one was even missing the "resizeclaimtosmall" Happens when you try to make a claim smaller than the min size and a lot of the messages have the {0} showing instead of the variables.
I updated today from 147 because i was unable to delete claims kept telling me to stand in one and according to the stick there was a claim there but all the protection was not working Making me think the stick and message in chat was in the wrong.
Plugin is currently Unusable to me :(
-
View User Profile
-
Send Message
Posted Aug 8, 2013@Alshain01
"Couldn't you do something similar, but have it set an additional accrual amount instead?
/adjustbonusaccrualrate [myservergroups.vip] 20"
Were you talking to me or the dev at that point..? Because I don't think that command exists
@Alshain01
Hmm, I may attempt a custom solution, it's probably gonna be the best way to achieve what I want. Thanks anyway! :)
-
View User Profile
-
Send Message
Posted Aug 8, 2013<<reply 1697706="">>
Okay, I think the confusion comes from something like this:
and this statement in the documentation:
"Valid values for ClaimControl are RequireNone, which means that no claim check is performed at all and it should be allowed. This will force this action to be available to all players."
Makes it seem like the RequireNone setting will force the action to be allowed even if it is denied in the SeaLevel settings. Anyway, thanks for clearing that up for me.
-
View User Profile
-
Send Message
Posted Aug 8, 2013@jbanto
That is correct.
The rules basically work like this.
Obviously, all actions will occur in a Location. So the first determination is whether it's in a claim or not. That selects whether to use the 'Claims' or 'Wilderness' Portion of that rule.
Then it get's the sea level of the world; This can be overridden in the world configuration (and in the latest dev build, even (optionally) overridden on a per-placementrule basis)
If the area the location is is determined to be denied, it goes no further- it doesn't actually check permissions after that.
If it determines it is Allowed however, and a ClaimControl setting is present, it will then check those permissions.
What this means is that:
This would Prevent placing trash blocks above sea level in the wilderness, but you can place trash blocks underground in the wilderness. Within claims, nobody would be able to place any trash blocks below sea level, and in order to place them above sea level, you would need Build Permissions.
Bear in mind that not all options really make sense for all the rules. For trash blocks this particular setup would be a bit silly since it will prevent even the owner of a claim from placing blocks in that claim. However you might also want to prevent placement of TNT by anybody even within their own claim, or prevent players from trading with villagers in claims (even their own) below sea level to encourage people to keep their villagers closer to the surface (for whatever reason, possibly some villager kidnapping thing, I dunno).
-
View User Profile
-
Send Message
Posted Aug 8, 2013@Alshain01
So in the first one, they still can't place trash blocks in a claim even if they have build permission?
-
View User Profile
-
Send Message
Posted Aug 8, 2013@jbanto
The first one prevents users from placing trash blocks in claims that are above or below sea level. The second one allows placing them anywhere (as long as you have build permission).
-
View User Profile
-
Send Message
Posted Aug 8, 2013The new config settings are confusing...
What's the difference between
and
-
View User Profile
-
Send Message
Posted Aug 7, 2013I think it's the approach that is the problem. Instead of having a permission node that sets the accrual rate. There is already a way to have a permission node receive a flat number of blocks...
/adustbonusclaimblocks [myservergroups.builders] 5000
Couldn't you do something similar, but have it set an additional accrual amount instead?
/adjustbonusaccrualrate [myservergroups.vip] 20
-
View User Profile
-
Send Message
Posted Aug 7, 2013@BC_Programming
There possibly may be some way, however I'll take that as a no then... I'm guessing there's no other way to achieve what I described...? Thanks
-
View User Profile
-
Send Message
Posted Aug 7, 2013Could you make building in claims during PvP Configurable?
-
View User Profile
-
Send Message
Posted Aug 7, 2013@revels21 I'm not familiar with the inner workings of permissions plugins but I don't think you can change configuration settings based on permissions like that.
-
View User Profile
-
Send Message
Posted Aug 7, 2013Hey, On our server we want to make it so that donators accrue a greater amount of blocks per hour, say normal players get 50/hour, $10 donators get 80/hour, $20 get 100/hour etc. however using the permission node "- Claims.BlocksAccruedPerHour: 100", in PermissionEx, to set the blocks accrued per hour for the $20 donator rank, for example, seems to have no effect, and this applies for all the ranks. Everyone just seems to receive the default amount regardless of what permission group/node they have. This may not actually be the correct method, however I was led to believe it was by one of the devs a long while back. Please could you correct me in what I am doing or let me know if this is not actually possible. Thanks
-
View User Profile
-
Send Message
Posted Aug 7, 2013What is the permission to always ignoreclaims so you don't have to type /ignoreclaims? Also since one of the dev builds, I'm unable to build in an admin claim i created without typing /ignoreclaims.
-
View User Profile
-
Send Message
Posted Aug 7, 2013is there anyway to disable this in a world..i don't need it for my skyblock world since worldguard does it all.. but in my regular world I want to use.. aslo how can I enable it so ppl can light a fireplace with flint and steel.. if I disable the plugin they can but when enabled they cant so I no its this.. thanks
-
View User Profile
-
Send Message
Posted Aug 6, 2013@Smac3223
Alshain pretty much covered this ETA business. "When it's done and we are reasonably satisfied with the quality" is really the best answer to give.
Originally I was hoping to "follow" bukkit's beta and recommended releases, but that doesn't look like it's going to be possible. I may have a new Job as well and will use that spare time to refine the skills necessary for it (mainframe work and C#, specifically).
Another consideration is that fundamentally there isn't going to be anything particularly different between some given development build and whatever get's uploaded as a Beta or Release.
Professionally, estimates are still difficult to give, and that's when you know you will be able to put some specific set of hours into the project. (And you're getting paid partly to make those estimates too) With things like this it's basically a few minutes here, and hour or two there, etc. One day I could spend 8 hours on GriefPrevention tasks, and then I could not touch it for a week, etc. Making any estimate impossible to give but if such an estimate is given, people will hold you to it, so it's best not to give one at all.
-
View User Profile
-
Send Message
Posted Aug 6, 2013just a info... with latest beta1.6.2-R0.1 (Build #02838) and dev build Build #150 (Aug 3, 2013 8:36:02 AM) server act strange. Every 4-10 seconds it freezes. Of course that manifests as huge lag on client sides.
No console output, no nothing. It just freeze. Im using flat file, and i suspect to RW state to it.
cheers :)