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 Dec 14, 2013Awesome plugin! Players of my almost done server are really happy about this plugin!
Thanks!
Site: http://www.orbitmines.com In 2 weeks online: OrbitMinesMC.com
Best regards, Fadi
-
View User Profile
-
Send Message
Posted Dec 14, 2013There's an issue with siege mode still. With automatic item transfer on, the armor slots are not accounted for as they are not a part of the inventory according to bukkit, you have to access them separately. Therefore, during siege, the armor items are lost and not given to the victor. It's quite a simple fix and easy to overlook, so hopefully it can be fixed for the next update?
Thanks, CoolGamrSms
-
View User Profile
-
Send Message
Posted Dec 13, 2013@Pippl
In 7.8 claim logic is on or off. Turn it on so that you can have admin claims. Then use the option "CreationRequiresPermission: true" so that non-op players may not create claims. If you later decide to allow certain people to build claims there, use a permissions plugin and give those players the "griefprevention.createclaims" permission in order to create claims. Although it was more intuitive to have admin claims always available, this is far more functional and honestly just as easy with just one config change.
-
View User Profile
-
Send Message
Posted Dec 13, 2013@hillsoftware
If I follow you on the permission for circumvention, that would give whoever I give it to blanket permission to place blocks anywhere? That could work, but is less fail safe. Can this permission only be for the "wilderness" parts of the break and place overrides?
I was incorrect, the permission setting is possible within the Claims and wilderness parts of a Rule, not the rule itself. An example of this is in the default configuration- LavaPlacement requires GriefPrevention.Lava permission in the wilderness, for example.
Even if you set the permission on the claims section, it shouldn't override the required trust levels- eg. if it's set to require build trust with ClaimControl, then the permission would be required but you would also need to have that trust level.
@LEOcab
The page documenting the configuration for 7.8 is linked in the second paragraph of the main project page.
-
View User Profile
-
Send Message
Posted Dec 13, 2013@Titanaswarrior
From http://dev.bukkit.org/bukkit-plugins/grief-prevention/pages/administrative-topics/
do /trust public
-
View User Profile
-
Send Message
Posted Dec 13, 2013@BC_Programming
Thanks for the response.
I will look into the denialmessage for the place and break. That would help the normal users understand why they are having problems placing/breaking like they got notified of before.
If I follow you on the permission for circumvention, that would give whoever I give it to blanket permission to place blocks anywhere? That could work, but is less fail safe. Can this permission only be for the "wilderness" parts of the break and place overrides? That way admins can by default build/break anywhere that isn't claimed, but once they hit a claimed area they have to do an /ignoreclaims before modifying someones claimed area?
What I mean by that is currently with the older version I am running, admins can't place a block on someones claim, or non claimed areas initially. They get the message telling them it is already claimed, or needs to be claimed. They then do the /ignoreclaims and fix or take care of things. Next time they are online they are back to respecting claims, and have to repeat the process. Makes it safer for accidental changes.
With the permission thing, they would just be able to go around and ignore all claims and build/destroy in any area?
Our setup (just so you know what we are doing). I have a server in creative mode with 30x30 diamond mats spread out (1000's of them) in the world. Players can claim any 30x30 mat (they have 900 blocks only to claim), and then they build in that plot for that weeks theme (it is a build theme server). We then show some of the best builds on our YouTube channel (80K subs or so, so not a huge channel, but not small either)
We have a 5 block buffer in between the mats that are all over. Sometimes we need to build in that area and before we would just ignoreclaims and build there. Or ignoreclaims if we had a user do something that needed fixing or removing.
Ideally the way it works with the older version of the plugin, nobody builds including admins unless the area is claimed. Admins can /ignoreclaims to place/repair/fix anywhere on the map, but by default don't have to worry about ignoring claims and breaking things by accident (which is very easy to do with a mis-click while in creative).
Sorry for all the questions, just trying to adjust to new plugin if possible, while keeping things nice for users and admins.
-
View User Profile
-
Send Message
Posted Dec 13, 2013Sorry I forgot I had another question. Can you make a claim public? If a player makes an Inn,Bank,Tavern,Shop. Can you give all players access to chests doors and buttons? I know you can give people access 1 at a time. I wanted to know if you can do /containertrust ALL and /accesstrust ALL to let all players use your public claim.
-
View User Profile
-
Send Message
Posted Dec 13, 2013Hey bud, can we get documentation on the new (beta) configuration format? There are lots of options I don't understand (eg. ClaimControl) and I don't want to update my server without fully understanding what has changed. Thanks!
-
View User Profile
-
Send Message
Posted Dec 13, 2013Bug: The second line on sign eavesdropping becomes discolored (white). 7.8-beta-b197
-
View User Profile
-
Send Message
Posted Dec 13, 2013@hillsoftware
I changed the semantics of ignoreclaims.
Before it meant "ignore specific functionality of griefprevention which may or may not be related to claims" Such as what you mentioned.
I changed it to mean- "ignore claims". It will only ignore claim permissions. If something is not related to claim permissions, it won't be affected by ignoreclaims.
If you want to allow players to circumvent it, you can add a Permission to block placement and breaking.
You may be able to set the "DenialMessage" ( on block placement/breaking to a message to display. It is not documented since it hasn't been particularly well tested so may not work for what you need.
@Pippl
Do not disable claims. If you want to disabling claim<ing> than you can deny griefprevention.claims.chestcreate, griefprevention.claims.toolcreate. except for Ops. That will prevent any player from creating claims except for ops, who can also use adminclaims.
-
View User Profile
-
Send Message
Posted Dec 13, 2013till the new version, we were able to disable claiming, without losing the possibility for using /adminclaims.
I just want to create a farming world, where the spawn building and some other stuff is protected by AdminClaims, but there shouldn't be any claim-permissions for default players, like i did it with GriefPrevention 7.7.
How am i able to this with the newest version of GP?
-
View User Profile
-
Send Message
Posted Dec 13, 2013How do you remove everyone's claims?
-
View User Profile
-
Send Message
Posted Dec 13, 2013@hillsoftware I'm in the same boat here as hillsoftware I would like to disable all building outside of claims for all non admin users. To get around this I've ether changed the settings to allow the build or claimed the land I wanted to work with and deleted the claim after. I was really hoping I could get a setting so that admin can override place/destroy deny setting so I can build content for players easily without bringing down the server.
-
View User Profile
-
Send Message
Posted Dec 13, 2013I would just like to say that this is one of the best protection plugins ever. The /Restore?nature is natural looking and if the seed looks crazy, you can fix it with that command. Thanks a lot for this awesome plugin.
-
View User Profile
-
Send Message
Posted Dec 13, 2013@BC_Programming
Thanks for the quick reply!
Yeah, I have set the wilderness to deny for place and break. It does prevent people from placing blocks. They just appear and disappear. Also prevents from breaking blocks in non claims. They just disappear and come back.
Negative is it doesn't pop up a message like before telling the user they can't place blocks in unclaimed land. Also admins use to be able to /ignoreclaims and override being able to place/delete blocks in or out of claims.
Now I am not sure of an easy way for admins to be able to place blocks outside of claims.
-
View User Profile
-
Send Message
Posted Dec 12, 2013@KIMB00P
Set GriefPrevention.Claims.Enabled to false in that worlds configuration.
@ryan_the_leach
I cannot reproduce the problem. I was able to create a Nether portal in a claim without issue. Note that it requires build trust in the claim, of course.
-
View User Profile
-
Send Message
Posted Dec 12, 2013@navbarry
A question answered in the second paragraph of the main page.
-
View User Profile
-
Send Message
Posted Dec 12, 2013How exactly do you disable claims in a specified world?
-
View User Profile
-
Send Message
Posted Dec 12, 2013@navbarry
yes.
-
View User Profile
-
Send Message
Posted Dec 12, 2013@BC_Programming
Hey BC, players can't create nether portals in claims, but the firesetting should allow them to. any ideas?
FireSetting: Wilderness: AboveSeaLevel: Allow BelowSeaLevel: Allow RequiredPermissions: - GriefPrevention.Lava SeaLevel: '-1' Claims: AboveSeaLevel: Allow BelowSeaLevel: Allow SeaLevel: '-1' ClaimControl: RequireBuild