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 8, 2013Time to put some dev builds into action. Quick question though - how often do new builds on Jenkins come out? I don't want to be updating all the time.
-
View User Profile
-
Send Message
Posted Jul 8, 2013People can take saddles and armour off of horses, Will this be fixed when the plugin updates?
-
View User Profile
-
Send Message
Posted Jul 8, 2013@Alshain01
Thanks! I actually only recently got to learning those sorts of bits of the config API (Through Survival/Chests of all things, because I couldn't hack it like I did for groups) and it never occurred to me to rework the group stuff. Or maybe it did and I'm lazy :P
-
View User Profile
-
Send Message
Posted Jul 8, 2013Hey BC, I was looking at your groups implementation. If I might offer a suggestion, you can actually get your groups list in code without needing to have them defined twice. It leaves far less room for human error. I would suggest removing the Names: node and using this instead:
That will return all of your group names without the duplication. John did this for GPFlags clusters and it worked beautifully.
-
View User Profile
-
Send Message
Posted Jul 8, 2013Well, muted me when i put :yaoming:
-
View User Profile
-
Send Message
Posted Jul 8, 2013@2coolforu22
That setting is for enabling and disabling Spam. Claims themselves are toggled with the GriefPrevention.Claims.Enabled setting.
-
View User Profile
-
Send Message
Posted Jul 8, 2013I can't find "GriefPrevention.Spam.Enabled" to true for each world." I need to disable claims for my Factions Pvp
-
View User Profile
-
Send Message
Posted Jul 7, 2013@deleted_9935739 2147483647 is the highest value it will successfully parse.
Why shouldn't they be per world? Some servers may be set up in such a way that more "trusted" players have access to worlds that other players do not. For example a server may be setup in such a way that players start in a "beginners" world, prove themselves on the server, and then can enter the "main" world; and dedicated players, who clock a lot of time and are generally upstanding members, may be granted permission to enter a even more 'exclusive' world. The worlds that require more effort are likely to require less "Grief Prevention" overall, and this includes things such as the spam features.
-
View User Profile
-
Send Message
Posted Jul 7, 2013@BC_Programming
What is the highest value supported?
Why are there separate configs such as spam that shouldn't be per world?
-
View User Profile
-
Send Message
Posted Jul 7, 2013@deleted_9935739
You can set MuteThreshold, KickThreshold, and BanThreshold to extremely high values. (or just Kick and Ban in this case).
-
View User Profile
-
Send Message
Posted Jul 7, 2013@BC_Programming
"To disable spam stuffs set "GriefPrevention.Spam.Enabled" to true for each world." Could you elaborate? I don't want to completely disable everything spam related, just the banning and kicking. Setting the threshold to -1 didn't work either.
-
View User Profile
-
Send Message
Posted Jul 6, 2013@deleted_9935739
To disable spam stuffs set "GriefPrevention.Spam.Enabled" to true for each world.
Don't remove RequiredPermissions. If you want to remove the requirement for permissions, don't give it a value.
@LoneWolves32
use /ignoreclaims.
-
View User Profile
-
Send Message
Posted Jul 6, 2013Hi I got the plugin for my server but because im an admin I want to be able to have infinite claim blocks so is there anyway to make this possible
-
View User Profile
-
Send Message
Posted Jul 6, 2013How can I disable spam ban and kick? Setting the thresholds to 0 didn't seem to do the trick. I also can't seem to remove the "RequiredPermissions" section from "FireSetting" It just gets put back on restart.
-
View User Profile
-
Send Message
Posted Jul 6, 2013@2coolforu22
I'm not sure what you mean by "disable worlds". Claims can be disabled in each world by changing GriefPrevention.Claims.Enabled to false in the world configuration.
-
View User Profile
-
Send Message
Posted Jul 6, 2013GriefPrevention-118.Build how to disable world's ? Should I usually use pex commands to do this. But for some reason when I upgrade it allow people to bypass the permissions ..
-
View User Profile
-
Send Message
Posted Jul 6, 2013@roggbart Intended. You can change the rules in the world config by changing the "VillagerTrading" Rule.
Settings do not 'import' from other files except for the template file.
@Jadedwolfs
With 7.7 you can tie horses to a fence in your claim to secure them (And don't secure then to fences in other people's claims or they will be stuck). 7.8 (the dev build) should prevent both riding and inventory access of a horse within unowned claims, as well as the use of Leashes and Name Tags.
@roggbart
Seems I had a few comparisons going to wrong way. Which would have prevented the creation of any claims at all with a limit set. Should be fixed in #119.
-
View User Profile
-
Send Message
Posted Jul 6, 2013Perplayer limit seems not working correctly in latest dev build: My limit is set to 10, players can now have max 1 claim.
-
View User Profile
-
Send Message
Posted Jul 6, 2013@BC_Programming
I don't see any commits about not letting non claim access people not use or ride horses. Is this going to be a thing or option to prevent access of vehicles inside claims? (So people can not just ride off with your horse out of the claim)
-
View User Profile
-
Send Message
Posted Jul 6, 2013Question concerning world configs: Do settings not added in say world_the_end.yml import from world.yml?