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).
@bigscary
You just solved my problem. I was about to cancel my server subscription until such time as I found a solution to it. I can't thank you enough for the staggeringly fast addition of economy support. You're a miracle worker, and I wish you all the best. I will be switching to your plugin immediately upon it being updated.
My players and I thank you.
1.2 Updates!
Added optional economy integration! Requires Vault AND a Vault-compatible economy plugin. See the Vault page for a list of compatible plugins.
Use /buyclaimblocks to buy, and /sellclaimblocks to sell.
Both the purchase cost and sell value of the blocks may be set independently in the config file. If either one is set to zero, that function will be disabled (for example, you can allow for purchase, but not sale, if you want). If BOTH are zero, which is the default, economy integration is disabled, and Vault is NOT required.
Also adjusted the spam tolerances for fewer false positives (and thus, more spam).
I tested the Economy integration with EconXP. Not that it matters, since I trust the Vault guy's smarts. Probably won't release again tomorrow - need a break. :) Gonna play some board games, or engage in some other low-tech activity.
@burtthaman
Maybe they're doing something more complicated now, like taking a snapshot before the regen, then applying the regen and using the snapshot to "undo" the regen on the areas which are outside your selection. :) Anyway they should update their commentary.
burtthaman is correct. WorldEdit's /regen command is only applied to the selected area.
Btw, you are wrong about world edit. I believe that may be a warning in case something goes wrong they aren't "liable" lol. However I tested multiple scenarios of building and destroying different parts of the land RIGHT NEXT TO each other in different spots even. Every single time I hit regen ONLY the selected cuboid was regenerated leaving all other structures, blocks, destroyed, or built land in tact.
Is there absolutely no way to have an enter/exit message for claims without a database? If so are you 100% against databases? I know you want to keep it simple but a database can be a flat file. It doesn't have to be MySQL. Thus requiring no user setup. All I know is I have 5 other mods using MySQL databases with others using flat files as do most people with legit servers I would assume. So it's a non issue either way?
It would just be really nice to know when you are on someone's claimed property without having to check over and over and over. Also nice for power user created towns and cities etc. And useful for pvp siege etc later on.
@bigscary
Ah, I did not realise this. In this case, it would will definitely be a good feature to add for the reasons you say. I can imagine player's could be a bit annoyed if I accidentally regenerated the hill that had their house in it. :)
@bigscary
The problems I'm having with Residence aren't exactly anything specific about griefing. It's just plain not working anymore. Nothing I try is fixing it, and I'm getting no help from the Residence Dev. So, obviously, I can't go online without protection.
Kinda screwed, frankly.
@Mako_Shark
WorldEdit doesn't allow you to regenerate portions of chunks. It generates the whole chunk or nothing. From the WorldEdit source:
@Command( aliases = { "/regen" }, usage = "", desc = "Regenerates the contents of the selection", help = "Regenerates the contents of the current selection.\n" + "This command might affect things outside the selection,\n" + "if they are within the same chunk.", min = 0, max = 0 )
So GriefPrevention's /restorenature would be better in a sense, because it could warn you if you were about to regenerate part of someone's claim. That's especially valuable if the claim happens to be hidden, for example a house under a hill or in a deep cavern.
@Mako_Shark
Sounds like it needs an adjustment. The challenge is there's no way for me to know a chat command like /global or /local from other types of commands. If I stop monitoring commands altogether, then those commands become a way to spam without getting banned.
Anyway, there are two types of spam - three messages in quick succession (less than three seconds apart, I think, I have to check the code to be sure), or the exact same message or command more than three times in a row, regardless of how fast you send it. The second measure is designed to shut down advertising bots, which often wait several minutes between repeating a message. I'll increase the repetition to a much higher number, and reduce the message speed threshold to 2 seconds to see how that works.
I was wondering how the spam protection decides when a user is spamming and how long they have to wait before posting again after it warns them the second time to avoid getting banned?
I ask because my admin got himself banned several times before I added the permission to make admins exempt (he was using a lot of commands), and then one of my users got banned when he wasn't trying to spam. I also found it very easy to get banned when i was testing it.
@bigscary
I think it is a great idea for a plugin such as this, however this is already possible to do using world edit by selecting an area to regenerate. This is slightly more useful functionality as it allows you to regenerate areas without regenerating the whole chunk.
I still think you should add the function of regenerating chucks though, for servers that do not want to run world edit.
@bigscary
I personally love the idea since i have been using worldguard for this exact purpose!
Hey guys, I'm considering an administrative feature add and would appreciate your opinions on the idea.
The one type of "grief" that GriefPrevention doesn't yet cover is public grief. That's where a griefer does damage to the world where no one has claimed any land, for example by claiming land and building something unsightly, or intentionally disfiguring the landscape with explosives or a shovel or whatnot. These are lightweight griefs that don't really hurt anyone, but it bothers me that GriefPrevention doesn't do anything at all in those cases.
Other anti grief plugins which solve this problem do so by either requiring an administrator to take a snapshot of an important area (WorldGuard), which doesn't work for randomly located griefs like penises on mountaintops. LogBlock tracks every change ever made by any player, which requires a database, and databases introduce their own problems for administrators.
I'm considering adding a /restorenature command which would simply regenerate a chunk. This wouldn't require a database and would be much faster than fixing anything manually even in creative mode.
The only limitations are that it wouldn't always put the terrain back exactly like it was originally, and it couldn't be used when griefs are very close to legitimate players' builds. It would have a safety mechanism to warn the admin if any player has claimed part of the chunk to be regenerated, and an override option to regenerate the chunk anyway.
What do you think?
@bigscary
I see your point. Thanks for working stopping players creating portals into other players claims.
@Mako_Shark
I think that "oops, I'm in a basement" problem is one that shouldn't be fixed. Part of the fun and challenge of the nether is the unpredictability of the portals. Anyone who puts a portal inside their house should, therefore, consider using an iron door to prevent anyone who pops in via the portal from accessing the rest of the house. It's part of the challenge of building a well-designed, secure home in a multiplayer environment.
But I will work to ensure players can't create new portals inside of other players' claims.
@NLmitchieNL
It's not possible to reduce the minimum claim size. The minimum size is in place to prevent griefing by scattering tiny slivers of claim here and there, thereby preventing others from making reasonable land claims.
Administrators can use /adjustbonusclaimblocks to give or take away blocks for any player. Otherwise, players can only get claim blocks by playing on the server (they're awarded on logout, based on play time). I do have a plan to add economy integration, so servers with economies can allow players to "purchase" more claim blocks.
@ValawynV
I'm wondering this myself Val. I play on a dev server that has residence installed though i believe he uses the stable 2.4 build. No issues what so ever with grief other than building dirt towers to look/jump into property I guess. Nothing else can be touched if "configured properly". However that is the main issue with residence. Configuring it properly is for advanced users only and very confusing. One wrong move and grief city lol. It's like Big said here: http://dev.bukkit.org/server-mods/grief-prevention/pages/residence/
Unless you know all grief methods and set the proper flags (about 30 flags to set on or off) then you are still at risk. I love residence and the options it gives me as an admin, however I am planning on using this mod instead because it doesn't matter how great something is if no one can use it.
I do know that the dev of Residence is working on a GUI using spout and trying to rewrite the flags etc for ease of use... but its like you said, the guy never responds to anyone, never updates dev build, never answers tickets, and has too much on his plate imho.
@NLmitchieNL
You need to read the admin section: http://dev.bukkit.org/server-mods/grief-prevention/pages/Administrative-Details/
Look at Public Claims section and Bonus Claim Blocks under Administrative Features heading near bottom. These two things will help you do what you need to do. As an admin you can have unlimited block usage in admin claims mode. No need to adjust starting claim blocks which i assume is what you meant when you said "minimum block amount for a claim" There is also a config variable for that if you are trying to give EVERYONE at start more blocks. Look at Claims.InitialBlocks description near top on admin page.
Any other questions you have that are answered on that page already will not be answered by me... and I hope not by anyone else. Not trying to be rude but you obviously didn't even try to read any of the documentation.
Hello, I like the idea of this whole plugin, i have it installed but , how do i award/credit someone blocks to spend on a claim? And second, how do i change the minimum block amount for a claim? Because on the server, i have a house which is nowhere near 10 x 10 surface. And i need to protect it from griefing.