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 Jan 27, 2014@BC_Programming
Please make the first sentence of the 2nd paragraph bold and red. My other admins didn't see that section and I went off on you. My apologies. (They are the ones who were doing the upgrades on my network and installed and configured grief prevention in the first place). Through my ignorance, I didn't look at the previous version to see that, indeed, a lot of those same features were present in earlier versions.
I still say, however, that a lot of these features need to be disabled by default (such as auto-banning players upon join). That one took me by surprise and I didn't appreciate that surprise. I do believe that was not present (after checking) from the version we were using until the new version we upgraded.
Please, for future upgrades, code in a auto-transfer protocol to keep as much of the config as possible and transfer it over to new versions. I realize it's a lot of extra work, but larger networks will appreciate the extra time.
- EpicATrain
-
View User Profile
-
Send Message
Posted Jan 27, 2014Hi, Im getting the following error on startup, pointing to the adjustaccruedclaimblocks recently added.
http://pastebin.com/0E7bqzWq
-
View User Profile
-
Send Message
Posted Jan 26, 2014What's the permission for /ignore? My players don't have permission to use it.
Also, is it possible to add a feature to ignore private messages?
-
View User Profile
-
Send Message
Posted Jan 26, 2014@stgram
You can put it wherever you like. One less-than-clear consideration is that I believe it requires a "full path":
eg. make a file called template.yml in the WorldCfg folder, and change the 'template' setting in config.yml to "./plugins/griefprevention/WorldConfig/template.yml"
If a world's configuration is accessed and there is no file, the template will be loaded and used for the default settings. That world configuration (the one being accessed) will be saved at that point.
-
View User Profile
-
Send Message
Posted Jan 26, 2014Builds 261/263 are causing a mess on my server... See this ticket.
-
View User Profile
-
Send Message
Posted Jan 26, 2014@stgram
Same here! Using exactly same GP version and Spigot #1260
-
View User Profile
-
Send Message
Posted Jan 26, 2014@BC_Programming
I've been getting this error quite regularly. Could not pass event PlayerInteractEvent to GriefPrevention v7.8 #261 http://pastebin.com/dSqjxtez
-
View User Profile
-
Send Message
Posted Jan 26, 2014@BC_Programming
Hello BC, first off I'm glad you figured out the issue with the lowercase files. I know you have mentioned it many many times, but I cannot find any of your comments on the subject, how exactly should I name the world config file that I want to be used as a template for all future worlds, and where to place it?
-
View User Profile
-
Send Message
Posted Jan 25, 2014Thought I'd give those interested a bit of info on what I'm doing :)
I can't reproduce the issue with PlayerData on my laptop which is what I usually use for a test server, since it is running Windows. So I've started a VM. I mentioned this earlier.
I've observed some very screwed up behaviour. And not much seemed to be adding up.
What I was doing for testing was copying the playerData for my player (which was rightly saved as bc_programming), renaming it to BC_Programming changing it, and running the server. The plugin should prefer the capitalized name- in this case it should delete bc_programming, copy BC_Programming to bc_programming, and then use the lowercased name.
However as I tested things just got weird. Everything checked out- it was reporting everything properly. But the data was the default. It was copying the file perfectly fine.
However after about an hour I think I figured it out. In the case where there is a lowercase named file and a file that uses the same case as the player's actual name, GP prefers the latter, and attempts to lower-case it by deleting the lower-case name, copying the cased name over it, and deleting the cased name.
The problem appears to be that the copy is copying the file to the Bukkit folder, and not within the PlayerData folder, so the copy succeeds but goes to the incorrect location and effectively all playerData for that player is deleted.
Now that I know what is (hopefully) the underlying cause of these issues I should be able to fix it, hooray!
@Elithelion
There are two settings for TNT; the one that allows the explosion to occur in the first place, and the one that will be used per-block that is destroyed to determine if that block should in fact be destroyed, which I believe is referred to using "BlockDamageTNTExplosions" in the rules.
-
View User Profile
-
Send Message
Posted Jan 25, 2014I have a similar issue to anfereon. I set tnt enabled within claims yet it won't destroy blocks. It hurts mobs and people but that's it.I've quadruple checked my settings in GP as well as in Essentials itself. Both are set enabled. Any help would be appreciated. Server is 1.7.2 build 2974 with GP 7.8 (not sure which build) and essentials 2.1.2.1 as well as like 36 other plugins - none of which control tnt explosions.
-
View User Profile
-
Send Message
Posted Jan 25, 2014@EpicATrain
This new version is loaded with crapware/bloatware and I can't disable it completely and it comes complete with all the crapware/bloatware installed?
I'm not 100% what you could be referring to. The last folks to mention this sort of thing pointed to features such as spam, eavesdropping, and siege, implying they were somehow "new" features, when they have been in the plugin for some time, even going back a few years and to some of the earlier versions of the plugin made available. based on this:
Now this new version is totally trying to mess up my server by taking over control of areas of my server that others plugins are using that grief prevention has no business being in, such as auto-banning players on first-time join and anti-spam crap and it's totally messed up my PvP on my servers.
It sounds like you fall into that category, since the listed features have been existent in the plugin going back through several versions, at least.
7.8 however cannot and does not use 7.7 configuration files to determine it's defaults (the engineering workload is basically a task of having two completely configuration implementations, which is simply going to cause more problems rather than solve any), so those options that were probably disabled previously (eg. chat stuff, spam banning, etc. would have been re-enabled by default. (default options which, I should add, are effectively the same as 7.7, since those features were enabled by default for those versions as well).
They can be disabled via the appropriate options- griefprevention.spam.enabled should disable spam protections; griefprevention.Siege.Enabled should disable Siege, and so on.
Normally, I'm happy to help folks that have issues with as-of-yet undocumented features, and even those having issues with documented plugin settings. However What appears to have occurred here is a blind upgrade to a new version of a plugin without reading the second paragraph of that plugins main page, followed by raging when that plugin works exactly as described therein and doesn't use the existing 7.7 configs, and then a complete misunderstanding of features that you had disabled previously, as completely new features introduced in that version, even though the listed features go back at least 2 or 3 years. Instead of deciding "golly, maybe more things changed than I thought" and perhaps reading some of the documentation for that version, which, while outdated, most likely still provides the information you need, you decided instead to make over-exaggerated arguments to ignorance whose connection to reality is tenuous at best.
That said, I never do get tired of people blaming me for features that have existed for years before I had anything to do with the project, and asking for "classic" versions of the plugin which will indubitably contain those exact features to which they are so averse. It's somewhat comical, in a way.
That said, it's also worth note that If in fact the settings exposed for enabling and disabling certain features do not work, that's likely a bug. Many of the changes came about due to issues people had with the previous implementation- and some of the old implementation was a bit quirky and strange, or worked in a very specific way, so some of those were revised or changed. As a result however, it does appear that people that depended on the quirky behaviours will have issues.
-
View User Profile
-
Send Message
Posted Jan 25, 2014How do I get the latest version of the "Classic" Grief Prevention plugin? This new version is loaded with crapware/bloatware and I can't disable it completely and it comes complete with all the crapware/bloatware installed?
My network was doing great with the "classic" grief prevention but we needed to update it because it was causing errors. Now this new version is totally trying to mess up my server by taking over control of areas of my server that others plugins are using that grief prevention has no business being in, such as auto-banning players on first-time join and anti-spam crap and it's totally messed up my PvP on my servers.
Sorry but I've been wanting to say that for the longest time. Help?
-
View User Profile
-
Send Message
Posted Jan 25, 2014@Keaft
After talking to my friend about my idea, his idea seems a lot better: "Make an array for an area of maps. Then instead of having to check every claim every time, you would only have check the claims within that area. A sort of Index."
This is how GP does it now already. Tux2 added that in for 7.7, I believe.
All top-level Claims loaded are placed in a hashmap and indexed by their chunk. Searching for a claim at any given location only requires examining and comparing that location against the bounds of the claims that contain that chunk. This increased performance dramatically; instead of searching every single claim it had to search and maybe compare against at most 3, though typically none (in that if there are no claims in that area, GP knows immediately rather than only after checking every single claim).
@Eelviny
I'll look into that again. I couldn't see anything wrong when I was looking at the DB implementations that would handle that when I saw that ticket earlier.
In the meantime however, The PlayerData issues. I can't reproduce them at all, but I'm on a windows-based system, so I'm probably protected from the issues that will occur with multiple-cased files.
In order to give that a good test I'll be using a Linux VM to put it through the proper paces and perhaps figure out where things are going south.
Oh: Also, in the latest build if a player is detected as having negative claim blocks they are awarded enough accrued claim blocks to bring their total to 0. I didn't want to go overboard (again) with that since ideally I'll figure out what's going on on case-sensitive file systems that is causing so many issues.
-
View User Profile
-
Send Message
Posted Jan 25, 2014@Keaft
Pretty sure in 7.8 builds there's already a system like this. It hasn't loaded every claim on the map for a while now, pretty sure about that.
-
View User Profile
-
Send Message
Posted Jan 25, 2014Hey BC_Programming, I know you have a lot of bugs to deal with (Hope I'm making a slight difference, at least with the older ones) but would you be able to do something about this one? I need to update the name of the world for thousands of claims, and I'd really like to be able to switch over to MySQL as I don't feel like manually changing all those files :P Also with the latest 262 build, suddenly things went insane and player's starting claim blocks amount went millions into negatives. I don't think your fix fixed it... In fact, it only started for me after the fix.
-
View User Profile
-
Send Message
Posted Jan 25, 2014Just had a thought. I read through the info of how the increased number of claims can cause the server to bog down. My guess is that it checks the location of the [block ids 0-x] against the claimed areas. The more claims, the more blocks, the more players, would then mean bog down over time. If this is the case I have an idea, if not disregard and you may quite reading now.
After talking to my friend about my idea, his idea seems a lot better: "Make an array for an area of maps. Then instead of having to check every claim every time, you would only have check the claims within that area. A sort of Index."
-
View User Profile
-
Send Message
Posted Jan 25, 2014@Turqmelon
I'm fairly sure ClaimDeletedEvent should be called when a claim is abandoned.
@AuGsReaper
I just wrote that 'config' off the top of my head as an idea what you would need to do. I know it is possible since another user had a similar issue and I was able to make revisions to allow it to work in this fashion.
I missed a colon on specialRules, for example.
@Smac3223
Duplicate claims are STILL being made with the latest dev build thus putting players into the negatives.
Unless I can reproduce it, I cannot fix it except to flail wildly changing random crap hoping some transient issue that may indeed be a stupid user will magically fix itself, which pretty much guarantees a regression. I Can't reproduce this.
Any competent server admin knows not to use the standard /reload command. I didn't have this problem, I was using /gpreload.Please do fix as I've already been forced to reset the entire damn plugin as a result of the bug a few builds back that resulted in data loss.
"I used a development testing build and lost some player data, because I didn't back up any data". There is a reason these are development builds and are not yet uploaded to bukkit.
-
View User Profile
-
Send Message
Posted Jan 25, 2014Is there a way to make tnt destroy blocks in claims in version b213? Config works fine for wilderness, but not for claims. No matter what I do, I just can't make tnt destroy blocks in claims. I hope there is better way than upgrading to newer version, because newer versions actually cause more problems than they solve (I had to run my server twice from backup because of players claim and points loss).
-
View User Profile
-
Send Message
Posted Jan 25, 2014So my server is working perfectly except the claim block issue. When a player joins the server, the default claim blocks is 0. I set everything to 100 claim blocks (blocks that I want to start out with,) but still it doesn't work. I want the claimblocks for all players to be at 100 not 0. I don't want to manually adjustbonusclaimblocks or setclaimblocks. I've also reinstalled GriefPrevention, but the problem still rises when I ask a player how many claim blocks they can claim (the answer: 0.)
Issue: Player starts out with 0 claim blocks. I want players to start out with 100 claim blocks.
Help me!
-
View User Profile
-
Send Message
Posted Jan 24, 2014Hi, every time I restart the server or reload it, the claims disappear and then when right clicked with the wooden stick it says. No one has claimed this block. Any solutions or things I need to make sure I have enabled to make this plugin work so I can restart the server (all I have done is install it through Multicraft). Running latest 7.8 beta for 1.7.2
Cheers.