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 Feb 8, 2013@zrocweb
Yep, I think they're up to date. I haven't made any changes to the API in a very, very long time.
@orenbus
The plugin does support giving permissions in a claim based on server permissions, but creating server permissions groups is usually not available to players (only admins). It would be very, very difficult for me to introduce my own notion of groups which is separate from server permission groups, very few would use it, and many server admins would be confused about having two types of groups.
@Stevensaurus
That's right. Replace your old JAR with the new JAR and restart your server (or just /reload).
@ray73864
Okay, the config option is AutomaticNewPlayerClaimsRadius. If you have that set to -1, then new players will not get automatic chest claims. Also check with that player - if he builds a chest inside an existing land claim (with permission), he naturally won't get a new land claim because it would overlap the existing claim. Also if he places one right next to (but just outside) an existing claim, he may get a land claim which is ONLY the chest, due to there not being enough space to create a full 9x9 claim for him. You can check for that with your stick (right click from a distance so you don't open the chest by mistake).
@elirock12
Maybe. It depends on how hard it is to get it right - if it looks like I might be leaving a grief opening, I won't do it. Stay tuned.
@MustangTim
/help only shows commands players have permissions for, so they must have permission. Try explicitly taking away their griefprevention.claims permission.
@imaapseudonym
I've heard BukkitForge is at this time a very poor imitation of Bukkit, and that GriefPrevention is one of many plugins it does not run correctly.
@KlingL
See the bottom of the setup/config page.
@Eyeball114
If you just don't have enough claim blocks, use /acb to give yourself more.
If that's not the problem, then keep pushing for better plugin support in Voltz. A lot of projects have started up lately that try to run Bukkit plugins without using Bukkit, and most of them are in a state of "kind of but not really working".
@Kane_Hart
I guess you mean right clicks? In the config file, you can add IDs to the "BlockIDsRequiringContainerTrust" list to protect more block types from right click. I don't block all interaction outright because it would be very annoying to constantly get "you don't have permission to use that" when you're not trying to use anything. :)
-
View User Profile
-
Send Message
Posted Feb 8, 2013@Eyeball114
Just do /buyclaimblocks (number of claim blocks)
-
View User Profile
-
Send Message
Posted Feb 8, 2013Can you block all interaction with this? The one I'm using now is a bit more easy but does not offer any protection really from interaction but doing it by hand and ohhhh boy that becomes a pain hehe.
-
View User Profile
-
Send Message
Posted Feb 7, 2013@imaapseudonym
Seems as if it doesnt work. I have it on my voltz server now and when I pull out a gold shovel I get:
"To delete another claim and free up some blocks, use .AbandonClaim. Than right under that in Red text is: "You don't have enough blocks to claim that entire area. You need 73456 more blocks."
The only thing that seems to work is /adminclaims
Hopefully this does wind up becoming compatible. This is the best anti grief plugin Ive ever used and its the only one I use on all my community servers.
-
View User Profile
-
Send Message
Posted Feb 7, 2013@bigscary
I think it needs permission nodes to all the op commands so that I can give those commands to my Admins and Moderators.
-
View User Profile
-
Send Message
Posted Feb 7, 2013Does this happen to work with bukkitforge?
-
View User Profile
-
Send Message
Posted Feb 7, 2013Do you have a way to get rid of the GP commands when doing a /help? The reason I ask is my default group (people who haven't registered) only have access to a couple of commands. The problem is when they do a /help all of the GP commands come up even though they cannot use them.
Basically need to remove the GP info when doing a /help, or removing GP for the default group all together.
-
View User Profile
-
Send Message
Posted Feb 7, 2013@bigscary
Say oh ok can u make it in the future? I'm trying to recreate the TNT Olympics and its needs to kill villagers for 1 event
-
View User Profile
-
Send Message
Posted Feb 7, 2013@bigscary
Sorry it took so long to get back to you.
Anyway, i have checked the config file, i have no 'chest claim radius' option in there at all.
It is a brand new player never played on the server before, he placed a chest, no claim was created at all.
However, when he got a golden shovel, he was able to manually create a claim.
-
View User Profile
-
Send Message
Posted Feb 7, 2013@Bigscary
Alright, so I don't have the generate a new folder? I can just get a new .jar?
-
View User Profile
-
Send Message
Posted Feb 7, 2013Hi, Bigscary great plugin! My friends and I have really be enjoying it along with population density and I personally have made a decision I will most likely never play on another Mindcraft that does not have your plugin, its that good it's pretty much a requirement.
Now onto my request :)
A number of friends and I as well as people we have met online have been playing to create an organic town of mostly players with little to no administrator structuring of the town. Through use of claims and subdivisions we've been doing great however as the town gets larger we are finding the need to keep track of individuals into groups that break down into subgroups to apply to different sub-claims. Right now we are having to type in each individual name in the various pieces of property but ideally what would benefit us in a great deal would be to be able to assign individuals to groups using the plugin and then apply trust to a group which would give trust to those associate players in the groups.
I'm not sure how difficult this would be for you to implement but I think it would help others as well, as the plugin continues to mature and people begin to make it a defacto plugin to use on their servers.
Thanks again!
-
View User Profile
-
Send Message
Posted Feb 7, 2013@bigscary
BigScary, Believe me I understand where your coming from and understand your time constraints as I am as equally as busy with the same things. So no worries man. I think what I will do is start my own add-on for GP with these flags. I saw there was another plugin out there that has yet to be uploaded that was going to support using / setting GP flags. But I'm not waiting for it. Sound like it has issues already and it's not even released. So... I'll see what I can come up with. No worries!! Thanks for responding
oh.. Are the API pages up-to-date? I know you've had a lot of changes since the release of 1.4.6+, so I just wanted to check as I venture in to my own GP Add-on Plugin.
-
View User Profile
-
Send Message
Posted Feb 7, 2013@RustyDagger
Sorry, I'm just passing along the advice I've heard. I guess it's not an option for you, then. I can't make BukkitForge support plugins better - I'm not in charge over there. :\ You're not alone in being confused about all the new "flavors" of Bukkit coming out. Thing of them like emulators - they're not really Bukkit, but they're trying to support running Bukkit plugins anyway. You wouldn't blame Nintendo and ask for an updated version of Legend of Zelda which is compatible with the NES emulator you're using, would you? Of course not - the problem is that the emulator doesn't do a good job of acting like a real NES. In my plugin code, I say stuff like "tell me what block the player is looking at when a player right clicks with a shovel in hand". Bukkit tells me the right answer. If ForgeBukkit doesn't give me the right information, there's absolutely nothing I can do to make my code "work anyway". Slash commands aren't a good workaround because slash commands involving block counting or coordinates aren't usable by most players (it's too hard for them to figure out). So only players running ForgeBukkit who are really good with slash commands would use them, and then they would only use them until ForgeBukkit fixed its plugin support issues - it's just too much work for a small, temporary payoff (remember I work for free in my spare time).
@elirock12
No, it just enables exploding blocks. Maybe dump lava, if you need to kill a very large amount of villagers at once.
@AbbyMaeTaylor
Can you give me some examples of the commands you're trying to spam block? An option to limit the frequency of all commands wouldn't work out - consider for example the /spawn command. Because it doesn't take any parameters, a player who uses it several times in a row SLOWLY over the course of several minutes might be banned as a result (because the command line is exactly the same), which isn't fair. The spam blocker is meant for chat-type commands, not for all commands. If you've identified a non-chat command which could be spammed to cripple your server, please contact the developer of that plugin to insist that he close the security hole by adding a cooldown period, making the command more performant, or limiting its use to administrators by default. Commands vary VERY widely, so no general rule applied to all commands would work - that's why I scope the "spam" problem to chat commands, where they're similar enough that I can apply some reasonable rules without causing an over-banning or over-muting problem.
The bug you reported is already fixed in 7.6.1. Please update. :)
To fix whatever crashing problem you're having, I need more details. Please post a link to a pastebin with evidence which will help in my investigation.
@KlingL
What permission nodes do you think you need?
@zrocweb
Yep, I would love it if somebody would build an extension to add whatever flags you want. Then I could point people to that thing when they ask to stop spawning monsters. I've got my hands full - I run two test servers, code, develop, write docs, and answer questions for five plugins, have a full time job, and a personal life in the tiny time leftover. I'm drawing the line at starting another plugin - someone else will have to do it. The "right version" of the feature set you're asking for don't belong in this plugin because it's for anti-grief, and adding them would be extremely risky anyway because I would have to update the database schema. I won't take on that level of risk for a feature that's not important to stopping griefers.
I say "right version" because what you suggest will just get me into more trouble. It's the perfect solution for you, sure, but the minute I publish it, somebody else will come along and say "I have some admin claims where I want pvp on but monsters off, but others where I want pvp on with monsters on", and then we're back to flags for specific land claims.
-
View User Profile
-
Send Message
Posted Feb 7, 2013BigScary:
I know we have gone back and fourth of this several times over the past, but I just totally fed up with World-Guard and all it's pet-peeves in conflict with GP and other plugins. I want to eliminate WG altogether and just use GP as I, and I'm sure there are a ton of others, that don't need WG and GP. Gp does it all with the exception of some things.
So my suggestion is to add weather or not MOBS can spawn in a claim. Not asking for all claims, just for Administrative claims. My scenario is this for one of my servers. I have my spawn located in the main world and without having to totally blow up the lighting in the spawn, mobs will just spawn inside all the time. I originally have WG installed to eliminate that factor and it worked okay but then WG has other things that need to be toggled off, etc.. and it affected the rest of the server in other WG regions as well as GP claims. To me it's just crazy to have to invoke admin claims for the control you want as the owner/admin of that claim and then have to go back and do the same damn thing with WG and then have to configure WG for that region/claim, again.
One more additional request: can you add the claim id to the claims list output as well as when you are investigating a claim and the player has access to view the claim id, show the claim id when using the stick. Would make things a little easier especially in the claimslist when looking at claims of the administrative nature. Perhaps an added request would be to teleport to claim[id] for admins/owners/ops only. I bring this up for the reason that instead of having to tppos the coords of the claim when a player is having problems within a claim, admins/ops, etc.. can just tp to that player, do an investigation on the location they are in and identify the claim via the claimslist command and resolve any issues within that claim.
Most importantly, please add the MOB Spawning toggle for Admin Claims only, please.....
Thanks.
-
View User Profile
-
Send Message
Posted Feb 7, 2013@RustyDagger
Here for all your MCPC needs: http://www.mcportcentral.co.za/index.php?topic=4657.0
-
View User Profile
-
Send Message
Posted Feb 7, 2013Question about the new feature to disable PVP mode in user's claims. Is there a way to enable and disable PVP per claim? Like /pvptrust? Maybe I am just missing it in the docs?
I only see the setting in the configuration file:
<<code yml>>ProtectPlayersInLandClaims: PlayerOwnedClaims: true AdministrativeClaims: true<</code>>
-
View User Profile
-
Send Message
Posted Feb 7, 2013ok so after playing around with the plugin on Bukkitforge some more. I have noticed that its having issues with the set location systems for the corners.
Are there any commands that can be used to set the point that way As I think that would at this point in time be more reliable on bukkit Forge builds.
When you first join You are able to set your points fine but after the first selection is made it seems to set one of the points to 0,0,0 or some really far off distance preventing making a second selection.
Relogging Into the server fixes this. Maybe the above info will help you make some kind of temp workaround maybe Please?
-
View User Profile
-
Send Message
Posted Feb 7, 2013@KlingL
Check the Player Experience Link Up the top and the admin configuration pages.
From memory I think only the admin page has permissions on it listed All the player permissions are given to them by default via the plugin.yml.
-
View User Profile
-
Send Message
Posted Feb 6, 2013Spam prevention enabled caused server to crash. This have been happening for months, please look into it.
-
View User Profile
-
Send Message
Posted Feb 6, 2013Are there any permission nodes for this plugin? If there aren't, you should really add them. However, if there is an addon for this plugin that gives this plugin a bunch of permission nodes, then please do tell me what it is. Thanks, I love this plugin!