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 Jun 9, 2012possible to have lwc respect residence protection?
kinda annoying having players lock chests they cant access in residences they dont own
-
View User Profile
-
Send Message
Posted Jun 9, 2012@lexplay
@Hidendra
I have the same problem. The issue is to do with Vault support that was added in the latest build. If you remove Vault from your server LWC will work correctly again.
For the timebeing I am having to stay on 4.11 as well. I've posted an issue on GitHub about it and why I think it is happening.
-
View User Profile
-
Send Message
Posted Jun 8, 2012TNT is removing protections? How can I disable it?
-
View User Profile
-
Send Message
Posted Jun 7, 2012@YoFuzzy3
If you keep JUST the database file people wont have to relock their stuff again... :)
-
View User Profile
-
Send Message
Posted Jun 7, 2012Hey, I have a problem with the newest build of LWC. I use PermissionsEx, which is my favorite permissions plugin. However, the permissions are not working on LWC. Even without "lwc.protect," players still create LWC locks when they place signs, doors, and chests. Is this a problem on my side or yours? Thanks.
-
View User Profile
-
Send Message
Posted Jun 6, 2012@Hidendra
Is the wiki down - I can't get to it on griefcraft.com. If you need a place to host it, you are welcome to put it on my /wiki... just let me know and I will set it up for you.
-
View User Profile
-
Send Message
Posted Jun 6, 2012Sorry Hidendra,
Do you know if/when a support for multi worlds would be implemented? I see a lot of people trying to restrict LWC per worlds on their server, but for the moment, it seems that the only solution is to remove the automatic private security on chests (or others) and to remove the possibility to use the LWC commands per world but the default of this is that when then have to secure each chests manually in the authorized LWC worlds
hoping my message in clear :) thanks for your help and all the great job you did already!
-
View User Profile
-
Send Message
Posted Jun 6, 2012I have a question.
Since a few days, my players cant see the name of the people who protected Chests or Doors. I with admin permissions CAN see all the names, but my players cant.
is there a new permission or did i miss something?
Greets!
-
View User Profile
-
Send Message
Posted Jun 5, 2012Tekkit support is indeed available, just make sure you use http://ci.griefcraft.com/job/LWC/708/
@lexplay
1.Could you try assigning the permission group.groupname to the groups to see if it has any effect?
-
View User Profile
-
Send Message
Posted Jun 5, 2012Hey. Can you add Tekkit support? So we can protect Reinforced doors and energy condensers and crap.. Thanks.
-
View User Profile
-
Send Message
Posted Jun 5, 2012The 4.2.0 update broke some features that worked in 4.1.1:
1. Group limits do not work with PermissionsBukkit. The default limit works, and player limits work, just not group limits. It seems like LWC does not detect that you are in a group, and will not assign you the correct limit (it just assigns you the default limit).
2. showMyNotices: true does not work. Even if you have it set to true, players will not see the message they are supposed to see (Notice: That Private Chest is locked by you). Ops, however, see the message fine regardless of whether this option is on or off.
I'm certain my configs are correct, as I replaced the 4.2.0 jar with the 4.1.1 jar and found both of these features working again.
If anybody else is having these problems, I suggest downgrading to 4.1.1 and setting "method: MANUAL" in core.yml until these problems are fixed.
-
View User Profile
-
Send Message
Posted Jun 4, 2012@wynneth
Well I deleted the entire folder, including the database. Not sure if it was necessary. I think you would only need to delete the .yml files.
Just start with the .yml files, because the config files are quite different now. If that doesn't work, delete everything. But I warn you, if you do that, everyone will have to relock all of their stuff again.
Hope I helped :P
-
View User Profile
-
Send Message
Posted Jun 4, 2012Is there a wiki for this plugin, the current wiki is giving me a 404 error.
-
View User Profile
-
Send Message
Posted Jun 4, 2012@YoFuzzy3
I'm having the exact same problem as you it seems, lwc 4.2.1 with newest craftbukkit recommended build and those exact errors. Can you tell me what kind of updating of config files you did?
-
View User Profile
-
Send Message
Posted Jun 4, 2012dont know if this is the right place to post but I'dd like to know if it is possible to disable LWC per world?
without having to remove the rights in permission plugin as I still would have the automatic private LWC on chest on the world I would like to have LWC disabled, and I do not wish (if possible) to remove this
thanks for your help!
-
View User Profile
-
Send Message
Posted Jun 4, 2012Is it just me or are the tickets being ignored?
-
View User Profile
-
Send Message
Posted Jun 4, 2012Ok I'm so sorry, 4.2.1 is working just fine. I only needed to update the config files. Everything is working perfectly now! Amazing plugin!
-
View User Profile
-
Send Message
Posted Jun 3, 2012@YoFuzzy3
what permissions are you using,
also 4.2.0 is still working fine with the current bukkit build, and dev builds are known to have issues now and again
but thanks for testing it for them and letting them know they have problems but in the meant time if you want it to just work stick to 4.2.0
-
View User Profile
-
Send Message
Posted Jun 3, 2012Hi, I'm running LWC version 4.2.1 (b700) with CraftBukkit 1.2.5-R3.0 on linux. I've been getting these 3 errors.
The first one is definitely caused by LWC.
The other 2 I'm not exactly sure if they're directly linked with LWC.
and
Thanks, I hope you can help.
-
View User Profile
-
Send Message
Posted Jun 3, 2012Is it possible for you that if a user doesn't log in for a certain amount of time that the chest disappears and the lock too? It's quite annoying that some people place chests and never join the server again.