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 Jan 29, 2013@Pixiyo
Read the configuration, it is stated in there that water buckets can not be used above ground outside of claims, just toggle this to false.
-
View User Profile
-
Send Message
Posted Jan 29, 2013People on my server can't place water, why?
-
View User Profile
-
Send Message
Posted Jan 29, 2013Could you please move the crafting table from containertrust permissions to accesstrust permissions? I really would not want to give a player permission to access all of my chests when I only want them to be able to craft themselves some wool...
-
View User Profile
-
Send Message
Posted Jan 29, 2013@Jonasbilljensen
I assume you are using Tekkit Lite.
Replace your core with this: http://build.technicpack.net/job/MCPC-Plus/
Get disabler to remove half the ic2 stuff like lasers.
@OP
Thanks for this awesome plugin, you were right, it was totally worth the trouble to get working. My players are thrilled even though half of the items are banned until I get them fixed. The time griefers waste on my server is less time they are actually doing any damage. One griefer even took the time to steal cobblestone from a barrel! Cobblestone!
My cleanup each morning consist of right clicking away a few weird structures and maybe banning someone.
On a side note, this totally works with Tekkit Lite, you just need to replace the TekkitLite.jar with:
http://build.technicpack.net/job/MCPC-Plus/
You also have to download disabler and use this list to disable items. There are a few banned items I have custom to my server. As a request, if you could throw me some advice on how to get some of these items off the ban-list, it would be very appreciated. However, people are happy with this as it is. Thanks again for all of your hard work.
The following is a list of items that MUST be banned from Tekkit Lite:
- 3120:7 - 4092:6 - 1952:7 - 1953 - 1953:1 - 1953:2 - 1953:3 - 1953:4 - 1953:6 - 1954:1 - 1954:2 - 1954:3 - 1954:4 - 1954:5 - 1954:6 - 1954:7 - 1954:9 - 11372 - 11377:2 - 1952:1 - 223:1 - 30208 - 30208:1 - 30208:2 - 30208:3 - 30208:4 - 30208:5 - 30208:6 - 30208:7 - 30208:8 - 30208:9 - 30208:10 - 30208:11 - 30208:12 - 30208:13 - 30208:14 - 30208:15 - 30208:16 - 30208:17 - 30208:18 - 30208:19 - 30208:20 - 30208:21 - 30208:22 - 30208:23 - 30208:24 - 30208:25 - 30208:26 - 30208:27 - 237 - 246:5 - 27002 - 8956 - 8957 - 209 - 210:3 - 210:4 - 210:201 - 209:1 - 210:200 - 210:6 - 210:7 - 209:2 - 210:258 - 210:259 - 210:260 - 210:457 - 209:3 - 210:456 - 210:262 - 210:512 - 210:515 - 210:516 - 210:713 - 210:517 - 210:712 - 210:518 - 210:519 - 239 - 11559 - 30214 - 30215 - 31997:31 - 31998:6 - 763:1 - 763:7 - 153 - 192:1 - 192:2 - 11530 - 11531 - 11532 - 11533 - 11534 - 11561 - 155 - 157 - 763:7 - 225 - 4092:2 - 95 - 3128 - 233
-
View User Profile
-
Send Message
Posted Jan 28, 2013@bigscary
I suppose this gives me reason to remove LWC then... >.> The LWC dev has a habit of... vanishing... for a while... I suppose that's what LogBlock is for.
-
View User Profile
-
Send Message
Posted Jan 28, 2013Folks, please vote up https://bukkit.atlassian.net/browse/BUKKIT-3521 to get it looked at faster... Causing nothing but trouble with GriefPrevention and other plugins that use hasPlayedBefore()!
EDIT: Feildmaster recommends using PlayerJoinEvent instead of onPlayerLogin
-
View User Profile
-
Send Message
Posted Jan 28, 2013@hatixon:
It's at 80.000 As defualt
-
View User Profile
-
Send Message
Posted Jan 28, 2013@Jonasbilljensen
Check your config for total block size allowance.
-
View User Profile
-
Send Message
Posted Jan 28, 2013Hey, so I've been trying to get this to work on my 1.4.7 server, but I keep getting the same issue over and over, I can do the initial chest claim just fine, but after that when i want to claim more with the golden shovel, it keeps telling me that I need another 20.000 blocks to claim an area thats around 15x15 Hope you can help me out, as I really want this plugin on my server ;)
-
View User Profile
-
Send Message
Posted Jan 28, 2013@Urlryn
It doesn't work inside land claims. It's meant to undo player changes in the wilderness. If you want to remove something a player has claimed, you have to /deleteclaim first to remove the land claim. This makes it safe for you to remove something unwanted right next to a player's claimed land without worrying about accidentally removing something inside of the player's claim.
The reason I showed the restore nature to remove the npc village was to prove that it effectively removes all types of blocks, even on a large scale like an entire npc village, very quickly, restoring the location to a "natural" state. Generally in practice, I wouldn't use it on an npc village. It was just for demonstration purposes.
@xclucky
Oh, I get it. You want LWC to NOT create a protection. For that to work, the LWC guy would have to set his event handler to a higher priority than mine, so that his code would run after mine (and only if mine did not cancel the chest placement event). It's not something I can fix on my side, because my event priority is already set to the lowest it can go.
I suspect the LWC guy will tell you he doesn't want to do it because it may allow other non-anti-grief plugins to take actions based on the chest placement before he has a chance to cancel it. There aren't any 100% happy solutions to your problem, which stems from trying to run two player-driven protection plugins in the same world.
-
View User Profile
-
Send Message
Posted Jan 28, 2013@bigscary
Let me try to explain this another way. Yes LWC should have priority over GriefPrevention. There is a bug though, when a player without build permission trys to place a block that automatically registers (a chest for example), GriefPrevention removes the chest, however, the protection is still added. So say for example a server, like mine, were to have an automatic register on wooden buttons, a player without build permission could walk into another players claim, place a wooden button on a diamond block, and lock that diamond block. See where the issue is? Sorry if it's still hard to understand, I can make a video if you need me to.
-
View User Profile
-
Send Message
Posted Jan 28, 2013Awesome plugin! Combined with Population Density....just love them!
I'm fairly new to Minecraft so maybe I'm missing something obvious.....
Trying to figure out the restorenature stuff. I have yet to get it to work.
In the documentation you said you can't do this within someone's claim but just before that you said its used to very quickly revert player-generated changes
Players can only change things in their claims correct?
In testing I had a user build something in his claim and i tried to naturerestore...nothing happens. I had a user knock down a part of a hill in his claim....tried naturerestore...nothing I had the user get rid of his claim which left the mess....then tried naturerestore again.....still nothing.
In a video it shows how to use naturerestore but its on a NPC village....they aren't doing the griefing. Its the players. but with GP enabled...where does naturerestore come into play or use?
Thanks Urlryn
-
View User Profile
-
Send Message
Posted Jan 28, 20137.4 Updates!
-
View User Profile
-
Send Message
Posted Jan 28, 2013Hey everybody, there's a bug causing the "my brother got banned when I did" problem:
https://bukkit.atlassian.net/browse/BUKKIT-3521
There is no workaround, except to disable smart ban entirely, which will open you to attack by griefers who are aware of the vast lists of username/pass combinations published on griefer forums and websites everywhere.
@deleted_9935739
Fence gates lock to prevent players from using wheat to steal animals from fenced pastures, and buttons/levers lock because some redstone gadgets dispense goodies or provide some other services that players don't want to share with the public. The fact that iron doors lock is a happy accidental result of that.
So the ender pearls thing is only really an issue for pvp servers where players have no other means of protecting themselves from pvp than by building, and a patient griefer who has fighting gear and ender pearls, and the patience to seek out a worthy victim, and the knowledge of the bug and how to abuse it, and an opportunity (suitable door or window for example). Oh, and he has to have kept a low profile all the while, otherwise you would have banned him already, and he doesn't care that you ban him, even though he's spent time getting his gear together. So while this could be a problem, it's a very rare one.
Anyway I'm giving you a config option in today's version so you will be happy. :)
-
View User Profile
-
Send Message
Posted Jan 28, 2013@bigscary
If that's how you view things, then what's the point of locking doors in your plugin?
-
View User Profile
-
Send Message
Posted Jan 28, 2013@Ninja486
See admin details page.
@Absolutionmc
It's probably more efficient to use GP, but I don't think anyone has ever done a large scale comparison of the two, so if it's statistical proof you're looking for, you probably won't find it.
@deleted_9935739
Sorry, I still don't understand how being in a location in the world you shouldn't be in is a problem. Are you worried intruders will see the signs you've stuck all over your walls with your social security number, minecraft password, and the URL to your top secret sex tape?
@ooarashi
Suppose I added the 1 block buffer. Then players would build stuff inside that buffer (because it's protected, right?), and the problem would be the same.
@anfereon
It doesn't work in administrative land claims, so you can use those where you don't want players using the command. They need it for other cases, otherwise you'll be saving them all the time manually (or installing another plugin to fix it).
@AbbyMaeTaylor
GP doesn't leave files open. You can ask your hosting provider to give you a list of all the open files. You'll probably find that they are region files (meaning Mojang code is leaving them open). It's a not-so-common issue that plagues some servers whether they run GP or not. The best fix is to ask your hosting provider to grant you a higher maximum, or to schedule routine reboots of your server (say, every morning at 4am when there are fewest players online).
@LeeTheENTP
It's probably not really his brother, more likely the same player with a second account (possibly borrowed from his brother). But the option is labelled smart ban in the config file. It only bans players who have never been on the server before AND who have the same IP as a recently banned player. It doesn't make sense that a brother would decide to join a server AFTER his brother was banned, which is why it's probably not a brother/friend/sister/cousin/whatever.
@dmncpham
See common problems and questions page. :)
@deleted_9935739
Except for the config options, isn't that exactly how I have it?
@joshwenke
I think you can probably do it already, I'm not sure. If not, I'm sorry but I'm not planning to add it.
@RemyPas
As a workaround to the Mojang bug where ender pearls can get through doors and other thin blocks, suggest to your players that they build piston doors. I'll consider adding an option for this.
@Gamemasher
I'm sorry, I don't understand your question. "the under it that I own it"? Please explain.
@Absolutionmc
You have to learn regular expressions, sorry. It's a deep topic I won't try to teach you here. Bing it, it's all over the internet.
@ManBeastPigDev
It's still /deleteallclaims, not /abandonallclaims.
@jakenem12
Sorry no, it's a lot of work for me. Especially in the future, because I would have to keep the two projects in sync.
@andyhoi
Sorry no, it causes more problems with other plugins the old way than the new way.
@IwannaDashInName
There's no way I can try to support servers in offline mode. Disable smart ban, I guess.
@xclucky
Sorry you're having trouble, but others would argue that LWC should have priority. Most only have one or the other, not both.
Tickets are harder for people to use than comments, and nobody bothers to search existing tickets before creating a new one, so there's little benefit. So I just answer comments.
@Tuxtard
See notes for Tekkit servers above.
-
View User Profile
-
Send Message
Posted Jan 28, 2013Hello, can you please tell me how to protect my claims from Weaponmod's and IC2's explosions? I've tried making a claim and if an other person drops some dynamite from Weaponmod or IC2 it destroys both the land blocks and the chest as well :/.
Obviously nukes from IC2 would wreak havoc as well.
-
View User Profile
-
Send Message
Posted Jan 28, 2013This plugin does not have priority over LWC.
I have wooden buttons set to automatically register, however, a player can place a wooden button in another players claim and it will still place the protection, even though they do not have sufficient permissions to build there, however, the button will be removed. Could you please fix this?]
PS: Ever thought about a tickets section?
-
View User Profile
-
Send Message
Posted Jan 28, 2013Is there a way to better config of smartban? When player get banned and he try to log to other's player account (authme don't let them go), innocent player is banned. Even admins - griefers love to try login to admin account and trying stupid passwords.
sorry for not so good english
-
View User Profile
-
Send Message
Posted Jan 28, 2013Have you thought about using the Bukkit ticket system (or equivalent, Github?) for suggestions and bugs? I think it would strengthen the community around GP and make it easier to support suggestions/improvements and report bugs.
Also you wouldn't have to answer the same questions over and over again with long texts .. you could refer to the ticket system and it would be easier for anyone to help answering (I'd do that).