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 Aug 24, 2012I was wondering if you would add borders to claimed land, the reason being is that currently on tekkit servers when anyone places a quarry on the tile next to someones claim it will start to destroy it.
With a border of 10 tiles of protected neutral land this would counteract pretty much most avoidable grief.
-
View User Profile
-
Send Message
Posted Aug 23, 20126.2 Updates!
IMPORTANT CHANGES PLEASE READ
Other Changes
@tentonaxe
It's because of TNT cannons. I can never be certain that TNT inside a claim was actually placed there by the owner, because TNT physics an push TNT into a claim from outside.
-
View User Profile
-
Send Message
Posted Aug 23, 2012@bigscary
Understandable, thanks. For now we just disabled the sky tree protection globally. Also, is there a reason behind not allowing the owner of a claim to use tnt in their own claim underground? technical difficulty? or is it because you wouldn't really be able to 100% prevent someone else from setting it off by setting triggers for the owner to hit.
-
View User Profile
-
Send Message
Posted Aug 23, 2012@Keaft
Yep.
@HexaDroid
No, it won't. But it will help you clean then up - basically a single right click will wipe the whole tower.
@SweetMopy
Updating will not destroy any data.
@HCprofessionals
Nope. See "to don't" list above.
@HunterWolf105
Sorry, I really don't know what that could be. It must be another plugin I'm not familiar with.
@HCprofessionals
What do you mean by server reboot? Claims themselves are saved directly to disk as soon as they're created, so you won't lose them unless you go delete the data files. As for stuff built isnide claims, if your server crashes, I guess it's possible that you would see a rollback. But I think by default, Minecraft saves chunks on a regular basis.
@gusient
Check your config.yml and make sure that none of your survival worlds are listed under "creative rules worlds". The requirement to claim before building is only intended for creative mode players, who don't need to gather resources.
@DrFusion
The abbreviation command for subdivideclaims is /sc.
@tentonaxe
It's supposed to protect your whole server, even when you take away land claims in certain areas. I'll try to remember to only restrict building trees in the sky in claims enabled worlds, but I don't want to enable TNT and creeper explosions just because players can't make land claims.
@aroeira
This is by design. Tekkit doesn't tell Bukkit who owns the machines, so if I let the machines dig in claimed land, then a griefer could, for example, use a quarry machine to delete another player's claimed build. :(
The machines will work outside of claims. So for example with a quarry, you can have the quarry and engines inside your claim on the edge, facing outward. That way nobody can steal those blocks, but the quarry will actually be making changes outside of the claim, where it's allowed to do so.
Unfortunately, there's no fixing this outside of either updating Tekkit to talk to Bukkit, or updating Bukkit to know about Tekkit. I'm not the author of either of those.
-
View User Profile
-
Send Message
Posted Aug 23, 2012On my server tekkit, some blocks(machines) that digs holes, have no effect on protected lands. Do you know how can I fix it ?
-
View User Profile
-
Send Message
Posted Aug 23, 2012Is it possible to make grief prevention not affect worlds it isn't enabled in? i have it disabled in my skyblock world but it won't let players plant trees on 1 thick dirt blocks, and explosions aren't damaging the surface in the miningworld where it is also disabled.
-
View User Profile
-
Send Message
Posted Aug 23, 2012@bigscary
So there's a shorter command for subdivideclaims -.- I run several towns (and im too lazy to use towny) and i sold them the town,but now i needa get them to reclaim the town so they can subdivide, and now they gotta subdivide every plot, well thanks for the responce
-
View User Profile
-
Send Message
Posted Aug 23, 2012@HCprofessionals
That's a bug with your server, or other plugins. Check for map corruption or if another plugin is stopping the server from saving.
-
View User Profile
-
Send Message
Posted Aug 23, 2012This is an excellent plugin, I love it, but there's something that don`t like to the players of my server and that is that they can`t get resources. They Need to claim an area first. how i can configure it,for they can gather resources. excuse my if i wrote something wrong
-
View User Profile
-
Send Message
Posted Aug 23, 2012Also, I had to do a server reboot and everyone who built lost everything, even inside claims....
-
View User Profile
-
Send Message
Posted Aug 23, 2012I'm getting a bug on my server where if someone enters a command it does the usual "Our system has detected unusual bot activity." I'm using ServerSigns, if that matters.
-
View User Profile
-
Send Message
Posted Aug 23, 2012Is it possible to add a notice or warning when entering someone's claim?
-
View User Profile
-
Send Message
Posted Aug 23, 2012how do I update this plugin w/out deleting all the claims? Stupid question maybe, but i'd still like to make sure :)
-
View User Profile
-
Send Message
Posted Aug 23, 2012I wonder is this the plugin that stops my players from building 1x1 towers? On a survival server players use this often to get up their builds and its really annoying. If so, is there a way to toggle this check off?
-
View User Profile
-
Send Message
Posted Aug 23, 2012Does the idle claim deletion award back the claim blocks?
-
View User Profile
-
Send Message
Posted Aug 23, 2012Tonight's version will include a fix for fire grief (FINALLY), an option to allow creative mode players to shrink or abandon their claims (WOOHOO), even better restore nature results, and an update to make administrative claims permissions less confusing for new users, among other things.
@jbanto
I'll get this into the next version, later today.
@DrFusion
That's not something I really want to do. Unfortunately it will be difficult to accomplish (from a development perspective). Sorry about that. I will keep it in mind, though, and if I see a way to do it quickly without risking a lot of new bugs, I will do it. I think it should be very rare overall (although I understand your case is an exception). In my experience running a popular public server for months, players only very rarely ever use /sc, and you're the first who's told me he'd like to delegate that permission.
@RemyPas
Then /op yourself, that's the easiest way. Or you can give yourself the griefprevention.deleteclaims permission.
@Overload1525
Use /ignoreclaims. It's a toggle so that ops don't modify player builds without realizing it.
@HCprofessionals
So disable it. :) You have that option in McMMO.
@Peregrin5
Already have it. /accesstrust public. I haven't done /accesstrust all because of the potential for confusion - /untrust all untrusts EVERYONE, not just the players who you haven't explicitly trusted, while /untrust public untrusts only the general public (and not those you have explicitly trusted). So public means "all strangers" and all means "seriously everyone".
@epicrandomness2
You'll have to visit the Vault bukkit dev page to see if a specific economy is supported by Vault. Also as described in the administrative details page here, you do have to update your config.yml to allow playres to buy and sell blocks (you have to specify the cost per block). Check your log file during boot to see if you can see any error messages which will help you solve your problem.
@SweetMopy
See admin details page.
@Ryltar
/containertrust public. See above response, and also see the description above where this is mentioned.
@mathiash1998
I'm glad you solved your problem. The trouble with YAML is that when you have any error, it reverts back to defaults and destroys all your edits. I'm actually going to do better than this - a future version will have tekkit IDs by default.
-
View User Profile
-
Send Message
Posted Aug 23, 2012I solved my problem! And for all you Tekkit guys, here is a working config file: http://pastebin.com/ixKMeAPH
Bigscary... Please add this to the main text, for all of the Tekkit users :)
-
View User Profile
-
Send Message
Posted Aug 23, 2012I have a problem with mod support. Every time I insert the IDs for Tekkit and start the server it goes back to normal...
Here is how I insert it:
I have also tried it this way:
How am I supposed to insert the IDs?
Thanks!
-
View User Profile
-
Send Message
Posted Aug 23, 2012@SweetMopy
They are here: http://bit.ly/OatTJp They have the command, a description and the node.
From, Drew
-
View User Profile
-
Send Message
Posted Aug 23, 2012@Peregrin5
I second this. ContainerTrust All would be useful as well for places like Admin claimed spawns or towns.