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 Oct 20, 2014@asonofashadow
See "Claim Security" at http://dev.bukkit.org/bukkit-plugins/grief-prevention/pages/setup-and-configuration/ Also look in your config file. I think there might be additional options of use to you.
-
View User Profile
-
Send Message
Posted Oct 20, 2014Hello, I am really loving your plugin. I do have a dire request ( to my small world ;] ) request if it is at possible for the next update or hotfix.
I need players to be prevented from griefing, on purpose or not, yet still be able to use doors, chests, levers, ETC. without having to trust each individual player in a marked plot. If there is already a way to globally trust doors, containers, switches, ETC, with preventing block placing and destruction I will be over joyed and primed for your reply.
If this feature is not already present, then here is my request:
Could you please add, either a new feature to the trust system, or admin plots if need be, that would put someone into Adventure Mode when entering said plot, then back to Survival after leaving, or whatever their previous gamemode they were in.
So in the end a castle could be setup to be raided, monster battled and defeated, but no breaking or modifying of it's structure, in a survival server, oh shoot even a creative one.
Thank you so much for your work to the community so far and I hope all is well for you.
edit:
One last thing, it is actually possible for a player to get stuck in a land claim. I have a protected village and people have tried to follow them into the houses only to be locked in, ROFL. I personally find it quite amusing, but this is another thing that brought on this request.
-
View User Profile
-
Send Message
Posted Oct 20, 2014@bigscary
Well I have no idea what I'm looking at :D I'm just looking at the percentages :P
-
View User Profile
-
Send Message
Posted Oct 20, 2014@Turbotailz
You can delete the old "griefprevention" folder. You need only "griefpreventiondata".
Yep, I know it's not ideal. There was a time when there was no upgrade option at all from the beta versions produced by BC. So this is a big improvement, and recustomizing your config file is a one-time thing.
@xSnowBlitzz718
Send me your logs from the first time you booted with the updated version. There should have been a migration process which turned all your old data (player names) into player UUID's. For now, you should restore a backup and go back to using the older version until I figure out what went wrong for you.
@sparts
What's build #36? Did you grab something from the continuous integration server, which we're not using anymore? If yes, then you got an old build with bugs. Take your builds from our uploaded files (here on dev.bukkit.org). Unfortunately, I do not have access to take down the CI server, or fix it. I tried to contact Tux but he's been radio silent for weeks now.
I think you should leave the expiration off for a while (a few weeks at least) to give your current players time to log in, which updates their last login time with grief prevention so they won't have the wrong one anymore. Then you can turn the expiration back on, and only those players who haven't played while you had it disabled will be impacted.
Villagers are not protected from monsters, only from players who don't have permission. If you're observing something different, let me know and I'll investigate.
@dutchrastacraft
I disagree. :) The main problems are still interact, block break, and block place. I don't have a solution for login/logout (other than pushing that work to other events, which doesn't change anything overall). However I have a fuzzy idea about what I can do to reduce the three big ones mentioned above.
Thanks for the timings!
-
View User Profile
-
Send Message
Posted Oct 20, 2014Timingsssssss! http://timings.aikar.co/?url=8604095
Main problems: Login, Logout & Cleanuptask.
-
View User Profile
-
Send Message
Posted Oct 20, 2014I updated to build #36 and about two hours later a message in console popped up saying multiple players claims have expired. They are active and their claim blocks also reset.
Also on side note, can you add an option to allow mobs to attack villagers, iron golems, etc? I see ProtectCreatures: true but I don't want to shut if off if it affects animals as well.
edit: It set all the expiration times to 0 to stop more from happening. I noticed when I investigate a claim with a stick it says they have been offline for 379 days. I'm assuming when it converted the players to UUIDs, it somehow screwed up the last time they were online, thus making griefprevention think they have been inactive for over 60 days and deleting their claims.
-
View User Profile
-
Send Message
Posted Oct 20, 2014I've updated from an old version 7.7 to 8.5 and when I started the server, all of the claims turned into an administrator claim. When I did /trustlist to check who were trusted, it displayed "someone" several times depending on how many people were trusted. What's going on and How do I fix this?
-
View User Profile
-
Send Message
Posted Oct 19, 2014@bigscary
I have already discussed with a developer about the horses, so I wont say any more about them.
I have another issue I'd like cleared up and could not find an explanation on it - I now have 2 GP folders: GriefPrevention & GriefPreventionData. I assume the GPData folder was created when I updated to 8.4? I have also noticed the settings have been reset, so I need to re-configure it (not ideal btw). What do I need to do to get everything consistent and in the 1 folder without messing anything up? Will be updating to 8.5 as well FYI.
-
View User Profile
-
Send Message
Posted Oct 19, 20148.5 Updates
Why did I make the first change? The config is now (I think) MUCH easier to understand for new installers of GP, and there's a very good performance boost in totally ignoring events in worlds where no land claims exist.
-
View User Profile
-
Send Message
Posted Oct 19, 2014@dutchrastacraft
Yep, that is good news. I'm not sure I believe the Spigot team can handle such a huge task, but I hope they succeed. Will definitely be watching.
@Turbotailz
Does /containertrust not do the job? It includes animals as well as containers (it's supposed to mean "I trust this guy with my belongings, but I don't want him building").
@erik1988
Not sure, but there's a list on the Vault page.
@mcly
/untrust works for permission trust level, like LordDWT said. Thanks, DWT!
-
View User Profile
-
Send Message
Posted Oct 19, 2014@mcly
/UnTrust <Player>
-
View User Profile
-
Send Message
Posted Oct 19, 2014How do I Untrust PermissionTrust?
-
View User Profile
-
Send Message
Posted Oct 19, 2014@bigscary
What are groups created by vault? Is towns in towny vault group? is clans in simpleclans valult groups? If not, could they be? Any other examples of plugins that already use these groups?
Thanks,
-
View User Profile
-
Send Message
Posted Oct 18, 2014@bigscary
Ugh, you're right about /ic working. For some reason it must not have worked when I tried on the day I posted that. But everyone is really sick of they way horses are treated with this plugin. Being able to let people trust others with their horse would be great.
-
View User Profile
-
Send Message
Posted Oct 18, 2014@bigscary
Allright! I'll post timings from time to time here :) Also, epic news has just been announced! Spigot is going to be updated to 1.8, you won't have to convert to sponge anymore :D http://www.spigotmc.org/threads/1-8-progress-check.32792/
-
View User Profile
-
Send Message
Posted Oct 18, 2014@dutchrastacraft
More good news, thanks! I haven't come up with any solution to login/logout, other than just making the numbers look better without actually reducing overall cost. I do have some ideas around further reducing block interact, break, and place, though.
@LordDWT
Thanks for telling me, I'll look into that in a minute.
@erik1988
You make good points. What if I added Vault support, so that groups created by other Vault-supported plugins could be used?
-
View User Profile
-
Send Message
Posted Oct 18, 2014Some players have been complaining about that they can not trust players that are offline anymore, this is players that playing in big groups and have "towns". If it would have been possible to add players to a list like I have suggested earlier this would also solve the performance problem with adding offline players, as well as give the opportunity to add some of them as long as they are part of a group.
-
View User Profile
-
Send Message
Posted Oct 18, 2014@bigscary Just thought you should know. Snow covers the blocks. Making it difficult to see the claim area.
-
View User Profile
-
Send Message
Posted Oct 18, 2014Timings! http://timings.aikar.co/?url=8585983
-
View User Profile
-
Send Message
Posted Oct 18, 2014@JimFoxer
100% agreed!