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 Jun 1, 2013Even with GriefPrevention in place, Lockette or LWC is still needed. What if you want to have permissions for individual containers? GriefPrevention is good at protecting a building at whole, but needs more work for individual containers.
-
View User Profile
-
Send Message
Posted Jun 1, 2013@GodsDead
If GriefPrevention.Claims.PreventButtonsSwitches is not set, then other people can use beds in other peoples claims.
For block breaking, they only appear to break client side. temporarily. Not sure how t his would give access to a chest.
@rsod
What configuration are you thinking? inPvPCombat relies on the PvP TimeStamp which from what I can tell won't be set if the configuration disallows PvP.
-
View User Profile
-
Send Message
Posted Jun 1, 2013@GodsDead
This is block lag on the client end, although users shouldn't be able to sleep in another person's bed in GP. If that's possible then we need to check on if the event has changed.
-
View User Profile
-
Send Message
Posted Jun 1, 2013Hey, don't you feeling like you should add checking config file option to that piece of code?
-
View User Profile
-
Send Message
Posted Jun 1, 2013Hey! Found another problem, Users can temporary break block gaining access to whatever inside chests etc, which is annoying, but whats worse is that they can quickly select a bed and make that their home, kill themselfs then their inside your house!
-
View User Profile
-
Send Message
Posted Jun 1, 2013@ZTSoter
You should be able to use Messages.yml to customize/translate most of the messages the plugin emits.
-
View User Profile
-
Send Message
Posted Jun 1, 2013Hi,I'm Taiwanese.May I translated your plugins into Chinese?
-
View User Profile
-
Send Message
Posted Jun 1, 2013@digimbyte
i'm cautious as its possible with a person who has enough blocks can encase another persons claim with their own claims and build walls around it, so maybe set a min distance between claims if a person doesn't have 'trust' with that claim.
I messed around with ways to address this. My conclusion is that it is impossible. For example, imagine a person has a large claim. So another player creates some small claims right next to it, preventing it from expanding. If we add a minimum limit, those smaller claims will be made farther away- but they will have the same effect. The protection would work both ways; Resizing would have to take account of it, but no way to differentiate "bad" and "good" claims means that the player with the 'trapped' claim wouldn't be able to resize either.
One might think you could just make it so the larger claim "is better" such that it can be resized, but that still has the problem that it can only be expanded by the minimum blocks, and also, a player could simply make a giant claim next to somebody else. Essentially all the avenues for that issue simply made it easier for people to cause problems for others, rather than harder.
When you give WorldEdit or VoxelSniper type permissions to a player, you basically let them do whatever they want. VoxelSniper has it's own set of permissions and it does not check for claims, nor would I expect it to.
-
View User Profile
-
Send Message
Posted Jun 1, 2013I Love the plugin, really GREAT and I'd like to implement it further or get more from it
but i'm running into an issue with VoxelSniper and this plugin
but first i'd like to address a potential problem but is it possible to encase a claim, inside more claims?
i'm cautious as its possible with a person who has enough blocks can encase another persons claim with their own claims and build walls around it, so maybe set a min distance between claims if a person doesn't have 'trust' with that claim.
anyway, the issue is that i want to control VoxelSniper on my server i've been using Voxel as an Admin for a while and would like to share the 'lite' version on a creative server map for them to play with.
the problem I'm having is that voxel ignores claimed area's, causing blocks in that area to change despite the person not having the correct permissions, i would send a message to VS if the issue is more likely on their end, but i'd like to clarify here first, but there needs to be a way to enable/disable voxel changes inside/outside claimed area's if its enabled on that world
-
View User Profile
-
Send Message
Posted May 31, 2013@keytastic
I'll probably go over some of the commands and see if some can be made more "console-friendly".
-
View User Profile
-
Send Message
Posted May 31, 2013@BC_Programming
Oh oh ok! That is good to know. I hope I didn't come off as rude, I just was wondering if this was a "let's change this feature" or just a bug. I use it on my server as part of the donator package and enjin can't automatically issue it since it does it from the console.
Thanks for your hard work!
-
View User Profile
-
Send Message
Posted May 31, 2013@o0AzzA0o
I didn't remove buyclaimblocks.
-
View User Profile
-
Send Message
Posted May 31, 2013@BC_Programming you removed the option to allow people to buy claim blocks ? man people have no method on my setup to get claimblocks other then to buy them this is whole purpose of economy driven server. Is there any plans to re instate this feature ?
-
View User Profile
-
Send Message
Posted May 31, 2013@Alshain01
Ahh! Thanks, That ought to do the trick.
-
View User Profile
-
Send Message
Posted May 31, 2013Hey BC,
With regards to sphbecker's request, the Item class has an isOnGround() method. So the PlayerPickupItemEvent.getItem().isOnGround() should help you out.
-
View User Profile
-
Send Message
Posted May 31, 2013@Nuinethir
The config.yml should have two settings:
GriefPrevention.FireSpreads
GriefPrevention.FireDestroys
These should control whether Fire spreads and Destroys in the wilderness :)
@DQone
I can't find anything in the source that would explain this. Any specific messages or other information you can provide on the issue would be helpful :)
@sphbecker
There isn't a way to differentiate between items that are picked up from the ground and items that are given through a plugin. At least, that is my current assumption, since the only code dealing with preventing item pickup is the onItemPickupEvent, which unfortunately doesn't appear to expose any simple way to find out how the item was picked up. :( It would probably be possible to find out if it was fired by another plugin, by looking at the internal call stack, but that's prone to problems and will almost certainly just cause problems in the future. Hopefully a future version of Bukkit changes the event to have something like a "PickupCause" member so we can use that.
As a workaround, It would be possible to change the plugin/configuration logic to allow the pickup functionality to be disabled, and only rely on a timer. Of course during that time the Immune player wouldn't be able to hurt anybody else, either, but they would be able to pickup items. This opens a whole other can of worms whereby they can use their immunity to steal another players loot before the timer runs out and nobody can do anything about it, which is almost certainly why the item pickup prevention was added. I'll do a bit of research and see if there is a way to determine whether the event was fired naturally (through a real item pickup) or from a plugin giving the item to the player directly though.
-
View User Profile
-
Send Message
Posted May 31, 2013I tried to add the StarterKit plugin to my server and found that Grief Prevention blocks it from working correctly. The issue is with the 15 sec item pickup cooldown after spawning, it apparently prevents StarterKit from giving the new player the kit. Disabling spawn protection allows StarterKit to function correctly.
Would it be possible to detect the difference between picking up items from the world and items given via a plugin or admin command? If so, then allowing those items would fix this problem.
You then add a new problem of how to protect new players who are administratively given items instantly on login. Maybe they have 2 minutes of PvP immunity after their first spawn?
-
View User Profile
-
Send Message
Posted May 31, 2013It seems that I am limited in the number of blocks I can claim when in admin claim mode. Is this correct? How can I increase this?
-
View User Profile
-
Send Message
Posted May 31, 2013I am still unsure about the other features of this plugin but wanted to ask about fire spread. I have a customized Tekkit Lite 0.6.5 server running with BukkitForge (mainly for WorldEdit and WorldGuard). All I want to do is prevent fire spread.
However, WorldGuard doesn't prevent fires at all running on BukkitForge. I tried setting the doFireTick to false, but that just leaves random fires burning from lightning strikes and rain won't put them out. Also, I have already lost most of a jungle biome on our map due to a volcano lava flow.
I would appreciate some feedback from anyone that runs a similar setup and has experience with this plugin. Thanks!
-
View User Profile
-
Send Message
Posted May 30, 2013@Jemrada
If you deny the GriefPrevention.Claims Permission, you should be able to prevent anybody from claiming. You can also set the accruedBlocks amount to 0 and initial blocks to 0, and nobody will ever have enough claim blocks to make a claim.