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.
Any chance this will work with 1.8.3 Spigot?
Having some issues with the new doors. they will auto lock but anyone can open them. known issue or new one maybe?
Shiro from Deadman Wonderland ;3
Please fix this urgently: If the server that uses freeze bow to kill one chicken standing on the chest, it does not protect! After the freeze fired the arrow into the chest of anyone who disappeared without a trace. I've had headaches with this issue for more than 2 weeks now that no solution until there is a bug in mem disclose morebow with freezebows feature!
@mikethekitty
Thanks! Works great!
@AeonofShadow
Hey Aeon I can help you with this :)
You will want to go into your plugins folder and go to the LWC folder, open up the core.yml with notepad or notepad + + this is what you will want to edit >> http://pastebin.com/26yBfpaj << if you want you can do what i did with the last 2 items (i'v cut the paste short) where I have removed the text that says auto register false, on the furnace and everything else, and just left it on the chest as a reminder. hope this helps :)
Edit: Btw im running 1.8.7 and have no issues at all with this plugin either *high five* :D
Hi! I don't have any problems with the plugin! I was just wondering whats the setup to have placed chests unprotected and players must use the command to lock it themselves if they don't want it accessed. Thanks.
Hello!
I´ve tried to open a chest with "/lwc admin view [id]" but the command didn´t do anything (it wrote "/lwc" only). Is there a bug that needs to be fixed or am I doing something wrong? I couldn´t find any other help.
Thanks :)
please update this plugin on 1.8.x
Everyone wanting 1.8 support and item frames and armor stands ...
http://www.spigotmc.org/resources/lwc-unofficial-entity-locking.2162/
A update to Minecraft 1.8.x would be so good. :)
Huh... Last build 3 months ago... I was really hoping for armor stand support.
@IamYourDoodie
Ah never mind what I said below. Build#938 doesn't seem to work on frames and armor stands =/ Well, 1.8.3 isn't that ;)
@Bronzeteufel
I was wondering the same thing. Ended up trying a Jenkins development build #938 and is working great with Spigot 1.8.4 so far. Good luck!
Is there support for spigot 1.8.4 right now?
@alteropa
I think you seriously need to grow up. The plugin works, yes it does need some updating.
People running servers with such an immature attitude is what gives the server owner/admin community a bad name.
By the way, are you paying for this plugin via licensing for full time support? Is it costing you $20,000 plus per annum contract negotiated?
Something you need to consider before posting comments like that.
@alteropa
Works fine for me, must be your 'shit' server setup thats causing the problem.
@alteropa
This "shit" still works...
And try to be a little "kinder" for "shit" you need. Can't say it makes it sound like you're overly appreciative when you use the term "shit" in reference to something...
How rude..
And if you're finding that release builds on this page aren't working... Try looking at development builds. -.- Do some homework and you'll find it'll work just fine..
@Bronzeteufel
Delete and allow your config to reload. There should be support for Armor Stands if I recall
Update this shit!
i need this!!!
Would be nice if there were support for armor stands :)