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 5, 2015@The_PC_Tech_Guy
ah that explains alot xD thanks alot. its just me who is a noob :P
-
View User Profile
-
Send Message
Posted Dec 4, 2015Request: To be able to select a large area in worldedit and do /deleteclaims. I have literally thousands of unused claims all around my spawn from that first chest drop, these hardly ever expire and we need a way to bulk delete a bunch of claims. when you shift+right click, it shows all claims, you go through 1 by 1 deleting them but as soon as you delete the first, they all disappear and you have to shift+right click again!
-
View User Profile
-
Send Message
Posted Dec 4, 2015@kroko1992
What are you talking about? I think you're misunderstanding what /trust does: /trust gives access to building, destroying, and containers as well as virtually everything else except to /trust others.
-
View User Profile
-
Send Message
Posted Dec 4, 2015@The_PC_Tech_Guy
well that is kinda lame then.... if /trust is removed when /containertrust is given then you cant give right to a person to open stuff and build at same time. /trust will be removed and then the person can only open stuff and not build anymore....
-
View User Profile
-
Send Message
Posted Dec 4, 2015@kroko1992
That's how it's supposed to work. /containertrust only gives access to containers like chests and dispensers (and farms I think), as well as /accesstrust (which I just learned by reading BigScary's latest comment). Only /trust gives permission to build and destroy in a claim.
-
View User Profile
-
Send Message
Posted Dec 4, 2015my players are saying they cant build while haveing containertrust but they can with trust. can it be something i messed up in the config?
-
View User Profile
-
Send Message
Posted Dec 4, 2015@Jemrada
Glad to hear it's working for you now! :)
@The_PC_Tech_Guy
I've been spending some very rare focus time to code my ass off, since I can respond to threads while I'm distracted. But now I've fallen behind, so I'm about to go catch-up on all my threads. :) Thanks for reminding me.
My Java didn't like the pull - I modified it and republished as a standalone class (its own file). I think it's really public now.
The water thing is on my todo list. IP thing I pinned down and I think I fixed it as well.
@kroko1992
That's the correct behavior. The trust levels inherit - for example if you have containertrust, you ALSO have accesstrust because it's a lower level. So you don't have to explicitly give a player each trust level, just the highest trust you want that player to have.
PermissionTrust is the exception. It allows a player to give his trust level to other players, good in, for example, a tenant situation.
-
View User Profile
-
Send Message
Posted Dec 4, 2015i have a strange bug. my players are only allowed to have one type of trust at a time. so if a player had /trust and he then gets /containertrust, then he looses /trust. is that someting that can be looked into and possible fixed?
-
View User Profile
-
Send Message
Posted Dec 3, 2015Hey Big_Scary, here's a couple issues I posted on spigot discussion page. Not sure which is the best way to reach you regarding GP, and I know you don't want more places to check, but perhaps I could help compile issues in an issue tracker (either here in devbukkit or on a separate github repo)? Anyways,
https://www.spigotmc.org/threads/griefprevention.35615/page-69#post-1130252 - issue regarding playerinteractevent firing twice when clicking a fake block on water. (Also reported by SpacePuppeh via video and verified here: https://www.spigotmc.org/threads/griefprevention.35615/page-69#post-1138092) Also an issue of selecting a corner on water (which I submitted a PR for).
I'm also trying to experiment with the IP issue. My guess is that in some cases, the PlayerQuitEvent doesn't fire, thus not decrementing the IP count.
Also, it still seems CustomLogEntryTypes isn't public still, even though you merged my PR - perhaps you didn't pull the change locally?
-
View User Profile
-
Send Message
Posted Dec 3, 2015@bigscary
This is also one of the things I suggested, and probably the easiest to implement. Could be default "auto" (behavior as it is now) or specify claim mode for newly-loaded worlds.
-
View User Profile
-
Send Message
Posted Dec 3, 2015@bigscary
Thanks, for some reason it is actually working now. Might have been a plugin conflict that I didn't realize.
-
View User Profile
-
Send Message
Posted Dec 2, 2015@Jemrada
Check your server logs for some hints about that.
@opentexon
Cool! Added to the list of extensions.
@pr4xt3roy
The docs need updating, you're using the correct node. You're also right about the problem - GP removes nodes that aren't used to eliminate confusion. I don't know how to fix this correctly... I guess I could wait 2 seconds after the server starts, but that doesn't feel right. I'll do some thinking. Maybe a "default" or "other worlds" option would be good, to cover worlds that aren't yet available at the time GP loads.
@marubal21
The economy feature is disabled by default.
@unclemark
There's a permissions node. See permissions reference page. ("eavesdropsigns")
-
View User Profile
-
Send Message
Posted Dec 2, 2015@unclemark
Uhh, no. Lol. I was simply showing the fix for the spam. My server's IP is in my signature, anyway, so it doesn't matter if it also happened to be in the picture.
-
View User Profile
-
Send Message
Posted Nov 30, 2015@pr4xt3roy
I too have requested something similar/exactly like this: https://www.spigotmc.org/threads/griefprevention.35615/page-69#post-1133212
-
View User Profile
-
Send Message
Posted Nov 30, 2015@ MuricaGaming - That's advertising, which doesn't help people with real questions !!!
-
View User Profile
-
Send Message
Posted Nov 30, 2015AdminsGetSignNotifications: true
-So only OP gets this ?? There is no permission for it and our admins, mods, supermods, gameadmins headadmins do not see it- only * permissions seem to work and OPPED (and I will rather eat cyanide than give OP to admins)- That's pretty limited.-
View User Profile
-
Send Message
Posted Nov 30, 2015I just noticed that you fixed the lack of formatting for muted repeated messages. That was bugging me for a while and I didn't notice the fix until now. Thanks!
-
View User Profile
-
Send Message
Posted Nov 29, 2015@marubal21
This should disable it ;)
Economy: ClaimBlocksPurchaseCost: 0.0 ClaimBlocksSellValue: 0.0
-
View User Profile
-
Send Message
Posted Nov 27, 2015how do i disable the eco feature all together? i want to prevent anyone from buying or selling claim blocks.
-
View User Profile
-
Send Message
Posted Nov 27, 2015@bigscary
I created a new world using CommandHelper and TerrainControl plugins (not Multiverse) and added it to the bukkit.yml worlds list too. I stopped the server and modified plugins/GriefPreventionData/config.yml to add this new world to the list of worlds.
GriefPrevention: Claims: Mode: world_the_end: Disabled world_nether: Disabled world: Survival my_new_shiny_world: DisabledWhen I restart the server, I can still claim in that world and what I added to plugins/GriefPreventionData/config.yml is gone!
Is there something else I need to do?
The way CommandHelper works is that the world is configured 1 seconds after the server starts. So there is a moment where there are no such world... Could it be that the GriefPrevention plugin check for worlds before it gets "defined" and sees it does not exists (yet) and remove it from the config?
Thanks.
PS: Your documentation (http://dev.bukkit.org/bukkit-plugins/grief-prevention/pages/setup-and-configuration/) says that the configuration variable is claims.worlds when it looks like its more Claims.Mode instead, right? Does the documentation needs to be updated or did I update the wrong config variable?
@opentexon Your plugin looks very nice! :)