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 Dec 4, 2014@bigscary
When you try to protect the claim, an error appears because of the missing new blocks (from 1.8) because I'm using the Spigot 1.7.10.
-
View User Profile
-
Send Message
Posted Dec 3, 2014Thanks for updating to 1.8 ! I do have a question though - it seems when right clicking with the stick or the golden shovel to create/check for claims, it fires twice. Not sure why? Running Spigot 1.8, and the Essentials vTeamCity created by the Spigot team. Nothing special beyond those. Pretty vanilla configs, no craziness there either.
Photo of text box inside MC
-
View User Profile
-
Send Message
Posted Dec 3, 2014@bigscary
I posted my data file to the ticket I opened.
I can give you access to the server with the /restart command so that you can see the issue if you would like?
Thanks
-
View User Profile
-
Send Message
Posted Dec 3, 2014@yellolegalpad
Any chance you could zip up your griefpreventiondata folder and send it my way? I'm failing to reproduce your issue on my end.
EDIT: If you happen to also have a griefprevention folder, please send it, too.
-
View User Profile
-
Send Message
Posted Dec 3, 2014@bigscary
The number of claims in the log is correct. I was just trying it out on a test server. Thanks.
-
View User Profile
-
Send Message
Posted Dec 3, 2014@yellolegalpad
Just clarifying - are the numbers you see for land claims in the boot logs correct? Or do you have more land claim (files) than that?
@yohandu30
I'm not sure I understand your question. When in creative world mode, players can build ONLY inside their land claims. In survival world mode, players can build anywhere, and may optionally use land claims to protect their work. Creative/survival world mode is set in the config file for each world. Creative mode should be used for worlds where players (not just admins) are in creative mode - otherwise survival mode or disabled mode should be used.
@LeonardoGamer
I don't understand what you mean by "because of the missing blocks"? I don't want to release a version of GP for an outdated CraftBukkit.
-
View User Profile
-
Send Message
Posted Dec 3, 2014You added the old allowBuild() in the new GriefPrevention build! Cool!
The only problem that the new version is only for the Spigot 1.8, and I'm still using the Spigot 1.7.10 ProtocolHack, and when I use the new version, players are unable to protect the terrain (because of the missing blocks)
Could you put a new build with only the allowBuild() and that works with the Spigot 1.7.10? Thanks! (I always try to compile myself, but, for some reason, everytime that I do this, only on my Local Server works.)
-
View User Profile
-
Send Message
Posted Dec 2, 2014hi, sorry I'm french, my english is ... zero.
Is it possible to prevent players to break blocks outside the area they shall protect ??? Example, protects the world, and they can not build THAT in their field.
-
View User Profile
-
Send Message
Posted Dec 2, 2014@bigscary
Tnx for updating! Just updated on my server.
-
View User Profile
-
Send Message
Posted Dec 2, 2014@bigscary
Thanks for your quick work updating this!
On both 9.1 and 9.2, I'm having trouble when restarting the server. GP says it loads existing claims and the claim and user data files seem exactly the same as before the server restart, but it's as if they're not actually there. Using the stick does not show anyone has claimed a block, even though it was claimed before the server restart. This is on Spigot 1.8.
log: http://pastebin.com/dRNJzTbi
-
View User Profile
-
Send Message
Posted Dec 2, 20149.2 Updates
Known issues:
I think these are both CraftBukkit/Spigot bugs. I will investigate further and log a bug against the platform if necessary.
-
View User Profile
-
Send Message
Posted Dec 2, 2014@mikalaicz
I think the glass thing is just Vanilla behavior. Will investigate the arrows today.
@raum
Got it - will add the coords to my in-game logging.
@LeeTheENTP
Yep, should have the new 1.8 stuff protected with a release this afternoon/evening. :)
-
View User Profile
-
Send Message
Posted Dec 2, 2014@bigscary
It's back up now. Woo!
-
View User Profile
-
Send Message
Posted Dec 2, 2014@bigscary
The biggest reason I wrote a watcher for it myself is that our function shows the coords of the sign as well. We opted to go this route a while back when a few people would drop signs, and knowing that they're logged would /spawn or /home out of the location. Adding the coords was more of a convenience thing so we didn't have to manually run through the block logs to find out where they were when they did it.
On a second note, you're probably already aware, but GP doesn't protect Armor Stands atm.
-
View User Profile
-
Send Message
Posted Dec 1, 2014@bigscary
They still do not provide Nexus, but you can build all jar's needed. I hope this gets resolved soon, so everything is back to normal for bukkit and spigot.
Keep the good work. :)
-
View User Profile
-
Send Message
Posted Dec 1, 2014@bigscary
With archery I mean normal arrows. You can destroy item frames with them. I am running CraftBukkit 1.7.9.
And the last report.. If I place any block ahead of the item frame, that item frame is destroyed, too. For example if I want to "protect" my item frame with a glass. If a put a glass ahead of item frame, item frame is destroyed.
-
View User Profile
-
Send Message
Posted Dec 1, 2014Sorry guys, no update today. :( The download I need to do dev work isn't available on the spigot site due to maintenance.
-
View User Profile
-
Send Message
Posted Dec 1, 2014@Sniperkid720
Which version are you on? It sounds like a problem I solved in one of the recent versions.
@mikalaicz
There's a config option for claim initial depth.
What do you mean with "archery", is that a mod or another plugin? Or do you just mean normal arrows? Are you running 1.8, or the version of CraftBukkit I released for?
I don't understand your last report about item frames. Will you please rephrase it or add more details?
-
View User Profile
-
Send Message
Posted Dec 1, 2014Hi there,
I have some questions and reminders about GriefPrevention. Firstly, can you add some option to claim creation from bottom (bedrock) to top (as that was in older versions)? Now it's set to create only from your selected block to top.
The next thing is bow and arrows. With archery, you can destroy item frame and an item in it, too. I think it's a bug, isn't it?
And the last one, there is no possible to place a block before an item frame - that item frame is thrown out of the wall with containing item.
-
View User Profile
-
Send Message
Posted Dec 1, 2014Player keep having their claim blocks go negative...it doesn't happen all the time but what would be causing this? It happens to some players every once in a while and haven't seen this issue on any other server of site.
It seems to happen most when they go to unclaim something they have.