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 Jan 12, 2013Love your plugin. Small issue has only happened a couple times. Not sure how to reproduce, but this is what I see. Put down in an anvil armor and book, take the new item out of anvil, leave the anvil screen and the book & old armor get thrown onto the floor. Also your levels get taken away unless you relog. We discovered that if somebody that has this issue does /containertrust <theirName> that they can now do the enchantment. I know I should have put in a ticket for this, but it doesn't seem like a big problem. Another issue I see is the /deleteallclaims <player> doesn't seem to work. Thanks for all your effort with this plugin, it is truely the best out there. Jack
-
View User Profile
-
Send Message
Posted Jan 12, 2013@bigscary
Ah, OK.
Just waiting for your GitHub to update now, since I prefer to add my own ban method, rather than the default silent one :)
-
View User Profile
-
Send Message
Posted Jan 12, 2013Im not asking you to do this plugin for forge I was just wondering if it is at all possible to make a mod like this for forge. If it is I want to look into trying to attain someones services to do just that. As I am finding there is a complete lack of decent grief prevention mods for Ftb or other Forge based servers. Thank you I loved your mod when I was running bukkit. If this has been asked just smack me:P
-
View User Profile
-
Send Message
Posted Jan 12, 2013Hi bigscary, I did end up changing the item from golden shovel to wood shovel for exactly this reason. I have no problems otherwise now.
However, I do have another issue. I've premade a spawn area with shops and what not, everything works as intended, but here's a problem I have. The spawn area works great, except when zombies destroy the doors off my town. I don't want to turn zombie destroy doors off completely, but rather want to allow it to destroy doors and be replaced by players even without admin access.
Here's two options I think would work. Either give the admin claims ability to restore itself after a couple of game days (hopefully configurable), or allow players to place these items where there originally was an item. I'm guess the latter would be a lot harder to control, as players might forget what goes where, but this issue really only happens with doors so far.
I would also like an option for players to be able to share chests individually maybe? Or would it be a better idea to combine this with lockette? I'm currently running Gringotts so we all have vault chests. However, allowing containers will allow every container in the claim, and that'll allow even the emerald chests. If reverting back to lockette is the best solution then so be it. However, I'm trying to run as many "combined" mods as possible so updates will not bork my server as much.
Also, to kind of play in accordance to the first issue. Would it be possible for creepers to say destroy a part of an admin claim like they normally would, but have the regeneration happen after a certain time as well? This would allow creepers to blow up say fences, leading to other raids by other mobs. However, the town would fix itself (can't be player helped) eventually, but you have to hold out until it does. I know in a true "grief" sense this can be exploited, but right now it is not giving me much options. Takes a huge part of the game totally away. Creepers either do absolutely no dmg, or they do permanent dmg.
Thank you for your time.
-
View User Profile
-
Send Message
Posted Jan 11, 2013@Zilacon
I'll look over the source code to guess about your issue, but I can't make any guarantees about database related stuff, because there are so many potential issues which could come from database configuration on the server end.
@confuser
That's already fixed, I just haven't published the updated source.
@netherfoam
Almost everything you want to do is doable, I just need to update the API page. Use claim.ID to get your unique ID. Use claim.clearAllPermissions() for untrust all. Use claim.grantPermission(player, permissionLevel) to grant permission.
Figuring out everywhere a player has permission is not doable with my API. If you want to remove a player from a claim when he leaves his clan, you'll have to keep track of where he has permission on your end. It will be very difficult because there's no event you can hook into to notify you about permission changes. What if you give a permission group access to the clan claim instead, and add/remove players from that permission group as they join and leave the clan?
@KStorm1
You can use a starter kit plugin I guess, but it will be messy. You have to also consider that players could die and lose what you gave them, for example. If you want players to have easy access to customize land claims (golden shovel), consider changing the tool from golden shovel to something else common, like wooden shovel.
@TheReverend403
Already fixed, update to 7.2.1. :)
@notif
Your server was empty for so long that your database connection died of boredom. Consider switching to file mode.
@Siarys
Sorry, 5.5.1 is the latest version which works with Tekkit. :\ Tekkit hasn't moved up past Minecraft 1.2.5. I don't know what's happening over there, so I can't tell you what to expect.
@Code_Red11
Sorry but no. It would make it easy for griefers to pool their resources quietly. For example, a "good guy" griefer plays regularly, and creates land claims for "bad guy" griefers to use when griefing. This way, the bad guys always have lots of claim blocks with which to cause trouble.
-
View User Profile
-
Send Message
Posted Jan 11, 2013Feature request /transferclaim usable by all players to transfer their Own claims, and usable by admins in ignoreclaims mode to transfer admin and player claims
-
View User Profile
-
Send Message
Posted Jan 11, 2013@bigscary
Hey Bigscary.
I'm using the 5.5.1 build of GP seeing as I'm running a Tekkit server(1.2.5 MC); I noticed that with 6.2 you changed the default adminclaim behaviour to stop all usage of chests/levers/hurting animals. Is there any way I can do that with the 5.5.1 version? (By in-game commands, considering I got no java knowledge and all that) (Or does a later version still work by any chance?)
If not; I'll just set all Admin claims on my own name. It's not a big deal.
Thanks for the awesome plugin. Wouldn't know what to do without it.
Edit; To add. Any way to hide the following commands from /help?
-
View User Profile
-
Send Message
Posted Jan 10, 2013We're getting this error whenever a player logs in:
10.01 21:32:04 [Server] INFO GriefPrevention: Unable to save data for player shade1060. Details:
10.01 21:32:04 [Server] INFO GriefPrevention: No operations allowed after connection closed.Connection was implicitly closed by the driver.
-
View User Profile
-
Send Message
Posted Jan 10, 2013Well, I KNOW this shouldn't happen...
10:38:32 CONSOLE: [INFO] GriefPrevention: Banning TheReverend403 for spam.
10:38:32 CONSOLE: [SEVERE] Could not pass event AsyncPlayerChatEvent to GriefPrevention v7.2
10:38:32 CONSOLE: java.lang.IllegalStateException Cannot kick player from asynchronous thread!
It then proceeds to allow the person to spam as much as they like.
-
View User Profile
-
Send Message
Posted Jan 10, 2013Hey bigscary, I have a small suggestion. Could you have a permission that when a person gets banned for spamming, it sends a message to the person with that permission? Or maybe broadcast it somehow?
-
View User Profile
-
Send Message
Posted Jan 10, 2013Is there a way to make players start with the required items for claim and such? So players can immediately plop down a chest and have a spade ready to expand their zones?
-
View User Profile
-
Send Message
Posted Jan 9, 2013Never mind the question about plots in a town. I had missed one part of your documentation. Have now seen that your plugin allows for it.
-
View User Profile
-
Send Message
Posted Jan 9, 2013Oh, quick note. Your Player Experience and World Protection page (linked above) mentions using string instead of a stick. Just thought I'd mention it.
-
View User Profile
-
Send Message
Posted Jan 9, 2013I think I've read all the pertinent documentation. It looks like in order to have player towns where the town owner can give out plots to residents, we'd have to use a different plugin - like WorldGuard regions. (As in addition to using GriefPrevention which would as our basic claim/protection plugin.)
Is this correct?
-
View User Profile
-
Send Message
Posted Jan 9, 2013@bigscary
That is all well and good, but I wish to integrate GP into a clans plugin I'm writing for my server. I want:
To work like /trust and /untrust. For this, I need a few things:
As for /untrust all, I'm looking for a way to do it with your API.
-
View User Profile
-
Send Message
Posted Jan 9, 2013@bigscary
The reason it's still causing crashes is because you are using HashMap's forcing synchronisation. I'd suggest using ConcurrentHashMap instead as it is has a lot better lock handling etc.
Also noticed your kicking players from other threads, that's a massive no no, run it as a synchronous task for the kicking bit.
-
View User Profile
-
Send Message
Posted Jan 9, 2013@bigscary
Getting this error:
-
View User Profile
-
Send Message
Posted Jan 9, 2013@netherfoam
You can't reference claim IDs with this plugin, they're just used internally. But they are made available to other plugins (via my public API) who want to build on top of Grief Prevention.
/untrust all will remove all permissions from your claim.
@CityCraftOwner
/adminclaims lets you create administrative claims for free. Or use /acb to give yourself any number of claim blocks. Both of these are mentioned on the setup/config/administrative page.
@ridddle
Okay, that may be doable, thanks for the suggestion. :) I'll check into it.
Yikes. I'd rather not meddle with the claim block accrual code for a minor fix, sorry. :\ Risky business to dig into all that when it's been working bug free for months. If I have to get in there for something more serious later, I'll reconsider doing your thing while I'm at it.
-
View User Profile
-
Send Message
Posted Jan 9, 2013@bigscary How about allowing using fractions of an hour there? So, 0.5 would be 30 minutes. That way you won’t destroy config for everyone and allow more granular configuration.
Also, I realize how big such a change would be, but I have another request. Is it possible to doublecheck with real time in Java every so often to adjust blocks acquired per hour? Bukkit scheduler is dependent on tickrate and on busy nights TPS can be 15-10, not full 20. It means that when the server is popular, people get punished by playing by getting lower amount of blocks.
-
View User Profile
-
Send Message
Posted Jan 9, 2013it is a great plugin but i want that ops can claim infinite blocks, so how i can do that?