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 May 2, 2012@stgram
I don't understand how this is vital for preventing grief. Even without that feature, due to claim block accrual, players who contribute most to your server (by playing more) get to claim more land. Isn't that the point of granting higher ranked players extra claim blocks, to reward them for being MVPs on your server? By changing it to your way, or offering an option to do it your way, there's no improvement really - either way, no grief. Your way is just a little more convenient for you, since you prefer to manage claim blocks manually via groups rather than automatically. For most, it would be less convenient - automatic is less troublesome than manual management, and the current system doesn't involve any other plugins. I understand why you want it, but I just don't think it's worth the coding and testing overhead to add it.
It sounds to me like whoever is in charge of plugin decisions on your server hasn't given GP a hard enough look, OR just doesn't want to deal with the migration headache (converting residences to claims, and manually giving bonus claim blocks to loyal, long-term players, which I understand is a pain). GP has your server's scenario covered, but my solution just doesn't look exactly like Residence's solution to the same problem. We're both rewarding loyal players with more blocks.
As you can see, I've thought about it a lot, actually. :) I'm sorry to disappoint you. I'm always happy to reconsider if you come up with a stronger case for your feature request. You'll have to convince me that the workload involved in managing an additional plugin and manually adjusting groups of players is offset by somehow better anti grief protection.
Consider solving your problem this way. First, set the maximum accrued blocks according to your lowest player group (newbie or whatever). Now for each member of your higher groups, use /adjustbonusclaimblocks to give them the boost you think they deserve. Then you maintain this going forward by adding a few bonus claim blocks when you promote players. New players will have a rather small maximum, encouraging them to strive for a better rank, while ranked-up players will get an immediate boost, with a higher maximum block count.
@mdcollins05
There are some plugins which allow for toggling pvp on and off, and they don't conflict with GP's anti spawn camp. Since you want to allow players to toggle pvp off, you might as well go ahead and disable siege, since its purpose is to force players to pvp rather than hide. :)
By the way, since I'm on the topic. Somebody was asking me the other day why I included the optional siege stuff in the core GP, instead of making it an extension plugin. My "philosophy" in GP development is to prevent as much grief as possible without changing the way players play Minecraft, adding lots of slash commands, or requiring other plugins (like economies or logging/rollback). By giving players a way to create unbreakable blocks (by claiming them), I felt like I was giving PvP griefers a tool - a way to create a safe haven anywhere in the world from which to annoy people, and then hide. So I decided that offering /siege was vital in offsetting the impact of offering claims in a PvP environment in the first place. :)
-
View User Profile
-
Send Message
Posted May 2, 2012@bigscary
I love the siege/PVP elements, but would it be possible to add a "toggle pvp" option for those who don't want to attack/be attacked? It could stop them doing damage (and /siege) and not allow any damage to occur to them. Maybe with a cool down to prevent abuse.
Thanks for the plugin!
-
View User Profile
-
Send Message
Posted May 2, 2012Not every single one of them, but at least this one, which is in fact vital. You see, this is the only reason why a server I know, which is one of the main for my country, wont migrate to your wonderfull plugin. As for now, we will be stuck with residence... Is it certain that you wont think about this feature?
-
View User Profile
-
Send Message
Posted May 2, 2012@XanderCrews01
I don't understand exactly. Unless homes are stacked on top of each other, everyone should be able to claim their homes without also claiming someone else's home next door.
Players should always claim more than just their house - they should include some of the area around their house to prevent bad guys from building right up against their house, or otherwise too close for comfort.
If you have an already-built town, one option (although it requires more effort on your part) would be to put a private claim of your own over the whole town, then define subdivisions for the houses and give permission to the home owners for each of those subdivisions (/trust and /permissiontrust).
If I'm not understanding your situation, maybe sending me your server info in a private message would help. I could come over and actually see what's happening. :)
@marcovit
Using /abandonallclaims should clear that long list of locations out of his player data file. That's not happening? Are you seeing any error messages in the log when he tries it?
Which message do you mean? "You don't have an administrator's permission to build here"? What would you want it changed to? If you just want your name to show in there instead of "an administrator", then use /transferclaim to make the claim yours, then /containertrust public to give everyone access. Now when they try to build, they'll see your name.
@stgram
If you had read and understood that page about the Residence comparison, you'd know that there are many reasons to choose GP over Residence, and none of them are "because GP has every feature Residence has". Residence has several features which are handy, but don't help with preventing grief. That feature is one of them, and I'm happy to let Residence keep it for compete.
-
View User Profile
-
Send Message
Posted May 2, 2012@bigscary
Oh phew, ok well hopefully whatever caused it will be fixed wherever the problem is. I will try to test and see if I can figure out the problem and let you know if I do. Thank you.
-
View User Profile
-
Send Message
Posted May 2, 2012Well that is one hell of a problem. Don't you know that most servers have ranks, depending on what you pay? And the higher the group, the higher the benefits from the server... You see, having per-group limitations is a key component, please implement it. In the current moment, your Why not Residence? comparisson is invalid, just because the other plugin has it. Please take a note. :)
-
View User Profile
-
Send Message
Posted May 1, 2012First of all, thanks for this plugin @bigscary.
Is there a way to change the minimum distance from one claim to another? I have a residential area on my server and I would like for people to be able to claim small areas for themselves, but they are close to one another because this is in a town. Right now people too close to each other can not claim all of the land that the homes they built are on. If this is not possible is it likely that we could see this in the future?
-
View User Profile
-
Send Message
Posted May 1, 2012@ryvix
It was probably a bug in the CB beta build. I just checked 3.4 GP against the latest recommended craft bukkit and there's no issue with fire spread (at least on my test server).
-
View User Profile
-
Send Message
Posted May 1, 2012@bigscary
No change in the config. Used the latest beta build #2175 of CB. I reverted back to GP 3.3.2 and it went back to normal. I didn't try 3.4 though since I didn't want to risk it. Only one persons house burned down that I know of and I was able to roll it back so it was alright =)
-
View User Profile
-
Send Message
Posted May 1, 2012@zedadiaswick
Oh shit, I don't know how you got into that situation, Zed. All filenames have always had three coordinates in them. I can't imagine how you got a filename with only two coordinates. :) I'm very glad you were able to figure out the issue, and I sincerely hope it doesn't happen to you again. I have reviewed the code after your report there, and I'm just plain stumped as to how it could have happened. I'll keep thinking about it in hopes of figuring out the bug, if there is one.
@marcovit
Will you please find the player data file for one of the player who's having this problem (even though he abandoned all his claims) and post it?
@Turqmelon
I want to shorten the message. But I need a shorter message which still gets the job done. Maybe you have a suggestion? I've heard tinyurl, but I hesitate on that because I think many players still don't know you can press T and then click links in chat.
@ryvix
Holy crap. No change to your config file, huh? Are you by chance on one of the dev or beta builds of craftbukkit?
@stgram
No sorry, no groups support. If you want to reward an individual user, though, you can use /adjustbonusclaimblocks to grant some bonus blocks.
@Gamemasher
That should never work. You can't gain PvP immunity by throwing away an item. Only by having an empty inventory when respawning or logging in.
-
View User Profile
-
Send Message
Posted May 1, 2012@bigscary
Sorry, I meant throwing out items. It didn't always work so maybe it was a bug?
-
View User Profile
-
Send Message
Posted May 1, 2012Hi there, is it possible to set different number of claim blocks for the different user groups used by PEX for example? A guest shoul have lets say 100 blocks, but a user who pays for a VIP status should have at least 800 and so on....
-
View User Profile
-
Send Message
Posted May 1, 2012@shutka
The node is griefprevention.lava
Your welcome!
-
View User Profile
-
Send Message
Posted May 1, 2012@bigscary
In situations where they were fighting each other, in order to not lose some players would simply pick up an item ASAP.
-
View User Profile
-
Send Message
Posted May 1, 2012Fire seems to be spreading in this latest version for me. I don't know what other things happened but I reverted to an old version again.
-
View User Profile
-
Send Message
Posted May 1, 2012@Turqmelon
I would like that so the part with 'go watch the video thingy' Would be /protect (on my server)
Thank you!
-
View User Profile
-
Send Message
Posted May 1, 2012A lot of people are tired of getting the chat spam whenever they hold a gold shovel...is there anyway you'd be able to add a verbose toggle for it, or allow customization of the message? :)
-
View User Profile
-
Send Message
Posted Apr 30, 2012@bigscary
Okay, I created a new claim and trusted a player, rebooted the server and that stuck; tried untrusting in the new claim, checked the file and it had updated. So I then found the file for the troublesome claim, and deleted/renamed it. Trusted a player to a subdivision, in the hope it would create a new claim file. It did, with a slightly different filename (and two player names swapped inside the file). Tried trusting a few other players in various subdivisions, and it all works now! In case it's important, the old file name was world;195;30 and the new filename is world;195;30;784 - my assumption is that file-naming has changed recently? I see a lot of files by the old name style, and some with the newer name style. I'll have a look and see if any others under the old name style experience difficulty.
EDIT: Yeah, can confirm others with the old name-style also do not save to file. Also tested some with the newer name-style, and they save just fine. Also, there were no console messages about not being able to save to file.
-
View User Profile
-
Send Message
Posted Apr 30, 20123.4.1 Updates!
-
View User Profile
-
Send Message
Posted Apr 30, 2012@JustinM511
You might have a file access problem. Are you running any other plugins that save data to file, and if so, are they also having problems? Are there any other entries in the log from GriefPrevention above that stack trace you pasted? Is it possible you've run out of hard drive allocation (out of space)?