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 Apr 27, 2012Is the Documentation/plugin a little outdated?
I installed this... and by default ALL my players can use LWC without me giving them lwc.protect in bpermissions. Also, I'm trying to make it so the default behavior is to not protect. However, the documentation doesn't give any info on what to change in the core.yml for AutoRegister. its default to private. How do I set it to never auto lock?
I don't want people to go around everywhere littering the server with autoprotected chests... So I'm setting it so they have 10 max and it costs 500 game dollars to place one.
However, I would like for them to be able to normally place unprotected chests by default and only choose to protect.
I also don't want everyone to be able to lock by default.
LWC: 4.1.1 Bukkit: 1.2.5R1
-
View User Profile
-
Send Message
Posted Apr 26, 2012Long time LWC lover here. ^^ Requesting addition of a command for users to have LWC go quiet on either a global or individual basis.
i.e.
/lwc ignore self - remove own access messages
/lwc ignore <player> - remove access messages for protections by <player>
/lwc ignore all - remove all access messages
-
View User Profile
-
Send Message
Posted Apr 22, 2012In the config file, I saw that there is a value under protections called "quiet." It says this will disable messages for the protection. Does this disable all messages, meaning creation, deletion, and when other players try to delete or use a protected block that belongs to another player? I am looking for a way to not show protection creation messages, but when another player tries to break or use a protected block, they get the message telling them that they can't break or use this block. Is this possible?
-
View User Profile
-
Send Message
Posted Apr 21, 2012Server returned HTTP response code: 503 for URL: http://metrics.griefcraft.com/report/LWCI keep getting this error. I would like it to be fixed, though it doesn't seem to be affecting anything. Thank you!
-
View User Profile
-
Send Message
Posted Apr 21, 2012@Gunnerrrrr
Same here, but I don't think LWC have multi-world support...
-
View User Profile
-
Send Message
Posted Apr 21, 2012@G3nocider
After I switched to mysql, my server run just fine. Try Mysql.
-
View User Profile
-
Send Message
Posted Apr 21, 2012lwc better on mysql or h2?what better?im using now h2.its laggy,becouse in my server playing a lot of people.
-
View User Profile
-
Send Message
Posted Apr 20, 2012I want to deny people from just LOCKING items in my griefing world but be able to lock in my non-griefing world.
I probably did a basic thing wrong but idk...
-
View User Profile
-
Send Message
Posted Apr 20, 2012I am having problem with auto-registering. It is turned off but still it registers there signs automatically. It's quite frustrating because now I have a million signs that can't be broken until I remove each sign protection.
-
View User Profile
-
Send Message
Posted Apr 20, 2012@godgodgodgo
no it doesnt... cause i have the same error,too
-
View User Profile
-
Send Message
Posted Apr 20, 2012@tomomosius
That's what I did though! The plugin even has a config for groups it seems in limits.yml I set "Default" to 0, and "VIP" to unlimited... But Defaults still lock stuff automatically...
-
View User Profile
-
Send Message
Posted Apr 19, 2012@joannou1
try giving the nodes only to vip group i think that should do the trick
-
View User Profile
-
Send Message
Posted Apr 19, 2012Please i need your help, everething thai os usable(chests, furnaces, doors, etc) isnt working, you can put them on the groud, no one can destroi it but they can use it. att turolla
-
View User Profile
-
Send Message
Posted Apr 19, 2012@Hidendra
I don't know if you saw my comment, but I have tried everything to get it so that Defaults can't use LWC, and so that VIP's can. Instead when I give a negative node to Default, and a positive node to VIP, noone can use it. When I give no nodes to anyone, everyone can use it.
Can you PLEASE fix this? I am using PEX, and LWC 4.1.1 Build 691.
-
View User Profile
-
Send Message
Posted Apr 18, 2012Why doesn't LWC have multi-world support?...
-
View User Profile
-
Send Message
Posted Apr 18, 2012@11RJB
i have the same problem, too
-
View User Profile
-
Send Message
Posted Apr 18, 2012in my case is the same error, like 11RJB!!!!
-
View User Profile
-
Send Message
Posted Apr 18, 2012@11RJB
Use pastebin.com instead of spamming the comments next time
-
View User Profile
-
Send Message
Posted Apr 18, 2012@juodas
It works fine on 1.2.5
-
View User Profile
-
Send Message
Posted Apr 18, 2012Will you update to 1.2.5?