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 18, 2013@BryanChung
You'll have to rephrase that without the triple negative.
-
View User Profile
-
Send Message
Posted Jun 18, 2013Is it possible to NOT allow players to not place lava and water if they are not within their claim area?
-
View User Profile
-
Send Message
Posted Jun 18, 2013@hellishinc
It only attempts detection at first startup, and auto-populates the config data with what it finds. The regular Expression can be changed and I welcome suggestions. Most of the current Regular Expressions don't match anythng in bibliocraft's config. (ArmorStand,GenericShelf,Bookcase,Rack,Label,etc). So many of those won't be found. Some forge mods don't put their block ids in their config files very identifiably, The Ender Chests mod is one such case. If you can give me some specifics on what was and was not found I could see what I could add for the default regular expression pattern to match them. (Bibliocraft stuff doesn't match, for one). The current rules takes the elements it finds in the block{ section of the config file, inserts spaces before each capital letter and checks if that has a match for the regular expression pattern. If it does that name get's used as the description. for the cfg entry, but that's it (the description isn't used for anything else).
Admins can add container IDs by right-clicking on a container while holding a chainmail helmet.
-
View User Profile
-
Send Message
Posted Jun 18, 2013Is there anyway you could explain what and how to use the mods: contrainers/access/trash lines in config.yml?
While the auto detection of mod items is great for the "noob" server admin I think it may cause a bit more false bug reports than help in the long run. The reason I mention this is because it only detected 24 of 75 IDs.
The "old" format for items was "- 2255:*:Bibliocraft" now (at least for the auto configured) it's " - '2152:*:ward Chest ' " Are both accepted?
-
View User Profile
-
Send Message
Posted Jun 17, 2013@fungreenfox
Yes, each World config can be set to disable claims in that world. It's the equivalent of the older "claimsenabledworlds" listing. in 7.7 and previous, but placed in each world's config.
@sh474
Pretty much what Alshain said. That debugging output was added while experiment and adding support for modded blocks to figure out what passed in as well as testing container and other permission settings that weren't working in previous builds. They are mostly hard-coded println() calls so there is no "option" to remove them as it is. if there is debug output in release (or probably beta) releases of the plugin it will be configurable.
-
View User Profile
-
Send Message
Posted Jun 17, 2013@sh474
That's part of the life of a alpha tester. Debug messages are put in to help developers track down problems. They are usually turned off internally before release. Simply put, if you want to use a Jenkins build, you gotta live with it.
-
View User Profile
-
Send Message
Posted Jun 17, 2013I'm getting TONS of console spam with build #89. It seems like every click for every player is being logged. How do I turn it off?
-
View User Profile
-
Send Message
Posted Jun 17, 2013@BC_Programming
I have specific worlds not allowing GP, so i can just tell the config to ignore a world too, i guess
-
View User Profile
-
Send Message
Posted Jun 17, 2013Hey I have a question. I've noticed as the server owner I cannot be hurt via PvP in any of my player's land claims. I see where I can disable all pvp in claims (but I don't want to do that). I'd like to be able to only be hurt in my claims, just like everyone else.
Thanks!
-
View User Profile
-
Send Message
Posted Jun 17, 2013@fungreenfox
configs were changed quite a while ago to be very much more world-oriented.
GriefPrevention.claims.InvestigationTool and GriefPrevention.claims.ModificationTool respectively in the world configuration. They are world based because I couldn't think of a really good reason not to make them world-based. World configurations are generated only when GP receives an event involving that world, which often takes a few moments and sometimes requires a player to connect before they are generated, so the standard run-server, stop server might be too quick for any to be generated for editing.
Once one is generated you can edit it and rename or copy it to _template.cfg, and it will be used as the 'template' on which new world configurations will be created. You can change the template file in the 'main' config.yml, through GriefPrevention.WorldConfig.TemplateFile.
-
View User Profile
-
Send Message
Posted Jun 17, 2013@BC_Programming
Build 89 does not include same options in the config. I cant set the wand tool, no option for this and that..
-
View User Profile
-
Send Message
Posted Jun 16, 2013Build #89 is now available from the usual place:
http://build.yu8.me:8080/job/GriefPrevention/
Same guff as usual, use at your own risk, etc. I wasn't able to test everything, so it's possible something is broken as a side-effect of my low-level changes to how claims are managed. I changed th "ContainerTheft" config default setting and I changed it's name as well, to "Containers". Defaults to outside of claims and inside claims with container trust. Added more options and fixes for the Forge Mod search information; it now also saves the results to the template file, so new worlds should inherit that setting even across sessions. I also added a new "Administration" tool, which defaults to a Chain helmet for no good reason. The idea is to make it easier to "edit" the config. right-clicking on a block will add that block as a container ID when you have the permission to do so to the current world configuration. In order for the change to take full effect, you will need to issue a /gpreload (which erroneously returns false so it shows usage, but it does get executed). In my experimenting I was able to seamlessly add the Ender Chest from the ChickenBones Ender Chests mod as well as some stuff from applied energistics.
I was able to go through a mystcraft book, make a claim in the mystcraft world, go back, make a claim in the overworld, go to the Promised Land (Biomes o' Plenty), make a claim there, make another mystcraft book, make a claim in that world, use a linking book to go to the first mystcraft world, that I created, where the original claim was intact, even though the mod had unloaded and then re-loaded that world. Previously GP had, as many are no doubt aware, a lot of issues as a result of unexpected side effects of how it manages some of it's internal data and how it expected that data to remain consistent. The biggest issue was that GP really really wanted to load everything at startup- but you cannot do that since MystCraft and often dimensions like the twilight do not load until a delay has occured. The issue is that the way it was meant those worlds could never have claims- and when it found claims it would get confused and delete them. Now it loads and unloads claims as worlds are loaded and unloaded, which may have it's own side-effects I've not seen.
-
View User Profile
-
Send Message
Posted Jun 16, 2013@BC_Programming
That is awesome! Can't wait to try these new features out.
In regards to the "theft" of containers, I tried that and had no luck back in build 82. I'll be sure to try that again.
-
View User Profile
-
Send Message
Posted Jun 16, 2013@BC_Programming
Glad that was changed! Hopefully it'll work now as it did use hasPlayedBefore in the past.
-
View User Profile
-
Send Message
Posted Jun 16, 2013GP doesn't use the hasPlayedBefore entry to determine if a player played before, instead it uses it's own PlayerData. This could be the result of a change to fix the issue you saw. (I dunno).
May as well share what I managed to do in the meantime. MystCraft support. Remember all those comments 'blah blah we'd have to refactor everything blah blah too hard blah not worth it". Took me 30 minutes and it seems to be working OK. I moved throughout several mystcraft dimensions, went ot the nether, went to the Extra Biomes Promised Land, went to the Twilight; made claims all over the place, went around and they all stuck around; the worlds unloaded and loaded and the claims went with them.
I accomplished this by actually changing how claims are loaded. They are no longer loaded all at once, and instead are loaded on the fly when the worlds they are in are loaded. This makes sure that the World is valid when they load, otherwise GP would discard them as invalid. There are likely some caveats and I have only been able to test the changes to the "flatfile" datastore, but if it works out this means that GP will support multiple worlds MUCH better than it used to.
Sadly I figure this pushes back the next release of beta or release, because I changed some of the very core logic of GP. I haven't observed any major problems so far, so hopefully this will be in the next Dev build. I hope to actually test it on a plain Bukkit server as well to make sure it still works there too.
-
View User Profile
-
Send Message
Posted Jun 16, 2013@BC_Programming
It's been a while since I last heard about the bug's status. Basically the way GP's smart ban works is this:
1. You ban someone
2. GP, with smart ban enabled, will now ban all accounts from the same IP as the banned player if and only if these other accounts have never been on the server before
3. Players from the same IP that have played before (i.e. legitimate players) will be unaffected.
Basically there was a bug in the Bukkit code that didn't report correctly whether or not a player had played on the server before, so turning on smart ban essentially turned /ban into /ipban.
-
View User Profile
-
Send Message
Posted Jun 16, 2013@LeeTheENTP
I don't even know what you are talking about. What was wrong with it? what wasn't working? etc... how was it a bukkit bug? How long ago was it? and so on...
-
View User Profile
-
Send Message
Posted Jun 16, 2013Has the Bukkit bug preventing smart ban from working correctly been fixed yet? Me and a couple of other server owners would like to know.
You know, the one that IP bans alt accounts (accounts from the same IP of a banned player that have not previously joined the server).
-
View User Profile
-
Send Message
Posted Jun 16, 2013Im using version 7.6.2 on a feed the beast server and it keeps kicking people for "playerloggedout.spam" after they send 3 messages, is this a bug or do I need to change something in the config?
-
View User Profile
-
Send Message
Posted Jun 16, 2013@fungreenfox
Sounds good.
Bit of an update fwiw.
I managed to fix the container issue. It might be possible to fix it through the config in the currently available dev build by changing the "ContainerTheft" configuration to "Allow" it inside of claims. (it should still block those without perms). I've renamed that option to the more appropriate "Containers" setting name since it controls all containers.
I fixed the issues around mod support from my refactoring. It now is able to find most Container Object IDs automatically. the Option to "scan" defaults to on, and sets itself to off. This means at "first start" the plugin will scan forge mod configs for certain patterns that identify container blocks. This doesn't work 100% for some mods; I found it worked reasonably for most mods, but some mods don't use unique names for their block ID.
To address that more easily, I've added a new administrative item (it's configurable, like the shovel). it's current purpose is to simply add the block that is clicked to the configuration It's still heavily WIP but hopefully that will make it a lot easier to configure. "Admin this block doesn't work" can be addressed by the admin Teleporting and simply clicking on the block with the admin tool- bam, get's added to the cfg and everything is hunky dory, with no need to restart the server, either. Very useful. (naturally it requires a perm).
However, I also discovered (or rather rediscovered) the reported issues surrounding MystCraft, and they simply confuse the heck out of me. I can go to a mystcraft world, make a claim, leave, and come back; claimslist still lists the claim in the same place, but nothing seems to catch it. I suspect it's related to unloading and loading of the world by Mystcraft, such that the claim becomes "disassociated" with the world. I want to try to get that working before pushing the next dev build, which if all goes well could hopefully be considered a release candidate as I finalize the docs for the new features and config.