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 5, 2013Redstone signals transfer from outside the claim into the claim. This allows others to open doors or activate redstone that is on the border of a claim with redstone/buttons/levers. Obviously a player making a claim could just bring the doors or redstone in a block or expand the claim out one block, but this doesn't actually fall into "common sense" because of the land protection assumption. Is there anyway to make redstone signals work like water, blocking it from going into/out of claims?
-
View User Profile
-
Send Message
Posted Dec 5, 2013@Alshain01 They might have been a bit more stringent and critical because Tux is bukkitdev staff, so it's a bit eyebrow raising.
@Stryker76
As with any OSS project those contributing contribute their free time. I think it's fair to say that the majority of folks here don't do programming as their Job. I'm not saying that as a sleight- heck I wasn't doing it as a Job for the majority of my contributions to this project- I'm just saying that when you do it for 8-12 hours a day during the week, Saturday and Sunday are a blissful reprieve. I still like software development but when you do something almost constantly it kinda loses it's appeal. GP's list of known bugs is going down over time, with only one known 'showstopper' that has now been squashed. Hopefully we can resolve the known issues surrounding Spawn Protections this weekend, then try to update the documentation to cover the Block Overrides.
@Alshain01 GP's development builds are only really development builds in name. (And because they aren't on bukkit itself, obviously) Making them available as Betas occasionally would have probably been a good idea once the major changes were made (World configurations and rewriting how claims are loaded), in retrospect. I'm thinking a new Beta every 5 or so development builds. Once all the known bugs are eliminated, leave it for a bit (A time strangely equal to how long it takes to write documentation by not making further code changes) then promote it to a release.
-
View User Profile
-
Send Message
Posted Dec 5, 2013Are These Anti Grief Auto Plugin? Not This Plugin Need To Set To?
-
View User Profile
-
Send Message
Posted Dec 5, 2013@Stryker76
You'd be surprised who would run a dev build despite all the warnings.
Look at mcstats.org, check out Essentials, out of the 67 thousand reporting servers for them, 25% have already upgraded to 1.7 despite EvilSeph's persistent warnings that live servers shouldn't do that.
-
View User Profile
-
Send Message
Posted Dec 4, 2013@BC_Programming
Most, if not all, Software Development processes actually have a point where they decide to stop developing and make a public release based on the feature set developed against. This allows more eyeballs on the release and more bugs fixes as a result, it's pretty simple.
Your scope creep can be summed up with the lack of an official, sable, point in time release, that includes something as simple as support for Horses and Leashes, as introduced in 1.6, yet you just keep doing Dev builds.
If I were not already using some form of Grief Prevention on my server, and were searching for a plugin to do that for me now, I would pass this plugin over, simply because there hasn't been a release since 1.5 (aside from the beta you just released, which you admit that you didn't want to do in the first place)
I believe that most Server Owners, that actually care about the experience their players have, are not interested on running a Dev build, because yeah, it's just a Dev build. Just look at what the bukkit team is saying about their Dev 1.7.2 builds, not recommended for Production servers.
Listen, I completely understand your position, I code my own plugins for my server in my own free time as well. I'm not trying to be an ass here, I'm just saying that this plugin would be better off if focus could be put on an actually release that the majority of Server Owners would run, and then deal with the feedback/bug fixes that come as a result, and then progress from there.
-
View User Profile
-
Send Message
Posted Dec 4, 2013@Tux2
I can't believe they are complaining about GriefPrevention. Multiverse-Core hasn't had a release in over a year and they continue to use their CI. I know it's the rules, but seems a bit lopsided to me, often the BukkitDev team seems to overlook the biggest plugins on BukkitDev when they break the rules. I had an admin withhold approval because of Metrics and not enough documentation for their taste, when Essentials uses it and doesn't even mention it at all on their page.
-
View User Profile
-
Send Message
Posted Dec 4, 2013@Luficer
Looks like a badly administered Host. The Exception is caused when the Connection fails halfway through authentication, I think.
-
View User Profile
-
Send Message
Posted Dec 4, 2013Sorry to bring up something potentially unrelated to a GP error, but it seems my server has been receiving several database errors when saving player data. It is able to read from the database and fetch claims, but it seems to be resetting player data frequently and displaying this error (or similar ones): pastebin.com/ZKZsWRXY
We've rather exhausted ourselves trying to solve this, so was hoping you'd know about what it could be. We're using build #199, but have been getting this since 197 I think. I've tested the builds on my private server and a local database with no errors, so completely lost. Thanks for any help!
-
View User Profile
-
Send Message
Posted Dec 4, 2013@bunnyhop100
Actually it's already checking for null... Do you happen to have a stacktrace?
NVM Found it :D
-
View User Profile
-
Send Message
Posted Dec 4, 2013@bunnyhop100
Oh OK, thanks for clarifying! That should be an easy fix.
-
View User Profile
-
Send Message
Posted Dec 4, 2013@BC_Programming
Haha...sorry for the confusion...it's what happens when I try to make sense late at night. What I'm referring to is the BlockIdsRequiringAccessTrust: or BlockIdsRequiringContainerTrust: sections...nothing to do with banned items.
Toss an ID in there that does exist and bam...plugin breaking NPE. Now I know one might say...hey how about you (Bunny) configure the thing properly and not put in bad IDs...I would normally do that but if I remove a mod (even temporarily) or the mod updates and ninja removes an item that I don't notice then the plugin is dead until fixed.
I was able to sort it out but the average server owner would probably pull their hair out with this occurring and just blame the plugin.
-
View User Profile
-
Send Message
Posted Dec 4, 2013@Stryker76
I feel at least, has suffered from scope creep and an obscure view of how software development is normally done.
How is Software Development "usually done"? What "Scope creep" has occurred?
it's so far behind you are actually chasing bukkit releases and getting no where.
Aside from Bukkit API bugs (Item Frame's not firing events when you remove items from them) the current development build works with the current 1.7 development build, and if we make the next release aimed at 1.6.4's API I don't see it causing any major problems with 1.7.
Technically it probably would have worked fine to pop out beta's from the Dev Build now and then anyway. They are rather stable (the claims disappearing until server restart issue notwithstanding, investigating that now).
@Tux2
It wasn't my idea to issue a "beta" build either
I know, didn't mean to imply otherwise :).
-
View User Profile
-
Send Message
Posted Dec 4, 2013@Tux2
This is really the best thing to do. This project, I feel at least, has suffered from scope creep and an obscure view of how software development is normally done. It hasn't published an official release since 1.5.
I've been running this plugin on my server for 1.5 years, and do not want to update to some Dev build, especially when I read all of the issues in the comments.
Pick the feature set and solidify a release, and then move on from there, because now, it's so far behind you are actually chasing bukkit releases and getting no where.
Otherwise, most here, like myself, are thinking about moving on to a different plugin, which would be sad.
-
View User Profile
-
Send Message
Posted Dec 4, 2013@anfereon
Just FYI: anyone can hop in and help out, they just need to clone the repo and submit a pull request. Just refrain from re-formatting everything! Focus on the bug fixes and we'll take care of formatting and unused/out-of-order imports. If you commit enough changes and your work is high quality we might consider adding you to the git repo.
-
View User Profile
-
Send Message
Posted Dec 4, 2013@BC_Programming
It wasn't my idea to issue a "beta" build either, but we've had pressure from bukkit dev admins to release one as the jenkins is being updated regularly with no updates on the bukkit dev site. I have implemented a feature freeze however to work out any existing bugs and to get it polished up for a proper release. Also, I'll be doing some documentation work as well to bring the pages up to the latest beta build.
-
View User Profile
-
Send Message
Posted Dec 3, 2013@bunnyhop100
What "Banned Mod Item List"? The Only thing I can think of is the ItemUsageRules, but considering those are purposely undocumented and have never been in my test configurations I can only suppose you are referring to something else. Probably the Overrides? That's why they have a default. You can blank out their Material Lists.
-
View User Profile
-
Send Message
Posted Dec 3, 2013@BC_Programming:
Your more recent builds have a pretty nasty NPE in them if the banned mod item lists (either in access or container) do not exist. It basically fails when trying to locate the item. A full stack trace can be provided if needbe but you can recreate it simply by specifying a non-existent block or item id in your server build.
This NPE will cause GP to completely fail and not work.
-
View User Profile
-
Send Message
Posted Dec 3, 2013@anfereon
I can't add Developers/Maintainers, since I'm not an author. That would be up to Tux.
-
View User Profile
-
Send Message
Posted Dec 3, 2013@BC_Programming Just a suggestion. Maintaining this plugin seems a lot of work. Perhaps you could find some new programmers to help you maintain this plugin. Land claiming and protection is a function that almost all minecraft servers need. Therefore, this plugin is essential for some servers thus proper and regular updates are needed. Hope you will find the solutions for all the problems and thank you for all the hard work.
-
View User Profile
-
Send Message
Posted Dec 3, 2013Build #197 will soon be available here as a Beta.
-PVP spawn protection doesn't work. Haven't figured out why that is.
-Random claims disappear if using the MySQL dataStore and issuing a GPReload. They will re-appear when restarting the server. Some users have reported that there are a myriad of other claim issues (ghost claims, claims being shown where they aren't, etc.) Though I've not been able to reproduce them to actually find their cause.
-It requires Java 7. (The plugin itself doesn't, but it is a promoted development build).
-The documentation is still the Dev Build Documentation page, but that is a bit out of date, so there may be a bit of guesswork involved.
-It was not my idea to issue a Beta build. But the powers that be have spoken. I won't be eagerly cleaning up any resulting mess. I'll probably upload every few development builds as a beta now that the uh, "ice has been broken" in that respect.