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 Jun 25, 2012@typhoonwes79
Max claim depth is supposed to be a minimum Y value. If you set it at 255, I'd think you would not have any claims working very well. If your intention is to have claims able to go all the way to bedrock, set it to zero and tell me if this solves your problem.
Is 2222 a dev build? If so, that could also be the problem. Only RB's are supported.
@Kane_Hart
GP is certainly more comprehensive than precious stones. In my opinion, GP is also much easier for players and more efficient for the land claiming, and also prevents grief by overtopping, which if I remember, PS does not (claims dont go to the sky). I'm not making any effort to explicitly support mods. This plugin is built on Bukkit, so whether it supports your mod or not will depend on how well your mod integrates with bukkit. I suspect custom blocks that respond to a right click would be problematic.
@sillyrosster
Sorry rooster, I haven't figured it out, yet. Trying to make it reproduce on my test server but not having much luck. Is your config all default? If not, please copy/paste it to me in a private message.
@claycod4
My only guess is that buying claim blocks might be disabled. I'd think you would get an error message explaining that, though. Can't say for sure without knowing the details of how the server is configured.
-
View User Profile
-
Send Message
Posted Jun 25, 2012I'm having a problem with this plugin. On this other server I play on it's fine when i try to buy claim blocks. The server I'm an admin on, one greif prevention command doesn't work. Heck, I don't know it could be the owner making a mistake somewhere in the plugin download, but for everyone on the server and I the /buyclaimblocks command doesn't work. When I attempt the command (/buyclaimblocks 1000) it doesn't say anything in chat like it normally would. I can still claim land, though because of the basic amount of blocks you start out with, but not very much land at all. PLEASE HELP!!
-
View User Profile
-
Send Message
Posted Jun 25, 2012@bigscary
Any chance you have looked over my issue? It is really really annoying and we want to be able to play pvp fairly.
-
View User Profile
-
Send Message
Posted Jun 25, 2012I had tried this plugin out a while ago If I recalled I reported a bug or 2 I forgot my issue haha. But we never went and created a grey member server and the idea got scrapped. I been recently on a modded server using a nice protection system called preciousstones http://dev.bukkit.org/server-mods/preciousstones (Don't bother guys the plugin author is sort of mia now and not fixing bugs)
Anyways I had made a video on it and I was wondering if your mod is as easy or possible to be easier for my members to replace this mod.
My Video: http://www.youtube.com/watch?v=DXEKuXExaVM
Some the feature I am looking for and I will list all them even though I saw a couple these listed were the following:
- prevent explosions - prevent block breaking - prevent interacting with certain blocks (modded servers have a lot of interfaces) - prevent having your base being able to be at a certain level (prevent people covering up mining/subway routes) - dynmap - friends - sub plots
and yes like I said I see you have a couple these maybe not all of them. Another thing is when I say interact with some blocks but not others. We using a modded server like more and more servers doing with forge and such and one of the things I have are these outposts with rewards inside the top and such. We want players to be able to interact with certain blocks but ban them from others in these towers while the default player protection would have a different rule set done via config and never by the players.
Thanks for your time :)
-
View User Profile
-
Send Message
Posted Jun 25, 2012Bigscary, Our max claim depth is 255. Two of my users had this problem. One has a very very very large area and the other a smaller area.
We are on Build #2222
When they use the stick, it says no one owns it. But yet the PlayerData and ClaimData is all there.
We try delete claim but nothing there to delete. The only way to fix it is to remove the Playdata file and the ClaimData file.
Any Idea?
-
View User Profile
-
Send Message
Posted Jun 25, 2012@typhoonwes79
When you say the claim stops showing up, do you mean that the claim only reaches a little bit into the ground and then stops, or do you mean it actually completely disappears? If you go to the surface and right click with a stick (or string in earlier versions), do the boundary blocks appear again?
In your config file, have you set the "max claim depth" setting to something greater than zero?
Are you on a recommended bukkit build, or a dev build?
Clearing fluids is normal. If a player uses /abandonclaim, he will get a warning. Admins do not get a warning when they use /deleteclaim. Claims can be resized, so there shouldn't be any reason to delete a claim unless you're permanently getting rid of it (as opposed to re-claiming another size).
@iialias
I need lots more information. What is the specific error message you're seeing?
@Cordicuss
Yes, that's the case with all server plugins. Or at least, it should be.
@fungreenfox
Okay, sorry but not interested in investigating issues with dev builds. If that problem persists when we get a recommended build, then I'll work to fix it. For now, I assume it's a Mojang bug.
@Cordicuss
It looks like you've mixed a config.yml line into a permissions.yml? Also you might have to put :true. I'm sorry you're having difficulty, but I hope you understand I'm not an expert in permissions plugins and can't help you with that kind of problem.
Since you're the owner, why not just /op yourself? As for other moderators/admins, good luck. :\
@hillsoftware
Hmm... yeah I'm not sure this is something I can fix. It seems to me that the other plugin should see the player's death, since I'm setting his health to zero. But maybe because he logged out already, that might be the problem (there's no way to actually prevent the logout). Please take your detailed error message over to the death bans guy and tell him that the player is having health set to zero when he tries to log out in combat, so he may be logged out by the time the death ban code kicks in. With that information, he may be able to fix this for you.
@mvdhoning
Are we talking about a creative world? If yes, then don't worry. Any entities (dropped tnt for example) which are in the wilderness are automatically cleaned up. There's no way to stop tnt, animals, etc from leaving a claim without creating a horrendous performance problem. So the solution I'm using is to occasionally do a cleanup.
-
View User Profile
-
Send Message
Posted Jun 25, 2012Some players on my creative map recently discovered the fun of building tnt cannons and that is ok with me. Unfortunately the owner of the claim next to it not as fond on it as sometimes tnt drops on his claim. Lucky griefprevention prevents tnt from doing damage and cleans up the tnt :-). If things may go out of hand i move the tnt guys somewhat further on the map. But i wonder can tnt be preventend from leaving the claim?
-
View User Profile
-
Send Message
Posted Jun 24, 2012I know this probably doesn't qualify to be added to your plugin (which I love), but maybe someone has run something similar in conjunction with your plugin and can confirm they work together.
I have a server that is setup as a pvp world with a 1 hour ban on death. Initially I was using Ban On Death and it worked fine by itself. When I added your plugin it seemed to mess up death detection with that plugin (not pointing blame either way, they just don't seem to get along together). There would be some major ugly crashes in the log files when two people fought to the death(thousands of lines per death). Along with that non-pvp deaths didn't register for a ban like they normally do.
I switched to Hard Core Worlds plugin for the death ban, which seems to handle things better. If players die by pvp, mobs, falls, lava, drowning, etc. They get banned as they should.
The problem arises when someone quits during a fight. Grief Prevention says they died and they give their drops. When the player who quits logs in it comes up saying "you died" on the screen and then they can respawn. The hour ban doesn't register.
So I am curious if anyone has run a ban on death style plugin with Grief Protection? Or possibly any thoughts on how to get the two plugins to co-operate together to fix these quits players do to save themselves from the hour ban.
-
View User Profile
-
Send Message
Posted Jun 24, 2012I cannot for the life of me get "griefprevention.adjustclaimblocks" to work for me. As the server owner I should be aloud to have as many claims, and claim blocks, as I need. Am I doing something wrong? My owner permissions look like this:
__________
-
View User Profile
-
Send Message
Posted Jun 23, 2012Running dev build from yesterday, and GP 125 R4 from 2 days ago together with 30 plugins, all working. But GP turns trees into 2 log blocks when turning a sapling with bonemeal. Tryed disable both in config and reboot, but same output. Inside a claim, trees become 2 blocks.
-
View User Profile
-
Send Message
Posted Jun 23, 2012As the admin, only I will need this? None of my server users will need to install anything?
-
View User Profile
-
Send Message
Posted Jun 23, 2012@bigscary
I share the sentiments with wanting creative worlds to be more open and free, but I do still want the limitations of creative rules and limited claim blocks. So I would rather allow new players to a creative world be able to claim land more initially than in a survival world. 100 blocks in creative doesn't go very far. You could add different claim blocks per world, but maybe it would be better to change the cost of claiming land in creative rules; if a 10x10 area cost only 50 blocks, instead of 100? Players could still choose which world to spend claimblocks in, but they'd go further in the creative world. Then make that creative world cost a configurable option, depending on how free the server admin wants it to be.
-
View User Profile
-
Send Message
Posted Jun 22, 2012@bigscary My server says there is an error(is it set up right?) I just got this today, and never had any problems. All claims are gone, and no one on my server can claim anything. help?
-
View User Profile
-
Send Message
Posted Jun 22, 2012ok.. we are running in to problems with this. One of my clan area is very very big. He is able to clam it. but once he starts going down, his clam stops showing up. Like it was never there. But when you try to make another one. it says there is a clam there.
Another problem is, if we clear a claim, it clears water and lava that was there before. are we doing something wrong.
-
View User Profile
-
Send Message
Posted Jun 22, 2012@bigscary
It's affecting creative worlds, but we Pvp all the time in the creative worlds, in survival mode.
I'll try disabling it, but having over 1000 claims and 30 + people on at all times, it's hard to do that with order, if you know what I mean.
Sorry for not being clearer.
Edit: We also have Hunger games and I always win =P
-
View User Profile
-
Send Message
Posted Jun 22, 2012@TehTheve
Yes, use /transferclaim to make it your private claim.
@ArkGullwing
Yep that's right. Taking a creative world out of your creative rules worlds list will open you up to a lot of (wilderness) risks, but it will also allow players to build there without having to claim first - they will still have the option to claim something to protect it if they like.
Here's one simple example of something that might happen if you leave a creative world in "survival rules" mode. A player could construct a powered railway up in the air, pointed at his neighbor's house, then right-click rapidly to deploy 500 minecarts onto the rail in a short period of time. The minecarts would sail through the air and stack up on his neighbor's house (even if it's protected), leaving a big mess and effectively griefing that player. In a creative rules world, this mess would be automatically cleaned up so that probably no one would ever notice it. But in a survival rules world, those minecarts would have to be cleaned up by the claim owner.
Allowing players to build in the wilderness will also allow them to spam an area with an absurd number of NPCs, boats, paintings, and minecarts. You could clean this up with /restorenature, but in the meantime it will drag your server performance and be unsightly. Further, it's possible to build something that actually rapidly spawns NPCs even after the player has logged off.
@re4397
Yep.
@sillyrosster
That sounds extremely odd to me. I will look into it. In the meantime, will you try temporarily disabling GP just to see if it still happens?
EDIT: Wait, I'm confused. Are you in creative mode and trying to die? I ask because in your last comment, you mentioned about this PvP effecting creative worlds.
@Nickbbeezy
Newbie claims automatically get cleaned up. For other claims, you can set an expiration in days in your config file. Beware - this may mean some of the coolest builds on your server will become vulnerable to grief, just because the builder hasn't been around lately.
-
View User Profile
-
Send Message
Posted Jun 22, 2012Is there an option to get rid of inactive claims or a slash command that'd remove old claims? Over time they seem like they would build up.
-
View User Profile
-
Send Message
Posted Jun 22, 2012@bigscary
I'm not 100% sure that it is your plugin, but I'm pretty sure it is as it is almost the only one that has a Pvp option like the one it has.
Pretty much, I cannot die, which is annoying when I want to die :P Whenever I try to fight someone it says, "Player is defenseless" or something like that and they cannot attack. I have to go open a chest and then it says I can now fight with other players. So I was thinking I can die now, nope. When I get down to half a heart, it says "Player is defenseless" again and nothing will kill me. Nothing.
-
View User Profile
-
Send Message
Posted Jun 21, 2012how disabel "CombatTimeoutSeconds" ? Put 0 ?
-
View User Profile
-
Send Message
Posted Jun 21, 2012@bigscary
OK so the situation is, while I understand the logic of "choose which world to use your claim blocks in", I'd rather not limit my players in the creative world. While it does give a certain risk by not making them utilize this plugin's claim process in creative world (allows a griefer to just do whatever wherever in that world), it also makes a vast change that most of the players won't like; adding structured claims to creative world. If it's at all possible I'd like to use this plugin only on my survival worlds for land claims, and leave creative as is.
Now that I think about it, just enabling the plugin for all worlds and setting none of them to creative world rules, would accomplish that right? They'd have the OPTION to claim land in creative world but they wouldn't need to in order to build, because the plugin doesn't prevent you from building in 'wilderness' so long as you aren't in "creative world rules" correct? Then, if they WANTED to they could put their claim blocks on their creative builds but wouldn't be forced to claim land in order to build?