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 Oct 1, 2012Getting the same error. The "Could probably ignore...thread 14" error
-
View User Profile
-
Send Message
Posted Oct 1, 2012Is there going to be an update for CB 1.3.2?
-
View User Profile
-
Send Message
Posted Oct 1, 2012Feature requests, Suggestions and Issues IRC - Live Chat ( irc.esper.net #LWC )
These two links don't really work in the description...
-
View User Profile
-
Send Message
Posted Oct 1, 2012Same issue here,
21:27:33 [INFO] [LWC] [LWC] This can probably be ignored. 21:27:33 [SEVERE] Exception in thread "Thread-11" 21:27:33 [SEVERE] java.lang.NullPointerException 21:27:33 [SEVERE] at com.griefcraft.util.Updater.shouldAutoUpdate(Updater.java:442) 21:27:33 [SEVERE] at com.griefcraft.util.Updater.tryAutoUpdate(Updater.java:302) 21:27:33 [SEVERE] at com.griefcraft.util.Updater$1.run(Updater.java:183) 21:27:33 [SEVERE] at com.griefcraft.util.Updater$1Background_Check_Thread.run(Updater.java:506) 21:27:33 [SEVERE] at java.lang.Thread.run(Unknown Source)
Bukkit version: 21:28:10 [INFO] This server is running CraftBukkit version git-Bukkit-1.3.2-R1.0-b2377jnks (MC: 1.3.2) (Implementing API version 1.3.2-R1.0)
Operating system: Debian Squeeze x64 Java version: Oracle Java 7 x64 LWC version: LWC 4.3.0
The error werent there at the last bukkit version i had i believe that was 1.3.2R0.1 though im not sure if i were using the same LWC version there. Hope this helps a bit, though im not experiencing any real problems as far as i noticed
-
View User Profile
-
Send Message
Posted Oct 1, 2012@xMinecraft
Hi, similar error for me too
2012-10-01 20:43:15 [SEVERE] Exception in thread "Thread-10"
2012-10-01 20:43:15 [SEVERE] java.lang.NullPointerException
2012-10-01 20:43:15 [SEVERE] at com.griefcraft.util.Updater.shouldAutoUpdate(Updater.java:442)
2012-10-01 20:43:15 [SEVERE] at com.griefcraft.util.Updater.tryAutoUpdate(Updater.java:302)
2012-10-01 20:43:15 [SEVERE] at com.griefcraft.util.Updater$1.run(Updater.java:183)
2012-10-01 20:43:15 [SEVERE] at com.griefcraft.util.Updater$1Background_Check_Thread.run(Updater.java:506)
2012-10-01 20:43:15 [SEVERE] at java.lang.Thread.run(Unknown Source)
-
View User Profile
-
Send Message
Posted Sep 30, 2012The part of error:
15:31:05 LWC: [LWC] This can probably be ignored. 15:31:06 CONSOLE: [SEVERE] Exception in thread "Thread-13" 15:31:06 CONSOLE: [SEVERE] at com.griefcraft.util.Updater.shouldAutoUpdate(Updater.java:442) 15:31:06 CONSOLE: [SEVERE] at com.griefcraft.util.Updater$1.run(Updater.java:183) 15:31:06 CONSOLE: [SEVERE] at java lang.Thread.run(Thread.java:679)
This is problem of the conecction to griefcraft.com please fix.
-
View User Profile
-
Send Message
Posted Sep 30, 2012I am just making a suggestion, but sometimes this is used on faction and raiding servers. Maybe there could be a way to pick locks? The owner can turn picking of locks on or off. The owner can also set how hard it is to pick the lock. Or maybe there can be a second type of lock that is unpickable. The limit count on this lock is different than a normal, pickable lock.
I think that this would be amazing. Even if this doesn't get put it, this is still a pretty good plugin. But (optional) picking of locks like how I put it would make the plugin much better in my opinion.
-
View User Profile
-
Send Message
Posted Sep 29, 2012@deleted_8591593
I use PEX, could you explain how I would do it with that, I don't really understand :s
-
View User Profile
-
Send Message
Posted Sep 29, 2012Please help me, players can't open chests on my server. http://pastebin.com/WD7C4t9Q It just says "Notice: That Private Chest is locked by you." and doesn't let anyone in to the chest. Any help is appreciated.
-
View User Profile
-
Send Message
Posted Sep 29, 2012@TheMagicPostman
you would achieve this with permissions. Get a permissions client that has per-wrold configurations.
-
View User Profile
-
Send Message
Posted Sep 27, 2012Is it possible for the plugin to only work in certain worlds?
-
View User Profile
-
Send Message
Posted Sep 27, 2012@stealth62
Have you tested or just assuming? Are you sayig "rather sqlite" as in its the best, or rather THEN?
-
View User Profile
-
Send Message
Posted Sep 26, 2012@mrchasez
code wise, lwc has more session handling, and thus less intensive. if you configure with mysql, rather sqlite, you will find much better results
-
View User Profile
-
Send Message
Posted Sep 26, 2012Hey i need a real answer. Is LWC or Lockette more CPU intensive? Ram really isn't an issue. I'd appreciate a quick response.
-
View User Profile
-
Send Message
Posted Sep 23, 2012Oh.. sorry guys
-
View User Profile
-
Send Message
Posted Sep 21, 2012@V0ROBEY
Man read FAQ etc first before asking, to your question : just add the items in the config then you can protect them
-
View User Profile
-
Send Message
Posted Sep 21, 2012Protect for fancedoors or Enderchests?
-
View User Profile
-
Send Message
Posted Sep 21, 2012@Bimmr
PEX works fine for me, if anything essentials breaks more things then PEX does.
@Dragonowy Most of the time, if you have full permissions, you have made yourself a lower rank, but forgot to deop yourself.
@n1s2e usually the only ops you should have on a server is yourself. all other players should be placed into permission groups that contain what they are allowed to do.
on my server i could remove op from myself, and be able to play with no change, because my owner permission group contains everything i need.
the same is for my other groups, they all have what i need them to have, except there are some things i only want me to be able to do, for you that is opening other players chests.
so basically instead of oping everyone, create a group that contains everything, then just remove the things you don't want them to do
-
View User Profile
-
Send Message
Posted Sep 20, 2012@n1s2e
I'm pretty sure you can disable OPs from getting in to chests by using - ^lwc.mod and - ^lwc.admin in their permissions groups
-
View User Profile
-
Send Message
Posted Sep 19, 2012@Dragonowy
Your problem is that your using Pex... it doesn't always work...