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 1, 2014@BC_Programming
Under the recent files, 7.8-beta-b213 is said to be for CB 1.7.2-R0.2. I thought that was 1.7. If it's not, that's very misleading on Bukkit's part since it's marked as 1.7.2.
-
View User Profile
-
Send Message
Posted Jan 1, 2014@BC_Programming
That event worked perfectly well. bigscary had it documented on his jdocs site. You already have the maven repo plugin installed http://build.yu8.me:8080/plugin/repository/everything/ its already setup for ProtocolLib.
We have been using GriefPrevenion for almost 2 years, one of the best player self protection plugin. This latest update has caused more hassle than was needed. We had to completely re-configure the configs on a per world basis. There is no warning of this needing to be done on the change log nor in the console. Nor does it state on the 7.8 page that configs do not automatically migrate over which is unexpected as the claims do migrate. I do take note that this is just a beta, but the sheer lack of these changes is extremely unhelpful. Permissions have changed completely, even after reading the 7.8 migration guide I am still none the wiser as to how to allow our staff to delete claims, giving them the permission through pex griefprevention.claims.delete seems to make no difference. There is really no need for such passive aggressive responses. Before this update, I could not mention even one fault with this plugin.
-
View User Profile
-
Send Message
Posted Jan 1, 2014@DigitalStuffMan
there is no 1.7 version so I'm not sure what you could be referring to.
-
View User Profile
-
Send Message
Posted Jan 1, 2014A little bug i found for the beta is when you make a chest claim it doesnt save and people can edit your claim, it only saves when you reload the plugin.
-
View User Profile
-
Send Message
Posted Jan 1, 2014A little bug i found for the beta is when you make a chest claim it doesnt save and people can edit your claim, it only saves when you reload the plugin.
-
View User Profile
-
Send Message
Posted Jan 1, 2014@Dutch_Boy
Make sure they don't have AccessTrust.
-
View User Profile
-
Send Message
Posted Jan 1, 2014Hello, I was just curious if you planned to continue updating the 1.6.4 version of the plugin or if you're only doing 1.7.X now. I'm stuck on 1.6.4 due to having an FTB server. Thanks in advance!
-
View User Profile
-
Send Message
Posted Jan 1, 2014Bug:
But members can still open doors etc.
-
View User Profile
-
Send Message
Posted Dec 31, 2013Has anyone else been having issues with subdivided claims vanishing? It has become a recurring problem for my server. I shall post a ticket.
-
View User Profile
-
Send Message
Posted Dec 31, 2013Any way to let mobs (e.g. zombies hurting villagers) and such (machines if on FTB) hurt villagers & animals? (as a user, not an admin)
-
View User Profile
-
Send Message
Posted Dec 31, 2013@confuser
Please enable a maven repo on your CI server for this plugin. It'll allow making this an easier dependency.
That's not going to happen, for a number of reasons. Unless it's toggling a Jenkins option.
Please update your public API documentation.
Well, at least you are saying please.
No documentation anywhere cites the NewClaimCreated event at all. It's only existed in Development builds. The classes exist in 7.7 but they weren't fired properly. It's purposely undocumented because some of them are likely to be changed.@linusgjersvold
@gchamblee
the 7.8 doc page covers permissions near the bottom.
-
View User Profile
-
Send Message
Posted Dec 31, 2013Hi
I can't interact with villagers when Grief prevention is installed arai
-
View User Profile
-
Send Message
Posted Dec 31, 2013when players type /gphelp they are told they do not have permission to use that command. what node permission should i add to groupmanager for them to be able to access the gp help documentation?
-
View User Profile
-
Send Message
Posted Dec 31, 2013Hello! Is there a permission for creating claims with the shovel now? I am just getting "You do not have permission to create claims" when I try making claims.. Please help me!
-
View User Profile
-
Send Message
Posted Dec 31, 2013Please enable a maven repo on your CI server for this plugin. It'll allow making this an easier dependency.
Please update your public API documentation. I had to delve into the source to see the NewClaimCreated event had been changed into ClaimBeforeCreateEvent and ClaimAfterCreateEvent.
-
View User Profile
-
Send Message
Posted Dec 30, 2013I guess I'll have to wait until you guys add a way to disable horse protections or use /butcher to kill them all :(
Alternatively if someone knows of a plugin that can manage horse ownership that would be great, I've looked at about 10 different horse plugins and none seem to actually do this :/ time to start looking at general animal ones..
-
View User Profile
-
Send Message
Posted Dec 30, 2013@netherfoam
I don't know what you are referring to, to be honest.
@diannetea
Whether it's Minecraft itself or CraftBukkit doesn't matter. the fact is that the API itself defines Horse as deriving from Tameable. Tameable defines an Owner accessor and setter. Other interfaces deriving from Tameable include those for Wolves and Ocelots.
Horse derives from this, and CraftHorse (the class in question) implements this. The Bukkit PR you link specifically says that it cannot implement that interface because that data was not tracked. That has changed since, for the obvious reason that Horse's not implementing Tameable would be rather dumb.
The point is that griefprevention is not managing Horse ownership, and it's using the exact same mechanisms that are exposed to every other plugin.
-
View User Profile
-
Send Message
Posted Dec 30, 2013I actually did some digging, and Horses do not actually store ownership in Minecraft. I do not know if Bukkit changed this.
Per this: https://github.com/Bukkit/Bukkit/pull/895 and this: https://github.com/Bukkit/CraftBukkit/pull/1189
-
View User Profile
-
Send Message
Posted Dec 30, 2013Can I allow certain worlds to allow/deny claim creation? Please PM me answer because I mostly check them! - James
-
View User Profile
-
Send Message
Posted Dec 30, 2013@BC_Programming
Appears that the node didn't copy across properly, this is in config.yml next to InitialBlocks, yes? I've readded it now, but just FYI that it seems to not have copied across properly. Cheers for the info!