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 Jun 22, 2013Sorry but I didnt had the chance to answer.
How I said before all works fine but there is a problem with Sticky Pistons. If I enable the plugin the sticky pistons work badly.
I turn off the switch of the piston and the piston stay in opened position, if I press the switch the piston do nothing stay in opened position. Make nothing but if the plugin is disabled all sticky pistons work well.
How can I fix the problem? Please help.
Naturally I tried out to off all other plugin and it was bad too.
I am using build #2788 1.5.2-R1.0 Craftbukkit. (If it helps)
Only the bukkit and this plugin were active during the tests.
Thank you for your answer and sorry for lating with my answer.
Regards Batyesz
-
View User Profile
-
Send Message
Posted Jun 22, 2013@Askotion
If you are using 7.7 or the dev build, it doesn't work with 1.4.7.
@TrenTech
Unfortunately there is no way to address those. The only one I can think would be possible would be mining turtles, because on a cursory investigation they appear to "emulate" a player. Here's the rundown:
Thaumcraft Wands, The Arcane Bore, Buildcraft Quarries, Mining Lasers, the Portal Gun, Throwable Explosives, and Gravity Guns to NOT fire bukkit events. this means GriefPrevention has NO notification that these things are occuring and NO way to stop them from happening. I'm surprised Throwable Explosives aren't raising the explosion event, but when it comes to MCPC and Forge Mods whether bukkit events get fired is a bit sketchy. The only way to fix this would be to make GriefPrevention a Forge mod.
And let me be perfectly clear: As it stands right now I will avoid touching the forge 'API' ever again. I'm not even sure if that would solve the issue anyway. The thing is that while I have been adding a few features to better support modded servers, once that support requires me to "step outside" of bukkit, it stops. If I can address something through the bukkit API, I'm game- but otherwise, it's not something I am personally interested in at this time.
Now, that said, I'm not the only maintainer, Tux2 might have other ideas, and has even expressed a desire to create a Forge port, and has also ported plugins to mods (or made adapters of some sort) So he not only has more experience with forge but I suspect he can actually tolerate it.
If anything, I think the ideal case would be a forge mod that actually causes the proper bukkit events to be raised with MCPC; I don't know how possible that is but it would fix not only some of the issues with GP but could help with the issues with various other bukkit plugins on modded servers.
-
View User Profile
-
Send Message
Posted Jun 22, 2013This combined with hexrestrict works well, but certain there are certain things, i hope get addressed. A few examples are gravity guns, mining turtles, mining lasers, portal gun, and any throwable explosive. I do not like having to ban items due to grief. That was the whole point in having this plugin. It's very player friendly and covers 80% of grief, but the other 20% is still a problem.
-
View User Profile
-
Send Message
Posted Jun 22, 2013Hi, i started a FTB Ultimate Server and run the MCPC+ Version 1.4.7 (latest build of 1.4.7). And i put the GriefPrevention plugin in the Plugins folder, restarted the Server and it created a Folder. But on the Server none of my players exept of me get a message if the right click on the ground with the golden shovel. Should i give them Permssions or something of that? Ty :) PS: And sry about my terible englisch i am german ;)
-
View User Profile
-
Send Message
Posted Jun 21, 2013@hellishinc
It checks for strings in the config, this is with the dev builds: 7.7 doesn't check at all (just making sure that is clear). It checks for the config/ folder, which is typically the Forge config folder. It looks for the IDs assigned by the mod configurations. It doesn't always find them, it depends on the specific names the mods give it; eg. ThaumCraft's config lists the Hungry Chest with the config name "BlockHungryChest" and GP finds Chest so adds the ID. not all mods use descriptive names, though, so it can't find them all. (the EnderChests mod uses a rather generic "blockID" name or something).
The blocks representations are only sent to the client, and never actually change the block as far as the server or server logic is concerned. Adding a "custom model" of any sort would require the use of Forge which I refuse to deal with.
The "canexplodeIDs" section was removed because I changed the logic to allow the block at the center of an explosion to be destroyed. The setting was used to allow reactors and other blocks to explode; whereas before they would simply explode over and over because their block wasn't being destroyed. Now if explosions are disabled in that location, the block at the center of the explosion is still destroyed; this is because the only blocks that can be at a the center of an explosion are things from mods that are designed to explode, such as when given too much power. If they aren't destroyed, they will simply continue to explode over and over again; if the explosion is cancelled, it will just keep trying to explode over and over again as well; so I changed it to remove that particular setting and simply allow any block at the center of an explosion to be destroyed, which to my understanding should address the issue better.
-
View User Profile
-
Send Message
Posted Jun 21, 2013@matthewpopcorn
http://dev.bukkit.org/bukkit-plugins/grief-prevention/pages/administrative-topics/
You really should read the information provided to you before you start asking for help.
-
View User Profile
-
Send Message
Posted Jun 21, 2013@Alshain01
Yes, I know that it makes your first claim but it keeps saying you have o claim spaces left, how do I set it so the players join with 10,000 and it doesn't increase over time
-
View User Profile
-
Send Message
Posted Jun 21, 2013@matthewpopcorn
You place a chest.
-
View User Profile
-
Send Message
Posted Jun 21, 2013Plz help! I can't find out how to have the default claim space set, I've tryed the many things in the config but it still didn't work. What do you change?
-
View User Profile
-
Send Message
Posted Jun 21, 2013I'll be glad to list what GP did not autodetect, however it is possible it missed them because I use modified IDs. From what you said you check for strings instead of IDs (sorry i just woke up bear with me)?
One thing I would love to see is having the marker blocks "ghost" in the world. They currently act as solid blocks and also emit light, which blocks mob spawns, and also take the "fake" blocks properties when broken. For example, the glowstone block that marks the very corners is basically an instant break with any higher pickaxe and I frequently break them on accident when clicking on it to "refresh" the block. Since it also "replaces" whatever block was actually there, it also causes issues with things such as doors, pistons, and various mod items should they be placed where a marker overlaps.
I understand with "base bukkit" that you are limited to what can be seen by the players but for those using MCPC+ there could be some sort of option to use a custom model. If thats too much work perhaps it could draw a specific model in the game using a specific texture (say chicken with glowstone texture?) so that it would be visible and also not have to forceably replace the exsisting block.
I noticed you removed the "can explode" config section as well. Does this mean that things such as buildcraft engine will no longer explode and cause damage?
I havent had any issues using build 89 thus far, will give build90 a try soon.
-
View User Profile
-
Send Message
Posted Jun 21, 2013@ADEgeneral
Sounds like NoSurvivalBuildingOutsideClaims was enabled. Also check that the world they are in isn't in the CreativeRulesWorlds list of names. (I'm assuming 7.7)
@Daelmaron
/trust gives Build, Containers, and Access trust.
/containertrust gives Containers and Access trust.
/accesstrust gives Access trust
-
View User Profile
-
Send Message
Posted Jun 21, 2013I have a problem where I am unable to give a player access to all three, building, access, and containers. Am I missing something with this?
-
View User Profile
-
Send Message
Posted Jun 21, 2013I am sorry if this has already been answered. I have started using this plugin, and I love it. However, now, for some reason, whenever a new player places a chest, it gives an error saying that they must claim land first. I feel like there was a setting I changed... but I can't figure it out!
Please help!
-
View User Profile
-
Send Message
Posted Jun 21, 2013@deleted_9935739
The claim data saved in the PlayerData file is not read in for any purpose. According to the source comments, "fourth line is a double-semicolon-delimited list of claims, which is currently ignored"
-
View User Profile
-
Send Message
Posted Jun 21, 2013@BC_Programming
How would the existing claim player claim settings be handled? Would it be added/overwritten/deleted? Will it have any kind of negative effect?
-
View User Profile
-
Send Message
Posted Jun 20, 2013@deleted_9935739
Keeping PlayerData should work.
-
View User Profile
-
Send Message
Posted Jun 20, 2013@fungreenfox
-1 goes by whatever the world implementation returns. For the nether this is 32; for the overworld, 64. The option is only if you want to forcibly change what GriefPrevention regards as Sea-Level. it is most likely useful only for custom world generators and Forge mods (such as Mystcraft).
@fungreenfox
Presumably you mean WorldGuard, and of course it doesn't. It respects GriefPrevention claims, not arbitrary claims made by other plugins.
-
View User Profile
-
Send Message
Posted Oct 24, 2013Stand in the claim you want to get rid of, and type /abandonclaim. If you have subclaims, well, thatsa whole 'nother problem.
-
View User Profile
-
Send Message
Posted Jun 20, 2013i cant figure out how to abandon a claim!!! its so annoying. im vulneravle to players and im constantly getting griefed!
-
View User Profile
-
Send Message
Posted Jun 20, 2013I am going to be resetting my map but want to let players keep their claim blocks. Would I just keep the PlayerData folder and delete the ClaimData folder or would that not work out? I see that there are dates and coordinates in the files so would leaving them without those claims existing anymore cause problems?