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 Jan 15, 2014/trust grants access to the ENTIRE claim, so you do not want to do that. /accesstrust grants access to buttons, doors, trapdoors, and levers. So if you want people to have access to your doors, /accesstrust is the way to go.
-
View User Profile
-
Send Message
Posted Jul 21, 2013when assigning an admin claim, fresh install, 1.6.2 CB (craftbukkit-1.6.2-R0.1-20130715.060238-8.jar) using GriefPrevention-141.jar, development build.
I can start the initial placement from the first block but when I move to the alternate corner to end the selection region of the claim, the below error is thrown in the console.
It's worth noting that on claims < 10x10, the message is successfully passed to the client about the claim needing to be bigger than 10x10 but as soon as you move outside of that 10x10 area, this error is thrown.
-
View User Profile
-
Send Message
Posted Jul 20, 2013@rfsantos1996
GriefPreventionFlags has the command option.
-
View User Profile
-
Send Message
Posted Jul 20, 2013Hello,
I got a little problem. I changed the main world from world (the normal standard) to Mainworld because we moved to a new mainworld.
We found out that this caused allot of problems with nether portals and end protals.
Is there a way to copy all the grief prevention data from one world to another world without changing any thing.
Like:
Old main world name is Mainworld New main world name is world (the standard mc world)
As far as i know is that grief prevention data is linked with the world name. So i cant just move data from one world to another world and it works without chaning any thing.
Hope you know what i mean.
Kind regards.
-
View User Profile
-
Send Message
Posted Jul 20, 2013Could you enable AutomaticNatureRestoration when a player unclaim his place? Or something to "clean" the rest after some days/hours? :3
@EDIT: another sugestion: could you make something to "ban" commands to people who don't have trust? Some players use /sethome on other houses.
-
View User Profile
-
Send Message
Posted Jul 20, 2013Despite the built in messages and the video link this plugin provides, I find myself manually fixing numerous new player's subclaims. If a player needs a subclaim, I assume the could figure out /subclaims similar to /adminclaims. It really would solve much manual labor as an admin on my part. Though I'd prefer a config setting to simply remove subclaim capability for simplicity's sake. I have yet to have a player need a subclaim, but hundreds accidentally create them. Perhaps I overlooked a permissions node to prevent them?
-
View User Profile
-
Send Message
Posted Jul 19, 2013@Diemex
I thought I already implemented this but it doesn't appear that I did. I (re?) added it again. It will appear in 7.8, and the next Dev build on Jenkins.
-
View User Profile
-
Send Message
Posted Jul 19, 2013@WsupPanda
It's reasonably trivial to perform a grep on the File data or perform an SQL query to try to find all the claims in the area.
FWIW the dev builds and thus 7.8 add the capability to use the investigation tool while sneaking (with appropriate permission) and view all claims in a range of the location clicked.
-
View User Profile
-
Send Message
Posted Jul 19, 2013@BC_Programming
Yes, that does happen, but since the space is relatively big, the markers are nowhere to be found. There needs to be something that can tell us exactly where that claim is, or at least let us override any claims using adminclaims. Searching for the claim throughout the area can be a bit of an inconvenience, and in my case, a huge one.
I've been searching for hours and hours for the claim in the way, with nothing found. It needs to be easier to find the claim without having to look everywhere searching for it, please.. My spawn still cannot be claimed due to the unfound claim in the way.
-
View User Profile
-
Send Message
Posted Jul 19, 2013I would like to be able to set the minimum claim size in total blocks and not just the minimum length of the edge.
This would be especially helpful for nether tunnels as they are very long (200-300 blocks) and only 1-3 blocks wide. Claiming the tunnel with a 10 wide minimum claim size would waste a lot of blocks. But I can't just decrease the minimum size because then I have 1x1 claims and I don't want that either. This
in addtion to the existing
would work.
-
View User Profile
-
Send Message
Posted Jul 19, 2013@JaguarJo
Found my problem. The area the villagers was in was a subdivision. Even though all trusts were removed inside the area, the larger claim containing it had containertrust on public. I feel like a doofus, lol.
Problem has been corrected and Grief Prevention continues to be essential for keeping my server safe. I love you guys.
-
View User Profile
-
Send Message
Posted Jul 19, 2013@WsupPanda
The overlapping claim(s) are visualized when that occurs. They appear as netherrack and glowing redstone.
-
View User Profile
-
Send Message
Posted Jul 19, 2013I really am in need of a command to remove all claims within the selected region, or override all claims even if the claim we are trying to make overlaps another. I am trying to reclaim the entire spawn, and since it has first been claimed players have made claims within the region and I have searched for long hours to find them, yet I have not found the last few claims overlapping. Any chance this can happen ?
-
View User Profile
-
Send Message
Posted Jul 18, 2013@brian163b The docs are written for release versions, not for development builds. And I didn't write them. In fact, they were last updated quite a few months before I was ever added to the project. The plugin.yml hasn't been updated with new help text because the way /transferclaim works is temporary and it might be removed in favour of extending /giveclaim, or possibly vice versa.
-
View User Profile
-
Send Message
Posted Jul 18, 2013@BC_Programming
Sorry, color me confused. 8-( From the Administrative Topics page:
Creating for Others
"Anyone with both the griefprevention.adminclaims permission and the griefprevention.adjustclaimblocks permission may create a claim for another player by first creating an administrative claim with /adminclaims, then using /transferclaim. "
And if it is just for re-assigning a claim to admins, why does the help say "/transferclaim: Converts administrative claim to private claim." Isn't that the opposite?
EDIT: Found one more ref in messages.yml:
TransferClaimAdminOnly: Text: Only administrative claims may be transferred to a player.
-
View User Profile
-
Send Message
Posted Jul 18, 2013@BC_Programming
Well dangit, something's broken on my end then. I've got protect creatures set to true in the config and it protects farm animals perfectly, but the villagers have been getting murdered right and left by players who do not have any trust levels within the claim.
Thanks for the fast response though; I'm really scratching my head on this one. I think I'll try updating to the dev build and see if that helps anything.
-
View User Profile
-
Send Message
Posted Jul 18, 2013You are a master; this plugin is also compatible with choptree2 :D
-
View User Profile
-
Send Message
Posted Jul 18, 2013So I need a little help with something. I have a spawn that is protected by spawn default and by a worldguard region. Players are still able to claim chunks within the spawn. I want to know if I can prevent this without having to claim the whole spawn myself. They can't make any changes to any of it because of the worldguard region. I just don't like that they can claim spawn areas.
-
View User Profile
-
Send Message
Posted Jul 18, 2013@JaguarJo
No. Villagers should be protected the same way as other creatures. I think this functionality was present in 7.7 as well, reliant on one of the trust levels.
-
View User Profile
-
Send Message
Posted Jul 18, 2013Is there a way to protect villagers from being killed by players inside of claims the same way farm animals are protected? I'm using grief prevention 7.7 on a 1.62 server right now and players keep murdering the villagers inside spawn, which is an admin claim. I saw on the page for the dev build that villager trading has a permissions section, but does that also affect the ability to kill them?