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 Sep 21, 2012@bigscary
Completely missed that part, sorry.
Btw a section on here with all the commands and permissions would be great.
(I don't need it any more because i went to github opened up plugin.yml and documented all the commands and what permissions affect them and descriptions onto my plugin list for future reference. But it would help other server owners who don't know how to find that info.)
-
View User Profile
-
Send Message
Posted Sep 21, 2012@JSmoove98 It's already exists. Claim automaticaly grows down when you dig or place blocks.
-
View User Profile
-
Send Message
Posted Sep 21, 2012Is there any way to make it so that when u make a protection it doesnt effect the blocks under it because sometime people's caves go under other people's claims so yeah...
-
View User Profile
-
Send Message
Posted Sep 21, 2012@bigscary
Claim.java (overloaded function)
BlockEventHandler.java (overloaded function)
DataStore.java
Why it's expensive? Plzzzz, make this as option in config. =)
-
View User Profile
-
Send Message
Posted Sep 21, 2012@bigscary
hmmm. I just checked my GP config.yml and found some really weird shit. The mods section...
<<code lua>>
Mods:
BlockIdsRequiringAccessTrust: []
BlockIdsRequiringContainerTrust:
- 227:*:Battery Box
- 130:*:Transmutation Tablet
- 128:*:Alchemical Chest and Energy Condenser
- 181:*:Various Chests
- 178:*:Ender Chest
- 150:*:Various BuildCraft Gadgets
- 155:*:Filler
- 157:*:Builder
- 158:*:Template Drawing Table
- 126:*:Various EE Gadgets
- 138:*:Various RedPower Gadgets
- 137:*:BuildCraft Project Table and Furnaces
- 250:*:Various IC2 Machines
- 161:*:BuildCraft Engines
- 169:*:Automatic Crafting Table
- 177:*:Wireless Components
- 183:*:Solar Arrays
- 187:*:Charging Benches
- 188:*:More IC2 Machines
- 190:*:Generators, Fabricators, Strainers
- 194:*:More Gadgets
- 207:*:Computer
- 208:*:Computer Peripherals
- 246:*:IC2 Generators
- 24303:*:Teleport Pipe
- 24304:*:Waterproof Teleport Pipe
- 24305:*:Power Teleport Pipe
- 4311:*:Diamond Sorting Pipe
- 216:*:Turtle
BlockIdsExplodable:
- 161:*:BuildCraft Engines
- 246:5:Nuclear Reactor
PlayersIgnoringAllClaims: []
<</code>>
I gather this is not standard? :D
-
View User Profile
-
Send Message
Posted Sep 21, 2012@junebugjump
Hm, you might try AntiXRay instead of orebfuscator (I assume the problem was running out of memory?).
I'm sorry the issue is still unresolved. I hope you don't experience it again. :)
@PsychoFad
Then it must be something to do with TerrainControl, no one else has experienced the problem to my knowledge (maybe someone didn't report it).
@PsychoFad
As you said, it's not possible to fix any of these problems with Bukkit, unfortunately. The only "real" fix would have to be on the Tekkit mod side. I recommend the TekkitCustomizer plugin, which will ban the items that bypass anti grief (it has a good default config file, so you just install it and go).
@Tr33x0rs
I'm very sorry to hear that! :( I'm also running a Tekkit server with the same GP version, and I don't have the same issue. Did you remember to reboot your server after adding GP? I can't imagine an explanation for this right now, but I will think on it some more.
@ray73864
Those notes apply to Tekkit-specific items, like for example the "Dark Matter Hammer" which removes blocks without first checking with Bukkit. Buttons, levers, containers, etc should still be correctly protected.
@yurikoma
Isn't there a siege worlds option in the config? Players should only be able to use /siege in the worlds you specify (siege is totally disabled by default).
@spazmonkey777
griefprevention.spam :)
@Praqoon
Hmm I wonder if 1.3.2 has something to do with it, not sure.
@voodoo12334
Sorry, but it's too expensive to try and keep fire from crossing claim boundaries. Water is already expensive, and fire would be much worse because it can spread up as well as down.
-
View User Profile
-
Send Message
Posted Sep 21, 2012Please, make the feature, that fire cannot spread inside claims, but can spread outside. Now it spread inside and outside claims.
-
View User Profile
-
Send Message
Posted Sep 21, 2012@ray73864
I have CraftBukkit 1.3.2-R.01 (beta) with Grief Prevention v6.5.1 and Transporter v8.6 installed. I'm running Slackware64 13.37 Linux with OpenJDK (IcedTea7 2.3.2). The game world is survival and GP is set to reward players with a maximum of 30 claim blocks per hour with an automatic "first chest" claim of 5x5 squares.
I have set up a test server and I'm running GP versions which are months old and I still have the same problems on the test server using the out-of-date plugins. I've tried different versions of JAVA, deleting all user and claim data and starting from scratch, different locations doing different activities, etc. Nothing seems to earn me anywhere near the correct number of claim blocks. In fact, if I check my claim block total often (maybe once every 15 mins) I find the value decreases or stays the same and this seems totally random. The only sure way I can earn claim blocks is to not use a golden shovel until I'm ready to log out of the game. If I have to use a golden shovel to create or modify a claim I need to log out and back in to the game in order to keep earning claim blocks.
Thanks for your interest in this problem of mine. It's driving me crackers. LOL! :D
@yurikoma
I think you can specify the world name(s) in the server.properties seige section?
-
View User Profile
-
Send Message
Posted Sep 21, 2012Is there a permission to give my Moderators the ability to 'spam' chat, since a lot of times they have to repeat themselves because they chat in admin chat on accident, and auto-repeat in global. But as of right now, they are blocked.
I don't want to give them the admin permission I saw on the list, just a certain permission to avoid the anti-spam part of the plugin. If it's listed or been mentioned, I couldn't find it. Thanks for any help!
-
View User Profile
-
Send Message
Posted Sep 21, 2012@bigscary
Hey, i am sorry if this is mentioned somewhere, i honestly couldn't find it.
but is there a way to disable the siege features of this plugin in all worlds except the one i want, without disabling pvp completely?
-
View User Profile
-
Send Message
Posted Sep 20, 2012@Tr33x0rs
Look Up! The section at the very bottom of the description that says 'Notes for Tekkit Servers'.
There is no way for any bukkit plugins to control what actually happens on a tekkit server, although tekkit is basically bukkit, the tekkit mods are regular SMP mods, they don't go through the bukkit stuff.
Tekkit implements bukkit because it allows you to then install plugins such as WorldEdit, etc...
-
View User Profile
-
Send Message
Posted Sep 20, 2012Sorry if this has been mentioned already. I am running a Tekkit Server with GP 5.5.1. Although I have "PreventButtonsSwitches: true", players are still able to use levers and buttons on a claim that is not theirs and that they're not trusted on. They receive a message "You don't have XXXXXXXX's permission to use that" but the lever does its function. Any suggestions?
-
View User Profile
-
Send Message
Posted Sep 20, 2012@junebugjump
Tekkit Mods do not obey Bukkit plugin protections or show up in block loggers! I found this out the hard way when a member on my Tekkit server accidentally discharged his Red Matter Armor self-destruct in his own house leaving a huge crater where his house once stood. A griefer on a Tekkit server could easily use his Red Matter Morning Star to remove every block without any permissions on the land since it doesn't bother checking with Bukkit to see if its ok. Sorry for your player's misfortune, but what Tekkit needs is a Grief Prevention type Mod that blocks the use of Mod items on protected land, but that would probably have to be a collaborative work from all of the actual Mod authors in order for it to effectively "short circuit" the items in protected areas. Since Tekkit is a collection of Mods, that makes it even more difficult for this to be achieved since the authors of these Mods never really intended for them to be used all together when they created them in the first place.
-
View User Profile
-
Send Message
Posted Sep 20, 2012@bigscary
Well. I imagine if it was a Bukkit thing then other people using Grief Prevention would be realizing this same problem. Thoughts? I checked the config in my TerrainControl and this is what is set:
WaterLevelMax:64
WaterLevelMin:0
So I'll try bugging the TerrainControl Author to see if they have heard of any miscommunications of this level to Bukkit.
-
View User Profile
-
Send Message
Posted Sep 20, 2012The world is survival not creative. But thanks for explaining that scenario to me, as it is something that a server owner should know.
The LogBlock scenario could be likely but ONLY trusted staff have and the ones on the server would tell me if they deleted the house. Our server actually crashed that day but it tells which plugins were causing the issues, and the culprit was Orebfuscator.
Truthfully, 1.3.2 is the buggiest update to any software ever (I'm even going to throw Microsoft a bone here, and I hate MS). We've had so many issues with all of the plugins... I feel badly for the developers because it's like hitting a moving target.
I'll just monitor at this point and give the player a huge sum of money... If it happens again, I'll report back. Can't take these things too seriously.
You're the best, BigScary!
-
View User Profile
-
Send Message
Posted Sep 20, 2012@Praqoon
What plugins do you have installed?
-
View User Profile
-
Send Message
Posted Sep 20, 2012@Praqoon
Thanks for helping me investigate this. My plan is to temporarily add some logging and speed up the checks (to once per 10 seconds or so) on a test server in hopes that it will highlight the issue. I haven't gotten around to it yet. I'll let you know when I've had a chance to look.
-
View User Profile
-
Send Message
Posted Sep 20, 2012@bigscary
Regarding the claim blocks issue, I found something else. I can basically run around all day on unclaimed land and I will gain claim blocks at the normal rate. When I do anything on claimed territory I do not earn any claim blocks no matter how long I'm doing it. Although this is not always the case, it can change for a few earned claim blocks (on occasion) but no more than 6-8 blocks. The reason why I'm having so many problems giving you some hard facts and evidence is because the problem is not always manifesting itself in the exact same manner. Because nobody else is having this particular issue, I'm leaning towards it being something to do with other software running on the server.
I'll keep you posted. ;)
-
View User Profile
-
Send Message
Posted Sep 19, 2012@notif
It's already done and described above. Use /containertrust public. :)
I won't do no-pvp claims. Someone can create an extension plugin for that, I'm still waiting for somebody to actually do it.
-
View User Profile
-
Send Message
Posted Sep 19, 2012Hello bigscary, I would like to suggest the ability to trust everyone to things like containers, not simply individuals. . This would be very practical for our Arena that I am modifying, which has restocking chests, that no one can take items from. Otherwise we have to leave it unclaimed, which allows other players to claim it.
Also, the ability for admins to make a claim PvP free, such as for a shop, or spawn area.
I would appreciate this, thanks!