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/cremovein 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.
-
View User Profile
-
Send Message
Posted Jul 11, 2013@Andy_Fox
Update to the latest LWC-Economy from Jenkins ( http://ci.griefcraft.com/job/LWC-Economy/ ) as well - forgot to mention that in the changelog or my last post.
-
View User Profile
-
Send Message
Posted Jul 11, 2013I am running dev #881 and it seems to work without a hitch, but this update seems to have broken LWC-Economy. Is there any way to make players pay to lock things with the latest version?
-
View User Profile
-
Send Message
Posted Jul 11, 2013LWC release 4.4.0 has been uploaded to DBO and is pending approval. It is build #881 on jenkins.
@Dead_Island_Dude
That should be happening are you using a craftbukkit fork? Are you using latest builds of whatever CB you are using? Also try using the latest version of LWC on Jenkins as it's the very latest - beta 3 is 3-4 months behind the just uploaded release.
@raum
I did add entity support at one point but it was such a hack so it was only 'to see if I could'. Internally LWC has zero support for entities so I'm hoping to support entities much better in the rewrite
@Erudin1
Use the latest release / build #881 it should be ok.
@A7xConnor
You have `ignoreExplosions` set to true. LWC ignores all block destruction when that is set. You may also want to use the latest build. I just tried it and it's working fine for me.
-
View User Profile
-
Send Message
Posted Jul 10, 2013In the most recent version (LWC 4.3.2 Beta 3), I noticed that when you break a protected block, the protection is still there. To get rid of the protection, you have to use /unlock. Do you think you could set up again so that when the protected block is broken, the protection is removed? I have also found that the auto register function is not working correctly either. I know this is a beta build, but could this possibly be fixed sometime in the future?
-
View User Profile
-
Send Message
Posted Jul 9, 2013Fix this alreadyyy:
https://github.com/Hidendra/LWC/issues/588 http://dev.bukkit.org/bukkit-plugins/lwc/forum/40258-explosion-protection/
-
View User Profile
-
Send Message
Posted Jul 9, 2013Signs are not protactable with Passwords anymore on 1.6.2! I can lock them with a Password, but other players are still able to use the password protected signs like they are not protected. Fix it as soon as possible pls!
-
View User Profile
-
Send Message
Posted Jul 8, 2013@V0ROBEY
As of right now, LWC cannot lock donkies, or any other entity chests - Was just fixing to post a ticket feature request regarding this :)
In the mean time, Shameless Plug: The plugin 'Stables' (http://dev.bukkit.org/bukkit-plugins/stables/) will allow you to claim horses, effectively locking them from anyone else (amongst many other things).
-
View User Profile
-
Send Message
Posted Jul 8, 2013Is there possibility to lock donkeys' chests? Yeah, it's working fine with 1.6.1 though
-
View User Profile
-
Send Message
Posted Jul 7, 2013i have my server set so only admin can create lwc protections within worldguard regions, but every time a non-admin places a chest or other lwc protect-able block, it gives them this message: "You have exceeded your allowed amount of protections!" "LWC protections are not allowed outside of WorldGuard regions!"
Is there any way to remove these messages? it spams chat and annoys the players...
-
View User Profile
-
Send Message
Posted Jul 7, 2013@ ShawnPR1
How I said:D When you could save animals, so just YOU can ride and kill them, it would be grate:D
-
View User Profile
-
Send Message
Posted Jul 7, 2013I keep getting this error http://pastebin.com/RDbvysES and players have reported their locks dissapearing, am I doing something wrong? I had no issues prior to 1.6
-
View User Profile
-
Send Message
Posted Jul 7, 2013This plugin is working fine for me no problems (so far) on 1.6.1.
-
View User Profile
-
Send Message
Posted Jul 6, 2013I have it on my 1.6 server. Not one error and seems to be working perfect (:
-
View User Profile
-
Send Message
Posted Jul 6, 2013How about enabling this for the updated 1.6.1's leads?? You know : the thing with which you hook your horse to a fence
-
View User Profile
-
Send Message
Posted Jul 6, 2013Update To 1.6
-
View User Profile
-
Send Message
Posted Jul 5, 2013i end up doing stop to my server. it seem like my permission is mess up or that this plugin is broken. let me know if anyone got same problem before i report it with tickets
permission plugin i using right now is PermissionsBukkit 2.1 on MyMcAdmin. there lot of plugin down as well. you not the only one
-
View User Profile
-
Send Message
Posted Jul 5, 2013Srry that I write a comment, but I don't want to register extra to open a ticket. But can you make it possible to save Animals and not just Chests, Doors etc? Because then you can prevent horses to get stolen. And Animals of others killed.
-
View User Profile
-
Send Message
Posted Jul 4, 2013I have this error in my startup logs, since a very long time ago:
However the plugin works fine. I just like to have clean logs, so... could somebody help? Thanks.
-
View User Profile
-
Send Message
Posted Jul 3, 2013@XZhyperX
It worked fine on ours.
-
View User Profile
-
Send Message
Posted Jul 3, 2013Does it work okay with 1.6.1?