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 Dec 9, 2014@mcly
Do a plugins-list on your server, we might have some plugins in common that can explain the griefing of stands/frames =)
-
View User Profile
-
Send Message
Posted Dec 9, 2014@dutchrastacraft
I failed to reproduce the bug you reported over here. Here's what I tried - maybe I'm doing something different from what your players are doing?
@switorik
Yeah, taking damage puts a player into combat. I think players always take damage from teleporting with an ender pearl. The reason for build restriction is that players will surround themselves with blocks in claimed areas, thus making finishing them off impossible.
Any suggestions for making this better which aren't obscenely complicated? :)
@LeeTheENTP
Oh, I guess I missed it in the video. Seemed to me like there was no boom or smoke.
I'll work on the fire spread thing.
@mcly
Please explain exactly how players are taking armor off of stands? I tried left click, right click, projectiles, etc and couldn't manage to steal any myself.
@Turbotailz
I have a probable fix for that coming in the next version. :) Sorry for the long delay, I've been trying to fix it, but without reliable problem reproduction steps, I haven't been able to investigate fully or confirm fixes.
-
View User Profile
-
Send Message
Posted Dec 9, 2014@bigscary
Made a git pull request to fix collection warnings and make my maven build successful. I hope not to break something with this change. :)
-
View User Profile
-
Send Message
Posted Dec 9, 2014@GodsDead
Nah, just took a few seconds. That's all. If I remember correctly it replaces names with UUIDs, so the names are no longer available in the database.
-
View User Profile
-
Send Message
Posted Dec 9, 2014@bigscary
Nothing fancy, just right-clicked. Verified it at different locations in admin claims. Might be in combination with another plugin it happens?
[09:21:53 INFO]: Plugins (13): ChairStairs, SimpleBackup, WorldEdit, RealMotd, TreasureChestReloaded, SimpleColoredMOTD, PermissionsEx, Multiverse-Core, GriefPrevention, LogBlock, WorldGuard, dynmap, Multiverse-Portals
-
View User Profile
-
Send Message
Posted Dec 8, 2014If there's a way to protect armors on armor stands, that'd be great!
-
View User Profile
-
Send Message
Posted Dec 8, 2014@bigscary
The explosion occurs; I just moved out of the way to avoid damage in the video. I'll keep looking through my other plugins, though, just to be sure.
For fire spread, I think that's a great idea. It'd be even better if it was an option in the config.
-
View User Profile
-
Send Message
Posted Dec 8, 2014More VehicleDamageEvent errors in 9.1 FYI: http://pastebin.com/wT7QHXKF
-
View User Profile
-
Send Message
Posted Dec 8, 2014When a player throws an enderpearl, it puts them into combat. It does not matter if a player takes damage or hits a player. As soon as the pearl lands, the player has entered "pvp" combat for the duration set in the config file. The biggest complaint is being unable to build in claims during pvp combat.
-
View User Profile
-
Send Message
Posted Dec 8, 2014@CloakedAlien
Please tell me how they're doing this (the frames thing). People keep telling me, but nothing I try (right click, left click, explosions, projectiles) seems to do it. I need someone to tell me exactly how to do it so that I can fix the problem. :)
@dutchrastacraft
Thanks, I'll check on that.
@GodsDead
I don't know when you last tried to upgrade, but I've improved the speed of migration a lot. I think you should just try again and see how it goes - don't forget to back up, just in case. :)
@madtomic
No, I won't be moving backward, sorry. I know many of you are running on modded (forge/cauldron) servers and there's no cauldron update yet, but that's the usual problem with running a modded server. Just like we all have to sit on our hands while we wait for the bukkit/spigot team to get a platform update out after a Vanilla patch. I feel for ya, but doing what you ask would be basically running two GP projects at the same time, and I struggle to find time already.
@jazzyjokerm
That's a spigot/craftbukkit bug which has been fixed. Update to the latest Spigot/CB build.
@Dutch_Boy
I'll have a look. I've been trying to fix that damned bug for a week, now. Any idea what's damaging the minecart? Are you running any mods on your server?
@LeeTheENTP
Please do check your other plugins - iut's weird that there wasn't any explosion at all. GP doesn't stop the explosion, it just stops it from breaking any blocks. I think another plugin must be doing this.
As for fire spread, per world configs are on the todo list but I dunno when I will get there. What if I made it the rule that in worlds where claims are disabled, fire can spread and destroy blocks? What would you think of that?
@thedi1ceman
I don't understand - if you restored a backup from BEFORE your migration, then the migration should have run again on boot. Maybe you accidentally restored to a post-migration backup where you had a problem converting claims?
-
View User Profile
-
Send Message
Posted Dec 8, 2014Is it possible to force a UUID conversion again? We've had to revert to a backup, but the only one we had was before the conversion so all claims are now owned by the administrator.
Thanks
-
View User Profile
-
Send Message
Posted Dec 7, 2014I am having an issue with TNT destroying blocks.
http:youtu.be/143KX1GjPR8
Config: http:www.hastebin.com/putuhidaxe.vbs
The sea level override is set correctly, however TNT does not destroy blocks as it does in other worlds with the same sea level.
I'll continue looking through my plugins list for other causes, but this is my only anti-grief plugin (CoreProtect for logging, but it doesn't prevent grief).
P.S. I'd also like to enable fire spread in the world.
-
View User Profile
-
Send Message
Posted Dec 7, 2014Still getting the minecart damage error on 1.2.2 running Spigot 1.8
@jazzyjokerm
Update spigot or right click to select points from a distance. If the block is within reach 2 interact events are fired on older Spigot 1.8 versions, which instantly closes your selection.
-
View User Profile
-
Send Message
Posted Dec 7, 2014Found a error in console:
http://pastebin.com/HuPVUDT3
-
View User Profile
-
Send Message
Posted Dec 7, 2014I cant make admin claims? it only makes a corner? that's all, I do /Adminclaims to change the shovel then right click in to different corners and it doesn't work it just make 2 different corners. I tried resizing them but still didn't work. Am I doing something wrong or is this a problem? I have used this plugin a lot before just when I try on my server it doesn't work. Normal claims work. I am using the latest 1.8 version as well as Spigot 1.8
-
View User Profile
-
Send Message
Posted Dec 7, 2014Will you be adding some of the updates in cb1.8 to cb1.7.9 and cb1.7.10?
-
View User Profile
-
Send Message
Posted Dec 6, 2014@CloakedAlien
Did your conversion take that kind of time mine took on my dev server?
Does any of the other data structure change or does it just store UUID's with the player data? because if it does just add UUID's as a column or in a new table, then I could do the conversion on my home computer then upload the UUID changes.
I think I just need to experiment with it some more, but having background information for people that have already done it really helps :)
-
View User Profile
-
Send Message
Posted Dec 6, 2014@GodsDead
You should backup your stuff like there's no tomorrow. I made triple and quadruple backups before finally migrating from 7.8 now.
I previously had migration issues when I upgraded and then downgraded and got claims deleted. However going from 7.8 to 9.2.1 was hassle free except for my own misconfigurations. It converted all the names to UUIDs, no admin claims or user claims was lost (what we've been able to tell)
I copied my 7.8 database to a new one, made sure 9.2.1 had the correct datasource settings before even starting it (or it will create flat file data at first boot which it will then migrate, messing up your existing db stuff)
But yeah, don't test on your live data. Mess around with a copy first.
-
View User Profile
-
Send Message
Posted Dec 6, 2014Hey man, Im thinking its time I upgraded, im still using GriefPrevention 7.8. But as I have so many players im worried that claims could not convert or get broken, last time I tried this the conversion took 11 hours locally on my Windows Server, Do I have to unblock a port from the firewall to talk to the minecraft servers for UUID conversion? Also, how can I check that all claims were updated to the new uuid system?
Looking at my database, my nextclaimid just went past 7000, and my claimdata has 3,118 rows. Is a new UUID table created or is the old one updated? are the UUID's pulled from the world data or the GriefPrevention player data? My GriefPrevention playerdata is getting close to 15,000 rows now.
Could I also run this locally on my dev server first, then upload the updated sql? Could I perform this conversion using just my world file, the old database and the new plugin? Or do I need essentils data etc?
Thanks man, From a very nervous to upgrade server admin. I classify GriefPrevention as our most important plugin, so I don't want this to screw up!
-
View User Profile
-
Send Message
Posted Dec 6, 2014Massive bug People are able to claim unlimited claimblocks. This seems to be only a problem with my server since when I converted players had 0 claimblocks but had claims thus they had a negative amount of claimblocks. When they have a negative amount they can keep claiming.