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).
Is There A Permission Where You Can Give Different Ranks Different Amount Of Claim Blocks? This Would Be Very Helpful.
Monty70
Hi. Help please The server has stopped responding! Spigot 1.8.7 GriefPrevention 11.7.2 Console: http://hastebin.com/hewoziwuyu.avrasm
Bigscary Likely, your server is just overtaxed and GP got caught holding the hot potato. Please capture timings for about an hour or so during peak time, then share that report with me. /timings on to start, /timings paste at end of hour to get the report. It must be during a time when your server is busy (lots of players online).
Monty70 Timings running 50 minuts
Spigot 1.8.3
8 - 10 players online
http://timings.aikar.co/?url=11860733
[REQUEST]
As a Moderator/Staff on a server - I'm constantly having to assist in resizing claims etc. Especially in built up areas with multiple small claims scattered around
I find it a bit of a pain trying to expand & getting messages like 'cannot expand as it interferes with another claim' - then I have to spend time flying around & hitting with stick trying to find the offending claim 'cos the Netherrack blocks disappear after a short time
Could we have a command added that will allow 'show all claims in local area & keep the markers showing all the time'.. something like '/ToggleClaimMarkers'
Using this will keep the nearby claim markers showing all the time & should (in theory) allow us to figure out the best way to adjust claims as necessary
(As I'm typing this - would it be possible that while the claim markers are showing permanently that when you enter a claim - a message/popup shows the claimants name of that claim you've entered ?)
Anyway - keep up the great ork on this plugin
@bigscary
That makes sense. Alright, how about a method to prevent Right-Clicks? I know GP is in a very mature state so I am not necessarily asking for that feature lol but is there a way that GP may be able to work with another plugin to hook in and prevent right clicks in a claim unless they have the trust access? The main one that comes to mind is Gorea Restrict right off the top of my head.
Update 11.7.4 is here! GriefPrevention recently slipped to #2 on the Spigot site. Please help out by leaving a 5-star review. :) Thanks!
@Monty70
Likely, your server is just overtaxed and GP got caught holding the hot potato. Please capture timings for about an hour or so during peak time, then share that report with me. /timings on to start, /timings paste at end of hour to get the report. It must be during a time when your server is busy (lots of players online).
@HalestormXV
Sorry, I don't think it's fixable on my end. :( The correct solution is probably for TT to fire a "block break" event and then a "block place" event, then check to see if any other plugins cancelled those events before actually making the change to the world. This would make TT work with any anti-grief plugins, not just fix it for grief prevention. Generally if a plugin adds new functionality to the game which has potential for grief, it's up to that plugin's author to add anti-grief code, like the above example - asking other installed plugins if the player has permission to break a block before actually breaking it.
There are infinite possibilities for code other plugins could introduce that would circumvent anti-grief, so I don't try to solve those from my side. Bukkit provides mechanisms plugins can use to ask another plugin's permission before making changes to the world - please ask the TT dev to look into those. :)
Hey there, perhaps I am missing something. But is it possible to restrict the use of items while in a persons claim. On my server we have Thaumic Tinkerer. This adds an item that allows for a player to use an item to "dislocate" a block. So in essence they right click with their item and it picks up the block and they can then move it elsewhere. It totally bypasses claim prevention. Any way to add it so that they cannot right click that item in their inventory while they are in the other person's claim? Or perhaps a companion plugin that will work with GriefPrevention to prevent this from happening.
Hi.
Help please
The server has stopped responding!
Spigot 1.8.7 GriefPrevention 11.7.2 Console: http://hastebin.com/hewoziwuyu.avrasm
@Kenthria
Thanks for the compliment! It would be great if you shared that opinion as a review on the spigot site to help my rating. ;)
@bigscary
Thank you very much. Fantastic feature for a fantastic plugin!
@Kenthria
Yes, there's a "survival requiring claims" mode option. See setup page. No, it will not override world guard - but maybe with this mode chosen for GP, you won't need WG to do anything with that world anyway.
Is it possible to make it so players can ONLY build in their claims, and not outside them? Maybe overriding anti-build plugins such as world guard? Currently people arent able to build in their claims, if the world is anti-build.
Thanks!
Update 11.7.3 is here! GriefPrevention recently slipped to #2 on the Spigot site. Please help out by leaving a 5-star review. :) Thanks!
@Watson01313
Yep, that's an option in the config file.
Is there a way to make a claim expire after "x" amount of time if a player has not logged on for said amount of time?
@PixealCarftOwner
Yes, that's the default setting for pvp worlds.
@GodsDead
Yep, I already have a todo item to give you a custom ban command line for bans.
@AdrianVaughan
No sorry, it's unfortunately a big deal to store additional data - lots of headache involved in automatically updating everyone to a new data format. :\
@GodsDead
Hey about the URLs allowed in allowed ip addresses list - current behavior doesn't block any URLs, or at least shouldn't. Will you please give me an example of a URL which was blocked? Thanks!
A small request, Is there anyway for this plugin to log the date that a claim was placed ? as when some items get stolen ect , it would be nice to see if at that time they were stolen there was a claim down.
Thanks in advance.
Another small request, the Spam Bans: Can get get a simple Log for people that get banned for spam. The ban message does not get set correctly, The ban comment is "banned by operator" Do you also hook directly into the ban mechanism or run the /ban command? Im using bananager which keeps all bans nice neat and tidy, easily manageable, where as I think GP just uses the built in ban directly bypassing this, So when a player says they are banned, I cant look them up quickly to find is they are banned, in-game or via the web UI, there not in the database. Would it be possible to give us the config for the ban commend, this would also mean we could punish people in other ways apart from a ban, so have a config option thats like this:
{reason} would be whether they triggered the spam punishment via Advertising IPs/Website or if they triggered it by sending multiple things over and over. This gives the option to run any command or do whatever you wish with naughty spammers. My prefered method would be letting me use the default /ban {username} reason, this way everything is logged in the banmanager database.
Hello. Cai set PvP off in claims? That PvP off is in claims and out-side claims On?
@MALONN
I already removed that feature - you shouldn't be getting any more islands in the sky. Set sea level to zero for flat worlds, I think. You don't have any water, right? If you do get some water, then set it to what Y level for the lowest blocks your players stand on. You can get it with F3.
@jenks1999
No sorry, there's no per-land-claim pvp toggle. Using the config file, you can set classes of claims to have pvp or not (player, admin, and subclaims of admin claims may all be set separately).
@bratpitt
I'll re-test this for you. BTW, I see what you did there with your name. ;)
@erik1988
The permission is griefprevention.deleteclaims. Check to make sure you have it?
@GodsDead
Yeah, let me adjust that feature again. It's too aggressive in deciding what is an IP address, I think.
Tiny request: Allow URLS in AllowedIpAddresses, I want people to be able to paste URLS to my own website for guides etc.
@jahangir13
@bigscary
okay cool cool thanks for the help :) I didn't know that command even existed. :p