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 Feb 25, 2012@bigscary
Im running your (great) plugin on my server - do i also have this "trapped" thingy ?
-
View User Profile
-
Send Message
Posted Feb 25, 2012@bigscary
Sorry but i dont know... i just saw it in the log :-(
-
View User Profile
-
Send Message
Posted Feb 25, 2012Hey guys, I'm running the new /trapped command on my server. Come check it out and see if you have any feedback about how it works.
50.31.24.211:25566
Also note that if a player mentions "trapped" or "stuck" in chat, he will get a private message reminding him about this command. This command is designed to get people out of "traps" inside of other players' claims which are designed to prevent players from leaving once they come in.
-
View User Profile
-
Send Message
Posted Feb 25, 2012@briankdk
Thanks Brian, but there's not enough information there for me to understand what's happening. Can you tell me what you (or another player) is doing to make this call stack appear in your log?
-
View User Profile
-
Send Message
Posted Feb 25, 2012after 1.8.2 im getting this error:
-
View User Profile
-
Send Message
Posted Feb 25, 2012@Dreeass
Rtzon is correct, you can set login cooldown to zero. However, you should know that doing that will allow players with hacked clients to spam your server by rapidly logging out and back in. So if there's no moderator online to ban that player, other players won't be able to use the chat box.
@Tux2
Thanks Tux, I'll try that in the next version.
@ubuntu10
Ubuntu did you create an administrative claim? That sounds like the correct behavior for an admin claim. Be sure you're using /trust with a private claim, and then the player you trusted should be able to make changes.
-
View User Profile
-
Send Message
Posted Feb 25, 2012@Dreeass
Change to Spam.Enabled: false or change the login cooldown to 0.
-
View User Profile
-
Send Message
Posted Feb 25, 2012How can I change it so there's no 5 minute wait after logging out to log back in?
-
View User Profile
-
Send Message
Posted Feb 25, 2012My subdivision issue seems fixed in 1.8.2. Thanks for this tremendous plugin.
-
View User Profile
-
Send Message
Posted Feb 25, 2012Wow, the comments thread on this plugin moves quite fast. A possible, untested solution for the fire problem:
Catch the BlockDamageEvent and cancel that as well if the material is netherrack and the player doesn't have permission for that area.
-
View User Profile
-
Send Message
Posted Feb 24, 2012hey Bigscary I found a bug win I do /trust in a subclaim the player can get in chest and buttons but can't place or brake blocks if you like I can do a video of the bug so you can see.
-
View User Profile
-
Send Message
Posted Feb 24, 2012@bigscary
Ah thank you bigscary. I see that for people the chest will not make a claim on the worlds without permission. I must have accidently given permission or something. It is working fine. Soryy for the inconvenience.
-
View User Profile
-
Send Message
Posted Feb 24, 2012@bigscary:
You are right! Kudos to you. Just completed testing with groupManager, and bPermissions in same setup, had no issues with the permission. Also forgot to mention below that I had vault installed as well.
So the problem is with PermissionsBukkit+SuperPerms Bridge.
Thanks very much for your quick reply. Very good job with this plugin.
Peace.
cdrgnfly
-
View User Profile
-
Send Message
Posted Feb 24, 2012@cdrgnfly
I checked into this. My code is straight forward and looks correct to me. Please double-check your permissions config file (I'm not an expert in that plugin), and also try a different permissions plugin to see if you can determine the root problem. Here's my snippet, sorry for the bad formatting:
-
View User Profile
-
Send Message
Posted Feb 24, 20121.8.2 bug fixes:
@cvxx7q
Like the others mentioned, duplicating blocks isn't cool. Some blocks are extremely valuable and shouldn't be duplicated, even when a player can't control that duplication (because endermen are unpredictable).
@majoraw
@saintcrime
Yikes. Okay, I get it now. But that would be really hard to shoehorn-in at this point. I'll keep it in the back of my mind for a later time. I've always said admins shouldn't try to mix pvp, survival, and creative on one server. There's too much effort involved in keeping them separate - chat, items, experience for enchants, respawns, the list goes on. For creative, I recommend a much higher initial block count, a faster accrual rate, and a very carefully chosen maximum blocks. But you can imagine where that would be bad for survival, where players might not be able to build fast enough to keep up with their claim blocks, leading to lots of claimed area not being used.
Sorry! :)
Hey saintcrime, are you sure players can still create chest claims in the world where you've not enabled claims? That should not be the case, and if it is, that's a bug. If you disable claims for a world, that should block ALL non-administrative claims. Please try to create a chest claim in one of the disabled worlds and if you can succeed, tell me right away. Otherwise, I think both your problems are solved.
-
View User Profile
-
Send Message
Posted Feb 24, 2012it wasnt a bug. i was suggewting it for the enderman code you mentioned u werent sure of it working or not. of course you can juat plain out stop them taking stuff. but i thought it was more consistent with their behaviour of moving blocks by just letting them duplicate the block they want to pick up ;)
-
View User Profile
-
Send Message
Posted Feb 24, 2012@bigscary
What i mean about Multiworld is the possibility to separate the claim blocks by groups. In my server we have survival+nether worlds and a creative one
I would like to separate the amount of claim blocks each one have according to the group of the world, so users can protect also on creative world but without the same amount of effort it does on survival.
I know it complicates things that you made to be simple, but the complexity of some servers (like mine) asks for it!
Thank you anyway!
-
View User Profile
-
Send Message
Posted Feb 24, 2012@bigscary
Turn off AutomaticNewPlayerClaims certain worlds/groups: Cont.
@bigscary Here is my situation/world setup/reason for this: I have a main World - PVE and it's Nether- PVE. They are listed in the Griefprevention: Claims: Enabled: world, world_nether. So Griefprevention is only active for claiming claims with the gold shovel on these two worlds. Also on these two worlds I want AutomaticNewPlayerClaims to function as it does right now. It is great.
Now here's where I find I have an issue: I have a PVP World where people can not build claims with the golden shovel (because it's not in the Enabled list, like I want) because I want the world to be At You Own Risk and Lawless. Problem is people can circumvent this and create a AutomaticNewPlayerClaims with a chest. They could even go and abandon all their claims in other worlds to be able to place a new chest that creates an AutomaticNewPlayerClaims. They would not be able to make it bigger with the golden shovel but just having a AutomaticNewPlayerClaims here takes away from the Risk.
And Lastly, I have a Dungeon world. This world is also not on the Griefprevention: Claims: Enabled: list like I want. So like the PVP world no one can claim with a golden shovel. Yet like the PVP people can claim AutomaticNewPlayerClaims. This world is where you get Teleported to from world, world_nether and into a Dungeon. These dungeons exist in the dungeon world but reset for new players. Problem is people could claim the dungeon or parts of it with chests and AutomaticNewPlayerClaims.
I just want to be able to turn off AutomaticNewPlayerClaims in these specific worlds like I did for Griefprevention: Claims: Enabled: world, world_nether. Or have the ability to with permissions use griefprevention.createclaims.AutomaticNewPlayerClaimsRadius= false/true per group or world similar to griefprevention.createclaims: true/false. Or AutomaticNewPlayerClaimsRadiusCreationRequiresPermission: true/false like CreationRequiresPermission: true/false
Hope I explained this clearly :)
-
View User Profile
-
Send Message
Posted Feb 24, 2012@RaesWolf
Nope. No groups support planned. Consider that when you promote a player to a new rank, you could just /adjustbonusclaimblocks to give them some bonus blocks reflecting their promotion.
On my own server, I'm planning to eventually reward donations with claim blocks among other stuffs (enchants, priority login).
I've also been known to grant 2k-10k claim blocks just for building something cool that contributes to our server's prestige. So there are many ways to use claim blocks to reward players without changing the accrual rate.
-
View User Profile
-
Send Message
Posted Feb 24, 2012is there planned or can be planned a configuration to support groups separately if defined i.e:
default gain 60blocks of land claiming per hour members gain 100 blocks of land claiming per hour
admin gains 15 of land claiming per hour in game
Etc