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 6, 2014Ooops, looks like users can remove items that are contained in frames, within admin claims. Perhaps even other users claims then?
-
View User Profile
-
Send Message
Posted Dec 6, 2014@bigscary
Ahhh, that explains it. The double-trigger was a spigot issue was it not? Hope it gets sorted soon then =)
-8<- Edit: god damnit, I've gone full retard. The "worldconfigs"-folder isn't really relevant anymore is it? Because that's where I've got my per-world configurations. I just saw the expirations were set in the config-file and they are indeed non-0 =P-8<-About the expiration, no. I've had this issue between stopping/starting the server several times. I've also copied the configurations used from 7.8 so that MIGHT be source of issues.
Just noticed two more claims expired during midnight. Players that haven't been active for ages. It's their new player claims. Since I'm working against a copy of the 7.8 data I can check the 7.8 data and see that their playerdata claims that they were last seen 2014-07-23 and 2014-05-28 respectively yet they were both deleted 5 minutes apart.
From what I can tell those dates were migrated prefectly into the 9.2.x playerdata and their claims are actually removed.
Any way to check that the correct values are loaded from the configuration file? =)//
-
View User Profile
-
Send Message
Posted Dec 5, 2014@SuperPyroManiac
I tried with the config changes, and it worked for me. Did you possibly forget to /reload or /gpreload after making changes? Please try again, and this time check your boot logs for any errors. Also, check your config file after a reboot - if your changes have been reverted back to the default tools, that means you made a YAML syntax mistake in your config file and will have to edit more carefully.
@Turbotailz
9.1
@LordDWT
That looks like an issue I fixed yesterday in 9.2.2. :)
-
View User Profile
-
Send Message
Posted Dec 5, 2014@bigscary
I noticed a error on the console today. I'm not sure how it occurred but here it is:
http://pastebin.com/yaeixb1V
-
View User Profile
-
Send Message
Posted Dec 5, 2014What is the latest GP version I should be using with 1.7? I'm not upgrading to 1.8 just yet and don't want to install a version that won't work.
-
View User Profile
-
Send Message
Posted Dec 5, 2014@CloakedAlien
Yep, it's that damned double message thing. One click = two. Since admin claims can be 1x1, it creates the claim right away. Just get farther away from the block and create/resize your land claims that way (remotely).
About the claim expirations... I can't reproduce the same problem over here. Did you remember to /reload or /gpreload after changing the config?
-
View User Profile
-
Send Message
Posted Dec 5, 2014@bigscary
Oops, just noticed another thing. I'm experimenting with MultiVerse on Spigot 1.8. Can't seem to handle claims properly. Just one right-click with the shovel claims it has created the claim and just gives me one moveable block. It's really weird.
Seems to happen both in the normal world and my new multiverse-generated world.
Standard claims seems to work but admin claims are really buggy =)
Edit: Might have something to do with the already known double-message thingy? At any rate I seem to have a few single-block adminclaims now =P
-
View User Profile
-
Send Message
Posted Dec 5, 2014@mcly
Thanks for clarifying. I have to think about this a while - no immediate answer comes to mind.
@CloakedAlien
That's odd, I will look into it for sure.
@westagram
No - sorry, but that feature has been a giant pain in my ass ever since I mistakenly added it. Almost everyone who tries it complains that it's not what they really expected, and then they all disagree about how it should actually work, so the only way I can win is to do a lot of work to make it very configurable, for the VERY few servers who are even interested in trying it out. :\
-
View User Profile
-
Send Message
Posted Dec 5, 2014@bigscary
Awesome - so it's just spigot being wonky. Thank you again!
-
View User Profile
-
Send Message
Posted Dec 5, 2014Great plugin!! Can you revived this feature?
NoSurvivalBuildingOutsideClaims: true
-
View User Profile
-
Send Message
Posted Dec 5, 2014@bigscary
Just noticed that the server seems to be letting claims expire despite me configured it to never expire claims. Keep in mind I haven't touched the configuration in a great while and I've only glanced over this, but the configuration for my world says: Expiration: ChestClaimDays: 0 UnusedClaimDays: 0 AllClaimDays: 0 AutomaticNatureRestoration: false
Yet the log states: [13:55:34 INFO]: GriefPrevention: <user>'s new player claim expired.
I think this is the second or third expiration I've seen since performing tests. No worries though as I'm working with duplicated data on the side =)
-
View User Profile
-
Send Message
Posted Dec 5, 2014@bigscary
No worries mate. I've already figured I can use WG as a fallback worst case. I can't stress enough though how happy we are to see that WP is still alive and kicking <3
Edit: Btw, it was 7.8 I upgraded from (using mysql as storage).
-
View User Profile
-
Send Message
Posted Dec 4, 2014@bigscary
The data is: InvestigationTool: WOOD_SWORD ModificationTool: WOOD_SPADE
According to that link you set me, that's correct. It's still using the default tools.
-
View User Profile
-
Send Message
Posted Dec 4, 2014@bigscary
Some people know where to ask for assistance (server forum), but most of them don't bother to ask.
Players can't type chat or command while standing inside a nether portal, they need to move out of the portal to do command or chat. In this case, since the portal is claimed by others with built walls on both sides, the stuck player is forever stuck.
-
View User Profile
-
Send Message
Posted Dec 4, 2014@bigscary
Updated some things, changed some configs, and I'm no longer seeing the issue with claims breaking on server restart. Not sure what resolved this. Thanks.
-
View User Profile
-
Send Message
Posted Dec 4, 20149.2.2 Updates
@mirolm
Thanks, I'll post there. I've already submitted the report on their forums.
@CloakedAlien
No sorry, it doesn't work right now (or so I've heard). I do plan to get it fixed up eventually, but right now I've got bugs to squash in the core plugin which potentially impact all GP servers. :\ For now, maybe you can get the same done with WG flags, since you're already running with WorldGuard?
-
View User Profile
-
Send Message
Posted Dec 4, 2014@bigscary
I saw they have a Jira opened in their hub and alot bugs are registered there. Maybe you should post them there.
-
View User Profile
-
Send Message
Posted Dec 4, 2014Currently experimenting with migrating our server. So far so good!
Daily build of spigot, latest downloaded grief prevention, worldedit, worldguard, etc.
Copied over all relevant worlds and configs, updated GP-config to access a copy of our old GP database.
Works like a charm!
Now I've got only one question. We previously used Flags to disallow create spawn in our central town (admin claim). Is there any way to do this with the current version of GP? As I understand it Flags isn't compatible anymore because of the recent "rewrite"?
-
View User Profile
-
Send Message
Posted Dec 4, 2014@warderkeeju
That's a spigot/craftbukkit bug I'm waiting to get fixed.
@LeonardoGamer
Oh, right. You'll have to update to 1.8 to use the new GP.
@mcly
You said they can ask for assistance - why can't they type a command? I'm thinking of the /trapped command.
@yellolegalpad
Thanks, I'll look into it today. :)
-
View User Profile
-
Send Message
Posted Dec 4, 2014When a player goes through nether portal and ends up in a nether portal trap (the trap is a claimed nether portal region with walls on both sides of the portal to block others from moving out of the portal), the player then can't type any command and can't move anywhere, and often either quit server or seek admin's assistance. Is there any way to prevent this? Thank you.