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 Oct 31, 2013@BC_Programming I like where you're going with that. But since the lines are optional and not included per default, why not do it like this? More intuitive to me, more flexible:
(of course block breaking section not pasted here would have the same functionality) I don't know about the code side of things but to the user this makes a lot more sense than having an "overrides" and "trashblocks" subsection to learn to understand. It also doesn't hijack the trashblocks functionality for something it wasn't meant for.
-
View User Profile
-
Send Message
Posted Oct 30, 2013Sorry to keep harrassing you about this, but I've recently tried narrowing down what else could be causing the errors I've been having, and I've updated to Bukkit-1.6.4-R2.0 (MC: 1.6.4) (Implementing API version 1.6.4-R2.1-SNAPSHOT), and removed every plugin from my plugins folder aside from GP (Build 188 this time), and let it generate a new data folder, however I'm still getting the same errors regarding explosion and block ignite events. I'll put pastebin the errors below somewhere. Is there a chance that the source for this version is public? Wasn't compiled into the jar like BigScary used to do it XD
If you think it could be something to do with my bukkit.yml or server.properties, I can look into that, but I can't think of what else to rule out. Here's the pastebin of the errors if you need to refer to them again: http://pastebin.com/HH6pnKU0
-
View User Profile
-
Send Message
Posted Oct 30, 2013@Roenie82
The "overrides" feature applies to every single rule. Prevalently it would only really have a use within rules about placing blocks. It's essentially an equivalent to the existing capabilities (ClaimControl), permissions, etc. which control what players will be allowed or denied the action of a Rule. The idea being that BlockPlacement and BlockBreaking nodes might look like this if the rule is used. It would be optional and not appear by default (except, that trashblocks might be integrated into it, and removed as a separate option).
That's an idea of what it might look like. Basically there would be an Overrides node that would contain it's own set of rules. In this case the name doesn't matter at all, since it's not used for anything. When the Rule is processed the block location being investigated can be compared to the material lists of those override rules, and if it applies the rules within that override used instead of the "actual" rules. Obviously such overrides would be a bit pointless in most cases, since very few rules apply directly to block placement. Those that do will work with such overrides- including any rules added later on.
-
View User Profile
-
Send Message
Posted Oct 30, 2013@BC_Programming NoSurvivalBuildingOutsideClaims paired with the trashblocks should do the trick.
Not quite, as that will disable building below sea level too, and breaking both above and below sea level.
The Rules section is much more flexible, allowing me to only disable block placement and only above sea level. (This is my goal for a new 1.7.2 server soon, but like I said, some blocks I'd still like to force allow.) Having TrashBlock Rules override the standard placement rules sounds good to me.
Why do we need NoSurvivalBuildingOutsideClaims when we already have the Rules section? If I wanted that setting's functionality, simply this would achieve the same thing, wouldn't it? :
The as-of-yet not yet actually in the configuration file capability for block-specific overrides you mention sound less flexible than the Rules section + TrashBlocks.
-
View User Profile
-
Send Message
Posted Oct 30, 2013@Roenie82
NoSurvivalBuildingOutsideClaims paired with the trashblocks should do the trick.
Ideally I should probably rename TrashBlocks to something else, since it's sort of being overloaded for these weird things, such as what blocks can be placed and broken outside claims with noSurvivalBuilding outside claims, etc.
I can think of two ways to address that: the first is to make it work how to expected- have TrashBlock Rules override the standard placement rules.
the other is to enable the as-of-yet not yet actually in the configuration file capability for block-specific overrides. It would basically allow one to have a list of materials and actually say "This is always allowed in the wilderness, but never inside claims" for both breaking and placing. I've not been able to give it a proper whirl. except for some basic tests that forced dirt to be allowed to be placed on claims as well as another that would only allow the owner of a claim to place obsidian in it, which I thought was pretty nifty in terms of allowing one to control how things work.
The current trashblocks setting could easily just automatically add that data on the fly. I don't like the idea of replacing one little config option with a half-page of config options that do the same thing, but the power of the options could be useful, so it'll probably end up as "optional" configuration nodes- the "trash blocks" configuration options would be pretty much all that would be needed I think.
Also I didn't reply to the second bug before: That one seems like it was, the shovel was checking the chestclaim perm instead of the permission for the shovel.
-
View User Profile
-
Send Message
Posted Oct 30, 2013I see, my apologies. It's exactly what I need though. (I don't want players to build outside of claims above sea level, but not allowing them to place torches to see at night is too harsh. I'd like them to be able to still place a crafting table, make an axe, chop down a tree. Just not build. I want them to have a chance at exporing and staying alive long enough to find a nice place to claim.)
-
View User Profile
-
Send Message
Posted Oct 30, 2013@Roenie82
That's not a bug. Trash block placement rules do not override placement rules. (or breaking rules, for that matter)
-
View User Profile
-
Send Message
Posted Oct 30, 2013Bug in 185 (still in 186 probably): Using bPermissions: ^griefprevention.claims.chestcreate (=deny it, because you only want everyone to use the shovel) will override the permission: griefprevention.claims.toolcreate ...so you cannot make any claims at all.
-
View User Profile
-
Send Message
Posted Oct 29, 2013I may have found a bug with the trashblocks in build 185.
or
(not sure where to put it, as a newly generated config does not generate a TrashBlocks section)
and
The TrashBlocks section is not deleted anymore in 185 but I can't place any of the TrashBlocks. Tried it with item IDs, same result. (Can't place any blocks at all above sea level, even players in ops.txt)
-
View User Profile
-
Send Message
Posted Oct 29, 2013@Eyeball114
I Specifically mention 7.7 for a reason. I Completely rewrote how claims are loaded in the development build quite some time ago for this exact reason. Now claims are loaded and unloaded with worlds. on MCPC+, for example, Worlds such as the Promise Land or even Mystcraft worlds preserve claims.
The issue was simply that they were being loaded at startup, and all worlds didn't exist at startup- so when it tried to read in the claim, the world didn't exist, so it figured the claim was invalid or the world was removed (or somesuch) and deleted it. Now it tracks world Load and unload events and loads the claims for those worlds then- making sure that the world exists. It also keeps unneeded claims out of memory as well, if a world isn't loaded, claims for that world don't exist.
There are of course some minor issues with that since some parts of the logic almost certainly make the assumption that every claim is loaded, but the important part is that claims are preserved in non-default worlds.
-
View User Profile
-
Send Message
Posted Oct 29, 2013@BC_Programming
That fixed everything thanks!!! Again a very quick response.
-
View User Profile
-
Send Message
Posted Oct 29, 2013@BC_Programming Thanks.
Next! ;) :
This seems to deny even players in ops.txt. How to exempt ops or any other specific player? Does not seem to be possible?
Edit: dev build 185: block accrual amounts now support fractional values ... for example, 50.1 set as the value will add 50 blocks, on average, every hour to a active player, but will also add 10% 'interest' on their remaining claim blocks.
Thank you for applying the feedback! Wondering though, does "remaining claim blocks" mean the amount they have spare in their claimblocks balance, or their spare claimblocks balance + the number of claimblocks tied up in their current land claims? (I would include those.)
-
View User Profile
-
Send Message
Posted Oct 29, 2013I noticed that there was a death trigger in this plugin as indicated by the "DeathMessageCooldownSeconds" line in the config.yml file. Is there a type of hardcore option that will reset the number of claims back to whatever the setting is for "InitialBlocks:" when the player dies? The idea here is to reward players with more blocks to claim as this plugin does, but then revert them back to the beginning if they die so that there previous claim goes unprotected and thus provide a type of optional death penalty.
-
View User Profile
-
Send Message
Posted Oct 29, 2013@BC_Programming
Ok guess Ill look for another plugin to use :/ been using GP for 2 years I was hoping to keep it going.
-
View User Profile
-
Send Message
Posted Oct 29, 2013@Roenie82
TrashBlocks are set in the World Configurations. GriefPrevention.TrashBlocks, it's a list of Material Names. The Mods section is for trying to find blocks to qualify as Trash Blocks within Forge Configuration files.
It looks like it's not being saved anymore though so it get's obliterated when the config is loaded.
Claim Cleanup looks at the entire claim, if I recall.
-
View User Profile
-
Send Message
Posted Oct 29, 2013I Have The Pluggin On My Server And It Was Working Great Last Night When I Installed It But Now This Morning Whenever I Try To Claim It Says "Land Claims Are Disabled Is This World"
Please Help! I Need To Open My Server ASAP!
Thanks
-
View User Profile
-
Send Message
Posted Oct 29, 2013Hey BC,
You said that you recently added the capability to customize the "trash" blocks". How and where do I customize them? The only place I can find is the Mods section in config.yml and I'm not sure what to do with that. I am guessing it involves creating a specific directory and file and putting the block names in there, but that might just add to the default list rather than replace it(?) and I suspect there must be a more direct way to to this. There is no TrashBlocks section in my config.yml like there was in 7.7 and it's not in the world yml either.
This early 7.8 documentation didn't make it clear to me.
Edit: Does ClaimCleanup's MaxInvestmentScore consider the entire volume of the claim or only what's on the world surface? Scenario: someone builds a mob farm underground in his claim but places nothing on the surface, would ClaimCleanup delete his claim?
Let's say that it does clean up his claim, and automatic nature restore is on, would that do anything to remove the mob farm or would it only look at the surface (and do nothing)?
-
View User Profile
-
Send Message
Posted Oct 29, 2013@Eyeball114
In 7.7 you can't. Only the Nether, Overworld, and the End are actually loaded when plugins are, and 7.7 tries to load every single claim in every world at that point in time. Any claim in other worlds are deleted and numerous configuration settings that would involve other worlds don't do anything either.
-
View User Profile
-
Send Message
Posted Oct 28, 2013How can I set the config to allows claiming in all worlds? Including the over world, nether, and, Galcticraft planets. I tried adding the worlds to the config manually but the config reverts on the next restart.
-
View User Profile
-
Send Message
Posted Oct 28, 2013@DarkValaMorgoth
Anybody with Deleteclaims permission can modify non-admin claims at any time also. I believe that perm is given to ops by default. It always had that check but it was always combined with a check for ignoreclaims as well, but somebody requested that be removed... I'll put it back though, since Ops shouldn't have to do anything extra to play normally.
I cannot replicate the permissiontrust issue, assuming that is still present.