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 Jul 6, 2013Need to be added to claim to trade with villagers, not sure if intended or not. Just saying :) (using latest dev build)
-
View User Profile
-
Send Message
Posted Jul 6, 2013@BC_Programming
Good call on the worldguard - I looked into the world folders via worldguard and found that each of my worlds had different permissions on TNT/Creepers. Removing the config for them and replacing it with nothing has enabled grief prevention to handle TNT.
Much appreciated.
-
View User Profile
-
Send Message
Posted Jul 5, 2013After updating to 1.6, all my players are receiving the "You must wait 25917265 more minutes before logging-in again." error. I have tried giving them the "griefprevention.spam" and "griefprevention.loginspam" node with no luck. I have also tried /pardon Player... Any ideas?
This is with the newest Bukkit build #2807 and your dev build #116
Edit I reverted back to the old version I was using, with no issues, so who knows!
-
View User Profile
-
Send Message
Posted Jul 5, 2013@xOMutleyOx
You could try disabling essentials or worldguard and see if that fixes it. If I had to guess, I'd imagine it may be a worldguard conflict. I'm not familiar with it myself, but I imagine it has some TNT protections of it's own which may be conflicting in some way with GP.
@MistPhizzle
Should be fixed in the next/latest dev build (#116, if it succeeds).
It was because it changes the login cooldown setting from minutes to seconds. If it finds a minutes entry it will multiply it by 60 and use it as the seconds setting, but it was saving that seconds setting as minutes, so every time the server started the login timeout would multiply by 60.
-
View User Profile
-
Send Message
Posted Jul 5, 2013I'm having issues with the TNT for below sea level only. Wonder if you could help?
I have these two nodes set to true as you would expect: BlockSurfaceCreeperExplosions: true BlockSurfaceOtherExplosions: true
yet Creepers and TNT still work on the surface. I'm thinking this might be a conflict with another plugin - perhaps Essentials or Worldguard?
Should those to be set to block or allow damage via creeper/tnt? I would have thought that they all need to be set to allow, allowing GP to handle it, but clearly not?
Advice appreciated!
-
View User Profile
-
Send Message
Posted Jul 4, 2013I have the Spam features disabled per world (Using Latest Dev Build) and it's having players wait like 5 days to log on.
I just used the permission node to bypass this, but could a fix be implemented soon?
-
View User Profile
-
Send Message
Posted Jul 4, 2013@ThePMSBeast
you can use public as the name for /accesstrust, /containertrust and /trust to give everybody the specified permission.
/accesstrust allows people to use buttons and levers.
/containertrust allows people to use buttons and levers and containers
/trust is the build trust and allows building in addition to both of the above.
-
View User Profile
-
Send Message
Posted Jul 4, 2013I have a question, is there a command for trust all? Say i make a chest shop inside my claim, but i don't want to keep adding each person individually with /trust, is there a way to allow people to use chests/door etc, but not be able to build? And if so, is it under admin or something?
thanks, great plugin btw
-
View User Profile
-
Send Message
Posted Jul 4, 2013@deancohen1994
Can you write on signs in areas claimed by Grief Prevention but not WorldGuard? If so it's a WG problem and should be posted on its page.
-
View User Profile
-
Send Message
Posted Jul 4, 2013sorry this may be a problem on my part but i cannot write on signs, i am owner with full perms, i can only write signs in unclaimed areas and areas without worldguard, how can i allow myself to write inside worldguard? thanks
edit, seems it only prevents me making wall signs?
thanks
-
View User Profile
-
Send Message
Posted Jul 4, 2013@TJW28
Would it be reasonable to request a zip (via PM) of your 'GriefPrevention' folder from /plugins? If I can replicate the issue, I should be able to figure out the cause and fix it :D
-
View User Profile
-
Send Message
Posted Jul 4, 2013@BC_Programming
Sorry to "bug" you again, but, once more, I lost Most claims when updating to #113.
This time, not alll claims disspeared, but the majority did. I can see no errors in the server logs, so nothing to direct you to Im afraid.
-
View User Profile
-
Send Message
Posted Jul 3, 2013@TJW28
GriefPrevention.PvP.Enabled wasn't in the configs because I forgot to write it to the config- my mistake. Should be fixed in #112.
-
View User Profile
-
Send Message
Posted Jul 3, 2013@BC_Programming
Yes, you understood me correctly. When i updated to dev build #108, everything worked well, claims were read fine. It was only when i updated to dev #110 that the claims somehow got removed.
I noticed the "UnrecognizedOwner" setting, and have since changed that to false.
Just one further thing, Im not seeing a GriefPrevention.PvP.Enabled option anywhere. I had assumed it would be added auto on reboot, so, do I need to regenerate the world.yml files to see it ?
-
View User Profile
-
Send Message
Posted Jul 3, 2013@n33dy1
Yes. Hopefully before it is available as a Beta I will be able to add some automatic data migration. (Right now it uses a separate data folder that would have to be copied manually but I'll probably add logic that copies the old data folder to the new data folder if the new data folder doesn't exist but the old one does).
@TJW28
Oh... Interesting. This could very likely be the same issue that is presented in this Ticket:
http://dev.bukkit.org/bukkit-plugins/grief-prevention/tickets/216-claims-being-deleted/
And do I understand you correctly that, when you restored the data from a backup, the version you had updated to (#110) was able to read the Claims? Or did you have to rollback to a previous version as well?
I suspect this could also be related to the new "GriefPrevention.Claims.DeleteWithUnrecognizedOwner" option, which currently defaults to true and will delete claims on load if there is no playerData for the Owner specified. I will change the default for that option to false, we'll see if that fixes it.
Obviously these are the exact sort of problems we want to eliminate, Thank you for being a guinea pig! :D
-
View User Profile
-
Send Message
Posted Jul 3, 2013@BC_Programming
This is my confusion, I already did as you suggest on a previous dev build ( #108 ). I simply updated to dev build #110 and on reboot, the claims got lost. So the server was already running 7.8.
I will see if it happens again, and report back if it does.
ps: Keep up the great work ;)
-
View User Profile
-
Send Message
Posted Jul 3, 2013I just setup a new dedicated server. Would you recommend I use 7.7 for now and when 7.8 comes out just drag the .jar in and restart my server? Is that how updating works?
-
View User Profile
-
Send Message
Posted Jul 3, 2013@TJW28
The dev build uses a different data folder.
7.7 uses /plugins/GriefPreventionData/
Dev builds (and 7.8) use /plugins/GriefPrevention/ as the data folder.
The reason for this is that data migration is one-way: once 7.8 loads the configs, claims, and player data, that's it- you can't go back to 7.7 with that data. Therefore I figured it would be sensible to require a more active role in the migration beyond dropping the jar. I recommend copying the current GriefPreventionData folder in plugins to a new GriefPrevention folder, that way if anything goes wrong you will at least have the data you had when you first switched to the later build.
Sorry for the confusion.
-
View User Profile
-
Send Message
Posted Jul 3, 2013@BC_Programming
Thanks for the clarification
I have just updated to the latest dev build, but, somehow, ALL claims were removed. I have had to revert to a backup i made, but how can i prevent this from happening again.
No settings were changed from the default claim expiration, so Im at a loss as to what happened. Ive run GP since it earliest versions, and have never had this happen before.
-
View User Profile
-
Send Message
Posted Jul 3, 2013@MarinaBrandsen
Hi, That sounds like this currently open Ticket:
http://dev.bukkit.org/bukkit-plugins/grief-prevention/tickets/212-could-not-pass-event-async-player-chat-event/
If you could provide the Stack Trace in that Ticket, it would really help track down this issue. thanks! :)