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 Nov 19, 20122012-11-19 13:59:15 [INFO] GriefPrevention: Error: PvP Configuration: There's no world named "events". Please update your config.yml
2012-11-19 13:59:15 [INFO] GriefPrevention: Because there was a problem with the database, GriefPrevention will not function properly. Either update the database config settings resolve the issue, or delete those lines from your config.yml so that GriefPrevention can use the file system to store data.
Can you please change both of these messages to [WARNING] and default SQL connection errors to use file claims?
@bigscary
Which commands were you thinking of adding the claim IDs to? Looking at the code, you should have a claim object right?
As a software dev, I also suggest that you refactor your code to make it easier to maintain. If it's still open sourced. I might help pitch in to help if you have room :P
-
View User Profile
-
Send Message
Posted Nov 19, 2012Hooray, Bukkit 1.4.5 Beta is out :)
-
View User Profile
-
Send Message
Posted Nov 19, 2012Do you know why Bukkit haven't approved v7.0.1 yet, bigscary?
<edit> Only issue I have found with GP v7.0.1 so far is a typo in the messages.yml:
BuySellNotConfigured: Text: Sorry, buying anhd selling claim blocks is disabled.
It's pretty damned perfect in any case! Great work. Thanks a million. :)
-
View User Profile
-
Send Message
Posted Nov 19, 2012@Ugpzt
That depends on how the item frame shops plugin does things. Regardless, you can probably configure GP to be compatible, for example by turning off its protections in the item frame shop area so that the item frame shop plugin can implement its own rules (you'd use /trust public for this).
@krisdestruction
I know I have the data. The hard part is updating all the various slash commands to accept IDs without breaking other functionality in those slash commands. They've become somewhat complex already due to the applying changes to all claims versus only the local claim, four different permissions levels as well as a command to remove permissions, support for both online and offline players, support for permissions-based trust with and without brackets, and support for "all" and "public".
@aczchef
If you want pvp disabled server wide, do it in server.properties. Then GP will allow you to have an empty pvp world list.
@chrishillz
If your server is simple-ish, meaning you don't have different play styles on different worlds, then the defaults are perfect. If you have a few worlds where pvp is enabled and some others where it's not, or you have some survival worlds and some creative worlds, then you'll have to go to the config file and tell GP how to treat each world. You'll see when you get the config file open, I hope it will be easy for you to understand without having to read lots of docs or ask lots of questions.
-
View User Profile
-
Send Message
Posted Nov 18, 2012@chrishillz
Config everything to your needs. Go through it line by line and make sure features you need are enabled and those you don't aren't enabled. It's got a few buffed features so you might not need it on your server, disable those if needed.
@chrishillz
Don't put anything then.
-
View User Profile
-
Send Message
Posted Nov 18, 2012By the looks of this, this looks revolutionary... I just watched this video and will most likely have this take over the anti grief for www.minecraftnation.org :D
Edit: Any tips to edit in the config once I get it going? What should each server admin customize on the first few runs?
-
View User Profile
-
Send Message
Posted Nov 18, 2012since the config wont let me put 'nothing' under pvp.worlds could we have a pvp.enabled option to disable pvp protection server wide?
-
View User Profile
-
Send Message
Posted Nov 18, 2012@lordskout
I agree that we need an iteration of this for forge. It would be a great addition for the FTB server.
@bigscary
Any way you can start making feature requests to Forge devs?
When using a file based format, you already have IDs for each claim. Can you just use this ID instead? http://i.imgur.com/QlUUO.png
-
View User Profile
-
Send Message
Posted Nov 18, 2012Thank you for the updates, I am looking ahead to shops with itemframe, would they be compatible?
-
View User Profile
-
Send Message
Posted Nov 18, 2012@bigscary
Thanks!
The page is showing 7.0 as the latest. Is there a dev site I can get 7.0.1?
-
View User Profile
-
Send Message
Posted Nov 18, 2012@bigscary
Thanks bigscary!! :D
I'm running CraftBukkit 1.4.5-R.01 (#2480) and there's not much to report in the way of bugs. In fact, there was a scare with some non-sticky sticky pistons but that was down to PEBCAC. :P
Great work. Thanks again! :)
-
View User Profile
-
Send Message
Posted Nov 18, 20127.0.1 Fixes!
@krisdestruction
I don't think I want to do that (regarding claim IDs for remote management). It seems awkward and probably very, VERY infrequently used. And it would be substantial work for me to implement.
@CraftThatBlock
No offense intended, I hope you understand - giving my skype to you guys would eventually result in a message every few minutes. I'd rather you all referred to the documentation and helped each other, and allowed me to chime in on an as-needed basis here in the comments. :)
@Blazex224
Yep. See config file. Hybrid ban. Why is it annoying? If a player has played before, he should not be banned based on his IP address. Do you see this is not the case?
@notif
Thanks, found and fixed. :)
@ekemsend
It's a problem with ModifyWorld, I think. Another posted a similar issue, and he too was using ModifyWorld (in his case, GP was hardly in the logs at all).
@Zilacon
I can't help you diagnose your database problems. Anyway, GP works best without a database. I only put the database option in because some people just don't believe me when I tell them flat file mode is best for this plugin.
@add5tar
Sorry no, it's a bit of a privacy issue I think. If you want to check /trustlist as an admin, enter /ignoreclaims mode before issuing the command.
@ManBeastPigDev
Sorry, pvp in a pvp world not a grief issue, unless it's spawn camping which is already fixed by GP. Actually these flags might result in griefers placing land claims as a strategic camping ground (turning off pvp in a convenient spot where they can watch for opportunities to kill other players).
@Blorp6161
If your world is in the "creative rules worlds" list, then item dropping isn't allowed because it's a potential way to lag and grief a creative server. If your playres aren't in creative mode in that world, remove it from the creative rules worlds list in your config file.
@Azurago
Please provide more details. What specifically are you trying to do with redstone outside your land claim? If it's using a dispenser to dump water of lava, that is by design because it would allow griefers to dump water and lava where they shouldn't.
@xbenas
Someone's working on an extension plugin to allow flags not related to anti grief. :) Stay tuned, I will post a link here if/when it's available.
@lordskout
Forge can't do everything I need to support this feature set yet. Even if it could, I don't have enough free time to develop and maintain two versions of this more than 10k line plugin. Maybe one day forge will replace bukkit, but that's like betting that macs will replace PCs. If that happens, I will port. You're welcome to try porting yourself. :)
-
View User Profile
-
Send Message
Posted Nov 18, 2012Would love to see a Forge iteration of this. So done with CB.
-
View User Profile
-
Send Message
Posted Nov 18, 2012I've read your reply. Good points.
But what about administrative claims? Maybe you should put a "flag ability" to them since (mostly) only OPs can make those and they are very few so the hit on performance would be minimal. The most requested flagies are PvP and MOB spawning. What ya' think about that?
-
View User Profile
-
Send Message
Posted Nov 18, 2012I want to have the guest on my server not be able to use a chest or shovel to make a grief-protected zone. Is there a permission node for that?
-
View User Profile
-
Send Message
Posted Nov 18, 2012Redstone isn't usable outside a claim. Is this normal or a feature? If its a feature can it be disabled?
-
View User Profile
-
Send Message
Posted Nov 18, 2012@LeeTheENTP
Thanks for the reply, but it doesn't seem to work. In the plugin.yml it says you need "griefprevention.claims" but that also doesn't help and the docs say that permission is enabled by default.
I will make a ticket to request a special permission for this.
-
View User Profile
-
Send Message
Posted Nov 17, 2012I have Disabled Grief Prevention on my server with a plugin and found out that Grief Prevention is not letting me drop items i don't know if this is a bug or a i need a perm node [ If i need a perm node, please tell me what the node is]
Thanks, Blorp6161
EDIT: I am also going to say that this is not a fully configured and im still working on it at the moment
-
View User Profile
-
Send Message
Posted Nov 17, 2012@add5tar
I'm pretty sure you just give all users the griefprevention.trustlist permission node, but I may have the node wrong.
-
View User Profile
-
Send Message
Posted Nov 17, 2012@add5tar
I agree, i have a town with /subdivideclaims
but i can't find out who owns the claims.
That would be useful, as i've sold one twice now :)