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 29, 2013@BC_Programming
excellent! :-) +1
(i'm not sure if you already answered this but are permission-nodes case-sensitive with GP, and/or does this also depend on the used permission's system?)
-
View User Profile
-
Send Message
Posted Aug 29, 2013@ThisUsernameIsMine
giving claims away using giveclaim can only be done by the owner of a claim (or by other players that have griefprevention.claims.admin permission, which is usually going to be a mod).
Presumably, you can give your FailNoob ranking specific permissions. if so, you should be able to deny "GriefPrevention.Commands.Trapped" to prevent them from using the Trapped command.
-
View User Profile
-
Send Message
Posted Aug 29, 2013BC_Programming: Amazing how much time you put into answering people's questions, much appreciated! :-)
Btw: Can players that have been trusted in a claim give the claim to someone else using /giveclaim, or does this only apply to the maker of the claim?
Also: i finally have everything working the way i want, thanks a lot for the explanations m8!
edit: I've noticed something which has been going on for some time. We have a rank named FailNoob, which is for people that keep breaking the rules. They aren't allowed to escape a special area, but sometimes when they type /trapped, they appear on a different location. Is there a way to disable this command, cause more and more start to (ab)use it :-/
-
View User Profile
-
Send Message
Posted Aug 29, 2013@BC_Programming
You sir are a scholar and a gentlemen! :-) Thank you. I will proceed from this point knowing generally what to do.
-
View User Profile
-
Send Message
Posted Aug 28, 2013@deleted_9935739
Then they are probably gone. Though from what I can tell it would have just saved the claims with a blank Owner, and thus they would have been loaded as being admin claims. If an exception occured while it was saving though (which seems like it occurred somehow, likely because the deprecated field being accessed was null), than the claim data would not have been able to save properly at all. (And naturally that means they wouldn't load properly either).
-
View User Profile
-
Send Message
Posted Aug 28, 2013@Awsmpossum1313
Chest claims require griefprevention.claims.allow. I don't know what "user permissions" is. If it's a GP setting it's an old one that isn't used for anything (if it was I'd probably know what it was, hopefully, haha).
FWIW pretty much every single thing written, and every single video, made about previous versions doesn't apply to current versions at all, particularly when it comes to configurations and permissions, which have both been changed drastically.
-
View User Profile
-
Send Message
Posted Aug 28, 2013I hate continually asking questions. However I am nearly where I want to be on this new server and I can not get the chestclaim feature to work properly.
User permissions is set to false
The radius is set to 5
Grief prevention is enabled in the world file.
If I drop a chest on an OP'd account it behaves normally. On any non-opped it acts as if it doesnt have a permission literally nothing happens, no error no message about /trust just behaves like a normal chest.. But i am under the impression i dont need permissions or has that changed since the original documentation. If this is simply a need to set up permissions for all groups i konw what direction to go however thats not what i am reading. Thanks again.. i swear as soon as i can i will get a donation your way.. you have been fantastic.
-
View User Profile
-
Send Message
Posted Aug 28, 2013@BC_Programming
The original claims were not actually made into admin claims. They just never loaded.
-
View User Profile
-
Send Message
Posted Aug 28, 2013@deleted_9935739
If you are trying to fix the claims that were probably made entirely into administrator claims, you want /transferclaim. those with appropriate permissions would then use /transferclaim <player> to transfer the administrator claim to a given player.
Also, from the docs:
griefprevention.claims.give
Allows player to use /giveclaim to give their claims to another player.
-
View User Profile
-
Send Message
Posted Aug 28, 2013@BC_Programming
Ah, I see now. So I should use /giveclaim for what I'm trying to do. I removed the adminclaims and transferclaim permissions and left griefprevention.commands.giveclaim, however it only repeats the command "/GiveClaim <TargetPlayer>" when trying to use it.
-
View User Profile
-
Send Message
Posted Aug 28, 2013@deleted_9935739
They aren't in plugin.yml. I only added the commands.* permissions to the plugin.yml and a few others so far. Most of the permissions listed aren't even used anywhere anymore, either. (the old ones, specifically, such as griefprevention.ignoreclaims, griefprevention.adminclaims, and griefprevention.deleteclaims, etc. have been moved to other permissions.
These permissions aren't listed in the plugin.yml for two reasons. The first is that I simply haven't put them in the plugin.yml, and the second is that they aren't referenced by any of the commands in the plugin.yml, and are used internally. Usually for sets of commands or more often for things that aren't the result of a command such as interactions. The plugin.yml file doesn't magically update when I change permissions around and self-document that has to be added in manually.
/transferclaim either makes an admin claim a player claim or makes a player claim an admin claim.
/giveclaim gives a claim belong to one player to another. the difference is that /giveclaim doesn't require any admin or op permissions to use; normal players can use /giveclaim to give a claim that they own to another player.
/giveclaim can also be used with the transfer permission to take a claim from one player and give them to another. (This currently requires GriefPrevention.admin.claims permission).
The two commands use disparate sets of permissions.
-
View User Profile
-
Send Message
Posted Aug 28, 2013@BC_Programming
I'm not seeing any "griefprevention.admin." permissions except "griefprevention.admin.*" in plugin.yml. What exactly is their purpose?
I'd still really like /transferclaim to work on it's own for anyone without admin permissions like /trust.
Can you explain the difference between /transferclaim and /giveclaim?
-
View User Profile
-
Send Message
Posted Aug 28, 2013@deleted_9935739
I looked through it, and the perms that would be required for transferclaim are:
"griefprevention.commands.transferclaim", "griefprevention.claims.transfer" and "griefprevention.admin.claims permissions".
A few development builds ago I completely refactored the permissions, so the older permissions (griefprevention.adminclaims) have been moved to a more tree-style set of permissions. (I did this at the same time I added the commands.* stuff). (GriefPrevention.Claims.Transfer is supposed to apply to anything that transfers claims, which I believe also includes using /giveclaim to try to give a claim belonging to one player to another, (and if not yet, that is the intention with it).
-
View User Profile
-
Send Message
Posted Aug 28, 2013@BC_Programming
I'm planning on having my staff claim as many buildings as possible and use /transferclaim to give it to the creator, but they have no permission. The permission nodes they have are:
-
View User Profile
-
Send Message
Posted Aug 28, 2013@deleted_9935739
Yes. the data was destroyed as a result of the bug. Sorry for the inconvenience.
EDIT: Since they don't have a name, they should load as administrator claims, though; you could use /transferclaim to give claims back to the appropriate player, though that might be a bit more admin overhead than you would like.
-
View User Profile
-
Send Message
Posted Aug 28, 2013@BC_Programming
Is the only way of fixing this problem to start over with all claims?
-
View User Profile
-
Send Message
Posted Aug 28, 2013hopefully fixed in #165. Some portions were using the claim ownerName, which was changed from previous versions that used getOwnerName() since the latter will return "An Administrator" and the claims would be saved as beloning to a player named "An Administrator" and stop being admin claims. unfortunately ownerName isn't kept in sync (it's also deprecated now) and what they should have been accessing was claimOwnerName.
EDIT: Also somewhat secret update for #165 and later: When using the stick to investigate claims, Administrator claims now use Emerald Blocks instead of gold blocks to mark the corners.
-
View User Profile
-
Send Message
Posted Aug 28, 2013After some testing, I've tracked the source of this problem to build 164.
Steps to reproduce.
The claim file has changed from
Looks like it can't be fixed since it deleted the names..
-
View User Profile
-
Send Message
Posted Aug 28, 2013@BC_Programming
Build 165 seemed to have corrupted all claimdata.. Tried going back to #164 and this error still appears on startup and no claims are working.
http://pastebin.com/zx1CzVf1
Pretty sure it listed every claim. This is only a small snippet.
Edit: All claimdata files show they were last modified when I applied this update.
Edit 2: Upon further inspection of the log, these errors first started happening when I stopped the server while running build 164. Going back to build 163 didn't fix it so I'm pretty sure the claim files are corrupted.
-
View User Profile
-
Send Message
Posted Aug 28, 2013@deleted_9935739
Somebody was complaining that spam-cancelled death messages were causing blank lines, so I threw that in there.
Evidently it doesn't work. I'll just remove it.