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 Aug 25, 2013It looks like the reason the block is destroyed is because it would destroy server performance otherwise.
Pistons are exploded and dropped if the blocks they are extending or their piston arm extend into a claim, or if they are pulling a block out of a claim.
The reason they explode is because otherwise the event fires every single tick and quite literally destroys server performance.
They don't explode from simply placing, unless they are powered and this would try to extend in a way that would cause the above to occur.
EDIT: after further testing, this doesn't appear to be the case, so I'm not even sure why it was implemented the way it is.
Probably, this was a bug with an earlier bukkit version. I've changed them to simply cancel the event instead.
-
View User Profile
-
Send Message
Posted Aug 25, 2013@Sparcticus
Hmm. Well that's a dumb feature. Found it in the source- it's when a Piston Extends.
I'll try removing it and seeing if the Block Extension can simply be cancelled. It might be a hack for an earlier version of Bukkit that didn't properly handle that event being cancelled.
@Mushroomkngwasmo
Nothing odd about that. BuildTrust includes ContainerTrust and AccessTrust, and Container Trust includes AccessTrust.
-
View User Profile
-
Send Message
Posted Aug 23, 2013Odd, when my player tries to /trust, /containertrust, or /accesstrust another player, it will only allow one of the permissions. Ex: He enables build trust for her, but it will disable container rust which was already enabled. GP- v7.7 Craftbukkit 1.6.2 R0.1 Beta
-
View User Profile
-
Send Message
Posted Aug 23, 2013@BC_Programming
I was doing some more googling on the piston exploding and came across a form that referenced it was due to gp. They linked the gp video which shows at 5:49 the piston exploding because it was placed just outside of the claim. The video link is http://youtu.be/RWekSeMi1OE?t=5m49s.
so i'm going to assume that my player is a good person and wasn't trying to grief lol... and that he was just trying to set something up that just happened to be outside his claim area.
is it possible that in a future release it could be configured as such that there be defined rules for piston use inside/outside claims?
-
View User Profile
-
Send Message
Posted Aug 23, 2013@Sparcticus
Your issue is not caused by GriefPrevention.
-
View User Profile
-
Send Message
Posted Aug 23, 2013Is there any way for me to downgrade? There's nothing in my server logs... Sorry.. I can give you all my configuration.. You also more and welcome to join me on my ts amd my server and see it for yourself....
-
View User Profile
-
Send Message
Posted Aug 23, 2013first off, i just want to say your plugin is awesome and has been working great on my server!
now, off to the question lol. i'm running gp version 157 with spigot 1081 and quite a few other plugins. one of my players was trying to place a piston outside his claim. he said it exploded and dropped and was able to pick it up. i scoured the overworld world config yml file but didn't see any rule related to a piston.
is there a rule in the configs that can be defined to allow piston placement outside of claims?
-
View User Profile
-
Send Message
Posted Aug 23, 2013@ravenv12
You and one other person have claimed this problem. And few others have (aside from issues that have been fixed according to several tickets).
Thing is, Absolutely nothing anybody tells me is something I can work with. eg. "claims will disappear , and sometimes reappear. You will have to resize claims to fix it" Doesn't give me anything to go on, because in my testing claims do NOT disappear, and I do NOT have to resize them to fix it... and since I know nothing about your specific configuration, nothing about any specifics regarding how you figure claims disappear/reappear, or anything similar; The only thing all the mentions of this have in common is that they give me nothing to work with!
@SuperPyroManiac
With dev you can use GriefPrevention.Rules.WoodenDoors to change the trust level required to use and open Wooden doors. By default it doesn't require permissions in a claim but you can change that using the "ClaimControl" node. For example, for what you want:
-
View User Profile
-
Send Message
Posted Aug 23, 2013Do you think you could add doors to /accesstrust? Lots of users have been requesting it on my server.
-
View User Profile
-
Send Message
Posted Aug 22, 2013Since I have upgraded to the Development builds of Grief Prevention , claims have been glitch out .. is your any way to fix this? claims will disappear , and sometimes reappear. You will have to resize claims to fix it .. is there any way to downgrade 7.7?
-
View User Profile
-
Send Message
Posted Aug 22, 2013@ThisUsernameIsMine
Did you give GriefPrevention.Commands.AdminClaims permission? Each command has it's own permission now :) It looks like the error is from bukkit's perm check rather than GP, and the plugin.yml specifies the GriefPrevention.Commands.AdminClaims perm for that.
@timsavage
I don't like the idea behind this feature because it's practically useless without another plugin, specifically real-estate. Or rather, I Should say I don't like the idea of it being in the base plugin since the feature is pretty much specific to one add-on.
@Chaett
Claims should migrate. If you are using a database I recommend making a backup first.
the GriefPreventionData folder is now just the "GriefPrevention" folder. A migration would normally mean copying GriefPreventionData for your 7.7 configuration to GriefPrevention. Updating the plugin, running the server, stopping the server, and then setting up your configuration. if you are using a database, change the GriefPrevention.datastore node in the generated config.yml to "mysql". now run the server again, and the plugin will generate a "dataconfig.yml" file. Stop the server and edit the file and add in the appropriate substitutions for your mySQL server configuration.
Now you should be able to run and the claims should be successfully loaded. Note that some schema has been tweaked or modified since 7.7 (to my recollection) so I don't think you can go back from this without a db backup.
-
View User Profile
-
Send Message
Posted Aug 22, 2013Hey, I couldn't run a server without this plugin its fantastic, is there a changelog for the development builds so I can catch up with whats been changed and whats been added? Is there a list of problems with the dev version or is it stable enough to bring into a live server?
Also for people wanting custom enter/exit messages for claimed areas, you can use Claimcontrol - http://dev.bukkit.org/bukkit-plugins/claimcontrol/
-
View User Profile
-
Send Message
Posted Aug 22, 2013Feature request: Claim Groups
I would like to be able to create groups for claims, and have individual group limits on the number of claims that can be owned by a player.
I use this plugin extensively, along with the Real Estate plugin, to create towns in my survival world. The problem I've been having is that a few successful players inevitably buy up all available plots in a given town. I'd like to be able to (optionally) assign claims to a group, say 'Town A' and 'Town B', and set individual limits to the number of claims a person can buy in each group, while still allowing unlimited claims in the wilderness (no group). Taking it a step further, I foresee creating zones within one town, for example 'Town A - Residential' and 'Town A - Agricultural', so that I could assign different limits to different types of plots. (These names are just for illustrative purposes; I expect that actual group names would not have spaces, etc.)
I assume some API functions would likely be necessary, so other plugins could check the group membership of a claim, group limit, and the number of claims owned by a player.
Note that I have tried the per player limit in the world config file, but this falls short of my goal of having a per town limit, and no limit outside of towns. It is the stopgap that I'm using now, but players are just using their entire claim allowance in a single town.
Thanks for considering this! Using GP and GP Real Estate has been the best solution for this scenario so far, and this is the only real issue I've run into so far. I have given it a lot of consideration, and had originally thought that having a limit on claims within a WorldGuard region would be the way to implement this, but then this idea struck me. I think it is much more elegant of a solution, and does not require hooking into WorldGuard.
-
View User Profile
-
Send Message
Posted Aug 22, 2013Abandoning claims in creative world with these settings; automaticNatureRestoration to false and AutoRestoreUnclaimedCreativeLand to false is not working, resulting with craters in creative world as the world is flat made out of sandstone. But with those settings, it shouldn't try to restore.
Using 7.7
-
View User Profile
-
Send Message
Posted Aug 22, 2013What are the procedures to upgrade to latest dev from 7.7? Current claims can still be saved? or is it clean slate.
-
View User Profile
-
Send Message
Posted Aug 22, 2013@BC_Programming
Well, i did everything according to your suggestions but non-op players still have no permission:
- http://i.imgur.com/j2r7cXl.png
(using bPermissions 2.10.7 and Vault 1.2.26)
-
View User Profile
-
Send Message
Posted Aug 22, 2013In the dev build how would I disable this plugin on specific worlds?
Also the new documentation link is 403'ed.
-
View User Profile
-
Send Message
Posted Aug 21, 2013@BC_Programming
Would you be able to have a config for each animal to protect only horses for example.
-
View User Profile
-
Send Message
Posted Aug 21, 2013@BC_Programming
/transferclaim is able to transfer claims from admin claims to player claims and player claims to player claims in 7.7, but I never used it to transfer a player claim to an admin claim, so I wouldn't know if that works.
-
View User Profile
-
Send Message
Posted Aug 21, 2013@ThisUsernameIsMine
Yeah the help text hasn't been updated in the commands just yet.
/giveclaim is designed to be a "user-level" command. That is, with GriefPrevention.commands.giveclaim permissions, any player would be able to "give" their owned claim to another player.
/transferclaim is designed mostly for admin use. Ideally, it should allow the transfer of a claim from admin to user and user to admin claim (which if I recall is what it did in 7.7). It's also (supposed) to allow admins to transfer claims between players, too.
@deleted_9935739
IT should be GriefPrevention.Rules.CreatureDamage
It looks like the default is to require Container trust within a claim to damage creatures, as set by GriefPrevention.Rules.CreatureDamage.ClaimControl.