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.
You should add a oposite function of donation. That players can take out and not put in.
Is there a way to prevent the plugin from sending a message every time I open something?
Is there a way to stop the plugin from sending a message in chat every time I open something?
I do not understand this plugin. I have been trying to make it work on beta but all it does it update to the newest version and render itself useless. Disabling updates (to MANUAL) does not help either.
Can I do that when I put chests, they are always public and only private when I put the command?
Is there how I forbid protecting in a particular world?
Up to date version : https://www.spigotmc.org/resources/lwc-extended.69551/
So I'm on a server using this plugin, and I remember being able to lock and unlock doors that I owned with a protection on them by shifting and right clicking. This would make a noise kind of like an anvil and would make text saying that you locked or unlocked the door. They are claiming this feature never existed and I want to know if this is a feature of the plugin because I am 100% sure I was able to do this.
In reply to redstone_4:
How do I stop the blocks becoming private as soon as they are placed, because I would like it so you have to manually /lock them.
Where it says autoRegister: Private - Remove the whole line.
Then just save and make a reload, and you're done. :-)
Hello i am very sad the Update of this Resource here wars this:
https://www.spigotmc.org/resources/modern-lwc-continuation-of-lwc.2162/
and the Producer has give it up and mean i take it over that problem is soo many Puples want this resource so is my question can jou make great Again this Plugin ? Please!
In reply to Forge_User_29322148:
Hello, I have two problems, I would like for the next update of the plugin let us modify the messages since they only come in English or have some colors that are not very nice and I would like to modify it and the other problem is that when giving permission Of "lwc.mod" does not work for them, they can not interact and can not do anything and I would like you to solve that error please
LWC has ben update here: https://www.spigotmc.org/resources/lwc-unofficial-entity-locking.2162/
Is it possible to configure the .yml and add other blocks to give them /lock? For example: Shulker box
maak 1.11.2
In reply to Forge_User_33306948:
In reply to Forge_User_33306948: