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 3, 2013@LordKainzo
same bug
-
View User Profile
-
Send Message
Posted Oct 3, 2013Correct me if I'm wrong, but throwing %green% to lwc_en file is going to output &2 (which is dark green), right? What should I add if I want to use &a (light green)?
-
View User Profile
-
Send Message
Posted Oct 1, 2013How long till theres a working version for MC 1.6.4 ?
Thanks!
-
View User Profile
-
Send Message
Posted Oct 1, 2013hope in the next version 4.4.1 the problem with the opened chests will be fix
-
View User Profile
-
Send Message
Posted Sep 30, 2013@LordKainzo
What about so much CPU time on timings?, don't you have it?
-
View User Profile
-
Send Message
Posted Sep 30, 2013Correct me if I'm wrond, but %green% is outputing &2 (Dark Green) right? What should I add if I want to use &a (Light Green)?
-
View User Profile
-
Send Message
Posted Sep 29, 2013@LordKainzo
It's an exception on 1.6.2 too
-
View User Profile
-
Send Message
Posted Sep 29, 2013@LordKainzo
Alright, I am in the process of a big update on my server. After I get everything working and let it run for a few days to see it's smooth, I'll update LWC and report back here with the results :)
-
View User Profile
-
Send Message
Posted Sep 29, 2013I'm not getting any of the LWC issues except this one on 1.6.4
http://pastie.org/private/8lvdcs6fdbrwawn7w2qwxg
-
View User Profile
-
Send Message
Posted Sep 28, 2013@Hidendra
Would it be possible to add a user permission to allow owner lever of lwc to be shared? I often have partnered players that build but can't destroy the others blocks which means staff needs to be involved when only one player is on. It doesn't happen often but enough that I feel a perm is warranted. I'm thinking a perm added to their username for both players - lwc.share.snocat
EDIT: It'd be nice if this would be perm based as it wouldn't need to be added to each block.
-
View User Profile
-
Send Message
Posted Sep 28, 2013At the moment, my server has had no problems with players opening each other's chests. The plugin works perfectly and as intended. However, could this be because I am running it localhost with 5GB of ram? When I move it to a hosting service with only 1 or 2 GB, could this change, and not work properly? People were saying the plugin was broken because of timing, and maybe it's because the servers cannot keep up. Using that theory, I could see it being possible that if I were to give the server less RAM, chests may not stay locked. Does anyone know if my theory could be right or wrong? Thanks!
Edit: I'm using LWC version 4.4.0, bukkit version 1.6.2-R1.0 PC Specs: http://pastebin.com/zRydMynf
-
View User Profile
-
Send Message
Posted Sep 28, 2013I have also run into this with the newest version of lwc, none of the permissions seem to work for it. the chests auto register, you can use all the commands, but even putting the lwc.deny permission will not prevent someone from opening a chest.
-
View User Profile
-
Send Message
Posted Sep 28, 2013Hey Guys,
All Players can open Chests from everyone. Are you fixing this in the next Version? Our Server runs on 1.6.2
Thanks
-
View User Profile
-
Send Message
Posted Sep 25, 2013errors at 1.6.4, players can open other players chests :( hope update soon
-
View User Profile
-
Send Message
Posted Sep 25, 2013I have problem, maeby some one know fix? MCPC+ 1.5.1 build 400, LWC build LWC 4.3.2 Beta 3 All time like this:
-
View User Profile
-
Send Message
Posted Sep 24, 2013Good thing im not updating LWC, im still on 4.3.2 (b858-git-MANUAL) (March 16, 2013) and its running on 1.6.2 without problems! Atm I dont notice any issues with it. Hope to see it working on 1.6.4
-
View User Profile
-
Send Message
Posted Sep 24, 2013For you guys having low TPS rates from LWC; check out my previous post for a possible fix. Do NOT post bukkit timings, they are inaccurate and useless! Use spigot and share the result using aikar.co/timings.php
I have the fix installed and when I print timings using spigot I do not get any bad TPS performance from LWC.
Read this before posting about "TPS Lag"!
-
View User Profile
-
Send Message
Posted Sep 23, 2013TPS Lag? Look at this: https://github.com/Hidendra/LWC/issues/699
-
View User Profile
-
Send Message
Posted Sep 20, 2013at a warm reload (which i normally never do) i discovered this
15:08:55 [SEVERE] Error occurred while enabling LWC v4.4.0 (b884) (August 19, 2013) (Is it up to date?)
java.lang.OutOfMemoryError: PermGen space
only 50% of totalmem in use.
-
View User Profile
-
Send Message
Posted Sep 20, 2013I'm not sure what to use on my Bukkit server! XD LWC, LWC Economy, or LWC(something)5?
I'm using just LWC atm, but I can't help but wonder if that's going to continue to update in the long run. :P