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 23, 2015<<reply 2516983>
BlockLandClaimExplosions: false
@The_PC_Tech_Guy
Yes. Otherwise, I get lots of complaints like "I have a server that does EVERY TYPE OF GAMEPLAY IMAGINABLE IN MINECRAFT, and I don't want (insert feature here) to apply to my hunger games world, kit pvp world, factions world.... :(
The solution to this is to totally rework all the config options to turn it into a nightmare of configurability, which is great for those people but a huge pain for the masses who just want a simple setup. I'm stuck between a rock, a hard place, and a potentially amazing feature that will take a huge amount of time to code, but which few will actually use.
@MotheMan
Sorry I don't quite understand. What does pvp timeout have to do with monsters dropping items?
@Brycey92
Check your logs. If you see something about primary keys, you need to drop the primary keys on your database's griefprevention tables.
@erik1988
Thanks, will fix.
@pr4xt3roy
It sounds so painful for me... let me say tentatively yes, but low priority behind my other todo's. :)
-
View User Profile
-
Send Message
Posted Mar 23, 2015Apparently people with empty invenotry can kill and damage other players horses.
-
View User Profile
-
Send Message
Posted Mar 23, 2015Hello,
I've been using GriefPrevention plugin for +2 years now. It's great! :) I also voted for you on the Spigot site.
Someone suggested it already but I would also like to see some kind of history of each actions that is taking place.
How about this:
A configurable option which is disabled by default. You enable it only if you need it. It logs into a file in the GriefPrevention plugin /logs/ folder and creates (rotate) different log files per day. Using Java Logger or Log4j supports that.
It would log perhaps the following (or more):
If not in a file, it could in a the database table with a command/ui to access it? But that seems like more work.
Or what about using CoreProtect, or Prism to log all the actions? Is that even possible?
Anyhow, logging into a file would be the bare minimum and so helpful to track down problems. It would be a first step at least.
Thanks! :)
-
View User Profile
-
Send Message
Posted Mar 22, 2015I have an issue with GP 9.1 on MC 1.7.10. Subclaims seem to be deleted within a few hours to a few days of being created. This makes it impossible to manage a claim without giving permissions to everyone or running around all day re-creating subclaims. Please help me!
-
View User Profile
-
Send Message
Posted Mar 22, 2015Any way to have certain people not having to follow the combattimeout? meaning have mobs be able to drop items in pop for example whereas normal players can't. i'm sure it used to be like that however it seems to have changed recently??
-
View User Profile
-
Send Message
Posted Mar 21, 2015would still really love more siege options mainly attackers being able to place blocks config option
-
View User Profile
-
Send Message
Posted Mar 21, 2015Does the BlockSurfaceCreeperExplosions, other explosions, fire spreads, etc. only work on worlds with GriefPrevention claims enabled? I decided to enable them today in the config, but there appears to be no effect...
-
View User Profile
-
Send Message
Posted Mar 20, 2015Hello, I just Downloaded The Plugin And Put It In My Spigot Server The Server Did Detect The Plugin But When I Place A Chest Nothing Happens... Help
-
View User Profile
-
Send Message
Posted Mar 20, 2015For some reason I can't edit my post. What's the new configuration for explosions? My config.yml is exactly the same.
-
View User Profile
-
Send Message
Posted Mar 20, 2015@bigscary
Sorry if I made a confusion. I do know how /ClaimExplosions work. What I was telling you is there's no way to enable explosions INSIDE AND OUTSIDE claims, both ABOVE AND BELOW sea level. But then, I did not check the new explosions config from version 11.1. I will do it as soon as I can.
-
View User Profile
-
Send Message
Posted Mar 19, 201511.1 Updates
Please take a few moments to vote for Grief Prevention. :) Thanks for your support! http://www.spigotmc.org/resources/griefprevention.1884/
@Fluffbukkit
Please give me exact steps for how you created the admin claim, and how players are griefing it. Also, try /trustlist inside the land claim to make sure no one has granted permissions there. Finally, remember that anyone who has permission to create an admin claim has permission to modify them and build in them. Make sure the players who are "griefing" don't accidentally have the griefprevention.adminclaims permission.
@disciple218
I agree it shouldn't, but I think it does something with UUIDs, which might make the UUIDs not match what Mojang (or your local server data) says they should be.
@Mcraftpete
Please give me the complete server logs from the last time you booted before you noticed this problem. I'd like to look for any hints in your logs.
@Senophoe
/ClaimExplosions, when enabled, allows explosions to destroy blocks above sea level as long as they are inside the land claim where you've enabled /ClaimExplosions. If you want to enable all explosions above sea level, there are separate config options for that. I will make a note to myself to double-check this, since the whole point of adding /ClaimExplosions was to allow limited explosion damage above sea level.
-
View User Profile
-
Send Message
Posted Mar 18, 2015@bigscary
Current default for explosions is off, unless the claim owner uses /claimexplosions, and even if he does, explosions will only work below layer 63.
What would be cool to do on your to do list is make explosions like this:
ExplosionsOutsideClaim: true (true - default - makes explosions work outside claims, false makes explosions not work outside claims). ExplosionsInsideClaim: false (false - default - makes explosions not work inside claims, unless the owner uses /claimexplosions. True makes it always work inside claims)
Also, remove that layer 63 thing. It's annoying.
-
View User Profile
-
Send Message
Posted Mar 17, 2015Hi, I have been using this with no problems on 2 of my servers , all seems to be working as expected and I would say its a great plugin , however suddenly today players could access other players chests and furnaces in claimed land , like everyone , I had made no changes and hadn't updated or added other plugins that may interfere , my config is same as when I first set up .. http://pastebin.com/HDHtEHCS
Version : [GriefPrevention] Loading GriefPrevention v10.5 This server is running CraftBukkit version git-Spigot-d0d1d87-15e81cf (MC: 1.8) (Implementing API version 1.8-R0.1-SNAPSHOT)
Please can you let me know what could suddenly cause everything to become open ?
-
View User Profile
-
Send Message
Posted Mar 17, 2015@bigscary
I will compare UUIDs from log entries and database and get back to you, thanks.
As for Bungee, it's just a proxy that chains a group of servers together. It shouldn't really have an effect on GP functionality.
-
View User Profile
-
Send Message
Posted Mar 17, 2015The admin claim system seems to be busted. Players are still able to grief admin claimed areas. Regular claims are protected though, which is the main thing I'm worried about.
-
View User Profile
-
Send Message
Posted Mar 17, 201511.0.2 Updates
Please take a few moments to vote for Grief Prevention. :) Thanks for your support! http://www.spigotmc.org/resources/griefprevention.1884/
-
View User Profile
-
Send Message
Posted Mar 16, 2015@GodsDead
The fix was to give any players with negative blocks more blocks to bring them back up to an even zero. Also any players who had more than the allowed accrued blocks (set in your config file) were corrected back to max accrued blocks (with their bonus blocks remaining untouched). So many players who had more blocks than they should have been able to accrue in their accrued blocks total will now have zero, because they were first reduced, then had negative, then were given bonus blocks to bring them back to zero.
@Vanhout85
Players can't transfer claim blocks unless you have buying/selling allowed on your server, which you can set up with other plugins and in the config file (see setup/config page). However players can create land claims, then give other players /permissiontrust and /trust, effectively loaning a land claim to them.
@Senophoe
Current default is don't allow, with /claimexplosions turning it on until the claim owner logs out. There is no option (yet) to turn on explosion damage to land claims on a global level, but that is on my todo list.
@deano3663
I will add an option to allow explosion damage to land claims, but it will be up to server owners to "fix" the griefing potential by adding a reasonable plugin like CreeperHeal.
@disciple218
I'm at a loss, here. :( I know very little about how Bungee works. If their player UUIDs match the UUIDs in the claim data file (or your database) for that claim, then they definitely should have access. How are you determining their UUIDs? Did you check the local (main server) logs from when they logged in?
@Luficer
A good point, I hadn't thought of that. Let me ponder and see if I can come up with anything. My gut says I'll probably decide to just let it go. I'd rather leave the Vanilla behavior in, since the potential grief is very situational and opportunistic.
@iamthereaper89
I won't give players an option to be 100% siegeproof just because they're in another player's land claim. If you want players to not cause your claim to be besieged, your only options are to take away their permissions or convert it to an administrative land claim. Giving players an easy workaround for the siege mechanic totally defeats the purpose of having it turned on in the first place.
Sure, I'll probably make that change to the timer.
@GodsDead
See private messages - I'm at a loss for how to design this buy/sell in a way that would work for everyone. The way it works currently is the way I designed it on purpose. Most players (maybe not on your server, granted) don't have bonus blocks, so they wouldn't have anything to sell.
Don't you think making a log entry every time a player created a claim, resized one, or deleted one would be spammy?
Please explain about your second edit. What exactly are the steps to reproduce this?
-
View User Profile
-
Send Message
Posted Mar 16, 2015These Bug reports are piling up, I've had more reports of players selling claim blocks and relogging, they get the money & their claim blocks have not diminished. But When I tried this, everything worked as it should, exept I noticed a fatal flaw in the way you remove ClaimBlocks. In the database you have 2 Claim blocks storage: accruedblocks & bonusblocks.
I noticed that when you sold claim blocks the claim blocks were removed from accruedblocks!!!! This entry should never, be subtracted from, it should only ever increase with gametime played, If a player sells claimblocks it should be removed from bonusblocks, if they have 0 then it should go into a minus so 300 Earned 0 Bonusblocks, Keeps Earned as 300 and Bonusblocks goes to -200, then a simple calculation of 300+-200 gives you their actual blocks. This is extremely destructive at present, Please Fix this issue.
I am trying to find out a way to reproduce the selling bug that is giving my players infinite money.
Edit: We need a way to keep a log of absolutely everything, buying, selling, trading, resize, newclaims, Its nearly impossible to find out a history of what a player has done, especially if accruedblocks are being destroyed!
Edit2: The player responded about the infinite money for selling claim blocks; This happens after the server restarts, and they were able to sell ALL of their accruedblocks (Even though the database shows 115 accruedblocks still) as the player had an abundance of bonusblocks holding all their big claims.
-
View User Profile
-
Send Message
Posted Mar 15, 2015Is there a permission that I can give so that the anti-spam is bypassed. I've been looking but I can't seem to find it. Thanks in advance :)
EDIT: Nevermind, found it in https://github.com/ryanhamshire/GriefPrevention/blob/master/plugin.yml
-
View User Profile
-
Send Message
Posted Mar 15, 2015I appreciate your suggestion to turn myself siegeimmune. But I don't have an issue with being sieged at my property it's people who don't own my property being sieged while I'm offline. And as a player it's not fair to make myself immune to siege when we aren't gonna do that for any other players.
Also is it possible for you to swap the siege permissions timer around, some players are being ganged up on by groups of 4 or 5 players that take it in turn to siege the same person. Ideally the timer should be put to the player being sieged so no one can siege then again for an hour or whatever.