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 Mar 5, 20122 words AWESOME PLUGIN :D
-
View User Profile
-
Send Message
Posted Mar 5, 2012uberKat,
Same issue here, using PEX, allowing, denying LWC has no effect, everyone can use LWC commands.
-
View User Profile
-
Send Message
Posted Mar 5, 2012<<reply 570112="">> (see the 6th reply before this one)
No one replied to my problem, so I had to dig into the source code. In the interest of possibly saving someone else a half hour of digging, buried in an earlier log was this line:
It seems the server was unable to download whatever URL was supplied failed, causing this error, which in turn caused limitsv2.yml to be empty, and therefore rendering LWC unloadable by the server (due to the error linked in my previous comment).
If I may suggest, it might be wiser to include the default limitsv2.yml in the jar file itself rather than assume that the server is available; I think there would be close to zero chance that limitsv2.yml defaults would change without a new LWC version being released.
-
View User Profile
-
Send Message
Posted Mar 4, 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. -Aidan
-
View User Profile
-
Send Message
Posted Mar 4, 2012http://pastebin.com/Z5Yc6yq2
when i try to use /cprivate to lock a chest
-
View User Profile
-
Send Message
Posted Mar 4, 2012@mrcheesete0
Seems good to me, no errors with 1.2.3 by now
-
View User Profile
-
Send Message
Posted Mar 4, 2012can anyone confirm 1.2.3?
-
View User Profile
-
Send Message
Posted Mar 3, 2012@mafima
Probably because your new map will require the permission nodes to be set again
-
View User Profile
-
Send Message
Posted Mar 3, 2012I'm currently receiving these errors during startup, chest access, and shutdown. The same errors occur both when using v4.1.1 from this site and v4.1.1 build 648 from the continuous integration site.
The log pasted was received when running build 648 with craftbukkit v1.2.3 build 2032, but this same error also occur when running craftbukkit v1.2.3 build 2022.
I'm hoping you could point me to the right direction before I spend time diving into the source code.
-
View User Profile
-
Send Message
Posted Mar 3, 2012http://pastebin.com/7auGH0Gy :(
Edit: Nevermind, gone in lastest build on Jenkins
-
View User Profile
-
Send Message
Posted Mar 3, 2012i made a new map. now everything acts like no LWC is installed. but it is! help :/ my server is 1.1
-
View User Profile
-
Send Message
Posted Mar 2, 2012Can any of you make /cprivate g:<groupname> on a door but when someone in that group tries to use the door it wont open for them
-
View User Profile
-
Send Message
Posted Mar 2, 2012@ Hidendra
Can you make permissions nodes that act like a blacklist? (i.e. Steve747 doesn't want his players protecting signs, so he sets a permission node to "Regular" group. NoobLikeNob87 is in "Regular" group. when he trys to protect sign, "You do not have permission to do that shows up.)
I don't want players protecting their chests and I want them to use global banks to liven up the RPG experience.
Me and my admins don't have the time to go around my server reprotecting every chest to public.
-
View User Profile
-
Send Message
Posted Mar 2, 2012Guys that cannot access chests use this worldgaurd version (most recent dev version)
http://build.sk89q.com/job/WorldGuard/566/
-
View User Profile
-
Send Message
Posted Mar 2, 2012@user_892472 :
Try with __global__ instead of global ;)
-
View User Profile
-
Send Message
Posted Mar 2, 2012@wmchris
I am experiencing this issue. Sadly this fix did not work for me, I am running the newest dev build of Worldguard aswell.
Anything I might need to / am doing wrong. - It says that there is no "Global" region.
-
View User Profile
-
Send Message
Posted Mar 1, 2012You did it really fast, thank :D
-
View User Profile
-
Send Message
Posted Mar 1, 2012If you have the bug which always triggers "You dont have permissions to open that in your area" - then it's because of the latest worldguard version. You'll have to enter "/region flag global chest-access allow" - then everything works fine
-
View User Profile
-
Send Message
Posted Mar 1, 2012@fffizzz
in the core config you need to set showNotices and showMyNotices to true
-
View User Profile
-
Send Message
Posted Mar 1, 2012You want to get the lwc.shownotices permission ;)