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 Mar 15, 2015Setting public access trust allows anyone to be sieged in that claim. Players are coming back and finding their entire claim destroyed because of this bug. Ticket also created: http://dev.bukkit.org/bukkit-plugins/grief-prevention/tickets/864-setting-public-access-trust-allows-anyone-to-be-sieged/
-
View User Profile
-
Send Message
Posted Mar 14, 2015Can you please allow us to define which blocks are considered trash and shouldn’t trigger “Anyone can undo your work here” messages? Netherrack in Nether is the most obvious offender but of course this varies from server to server, depending on what they use to generate their worlds.
-
View User Profile
-
Send Message
Posted Mar 14, 2015I have a slight possible bug to report. I'm thinking it's partially intentional, but zombies can still pick up drops from a killed player (which is the intentional part), but other players can then kill the zombie and steal the drops. It's not a particularly problematic thing in most cases, especially since my players don't have a long cool-down on /back, but it seems even in that case, nearby players who notice can steal the drops from the zombie.
Not sure if it'd be worth preventing drops for zombies, up to you, but could somewhat be used to bypass drop protection cool-downs by luring a zombie over.
-
View User Profile
-
Send Message
Posted Mar 14, 2015Hi, I have made a brazilian translate... http://pastebin.com/Fbpf76J8
If you want to put inside the plugin feel free to do it :)
HW
-
View User Profile
-
Send Message
Posted Mar 14, 2015I'm having issues with players not being able to access their claims. I use a stick and it says I'm standing in their claim, but they don't have access. The database shows the claim under their UUID, too. It doesn't happen for all players, though. It seems like non-staff ranked players have the problem, but staff don't have any explicit GP perms set.
I'm running 6 Spigot servers in a Bungeecord, and it seems to be working on the other servers, just not my main server.
-
View User Profile
-
Send Message
Posted Mar 14, 2015Hello i really like your plugin but would love to see some additions mainly configuration options below is a list of options that would be great.
To be able to toggle if a attacker during siege's can place blocks or not Whether an attacker can use TNT during a raid Possibly more if you have time just general config options for sieges.
-
View User Profile
-
Send Message
Posted Mar 14, 2015@bigscary
Back in the day we changed a bit how GriefPrevention handles TNT and creeper explosions, but the feature was removed after you came back to the plugin and started to develop it again.
What we did was give the administrator full control over how explosions work. It was possible to choose if explosions would work outside claims, and if they'd work inside claims too, beeing possible to disable it with /ClaimExplosions.
Think you could do it again?
-
View User Profile
-
Send Message
Posted Mar 14, 2015VILLAGER BREADING
Anyone having problems there? Villagers do not break crops to give to other villagers like I see in videos... Is this a possible GP thang? I spent 2 solid days n countless hours and cannot find a fix. Any ideas?
Disregard this, now farmers are harvesting crops. found "gamerule mobGriefing false". Changed to true now they harvest
-
View User Profile
-
Send Message
Posted Mar 13, 2015Is it possible to share claims blocks?
Like i have 2000claimblocks, but i team up with someone, and they have 1000. So they can donate them to the team or me?
greetz van
-
View User Profile
-
Send Message
Posted Mar 13, 2015I have had a lot of players tell me they are missing a few thousand claim blocks, and they are right, We track time played for each player on the server, everyone can check this for themselves and therefore work out how many blocks they should have. I have mine quite easy to work out, since players get 60 Claim blocks per hour, that's 1 per minute played.
This seems to be a scheduled event, as they will see the blocks in their possession then at some point in time, they will disappear, resetting the player back to 0, I remember you saying there was an issue with how claim blocks were counted and this was to "fix" the negative claim block issue, But its caused issues with people loosing thousands of claim blocks they have earned.
-
View User Profile
-
Send Message
Posted Mar 12, 2015@disciple218 @Oneyedrooster
Update your server to a later 1.8 version to fix that. Yes, you should be concerned from a griefability standpoint.
@Nelinos
Sorry I don't think so - as far as I can remember, none of the 1.7.10 versions had that feature.
@ridddle
Yes, and unfortunately I can't fix it. In my opinion, there's a bug in bukkit - when you right click on an animal, it fires BOTH the block click event and the animal click event. So when there's a block click event, I have to also check your in hand item.
-
View User Profile
-
Send Message
Posted Mar 12, 2015I can’t open Ender Chest in someone’s claim (or use any other block that otherwise is public like crafting table) if I’m holding a dye (any). This is probably related to cancelling event on sheep, right?
https://v.usetapes.com/4ZWuJbCAFi
-
View User Profile
-
Send Message
Posted Mar 11, 2015@Primerblock
Is there something you can tell me about what i posted it has been doing that in my console ever since the update need this to stop i think it is causing my server to crash several times since the update.
-
View User Profile
-
Send Message
Posted Mar 10, 2015I'm getting this EventException when starting up my server, should I be concerned?
http://pastie.org/10016400
-
View User Profile
-
Send Message
Posted Mar 10, 2015hi is it posible to safe the whole main world like SurvivalRequiringClaims for minecraft 1.7.10? i try it with the global deny flag from worldguard but if i claim a land with griefprevention i cant build inside so it would be rly rly cool if some1 can tell me how players can only build in their claims in mc version 1.7.10 without the "Creative"
thanks
-
View User Profile
-
Send Message
Posted Mar 9, 2015@bigscary
OK that at least give me an idea where the wrong UUID is coming from. From the account I did find with the wrong UUID I can fix it by doing a search and replace across all the land claims with the correct UUID. Right now I'm creating a UUID vs username sanity check script to see if I can find any more corrupted UUIDs. Probably won't do anyone else any good because I have written it in tcl. I think the nicknamer plugin corrupted GriefPrevention or GriefPrevention got confused by nicknamer and created a whole bunch of player accounts with invalid usernames.
-
View User Profile
-
Send Message
Posted Mar 9, 2015@Ragnorok98
You can use the griefprevention flags plugin for that (the monsters thing). As for allowing pvp in ONLY land claims, I don't think so, but you can ask the GP flags developer to add it.
@PrimerBlock
The data comes from your "playerdata" folders inside each world folder. If you delete them, however, your players will lose their inventory and their locations in the world, among other things.
@GodsDead
I'd say just drop any index you've got for GP tables.
@Pippl
I will try to reproduce that problem on my end to investigate. THanks for telling me about it. :)
@iamthereaper89
There's a permissions node siegeimmune (see permissions reference page) to make a player immune to /siege. Or, you can use administrative land claims for your shops. Or, you can ask players to build shops in another world where GP's pvp rules don't apply, which means there would also be no /siege.
@Blokizaki
Please share your config file content, and also the name of the world(s) where you have this problem.
GP never needs worldguard to work.
-
View User Profile
-
Send Message
Posted Mar 9, 2015@iamthereaper89
What if you used WorldGuard in your shop region to disable the /siege command? That should take care of that problem and still allow siege mode elsewhere.
What I would like is a permission for the siege command. Maybe is already exists but I could not find it.
-
View User Profile
-
Send Message
Posted Mar 9, 2015Recently, in some Survival mode (or worlds) a broken block doesn't drop. Removed various plugins and it appears it's GriefPrevention causing the issue. I'm using Spigot 1.8, GP 11.0.1 and WorldGuard 5.9. Anyone know if GP 11.0.1 needs WG 6.0 to work?
Would love to keep GP on my server. Posted a ticket here 2 days ago but thought some other folks might know the answer or a fix (while a wait for a ticket response).
Anyone else have a similar issue and got GP working again?
-
View User Profile
-
Send Message
Posted Mar 8, 2015@Oneyedrooster
Hey Oneyedrooster! Next time use a pasting service like pastebin.com or pastie.org instead of posting your whole log file.