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 10, 2013@dpocai
The problem is, it didn't always do so and now that I've "upgraded" to the new version of GP the horses that have been given to other players can no longer be ridden by them, as the "owner" is someone else.
Except the Horses were never given to players. The Owner was always somebody else. GP is not going to be the only plugin that will have this effect. Anything related to tameable mobs will do the same thing.
If a Player rides a horse they do not own, that's stealing. it's prevented. You cannot "give trust" to ride a horse, because trust levels are per-claim. The only way to "fix" that would be to change Griefprevention to not only store all sorts of trust information per-claim, but also per horse which would be pretty dumb, and certainly not trivial. And naturally people would insist as per usual that I've lost the plot.
Fundamentally, I doubt changing GriefPrevention will fix anything for you in the long run. If I add an option to disable everything related to horse protection, than that will just let more and more people "give away" horses that are actually tagged as belonging to them.
This will become a problem as other plugins start to reasonably consider the owner of Tameable Mobs for their logic, just as GriefPrevention does.
The only reasonable alternative I can see is if players can mount horses they don't own if they have the proper trust or a permission, and then when they do the horse is set to belong to them. That does however kinda make the plugin a plugin part horseshop plugin too. It seems more reasonable to find and use a plugin already designed for dealing with tameables, then you can use that plugin to properly assign horses to their new owner. Also that would definitely be more a feature than a fix and new features aren't coming until more bugs get squashed.
@TheOcelot4000
It already works with 1.7.2. It doesn't seem worth it to reference the new Bukkit API when it's incomplete especially since the only changes needed would be for the new wood types for preventing griefed trees.
-
View User Profile
-
Send Message
Posted Dec 10, 2013Hi,
I have a suggestion.
Perhaps you could add a feature by which a server administrator can designate certain people to get an extra X blocks per hour?
This would be a good donation incentive for servers that rely on such provisions.
-
View User Profile
-
Send Message
Posted Dec 10, 2013Can you make it for 1.7.2 ?
-
View User Profile
-
Send Message
Posted Dec 10, 2013My moderators can't use /claimslist <playername> with the latest version, could you tell me the permission for it? I've tried griefprevention.commands.claimslist and griefprevention.claimslist but it doesn't work, please help! :)
-
View User Profile
-
Send Message
Posted Dec 10, 2013@dpocai
I would rather the ability to turn this off entirely. There are a number of players on my server who have horse farms and now they're basically out of luck when wanting to give away/breed horses belonging to someone else.
-
View User Profile
-
Send Message
Posted Dec 10, 2013@Alshain01
Thanks, but Grief Prevention already protects the horses. The problem is, it didn't always do so and now that I've "upgraded" to the new version of GP the horses that have been given to other players can no longer be ridden by them, as the "owner" is someone else. I need a way to /trusthorse or /givehorse or something along those lines for the already existing animals on my server. It needs to be something that works across all claims, not just the one I happen to be standing in, so /containertrust while standing in my claim is not an option.
-
View User Profile
-
Send Message
Posted Dec 10, 2013Is there any multiworld support where you could exclude certain worlds from "grief protection"?
-
View User Profile
-
Send Message
Posted Dec 10, 2013@Eelviny
Noticing features like /ignore and other things creep into the plugin in dev builds...
Those were requested, and reasonably simple to add. They were also requested by the original Author.
Banned Players Don't leave a disconnect notice - Requested. Added.
/SoftMute command for administrators - Requested. Added.
Ignore command for players Requested. Added.
Spamming chat is not griefing
The Original Author and Myself seem to disagree with you there. Note that ALL those features were requested by the Original Author. people can somewhat reasonably say stuff I add might not fit to the original spirit of the plugin, but it's a bit more difficult to try to tell that to the Original Author of the plugin, who essentially defined it to begin with. That means the person making that claim is trying to say they know the plugin and it's original intent better than the original author!
With the AutomaticNewPlayerClaimsRadius set to -1 will this option be disabled like it was in the old config file?
It should, yes. Also, if you have claims disabled Automatic claims should never be created as well, so if you disable Claims entirely you should be good to go for that world.
-
View User Profile
-
Send Message
Posted Dec 10, 2013Is it possible to her per-rank claimblock caps?
-
View User Profile
-
Send Message
Posted Dec 10, 2013Just a bit of feedback: Noticing features like /ignore and other things creep into the plugin in dev builds... Please, please keep to the point of this plugin, and the name of the title. Spamming chat is not griefing, but in the end it's not my plugin. Just hoping you will take my views into consideration though.
-
View User Profile
-
Send Message
Posted Dec 10, 2013Wow. Big update. A lot to read and figure out, but I think I'm getting the hang of it.
I use this plugin in only 3 of my 6 world server, in the config files for each world, I find the option Enabled: true (line 15) If I set this to False, will griefprevention be disabled for this world?
I ask this, Because I do like the spam protection and other functionalities to work in these worlds. But not the actual claiming system itself.
[edit:] I found out not to look in line 15, but in line 782. Here you can enable/disable the claims option per-world. Without affecting other settings. Nice.
But I do have another question. With the AutomaticNewPlayerClaimsRadius set to -1 (line 794) will this option be disabled like it was in the old config file?
-
View User Profile
-
Send Message
Posted Dec 10, 2013Using build #203, seems can break itemframes in unclaimed areas, but not in player or admin claims. Config options all set to Allow.
Just me?
Thanks
-
View User Profile
-
Send Message
Posted Dec 9, 2013It appears we still have issues with explosions destroying slabs and panes inside claims.
-
View User Profile
-
Send Message
Posted Dec 9, 2013@kiracookie
That was fixed in the dev build immediately following the beta release.
The cause was due to some older logic written in the before time, the long long ago. Essentially what happened was Some of the event handling classes kept a reference to the previous dataStore that had closed, so they saw no claims, whereas others had the newer one.
In my testing, the claims all re-appeared after a proper server restart. (rather than using gpreload, or otherwise unloading and reloading the plugin)
-
View User Profile
-
Send Message
Posted Dec 9, 2013Not sure if this issue has been stated before or not, but Grief Prevention's claims seem to "disappear" if the server has been reloaded. Not sure if claims reappear on a restart or not, but i'm certain my admin claimed house did not re-appear.
Running this plugin on a 1.7 craftbukkit server, using this version of Grief Prevention: B: 7.8-beta-b197 for CB 1.6.4-R2.0
-
View User Profile
-
Send Message
Posted Dec 9, 2013@RustyDagger
Build 2946 addresses an itemframe issue, and item frames now appear to be secure.
EDIT: BC is right: "Item Frames are impossible to break at all by any player with any permission in 1.7.2"
-
View User Profile
-
Send Message
Posted Dec 9, 2013BC, an idea. Two actually. Firstly, move the Rules: section to the bottom of the config. This way no one will have to scroll it in order to access the second half of the non-rule setup, and no one will ever complain. Secondly, I scratched the second idea, didnt seem viable.
-
View User Profile
-
Send Message
Posted Dec 9, 2013FireSpreadTarger+Origin are missing from the config docs.
-
View User Profile
-
Send Message
Posted Dec 8, 2013@dpocai
I've been looking for a plugin to do this function. It exists outside of Grief Prevention so it may already exist. So far most of the plugins I've found (Critter, PetShop, AnimalShop) are designed around cows and sheep and chickens, etc. but I was looking for one that dealt just with animals implementing the tameable interface, so if I don't find one soon I may start writing one.
EDIT: This one might work: http://dev.bukkit.org/bukkit-plugins/tamemanagement/?page=2
-
View User Profile
-
Send Message
Posted Dec 8, 2013With #201, when creative rules are enabled, people cant break but can place blocks outside a claim.