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 6, 2015@bigscary
It doesnt seem to work. I can still PvP in claimed areas :S
-
View User Profile
-
Send Message
Posted Jan 6, 2015@TheFireTroll
Will have that fixed today. :) It's a client bug, but I think I have a reasonable workaround figured out.
@P0WeRZz
That's already a feature, and it's enabled by default.
-
View User Profile
-
Send Message
Posted Jan 6, 2015@TheFireTroll
I have the same problem, and too with gold blocks :/
-
View User Profile
-
Send Message
Posted Jan 6, 2015Can you add function to disable pvp in claims?
-
View User Profile
-
Send Message
Posted Jan 5, 2015Mysterious pumpkins are appearing in the distance when using a stick and viewing a claim or creating one. Expanding a claim also seems to make the original claim look like its still there just with another boarder. Seems to be admin claims. Image here https://fbcdn-sphotos-h-a.akamaihd.net/hphotos-ak-xpa1/v/t35.0-12/10907088_1534755853459747_2092027455_o.jpg?oh=3a209df3fb1d45a37908e1c9d2190ebd&oe=54AD2B3E&__gda__=1420647919_73896659e239b27b7c0299508ec20812
-
View User Profile
-
Send Message
Posted Jan 5, 2015@Jikoo_K
Hey thanks for the tip and the specific test case, I'll get on this asap. :)
@switorik
Hm, that's definitely not what I intended, thanks for ht detailed explanation. I'm planning to do a bit of rewriting for this feature, both to improve performance and fix the issue you're describing.
@CloakedAlien
I plan to have another attempt at fixing this problem in the next version I'm working on right now. :)
-
View User Profile
-
Send Message
Posted Jan 5, 2015@bigscary
Oh, right. I know I mentioned this before but on the server we're experiencing accruedblocks-rollback is a server using MultiVerse and the two most active players are actually mostly building in the non-default world.
-
View User Profile
-
Send Message
Posted Jan 5, 2015@bigscary
I'll try and explain myself better. My last post was rushed.
We have a main nether portal at spawn. Both sides of the portal are claimed and do not have public build trust. The portal worked 100% fine all the time until I updated. Once I updated, As long as I have trust on the other side, the portal works. However, for a normal player, the portal would connect to someone elses portal that is claimed without public trust, and going through the portal again would put you in one of three random spots. His other portal, spawns original portal, or create a brand new portal way out somewhere. The results seem to vary every few times you enter. I downgraded and everything worked just like its supposed to.
I would like to mention I double and triple checked the coordinates. I am not getting any errors popping up in console.
To sum it up, it seems like the portal checks to see if you have trust on the other side, and if you don't it does one of three things. It works like normal, it puts you in someone elses portal, or it makes a new one and the result is random.
edit: After trying 10.1 again, I didn't say anything to the players when I updated and everyone started complaining netherp portals started acting up again. We had an incident where a nether portal was randomly generated in the middle of a players claimed house, even know that portal was already connected correctly to a portal. I downgraded once again until we can figure out what is causing this bug.
-
View User Profile
-
Send Message
Posted Jan 5, 2015@bigscary
I hear ya. I wish I had some experience with plugin development, I'd try and help to ferret it out. Any test versions you can throw my way I'd be happy to run =)
Edit: Oh, by the way. When manually trying to check stuff in the database it would help _a lot_ if the users last known username was listed alongside the UUID in the playerdata table =)
-
View User Profile
-
Send Message
Posted Jan 4, 2015@bigscary
If you're only after a regex filtering raw IPs, might I suggest
Non-IP links being filtered:
-
View User Profile
-
Send Message
Posted Jan 4, 2015@yoshi989388
I'm gonna need an error message.
-
View User Profile
-
Send Message
Posted Jan 4, 2015I CANT BUILD OR DESTROY IN MY OWN ADMIN CLAIM, OR THE WHOLE WORLD HELPPPPPPPPPPPPPPPP I CANT DO ANYTHING ON MY WORLD, I CANT EVEN BUILD ANYWHERE NO WHERE HELP HELP HELP HELP HELP
-
View User Profile
-
Send Message
Posted Jan 4, 2015@dddylan98
/rnf can be used to naturally fill holes. Regenerating the chunk also puts all the ores back, and if the chunk is old (world seed or generation code has changed since it was generated), then regenerating will give you a bad chunk that doesn't match its surroundings. Just some factors to think about. :)
@christhehill
You're using a GP version made for Minecraft 1.8+ on a 1.7 server. Either use an older version of GP, or update your server to 1.8.
@CloakedAlien
I have a vague guess about the cause, I'm going to try an update to see if the problem disappears. :\ Since I don't have to a way to consistently reproduce the bug, I'm never really sure if I've fixed it or not, and have to wait and see if anyone sees it again.
@Pippl
Yeah, that's an odd client bug that I'm trying to work around. Thanks for the additional info... I will try to figure out the root cause and get it fixed. It's been frustrating me for a while now. Hopefully your hint about the claim being bigger than your view distance / loaded chunks will help me pin it down. :)
@switorik
Nether portals have always been unpredictable by design. I don't think it's worse than the vanilla behavior, and the GP code only kicks in in the rare case where the player teleporting is creating a new portal AND that portal is in a land claim AND the player doesn't have permission to build in that land claim. Of course you're entitled to your opinion, but I think you're overreacting. :)
Do you have a suggestion for a better way to fix this problem?
@luke_smiff
Yes, see setup/config page. However, this may result in lots of griefing of new players, since protecting land will be fully manual.
@Jikoo_K
Sorry Planar, I don't exactly understand what you're asking for. Will you please rephrase?
@leojFIN
Thanks VERY much for sharing your timings info with me. This is a new event I've hooked into, and I will look into streamlining it.
EDIT: Just looked at the timings report. Of course I'll still streamline the event handler, but I gotta set expectations. According to this timings report, even if you had no plugins installed at all, you still would have been lagging during this timeframe. My event handler only accounted for a tiny 0.49% of your total CPU load during the timeframe you measured.
@cooldeal97
If it's not working, then either you installed a GP for Minecraft 1.8 on a 1.7 server, or you didn't install 1.8 correctly (update your buildtools.jar, then rerun it and pick one of the two JAR files which appear in the folder with alongside your buildtools.jar). If you're running Minecraft 1.7, use an older version of Grief Prevention or upgrade your server to 1.8.
@xtomyserrax
No, I won't release new versions of Grief Prevention compatible with old versions of Minecraft. Not enough free time. :\
@Jikoo_K
GP only mutes IP addresses, not other types of URLs. At least, that's the design. I use this regex:
If you've seen another message containing a URL being muted, please give me that exact message so that I can investigate.
-
View User Profile
-
Send Message
Posted Jan 4, 2015@dddylan98
Incorrect. Essentials' link filtering is part of EssentialsChat, which I do not run. It also filters the periods out of links but leaves the contents intact. GP's spam filter automatically filters and soft mutes all unapproved links, which makes the filter unusable for me.
As stated before, I want to use GP's spam soft mute filter, however, I run a custom chat plugin that already filters links sent in the main chat. I don't care what people want to link in their own private channels, so I would like either a permission to bypass only link filtering or the ability to use regex to define acceptable links.
-
View User Profile
-
Send Message
Posted Jan 4, 2015@Jikoo_K
I don't think this plugin does the link filtering. It might be essentials. Try adding the permission node to allow links.
-
View User Profile
-
Send Message
Posted Jan 4, 2015Can you make the updates for 1.7.2 too?
-
View User Profile
-
Send Message
Posted Jan 4, 2015Yes, This plugin is a really cool plugin. But, Land Claming/Protecting is not working. Can someone tell me how to fix this please
-
View User Profile
-
Send Message
Posted Jan 4, 2015This plugin is amazing. Love it, for the simple way that our players can use it. We do have a small problem. We use plugin called ancient gates (Nearly the only bungee cord portal plugin that satisfies us. But GriefPrevention's onPlayerPortal event seems to couse lag with it.
timings: http://timings.aikar.co/?url=9670357
We have 200 player normaly online.
-
View User Profile
-
Send Message
Posted Jan 3, 2015Could we possibly get a permission for ignoring link/IP filtering only? I've spent a lot of time getting my own json channeled chat plugin working with soft muting, and I really don't care what people link in their own private channels.
Edit: Alternatively, could it become regex? a simple .* would serve my purposes just fine and allow others a lot more flexibility in configuring. Not as efficient as just not checking for links at all, but still preferrable to not being able to use the anti-spam feature because of its rigidity.
-
View User Profile
-
Send Message
Posted Jan 3, 2015Is there a way I can stop Chests from protecting land?