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).
Update 11.8.1 is here! GriefPrevention recently slipped to #2 on the Spigot site. Please help out by leaving a 5-star review. :) Thanks!
@Treydun
That's a good thought! I just checked, and it is turned on in my test server. So that's not the reason they weren't breaking doors. Hmm... it was night time, server is hard mode, they were chasing me in survival mode, and it was a wooden door. Am I missing something? They walk up to the door, but don't attack it.
Please save the entire world and port to sponge! WERE ALL COUNTING ON YOU GRIEF PREVENTION !!!!
@bigscary "Zombies" Is mobGriefing true?
Update 11.8 is here! GriefPrevention recently slipped to #2 on the Spigot site. Please help out by leaving a 5-star review. :) Thanks!
@HalestormXV
Thanks for undestanding, and I'm sorry it took so long to reach that conclusion. Maybe I should have lead with "are you running a 1.7.10 forgemod server"? :)
@jenks1999
It's not so much about complication in this case - it's just that I don't want to spend CPU cycles on anything that's not preventing grief. Those are definitely good candidates for an extension plugin, but if I added features like those to the base plugin, I'd be making the same mistakes WorldGuard early versions of Essentials/Multiverse did - major bloat. :)
@bratpitt
I actually did look into that last night, and I'm not totally happy with the outcome. I put my server on hard mode and with that setting FALSE, zombies weren't breaking wooden doors when trying to chase me. But then when I set it to true, they still weren't breaking the doors, so now I'm not confident in the test. Any tips for making sure the zombies try to break down the doors I set up?
@bigscary
Have you looked at "HardModeZombiesBreakDoors: false" It seems not working, can’t tell sense when but noticed it suddenly when villagers disappeared and doors was gone.
Haven’t updated anything more then spigot,EHM and GP, side note village is in admin area but that should not matter I think, as it has always been.
@bigscary
Any new on the mob control in players claims? would be nice for players to be able to deactivate mob spawning/entry into their plots so they can build without hassle or even control it for players own private mob arena's.
Also maybe a vote/rating system where people can visit a plot and rate it from dirt,iron,gold,diamond,emerald etc etc or their own personnal rating system adjusted in the config, that sql all the data so it can be displayed on a website. Would either of these be possible? or too complicated?
@bigscary
That's understandable. I do appreciate the time and thank you for at least responding. I still vote GP as one of the best. Thanks.
@HalestormXV
That's no good - even if I put in a new feature for you now, you wouldn't be able to use it. GP is currently under dev for 1.8 servers, not 1.7.10. So anything I add wouldn't be compat with your 1.7.10 server. :\
EDIT: However if hypothetically cauldron were released for 1.8 servers, this would be a high priority feature for me.
@bigscary
I am running a 1.7.10 server that is Cauldron, it is still updated every so often under a new build/fork. The item that adds this feature is a Mod Item. Specifically a wand. Because they are activated via right click or holding right click.
@nakkettaja
Remove that key on ID from the table. All subclaims are supposed to have -1 for ID, so it's OK to have duplicates.
Y = -190 isn't harmful I think - what's the issue you're experiencing related to that data point?
@killyouslow
This site is for bukkit plugins, not sponge plugins. And since the cauldron guy quit the cauldron project, it's no longer possible to run forge server mods on the same server with bukkit plugins. :\
@HalestormXV
What you're describing is a feature I had planned before the cauldron guy decided he wasn't going to release cauldron after 1.7.10. Then I dropped it because the problem it was meant to solve suddenly became rare, with forge mods out of the picture. Are you running a 1.8 server? If yes, what is it that adds this new functionality to your server - a bukkit plugin? Some mod?
@bigscary
That is true. Giving them a low level of trust does mean that they would be able to grief you. But then that falls onto the player. If they are willing to trust someone even with that low level they should know the potential effects of it. And that is where a server owner or some type of staff would have to do their job and inform players of it. But by adding in the prevent right-click not only does it add an additional layer of protection but it would probably effectively become semi-compatible with a majority of mods as well as most actions require a right-click.
You said it is doable and I greatly appreciate the response. So if that is the case I would perhaps like to formally request that as I guess an added feature toggle-able via configs?
EDIT: This just came to me to address the multi trust concern you brought up. I don't know how the backend of the code works but what if it was something similar to how you have container permissions set up. Example:
Then any item ids within that list if within a protected claim and the user does not have rightclick trust the right click event gets canceled? This takes care of the whole issue relating to buttons and levers.
Is there a version of this specifically for Forge? or a version that will work with sponge / pore?
I have some kind of problem with subdivideclaims. One of my server's player said the subdivideclaims resets after every server restart. I made some researching and found there is one "bug" in database:
(Open in another window for the whole picture)
Whenever ANY player creates a subdivideclaim, it creates it with ID -1 and Y-coordinate is approx -190. After that if any player tries to make a subdivideclaim, console gives me this:
(Open in another window for the whole picture)
When I deleted the ID with -1, made the subdivideclaim at y:65, it tried to put it y:-190 and now the problem is:
1. It's trying to save every subdivideclaim with ID -1 2. It makes the subdivide claim to y: -190
GriefPreventionversion: 2015-07-15 12:20:50: [Server thread/INFO]: [GriefPrevention] Enabling GriefPrevention v11.7.4
@bigscary
Before every player could see the last time someone was online by cliking with a stick. I dont want to give everyone the permission to delete others claims ofc. So is it a way? It was really nice to know the last time the player was online and also cool for people that was waiting for the claims to expire.
@HalestormXV
Prevent all right clicks without some level of trust? Sounds doable, but... that means if you give anybody even a very low level of trust (/accesstrust), then they could grief you. If I required high level trust (/trust), then claim owners would be unable to effectively grant lower level trust, which would result in the same - "I want to give access only to buttons and levers, but because of this new rule, I MUST give players /trust and hope for the best, and then they grief me." :\
@CannonFoddr
If you hold shift and right click with a stick, all nearby claims will light up.
@Monty70
Looks green across the board! Hmm... are you possibly running on a very old hard drive? I don't know how to go about getting more information about this, since if your server crashes, you won't be able to capture the timings around the crash. :\
@minecraftbuildr0
Use /acb [permission.node] amount to grant blocks by permission node.
@maclarenss
Sorry, doesn't belong in the base plugin. I have a tentative (no guarantees) plan to build a flags plugin of my own.
@Yodaman598
Too expensive for the CPU (see PC tech's comment), and also in my opinion, walking into a land claim isn't griefing. Iron doors and some smart building will get the job done if you really want to keep folks out (ender pearls won't work).
@dutcholdskool
Yeah sorry, it's always been that way (even for private land claims). The trustlist command only shows explicit permissions for a claim/subdivision, and subdivisions always inherit permissions from the parent claim.
Not sure if this works "as designed" but, when creating an admin claim with /accestrust all the permission is automatically inherited by a subdivision claim. (And not visible as such when doing the /trustlist command)
@Yodaman598
Would require use of PlayerMoveEvent, and I don't think this plugin uses that? If it doesn't, adding this would increase overhead.
Is there any way to ban someone from entering your claim? If not, I think that would be a great addition to the plugin.
Just in case you haven't been checking into the Spigot discussion, there appears to be an issue with the latest spigot build as I detailed here: https://www.spigotmc.org/threads/griefprevention.35615/page-42#post-856435
Update: Appears to have been a PlotSquared issue, strangely...
hi!pls add only 1 flag pvp true/false in privat zone .another plugins flag for GP very old and not working ...((