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 6, 2012Hey bigscary,
Thank you for trying to help me out :) Well my server is quite populated i have about 80 players online at the same time quite often. That means a whole lot of people come and go and thats probably why those things come up in the sky all the time... most of them seem to begin in creative and not all of them tend to come back afterwards.. I will be awaiting version 6.7 i do hope that this is per world settable since this happens only in our creative world which i seem to have messed up on first creation (its only about 6 high)... I have been trying to figure out how to increase my sealevel to default 64 but i have really no clue if this is at all possible somehow... MCEdit crashes completely when i try to copy the entire map WorldPainter crashes already on trying to convert the map to a worldpainter world because the map is too big :( do you have any tips on this because that might be the best solution.. we are running 17 worlds so if the sealevel setting is multiworld compatible you have just made my day =D if not.. well then im a little afraid this new change might not be a really good idea since we have no problems at all in any of the other maps except the creative one and i dont eager for the same kind of issues in all the other maps to be honoust... id still love to see that little thingy in the config something like RestoreNatureEnabled = false would be the hottest thing ever! :P
-
View User Profile
-
Send Message
Posted Oct 6, 2012Thanks very much bigscary! Updating as we speak... :D
-
View User Profile
-
Send Message
Posted Oct 6, 2012@bigscary
It's possible that I did /reload. I'll keep an eye on it!
-
View User Profile
-
Send Message
Posted Oct 6, 2012@Chaett
Yes your config looks correct based on your description. :)
Are you saying you want playres to be required to create claims before building even in your survival world? Claiming before building is only required in the creative rules worlds. Requiring that in the survival worlds creates a lot of problems for players, for example making it hard for them to adventure and mine, and introducing the possibillity of them getting stuck in the wilderness because they can't change blocks to dig themselves out of a hole.
The few players who will hang around despite that annoyance will quickly discover there are many workarounds they could use to build where they want when they want anyway, for example temporarily claiming an area to build or mine, then deleting the land claim.
-
View User Profile
-
Send Message
Posted Oct 6, 20126.7 Updates!
@RasCas
Do a permissions dump for one of the players with the problem. It's likely what you put for [rank] is not actually a permission that player has. It has to be the full permission node with proper capitalization.
@mspaulding86
I understand your (rather rare situation) which gives you a need for height adjustment in claims. I'm sorry, but adding that would hurt performance, take a lot of coding and testing effort, and introduce lots of bugs, when 99% of players don't need it. And it creates a pitfall for players who use it, because now someone can grief them by building on top of their build.
For that one special case (just the casino), you might want to use another plugin like WorldGuard or Residence, then use GriefPrevention for all other anti grief.
@Grilor
Yep, /IgnoreClaims to build there. You can also resize it with your golden shovel or delete it with /DeleteClaim.
@ray73864
Thanks, Ray!
@mrcheesete0
Put all tekkit container IDs in the container list, the explosive blocks in the explosive list. For quarries, tell your players to place their quarry inside their claim at the edge, facing outward. It will be able to break blocks outside the claim, and will safely store the result inside the claim. Beware griefers placing pipes outside the claim to steal content of boxes on the edge of the claim. Good luck. :)
@Infuscu
That's right, not retroactively. You could use /AdjustClaimBlocks, but that will be on a per-player basis. There's no coding for this rare one-time-give-everyone-blocks situation. :\
@Infuscu
I could increase the time. Last I checked, it planted the right saplings. I'll check again.
@ChilleCharlie
I added a new config optoin for you in 6.7. You can set your actual sea level in the config file. To remove those floating chunks in the air, use /RNA and point at the bottom of the platform when you right click with your shovel.
t runs when not much has been been built, to remove what little there was (often a half-built house, or a few odd blocks). It may also repair the natural blocks there, for example if a griefer didn't place any common player blocks, but made a mess with dirt/grass, etc. It also fills in holes and does some other touch-up.
It's an extremely complicated, very effective mechanism which is designed to get its job done without any need for anyone to monitor it. When you start staring at it and trying to predict it, that's when you get confused and it seems like it's not working. It gradually scans claims over time, so just because nothing is built doesn't mean that it will immediately delete that claim, for example, because maybe it's looking at other claims right now and will get to that one later. Also, it only deletes claims for inactive players. If a player hasn't been gone a week or two (depending on the status of his claim), THEN it becomes eligible for scanning and removal.
Because I fixed the issue with sea level, I've not added the option to entirely disable the automatic /restorenature.
-
View User Profile
-
Send Message
Posted Oct 6, 2012Yes i am running a very low seelevel... I am using multiverse for our creative world and i know its stupid but our world is only like 3 high. Unfortunately i dont think our players will like it if we erase the entire creative world... -.- so starting over is not an option... Non the less, can the automatic restorenature be somehow turned off? because griefers figured it out i mean... they KNOW that creating a huuuuuge piece of claim will bring me severe headache and im going nuts cleaning the creative world all the time... Please please please make this possible to be turned off! this would seriously be THE best plugin EVER if this stupid automatic restore nature thing wasnt there.... because.. it only runs when there isnt build anything right? so whats the point? there hasnt been build anything so restore nature fires itself and repairs nature wich wasnt damaged anyways... while there wasnt build anything you know :P get my point?... nothing happened and it fires... something built and it doesnt fire... i dont get it... really it sux... badly :P Please can you help me either point me to the right direction in the code so i know where to start looking for it so i can try removing it myself or just make it switchable in the config i prefer the second.. im not so good with java anymore :P
-
View User Profile
-
Send Message
Posted Oct 6, 2012Awesome plugin, players love it, and so do I. I'm creating a creative world and want to add CreativeRulesWorld, is this the correct format?:
creative is in fact the name of my Creative world, and dothrakicraft the main survival world.
With this format, players are still able to build in the wilderness, This isn't what I want. I want them to claim first like it states in administrative page.
-
View User Profile
-
Send Message
Posted Oct 6, 2012In addition, I really like the tree replanting feature .. it's lovely. Only issue is that it doesn't replant the corresponding sapling to the tree it removed. This is especially "problematic" in jungles as normal oak trees looks sorta weird there.
Do you have any plans to change it, so it plants the 'correct' sapling? Maybe you could look at the biome, and plant the sapling according to that.
Also I feel like it's a bit too aggressive at times, I reckon that this is mainly due to the low replant time of three minutes. I suggest increasing the time to ten minutes, or making it customisable. I don't feel like this would decrease its function.
-
View User Profile
-
Send Message
Posted Oct 6, 2012I change InitialBlocks to 400 but it doesn't seem to be retroactively. Is that correct?
Is there any way to adjust the setting for the users who already logged in?
-
View User Profile
-
Send Message
Posted Oct 6, 2012I assume
was added to make things such as tekkit play nicely with this, do you know what I have to add here to make tekkit play nicely, specifically the quarries?
-
View User Profile
-
Send Message
Posted Oct 6, 2012@bigscary
I'll work something out with it, if i can get a viable solution for the exponential block increase, i'll let you know.
-
View User Profile
-
Send Message
Posted Oct 6, 2012@Grilor
You need to use the /IgnoreClaims command. ;)
-
View User Profile
-
Send Message
Posted Oct 6, 2012@bigscary
I'm right with you on that one bigscary. I haven't got a clue how much time and effort you put into GP but the results are outstanding! Cannot thank you enough for all the work you do. <3
A friend introduced me to Grief Prevention earlier this year advertising it as, "a way to stop griefers from screwing up your server". As soon as I started exploring this very webpage I quickly realised this was much more than just a plugin to deal with 10 year old kids c/w anger management issues. ;)
We use only 2 plugins on our PvP server and one of them is Grief Prevention. We do not need anything more. It's the No.1 plugin everybody should know about and have installed on their bukkit server(s). If I had to draw up a list of "Top Plugins" you would see Grief Prevention on the top of that list every time and I bet there's 1000s of others who hold the same opinion. Grief Prevention should be incorporated into Minecraft by default! :D
-
View User Profile
-
Send Message
Posted Oct 5, 2012is there away that an admin can eidt a players claim with out there permission? the reason i ask is on my server i have member who play very casually and are not on for long periods of time. and i had a mode installed(witch is now removed) that casued a major sand storm and there is sand everywere and i would like to remove the same from claims. thanks for any help
-
View User Profile
-
Send Message
Posted Oct 5, 2012@mspaulding86:
Use /subdivideclaims to create a subclaim which includes only that block. Then you can use the trust commands while standing on top of it to change who can use it. But there will be a danger that someone could break your note block.
I'm treating note block settings as "build" because usually, note blocks are tuned to a specific setting and then the owner wants them left exactly there, so that the right note or sound or song plays. Redstone repeaters are treated similarly.
@BigScary
The casino is on the fourth floor of a building. If I /subdivide, won't it let them break the blocks on the floors below and above it? Subdivide won't do a single block, it does all the blocks above it too I thought?
Or... make it so I can dynamically adjust the heights of claims:
Step 1) /ac
Step 2) /sc
Step 3) Click first corner, Click second corner.
Step 4) /heightabove 0
Step 5) /heightbelow 0
and it would make it so only that block was available?
I'm trying to be constructive!
Also, noteblocks; shouldn't they be access or something. I know some people use them as doorbells. They want someone to be able to make the noise without breaking it...
Please take this into consideration. I rant and rave about how much I love your plugin to my friends and other server admins.
-
View User Profile
-
Send Message
Posted Oct 5, 2012I am having troubles with trust for ranks. If i use /ct [rank] it says that group rank has access but if someone with this rank tries to, he is told that he needs the permission of claim owner.
Any ideas?
-
View User Profile
-
Send Message
Posted Oct 5, 2012@FordRacer2007
Try temporarily disabling war, monsterparty, and essentials, then checking to see if some fire you set with your flint/steel spreads. If it doesn't, your problem is one of those plugins.
@schmidtbochum
I don't understand. If there's nothing built there, then what's being destroyed? Also are you running a creative mode server? I will add an option to disable that type of claim cleanup.
-
View User Profile
-
Send Message
Posted Oct 5, 2012How can I disable automatic disbanding of "empty" claims?
Its destroying my map... the work of months.
-
View User Profile
-
Send Message
Posted Oct 5, 2012@bigscary
As far as what plugins I have, here's he list:
WorldEdit MonsterParty LogBlock War Vault Backpack SimpleHelpTickets BorderCrafter GriefPrevention FishingTournament Freeze Essentials BookShop Citizens Multiverse Core/Inventories Sign Bank ChestShop
-
View User Profile
-
Send Message
Posted Oct 5, 2012@FordRacer2007
Yes I understand. I checked it on my test server (same GP version) and didn't have the problem. That's why I asked you for more details, like a screenshot of the source of the fire, or a list of your other plugins.
@Praqoon
It really is the best, and FAR ahead of all other anti grief plugins. People don't believe me when I say it because I built it, but it's true. If only I could solve the "people still recommend WorldGuard in forums because they don't know about GriefPrevention" problem with code, then I certainly would.
Just yesterday a guy logged onto one of the test servers and proceeded to tell me that I must be new at servers because I didn't have "permissions set up" and Essentials. I asked him "If you're so smart, which is the best anti grief plugin"? He answered "I dunno, I don't use anti grief because I don't have a grief problem on my server." Some folks are beyond help.
@yurikoma
Nosir, remember restore nature is for putting back nature the way it was, so that's why it doesn't remove (or replace) water at or below sea level. Maybe try something like VoxelSniper or WorldEdit to clean up that brand of ugly. :)
@ChilleCharlie
Are you running a custom world generator plugin? When sea level is set incorrectly, you can get a problem like the one you described.
@ray73864
Use /subdivideclaims. :)
@mspaulding86
Use /subdivideclaims to create a subclaim which includes only that block. Then you can use the trust commands while standing on top of it to change who can use it. But there will be a danger that someone could break your note block.
I'm treating note block settings as "build" because usually, note blocks are tuned to a specific setting and then the owner wants them left exactly there, so that the right note or sound or song plays. Redstone repeaters are treated similarly.