LWC
- Download
- NOTE!: Development builds for LWC can be found at the below Jenkins server. These builds have not been approved by the BukkitDev staff and may not have gone through any QA processes. Use them at your own risk!
- Development builds (Jenkins)
- Feature requests, Suggestions and Issues
- IRC - Live Chat ( irc.esper.net #LWC )
- github
- wiki
- Donate
LWC is the longest-lived single block protection plugin that protects both the block itself and contents of Chests, Furnaces, and Dispensers. It can also protect any other blocks, and by default will also protect Doors (Wooden + Iron), Signs and Trap Doors.
Blocks can be protected with three basic protection types:
Private
By default, only you can access this protection. You can also modify it (or specify when creating) to add other players or groups to the protection, so they can access it. Say you wanted Notch and Hidendra to both access the protection. When creating the protection, you could do /cprivate Notch Hidendra
or if it already exists /cmodify Notch Hidendra
. If you wanted to remove Hidendra from the private protection, you can use /cremove -Notch
Password
A password is set on the protection and anyone that knows the password can open it. You yourself also need this password each time you log in.
Public
Mainly targeted at community chests, a Public chest means just that: anyone can access it, but no one can protect it which makes it advantageous because it cannot be made private by someone else.
Commands
/lwc
- The LWC command for everything, however aliases are available to make some commands shorter. Type /lwc in-game for more detailed help./cprivate
- The alias of /lwc create private (or /lwc -c private), it creates a private protection./cpassword <password>
- The alias of /lwc create password <password>, it creates a passworded protection./cpublic
- The alias of /lwc create public, it creates a public protection/cremove
- Allows you to remove a protection you own (or if you're an LWC admin, any protection) - you must click on the protection after using/cremove
in order to remove it./cunlock <password>
- Allows you to attempt to gain access to a passworded protection after LWC tells you you attempted to open a password protection.... more!
There are aliases for all major used commands and every alias is not listed here.
Permissions
Basic permissions:
lwc.protect
- Allows the player to create and manage their own protections. It also allows them to use enabled modes and flags.lwc.mod
- Allows the player to open any chest, but not remove them.lwc.admin
- Gives the player absolute power to LWC - this node should be considered dangerous if used incorrectly as this node essentially gives you the right to destroy every protection (and even the block & inventory contents associated with it) in one command!lwc.deny
- Prevents players with this node from interacting with anything LWC can protect. For example, from opening or destroying protected and unprotected chests, furnaces, etc if protectable.
@ukAdamR I also have the TNT not working near chest problem.. this is an issue for my server of Factions wPvP as it does not allow raids
What option controls this in the config or is this a bug?
I am currently running b489 - please advise.
@Hidendra
I configurated it like that in the worldguard file:
And users can still lock everything they want to whenever its in their region or not.. :(
@Hidendra Oh, VERY COOL! I will give this a shot, thanks. Edit: Just tried it with jukebox and brewing_stand, and it works GREAT. Thanks haha.
Also, is there any chance that you might add Towny support? I believe Lockette supports towny in that, a mayor of a town, can clear a plot, and removes all locks from chests in the plot. The Author of Towny has had many (several?) requests about LWC, and he is directing them to talk to you but, not sure if they have. Just wanted to run it by you. Thanks again for helping me out.
Just wondering but is it normal for LWC to block explosions? TNT doesn't seem to work at all if it is within around 5 blocks of anything protected.
It's nice to keep protected entities invincible, but is it possible to allow TNT to break all the blocks around it as normal?
<<reply 441316="">>
It is, you can have any block lockable. In
plugins/LWC/core.yml
find something like trap_door: xxxCopy that under it (so it copies that and enabled: true) and change trap_door to note_block.
You can do this for any other blocks including brewing stands. If you want to use the ID, you must encase it in quotes; e.g '54': NOT 54:
Hi, Hindendra, great plugins. A serious staple across MANY servers I imagine, including my own.
Had a question for you.
Would it at all be possible to be able to lock Jukeboxes? Discs are really rare, and I almost always hear about disc thefts on my server (I apologize if this has been asked, and I missed it.
Additionally, It would be great to get locks on the new Brewing Stands in 1.9/1.0. Potions can easily be taken from them with no locks at all. (Again, if it hasn't already been asked.)
<<reply 441173="">>
Replied as well ;)
The version of LWC-Economy you are using is not compatible with LWC 4.
Please upgrade it to the LWC 4 compatible version: http://ci.griefcraft.com/job/LWC-Economy/38/artifact/build/LWC-Economy.jar
Hopefully you can help with my lwc error and why chests and signs are not getting protected. http://forums.bukkit.org/threads/lwc-help-error-when-placing-signs-or-chests.47840/
<<reply 440877="">>
By default, chests, furnaces, dispensers, and signs are protected to Private by default. Doors are not protected by default. However, this can be changed very easily in "plugins/LWC/core.yml" (just search "chest:" and you should understand how it works). You can also disable any protectable block here, too, or add more.
As RustyDagger already pointed out, there is not a lot of ways to crack open or break a protected chest at the moment. There is, however, one way that it can be done but it is caused by Minecraft itself and there is no (easy) way for me to block it, which is why I will not be disclosing how to do this publicly. It does however take time to perform and whoever does it makes it obvious they did it.
Using lava and any other blocks will not stop chests from being useful. As RustyDagger also said, one can simply just wrap it in protected furnaces, but all this does is annoy the owner, nothing more, and even paints a "griefer" sign on the player's head. I have never seen this done in practice, however.
LWC prevents explosions from destroying any protections. LWC also prevents doors and signs from being removed by removing the block under them. For wall signs, LWC prevents the wall it is attached to from being destroyed.
<<reply 440980="">>
Ah, right :)
@bigscary There is no known way that i know of that a greifer can destroy a protected chest unless you know you were really stupid and they had lwc.admin.
in theory a greifer could surround a chest with his own protected chests however you could set limits from ingame so that X group can have more than X protections. (not quite sure how this work with superperms.) however on my server i allow unlimited protections and i have not seen a case of this yet as i was saying before iv been using it a long time (since hmod) so ya... its a good plugin and its easy as pie to setup.
@hidendra remember when I was requesting that mod's could not effect admins chests :D also it was the magnet feature i made a feature request for some thing like it and it just so happened u had already made it :D
Hi, Hidendra! Thanks for working so hard on answering a major griefing problem. :) From the docs, I'm unclear on one point - are chests and doors protected by default, or do players have to be aware of and use the slash commands correctly to protect those items?
Also I worry a little about resourceful griefers. Is there anything preventing a griefer from destroying a chest by placing lava next to it, or covering it up with his own protected block? Can a lava source block be protected? Can nearby explosions kill my protected chests or doors?
I know I could test these things to find out for myself, but in case others also want to know, maybe some notes in the description? :) Thanks again!
It appears the plugin is not downloading the files needed. I'm running CB1531.
Recieving this stack when enabling the plugin:
2011-11-29 20:33:06 [SEVERE] Error occurred while enabling LWC v3.54 (Is it up to date?): null
java.lang.NullPointerException at com.griefcraft.lwc.LWCPlugin.loadDatabase(LWCPlugin.java:163) at com.griefcraft.lwc.LWCPlugin.onEnable(LWCPlugin.java:291) at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:188) at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:957) at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:280) at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:182) at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:165) at net.minecraft.server.MinecraftServer.t(MinecraftServer.java:337) at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:324) at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:161) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:388) at net.minecraft.server.ThreadServerApplication.run(SourceFile:457) ======
<<reply 440748="">>
I refuse to make LWC require a plugin for permission or economy purposes. LWC already uses its own easy to use API that supports all major permission plugins, and all major econ plugins (iCo 5, 6, BOSE, etc)
This is already possible :)
In plugins/LWC/worldguard.yml, change
enabled: false
toenabled: true
and make sure you have- '*'
underregions:
Suggestions:
For easyer codding I suggest you make it use Vault (for permissions and iconomy) and other is to add option that allows users make protections in their WorldGuard regions cuz now some of them walk around and lock everything they want to...
But the plugin is SUPER doesnt require signs and other shits, easy to use and etc... only the things above are the missing thing :) Thank you for supporting the plugin once I tought that you are no more going to update it :) THANK YOU!!!
@RustyDagger
Thank you, I am much obliged. Can't say I remember exactly which feature it was but I certainly (definitely) remember you from ye olde hey0 days ^^
@Hidendra I would just like to say thank you for the awesome plugin with out your tireless work my server and I'm sure many others would be a greifers paradise. for well over a year now your plugin has been a constant in my server never once being removed due to a fault or issue I still remember that time you sent me an early build because it had a feature i was looking for :D.
so from me and the guys at crazycowgaming.net Thank YOU :D
Edit Sent you a gift as well :$
<<reply 440134="">>
Soon™
In all seriousness, I do not yet know and will not know until the day I decide it's ready. I'd like to say real soon but such ideals aren't working very well. I wanted LWC 4 to be released during October -- I didn't say it WOULD be, however, that was what I wanted; October was the month LWC turned a year old. Things happened and it got pushed back. I'm the only dev on LWC so while I devoted a huge amount of time at one point directly to LWC, these days I have a lot less free time :-(
There's still a backlog of stuff that needs to be done and of course the (large) undertaking of lessening the need of config files. But the last thing may be put off for a later version, because as it stands right now LWC 4 is >260 commits ahead of LWC 3.
I can't say when I plan to, but looking at the (ever-growing) backlog, I could most likely have it released by (or on, knowing my luck) Christmas if I were to drop the dreaded config stuff (for now?) and begin the translation phase soon. That idea is appealing to me and it may very well happen that way.
The testing aspect of the release can be lessened gladly, however. Many servers are already using LWC 4 and it has proven itself admirably. But alas, testing will still take a solid day or two of tedious work to ensure critical parts of 4 work properly (build-based updating has been tested thoroughly, but not so much the version-based updating portion.)
<<reply 438792="">>
Any permission plugin that supports SuperPerms. Backwards compat support is also in for those plugins that support the Permissions 3 API.
So, virtually every Permissions plugin :)
@Hidendra
When do you think the dev builds will be released? Cause I really want to release my plugin that requires a method not in the current build.
Heyho @Hidendra
I postet some bugs with the new builds in the Forum, because I don't want to register on github, for only on ticket ;) LINK
They should make this clearer, what permissions plugins is LWC compatible with?