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 Oct 24, 2014@ClimacticGaming
Do you have the WAILA (What am I looking at) mod installed?
Cause it tells you what you're looking at and you can enable it to show the block id in the world
For example check the image attached to this post (Edited in MS Paint lol)
As you can see the item id and block id in world are different
-
View User Profile
-
Send Message
Posted Oct 23, 2014@bigscary
In messages.yml on line 353, it says: "Text: Sorry, buying anhd selling claim blocks is disabled."
Very spellings. Much eye burn. Wow.
-
View User Profile
-
Send Message
Posted Oct 23, 2014@bigscary
Unfortunately, I can't find the block ids for these doors (for example, I am just testing with Carpenter's Block Door)...other people are telling me that these don't change when placing them. How can I find the block id specifically instead of item id?
I don't know if that's the problem or not...because I mean I am using 4948 which is the item id showing in NEI. I am putting 4948:*:Carpenters Door in the mod section of griefpreventiondata config so I am using a * to catch all the other numbers it could be...
No door is working except the vanilla wood door. No Natura, No Malisis, nothing...
-
View User Profile
-
Send Message
Posted Oct 23, 2014Everytime my server crashes, tested with flatfile and sql..the grief plugin wipes my freaken players claims on our skygrid world..I don't think we can use this plugin anymore because of it as it's a big issue..
-
View User Profile
-
Send Message
Posted Oct 23, 2014@bigscary
I looked at the code. But I think my explanation was wrong. On a second look, it seems that IdleLimitDays is ignored. (I had reading and writing the config file wrong.)
-
View User Profile
-
Send Message
Posted Oct 23, 2014@LordDWT
That's a really good question - I didn't know the answer right away myself. Turns out it does nothing at all - that was the old name for the "allclaimdays" setting. I will remove it from the config file in the next version. :)
Similarly, I stupidly forgot to remove that /trapped config option that's no longer used. So sloppy! Great catches. ::internet high five::
@ClimacticGaming
Alright, I think I know the answer. I'll bet the IDs you have there are the ITEM ids, not the BLOCK ids. Many items (doors especially) have a different ID when they're an item in your inventory from when they're a block in the world. Do some research on that mod's block IDs to confirm.
@Turbotailz
It was wiped when I pulled all of BC's work out to get the bugs out. I'd like to add it back in, but right now I have a lot of other stuff higher on the todo list. :) Sorry for the trouble! Also like Sinuce says there - plugin reload commands are very messy, and often lead to lots of very ugly bugs. It's another reason I put it off until later.
@Cra2ytig3r
Yep.
@Bobcat00
An excellent observation! Did you look at the code or experiment? Either way I'm impressed.
-
View User Profile
-
Send Message
Posted Oct 23, 2014@LordDWT
IdleLimitDays seems to be redundant with and overwritten by AllClaimDays.
-
View User Profile
-
Send Message
Posted Oct 23, 2014the markers for admin claims are Jack o' lanterns?
-
View User Profile
-
Send Message
Posted Oct 22, 2014@LordDWT
Isn't "IdleLimitDays" the amount of days a user is allowed to be idle (not coming online) before his claim is automatically deleted?
@Turbotailz
My guess would be for stability purposes. If you crave a plugin reloading function, you could try looking into "Plugman". It may or may not work for GriefPrevention.
-
View User Profile
-
Send Message
Posted Oct 22, 2014Can I ask why you removed /gpreload? I prefer reloading plugins than reloading the server...
-
View User Profile
-
Send Message
Posted Oct 22, 2014@bigscary
Please do me a favor and review this link which has my config in it. I am following everything exactly how I'm supposed to. Please look at the BlockIdsRequiringAccessTrust section and let me know why these 3 doors aren't being protected (I won't add in ALL the other items until I can at least get these three fixed).
http://pastebin.com/uMsCxPPi
-
View User Profile
-
Send Message
Posted Oct 22, 2014Sorry for a dumb question but what is "IdleLimitDays" it's not defined in the documentation.
Also you mentioned in your 8.5.1 update you remove the cooldown from "/trapped". "TrappedCommandCooldownHours: 8" still appears in the config. Just thought you might wanna know.
-
View User Profile
-
Send Message
Posted Oct 22, 20148.5.2 Updates
@ClimacticGaming
This worked for me, it made an error message pop up that said I don't have permission when I right clicked on any claimed book shelves. In the version I just released a moment ago, block types included in this list are ALSO protected from left click, which I think is important for doors.
@dddylan98
I think having a sketchy SQL connection is a general problem that you should address. I don't think you should blame specifically mySQL, as I expect the problem would persist even if you changed to a different database platform.
The UUID servers being down would make it impossible for players to log into servers everywhere, so I doubt that's the problem (everyone would have heard about that if it happened). If a player failed converting, I'd be interested to see what your logs said during the conversion.
Check your config file for brand new world settings in this week's versions. Choose "disabled" for a world where you won't have any land claims. In the latest versions, that should also mean no restrictions on where water can be dumped from buckets. Tell me if you see otherwise.
@dutchrastacraft
Still failing to reproduce that issue you're having with the shovel. :( My wild guess suggestions are /reload or maybe reboot your server? I don't really think it will work, but I'm out of ideas. Do other players have the same problem? Do you have that problem in other worlds?
-
View User Profile
-
Send Message
Posted Oct 22, 2014@bigscary
Also another question, how do you disable GriefPrevention entitrely for a world? For example, we have a PlotMe creative world and a SkyBlock world that use plugins which protect themselves, but I would like water to be able to be placed in those worlds. In pre-8.0 you could configure each world, which I found great. I can negate the permissions so people can't make claims in that world, but it still does not solve the water issue. :/
-
View User Profile
-
Send Message
Posted Oct 22, 2014@bigscary
Gotcha. Well I would mostly think it would be useful for if the server is down for a minute or two. Maybe for a little maintenance. My host isn't the most reliable and I occasionally see it losing connection with other plugins. (they display saying connection to MySQL database was lost) I apologize for being such a pain in the butt.
Do you think MySQL is the problem then? It just losing connection and not being able to save it? I also have an issue with some players not having their UUID be used in the database. The conversion was mostly successful when I did this around 3 weeks ago, but a small portion of players (maybe 10/500) didn't get converted. And a few players who are active do not have UUIDs as their main identity in the database. I can export my database if you would like to take a look at it. These players are players that have joined after the UUID switch. Most players work fine, but there are some that do not. It's very odd. (Maybe the minecraft.net UUID servers are down?)
-
View User Profile
-
Send Message
Posted Oct 22, 2014@dddylan98
I guess the timeout is based on SQL settings? I really don't know - I just say "Hey SQL, save this", and expect it to happen, or SQL to tell me there's a problem (which would appear in your logs).
@maddirox1222
In your config file, set the world to "disabled" for land claims. Then no one can create land claims there, and any claims already there won't work anymore.
-
View User Profile
-
Send Message
Posted Oct 22, 2014How do i ignore claims in only one world for everyone? I'm wanting a resource world.
-
View User Profile
-
Send Message
Posted Oct 22, 2014@bigscary
Wow, that's interesting that I'm the first haha. How long does it try to save it for? Could it be possible to store things temporarily in a file on the server until a connection is reestablished and is able to update it? This would probably be complicated to do though, so I do not ask of you to do this necessarily. Good work overall on the plugin :) Thank you for the quick responses and updates.
-
View User Profile
-
Send Message
Posted Oct 22, 2014@dddylan98
My guess is maybe the player's data wasn't successfully saved a few times, resulting in claim blocks he earned not being saved to the database. You'd definitely be the only person I've heard this from, so I'm not confident in my diagnosis.
No, sorry I won't add a reverse migration from database to flat file. :( It took me weeks to code the migration from flat to SQL, and in all the years this plugin has been out, you're the only server owner to ask for the other direction.
@ClimacticGaming
Yep, I understand. I'll have to look into the way it currently works to figure this out. I'll get back to you. :)
-
View User Profile
-
Send Message
Posted Oct 22, 2014@bigscary
Hi
Thank you for responding. I am looking in the GriefPreventionData folder. I just need assistance with the BlockIdsRequiringAccessTrust for modded. I am putting the exact item ID in the section below, but it does not work. I have tried various methods and none seem to work. Over the past 2 years almost I have used your plugin and this section in particular gets changed quite often. 2 years ago it was like how the current method is (it seems) last year for version 1.5 or whatever it was a separate file that you would do Include RE \ name of item \ and a bunch of stuff like that.
I just need a sample file of anyone's config showing how they are blocking certain modded items from either being opened or accessed.
Simple as that.
I have the item ID per NEI, I type it in, name it and it doesn't work. This should be a pretty easy thing to assist with if someone can help.