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 May 23, 2013Somebody know about this? Everyone in my server got disconnected :/
-
View User Profile
-
Send Message
Posted May 22, 2013@Senophoe
Likely. I've started attempting the major refactor.
Here is some information on my current plan.
Currently, as we all know, all configuration data is in config.yml. Now, there are two approaches to world-based configurations: either we can staple all that information into that one configuration file- eg. separate much of the configuration into separate sections per world.
However I've gone a different route so far; config.yml will be used for "core" configuration options. Most of the actual configurations, such as the maximum claims a player can make, the maximum size, etc. Will be world specific. They will be stored in /plugins/WorldConfigs/<worldname>.cfg
There will almost certainly be a way for "default" settings to be specified ahead of time. Most likely, config.yml will be used for configuration files that aren't found. This, ideally, will make the migration automatic, since in current versions all such information is stored there.
There will be some changes, of course; some of the configuration options in config.yml currently list things such as seigable worlds, PvP worlds, etc. which will be single options in each specific world configuration.
The biggest change of course will come to the API; any plugins that currently access the public configuration fields will break, since those options will be moved. I don't know how many plugins this will effect, but the change won't involve extensive revisions to those plugins to support the new "config API" as we could consider it.
The main idea is to make it both more flexible- so options can be more granular per-world; as well as try to cleanup the configuration options themselves to try to make them less confusing. I'll probably think of a more flexible way to handle where explosions are allowed, though it will probably be similar to the suggestion.
-
View User Profile
-
Send Message
Posted May 22, 2013@BC_Programming
I get it. Should I expect those improvements on a future build of GP?
-
View User Profile
-
Send Message
Posted May 22, 2013@Zilacon
Technically, this is an issue with PHPMyAdmin. Tables that lack a Unique Key are just as valid as those that have one.
That said, I'm surprised that it doesn't already use the ClaimID as the Primary Key.
In the meantime, in phpMyAdmin you can just click on 'add index' on the table structure page below the listed fields.
-
View User Profile
-
Send Message
Posted May 22, 2013@Senophoe
Confusing. GP already has way more special case configuration logic- "use this option, unless this other option is set or this third option is larger than some other option" type logic. My current aim is to practically redo a lot of the configuration to allow for World-specific options, as well as coalesce a lot of "hacky" options that are added. Take for example your idea. The best way to implement it would be to completely redo all the configuration options that are explosion related to allow for configuring which kinds of explosions can occur inside and outside of a claim. I could do that as-is but it would break every single existing configuration that uses the existing explosion settings.
-
View User Profile
-
Send Message
Posted May 22, 2013@BC_Programming
Could you guys fix this issue with your databases?
When i try to "edit" GP's database be it deleteing, or changing a entry in the database there is no checkbox to select or edit anything.
Also this error is shown on PHPMyAdmin:
This table does not contain a unique column. Grid edit, checkbox, Edit, Copy and Delete features are not available.
Fixing this would be awesome!
-
View User Profile
-
Send Message
Posted May 22, 2013@BC_Programming
What are your thoughts on this issue?
http://dev.bukkit.org/server-mods/grief-prevention/tickets/152-better-explosions/
-
View User Profile
-
Send Message
Posted May 22, 2013@Simo389 It would be no more our responsibility to hook into WorldGuard and add this than it would be WorldGuard's responsibility to hook into GriefPrevention and add this (eg. disallow creating new claims).
It would make sense as a separate compatibility plugin, but there is no reason to force every user of GriefPrevention to have to run this WorldGuard compatibility code (or the appropriate conditions) when they don't use it, anymore than it would be reasonable to force every user of WorldGuard to run GP compatibility code.
-
View User Profile
-
Send Message
Posted May 21, 2013@Simo389
a GP adminclaim with public build trust seems like it would have the same effect.
-
View User Profile
-
Send Message
Posted May 21, 2013Very nice plugin please could we have a config option to toggle pvp chest access plox ! :)
-
View User Profile
-
Send Message
Posted May 21, 2013Could there be an expiration setting where it regenerates everything in the claimed region?
-
View User Profile
-
Send Message
Posted May 21, 2013@applethegreat
According to the commit history it was added in version 7.1.2.
-
View User Profile
-
Send Message
Posted May 21, 2013The server I play on must have an older version because that command is not availabe. :-(
I also didn't see that command in the list of commands supported by the plugin.
-
View User Profile
-
Send Message
Posted May 20, 2013@applethegreat
/claimslist is already a command and lists top-level claims.
-
View User Profile
-
Send Message
Posted May 20, 2013I'd like to see a way to identify all your claims. Right now it's difficult for me to remember where I've made claims and I have to keep track of them manually.
One suggestion would be a command like '/listclaims' which would give a list of the center point of all of your top level claims and possibly your subdivided claims however I don't use subdivided claims so I don't know how simple that would be.
-
View User Profile
-
Send Message
Posted May 19, 2013Just sent a suggestion regarding the TNT issue: http://dev.bukkit.org/server-mods/grief-prevention/tickets/152-better-explosions/
-
View User Profile
-
Send Message
Posted May 19, 2013@DevVynlar
That's not it. /ClaimExplosions will only protect/deprotect the claim itself against explosions. Areas outside the claim will not change. I want TNTs not to work outside claims, and work inside claims.
@JerryFord
Thanks for that, Jerry. I set world: -1 to world: 256, and now I can use TNTs at any altitude. But still, I want them not to work outside claimed areas, and work inside claimed areas. I'm messing with the configs, but no luck so far. Any suggestions?
-
View User Profile
-
Send Message
Posted May 19, 2013Suggestion: /showclaims will provide visuals of all claims in a configured radius around you. Would be very useful to me.
-
View User Profile
-
Send Message
Posted May 19, 2013@Senophoe
/ClaimExplosions Toggles if explosions are allowed in the claim.
Would this be what you are looking for?
-
View User Profile
-
Send Message
Posted May 19, 2013Senophoe
Multiple items in the config that could be altered for above ground explosions:
SeaLevelOverrides:
world: -1
world_nether: -1
world_the_end: -1
BlockSurfaceCreeperExplosions: true
BlockSurfaceOtherExplosions: true
Explosions by claim owners can be done with additional command, although must adhere to configuration.
BC-
Thanks for the info.