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.
Is there a way to allow players to create their own groups without needing a mod?
Should I increase the cache size if the number of protections is getting close to the cache limit, ie what happens if the protections exceed the cache limit?
@sumdream
Frameprotect will do what you want
http://dev.bukkit.org/bukkit-plugins/frameprotect/
hi,im using LWC on 1.79 spigot r0.3.it can not lock Item Frame.can u help me?
@godgodgodgo
Yes, it is. :(
Jenkins is down.
@Jacold
I thought I read something in the config about hoppers, does that not affect this?
@thequestingbeast
1.8 won't be bringing the name change feature.
How to prevent stealing items from chests using minecart with hopper?
I noticed this item for the 1.8 update:
"Containers can be locked in custom maps by using the “Lock” data tag"
Will LWC be leveraging this in the future?
@thequestingbeast
If you check on the Jenkins system you will find the latest version. It does have UUID support in.
Hope it helps!
Can you give us some reassurance that LWC will be updating to 1.7.9 to handle UUID before 1.8?
BUMP:
How come just turning off click open for Iron Doors makes wooden doors no longer open and close automatically? Is this a bug I need to report or just the way it is?
LWC don't work for superior ID than 4095... How can I fix it ? ):
It's on my 1.5.2 unleashed feed the beast server.
core.yml : http://pastebin.com/URdSup4M
Suggestion:
How about a new command for admins, something like:
/lwc clear <radius> <..flags>
With certain flags such as:
-a : remove all items in locked blocks (if theyre containers)
-b : delete the blocked items
etc.
And maybe the permission:
lwc.admin.clear
Basically this command would act as a huge help for administrators on servers with lwc, who need to clear inactive items in towns, or maybe factions.
@manuelgu
It allows players to put in items, but once they put in the items, they cant take them out. Only the owner of the chest can take out the items.
Can you add a permission/feature to LWC that is like: lwc.protection.viewonly?
Basically this is similar to the lwc.mod permission, but the person who the lwc.protection.viewonly permission can only look inside protection inventories but can't take anything out of them?
@IcedEclipse
Mine works..my players wanted this so if a user was to stupid to protect their chest they wanted to raid it so I turned auto off...Here's the config...
How come just turning off click open for Iron Doors makes wooden doors no longer open and close automatically? Is this a bug I need to report or just the way it is?
Hey! Does anyone know a permission that restricts users to only locking chests privately (they can't make password protected chests, donation chests, etc.)?
Also maybe I'm doing something wrong but disabling autoregister doesn't allow chests to be placed down unlocked?
Thanks for any help.