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 28, 2014Hey! I like the plugin! But last version it was highly configurable, was confusing at start but very nice when i knew how it worked!
But after a update (and some problem after that with claims) I cant customize it that much anymore :( well ok can deal with that. but i made a train track with minecarts. and they automatically break (before the update) and now days the minecarts wont break by cactus anymore :( any fix or work around on this? Thanks! Pigna
-
View User Profile
-
Send Message
Posted Oct 28, 2014What's version of GP i must use on Bukkit 1.6.4?
GP 8.6 generates huge amount of errors on Bukkit 1.6.4
-
View User Profile
-
Send Message
Posted Oct 28, 2014@TakoMT
As far as I know this is not an option at this time.
-
View User Profile
-
Send Message
Posted Oct 28, 2014Great plugin... love it love it love it :).
One small question though, because I just cannot find the setting anywhere if it exists... well I hope it does..
How can I increase the distance between one claim and another? I want to try and avoid having people squishing their claims next to other claims.
-
View User Profile
-
Send Message
Posted Oct 27, 2014@LuiSinhuUu
What do you mean it doesn't work? Do you get an in game error message? If not, do you see any error in your logs?
-
View User Profile
-
Send Message
Posted Oct 27, 2014Someone can help me ?
the command /trust won't work .. i find this
https://github.com/ryanhamshire/GriefPrevention/blob/master/plugin.yml
what i do with this ? create a new Yml and put inside the folder grief ?
help '-'
-
View User Profile
-
Send Message
Posted Oct 27, 2014@dutchrastacraft
From the timings data you've been sharing with me, it seems like Spigot is just going as fast as it knows how. You could try tweaking the Spigot settings as recommended on the spigot site? If that doesn't do that job, I don't think you have good options - reducing max players maybe? That's disappointing, though. If you can hold out a while longer, MAYBE spigot will finally add those more detailed stats, which would reveal more about your spikes.
By the way, 19.73 average ticks per second is REALLY good. I think the server load thing is a non-issue until it starts impacting your TPS.
@xSnowBlitzz718
I do'nt want to build something like that in, because I'd be deciding for server owners when they should throw away claim blocks earned by their players. You can sort your files by last modified date, then delete some that way.
@fibsmaster
Sorry to disappoint, it's not doable right now and might not ever be - it would mean having a different claim block total per player per world which would be a lot of tough coding for maybe just a handful of servers. Similarly, that config option you mention shouldn't exist anymore in the latest versions (no building outside of land claims)? It sounds good on paper, but nobody ever liked the way it worked in practice.
@TJW28
I'm not sure what's going on there - I don't have the same problem on my test server, and I reviewed the code without spotting any obvious problem there. Did you remember to /reload or reboot after updating?
Does anyone else here see the same issue?
@erik1988
I think probably not, but I will research little. In the past, paintings and item frames have proven to be special cases that we need a Bukkit update to handle. I expect armor stands will be similar.
@ktole1999
Yep. Iron doors only open when powered by redstone, and both buttons and levers require /accesstrust or higher to use. So you can use an iron door (or a fence gate by default) to keep players out. You could also make wooden doors and trap doors lockable by editing your config.
There's no "invisible wall prevents players from walking here" feature.
-
View User Profile
-
Send Message
Posted Oct 27, 2014is there a way to keep players from entering your claim?
-
View User Profile
-
Send Message
Posted Oct 26, 2014Since its already possible to use plugins that gives access to 1.8 blocks and items. Does GP have support for 1.8 items yet? Or do we have to add them to the list in the config? It would be nice if they would be added to the code if its not to much hassle. :)
EDIT: seems like everything works exept the armor stand. I can place and remove armor stands from any claims even if I have no access.
-
View User Profile
-
Send Message
Posted Oct 25, 2014Hi
I have the lastest build of GP, and changed the LoginCooldownSeconds to 60.
Users are now coming back reporting that when they try and rejoin the server, its saying they have to wait 3600 seconds, which is of course 60 Minutes.
I disabled the spam protection, and they can log in as normal.
Any Ideas?
-
View User Profile
-
Send Message
Posted Oct 25, 2014Hi! Can someone give me a hint how i can a achieve this: I have 2 worlds with MV and would like to have different settings for both worlds. Like minimum claim size 3x3 in one world and 10x10 in the other. And most important would be to have world 1 with permissions only to build on claims, not in the wilderness. But in world 2 build everywhere but with the possibility to protect your farm spot with a claim.
Only way to get near this was to set world 1 to CreativeRulesWorlds and have NoSurvivalBuildingOutsideClaims: true But this will end up with world 1 not having mob spawns and all blocks you break will dissapear. (Maybe this could be changed somehow?) I hope you have a hint for me :D
-
View User Profile
-
Send Message
Posted Oct 25, 2014@AeroEden
Yep that did it. Thank you so much. So to anyone out there with a modded server trying to add modded items like doors and such, you must use the block id, not the item id in NEI. This can be found by using a plugin such as world edit. After world edit is loaded, choose an item (I chose an iron shovel) and type '/tool info' this will allow you to right click your placed block or item and see its block id. Use the number you see next to the #. Big big thank you to @bigscary for responding and at least helping as best you could, but a HUGE shoutout and thanks goes to @AeroEden for going above and beyond to help a fellow user out.
Thanks and now my server can enjoy this great plugin and I can finally move on to the next item on my list of things to do as the admin. Lol
-
View User Profile
-
Send Message
Posted Oct 25, 2014Also. We have like 40k player files >.< oh my gosh. 98% of those are inactive though so is there a way to just deleted them so the conversion process will take faster? Like when the conversion detects a player file that has not been online for a couple of months, it should just delete it to make it faster?
-
View User Profile
-
Send Message
Posted Oct 24, 2014@AeroEden
Thank you! I will do this and see how it goes. Will report back hopefully with success.
Much appreciated sincerely for you assistance.
-
View User Profile
-
Send Message
Posted Oct 24, 2014@ClimacticGaming
Just hold the shovel and type /tool info
Then you can right click on the block in world to see its id, you can do this multiple times no need to re-type the command
And yeah its item id was different
-
View User Profile
-
Send Message
Posted Oct 24, 2014@AeroEden
Thank you for doing this. Do you know what you did to make the shovel show the block id? Luckily I have world edit. Also...was this number different from the item id? Just curious. What was the item id before you placed it?
Thanks so much for all your help. I owe ya one!
-
View User Profile
-
Send Message
Posted Oct 24, 2014@ClimacticGaming
Had some spare time to download a 1.7.10 pack and get cauldron up and running :)
Yeah have no idea why WAILA isn't showing the id of the block
Anyway what I did is install worldedit and and assigned the info command to a shovel using /tool info, then any block you click on it gives information (check attached image on this post)
As you can see it shows the block id after the # and the meta data is in the [] but you should be using id:* anyway :)
-
View User Profile
-
Send Message
Posted Oct 24, 2014Im getting "An Internal error occured while attempting to perform this command." when trying to use commands such as /trust or /adjustbonusclaimblocks any idea why this could be happening?
-
View User Profile
-
Send Message
Posted Oct 24, 2014@ClimacticGaming
ChestShop has the /iteminfo command which shows you info about the item you're holding. Prism has the /what command which does something similar.
-
View User Profile
-
Send Message
Posted Oct 24, 2014@bigscary
Indeed, sadly enough :/ Any ideas (server sided) how I can improve my server a little more? And no, I'm sorry, I don't use flatfile :/