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 6, 2013Would you guys be open to expanding the permissions some Mainly in terms of the trust commands?
Currently every thing is grouped into the one node that's given by default, All commands are checking that one node. That makes Taking any trust command off a player impossible ( with out editing plugin.yml and sticking it back in.)
What I would like to see Is a Node for each trust type and then that being a child of the current node.
I personally Have already Done some changes to my plugin.yml allowing me to achieve the outcome i wanted but id rather not have to do it every plugin update i do. And it would be fully backwards compatible.
If need be I can even make the changes and Pass the file back.
The end Result would be Server owners having more Control with out breaking any thing, A server owner would then be able to negate a single trust command from his/her Permissions manager.
-
View User Profile
-
Send Message
Posted Aug 5, 2013@Smac3223
Even broad ETAs can be difficult when talking about volunteer work. For one thing people have lives outside of Bukkit, but more importantly, if you've ever done anything like this you will quickly find that no matter how many "disclaimers" you post about your ETA being a broad estimate, people will try to hold you to it like it was written on tablets upon Mount Sinai. It's easier not to give ETAs. Sadly some people don't do that, but it only take a few to ruin it for everyone.
@zero80472
Nothing in Bukkit 1.6 or what so far has come in GP 7.8 dev builds will break past versions of GPFlags, can't speak for Real Estate.
-
View User Profile
-
Send Message
Posted Aug 5, 2013@BC_Programming
All the third paragraph says really is it's being worked on. I realize there's lots of testing and bug fixes that need to be taken care of but what I think most of us are mainly looking for is some sort of ETA.
Even a broad one. Just something to look forward to instead of simply sitting by checking morning and night hoping it's been updated =/
-
View User Profile
-
Send Message
Posted Aug 5, 2013For those with update concerns: read the main page description. The third paragraph specifically answers that question.
-
View User Profile
-
Send Message
Posted Aug 5, 2013Not sure if this is me only. (Dev build #148) seems I cannot block players from teleporting away from combat. Commands are properly set in the config, but does not seem to block. Curious if this also happens to others?
-
View User Profile
-
Send Message
Posted Aug 5, 2013@zero80472
Also wondering this. If there isn't, any ETA on the update?
Server I play on is mainly just this and Population Density so we're kinda all waiting for an update or something
-
View User Profile
-
Send Message
Posted Aug 4, 2013is there a 1.6.2 version in the works or can i use a older version (i also use gp Realastate and gpflags ) would thise cause problems as well ?
-
View User Profile
-
Send Message
Posted Aug 4, 2013@BC_Programming
Oh, yes, I'm using 7.7, not a dev build.
-
View User Profile
-
Send Message
Posted Aug 4, 2013@AmicusMCS That is not from GriefPrevention.
I Say this based on the fact that neither message appears anywhere in the entire codebase...
-
View User Profile
-
Send Message
Posted Aug 4, 2013Hi,
how can i set a bigger number of blocks that players can claim?
-
View User Profile
-
Send Message
Posted Aug 3, 2013I updated to the dev build #150 and my CPU spikes from around 10% to 100% every 15 seconds. It happened with the the #149 also. I updated Bukkit and a few other plugins and finally figured it out. I think the build I am back to is 142 which runs normally. I will do more testing. Let me know what you need from me to help out.
-
View User Profile
-
Send Message
Posted Aug 3, 2013Can i remove certain features? such as they have to pick up an item to pvp?
-
View User Profile
-
Send Message
Posted Aug 3, 2013@Diemex
Just so you know, we are re-designing the mySQL database from the ground up for the next release, so we'll make sure to include your fixes with it.
-
View User Profile
-
Send Message
Posted Aug 3, 2013@Diemex
I saw it. I do not comment on or deal with Pull requests anymore.
-
View User Profile
-
Send Message
Posted Aug 3, 2013Hey I opened a pull request https://github.com/Tux2/GriefPrevention/pull/9 a week ago and have not gotten a response yet. Maybe you didn't see it?
-
View User Profile
-
Send Message
Posted Aug 3, 2013@BC_Programming
Seems to work perfectly. Thank you so much! One step closer to official release.
There's only one unhandled error that occurs when you select MySQL but GriefPrevention can't connect to the database or the MySQL information hasn't been entered yet, but that's no big deal.
-
View User Profile
-
Send Message
Posted Aug 3, 2013Hi, i have a problem. I turned FireSpreads ans FireDestroys to true, but fire still doesnt spread or destroy. What am I doing wrong? :/
-
View User Profile
-
Send Message
Posted Aug 3, 2013@AmicusMCS
should be fixed in #150. In the meantime you can manually populate the dataconfig.yml (I gave the wrong filename previously) for mysql:
-
View User Profile
-
Send Message
Posted Aug 2, 2013The latest dev build (149) returns this error when mysql is chosen rather than flatfile and the datasettings.yml file doesn't populate.
http://goo.gl/UYqRrI
-
View User Profile
-
Send Message
Posted Aug 2, 2013I know you're busy but I thought id just let you know, using the restore nature in my flatland creative world does not clear anything, and it also makes floating stone and grass platform about 20 blocks above the ground.