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 Jun 26, 2012How can i fix the lever problem? My players are having some trouble because others can invade their house using levers on iron doors.
There is anyway to disable door opening by lever?
-
View User Profile
-
Send Message
Posted Jun 26, 2012@NewMotion
That's not an answer, the chest is still autolocked. I've already mentioned to Hidendra that turning off autolocking isn't actually turning it off, and have provided my core.yml file via pastebin as requested.
-
View User Profile
-
Send Message
Posted Jun 26, 2012@zzaarr
You go into the LWC folder in your plugins list. Open up the core.yml with something like Notepad. You should see chests, furnace, dispenser, etc. Go to the block you want to change and then look for the word "autoregister". If you change it to public, that block will now be public whenever you place it.
-
View User Profile
-
Send Message
Posted Jun 26, 2012can someone please tell me how to disable autolocking? right now whenever i create a chest it autolocks!
-
View User Profile
-
Send Message
Posted Jun 26, 2012What permission can I give my admins so when they open a locked chest it tells them that it's locked, but without giving them the full lwc.admin (Just like it does when you open a chest while being OPed)
-
View User Profile
-
Send Message
Posted Jun 24, 2012On my server the limit for locks is set to 15 but when people donate they'll get a higher limit. The problem is that we have ranks so I cant use the group limits. Is there a way to add a permission for limits or a ingame command (Buycraft) to set the limits for players?
-
View User Profile
-
Send Message
Posted Jun 24, 2012and its possible to "make a server lag" when you place lots of chests because they are getting protectet automatically..maybe add a cooldown or something; max 1 chest in 4sec or something like that
edit: LWC is the "laggiest" plugin. dynmap, bananaregion and so have 24ms but LWC has got 243 ms!! and 99% is the task BlockRedstoneEvent
-
View User Profile
-
Send Message
Posted Jun 24, 2012Any idea why mods cant open other peoples chests? They have lwc.mod permission, I'm using essentials.
-
View User Profile
-
Send Message
Posted Jun 24, 2012heres the report: http://img443.imageshack.us/img443/1583/minecraftsp1.png
another question: do i need essentialsprotect when i use LWC?
whats the BlockRedstoneEvent? is there also a way to "disable" this?its one of the laggiest task (nolagg)
-
View User Profile
-
Send Message
Posted Jun 23, 2012@Hidendra
http://pastebin.com/YMK8rSfD
-
View User Profile
-
Send Message
Posted Jun 23, 2012<<reply 774057="">>
could you pastebin your core.yml?
-
View User Profile
-
Send Message
Posted Jun 23, 2012@Hidendra
I'm not sure what you mean, LWC is the only chest protection plugin we have installed. We have worldguard installed and essentials installed, but both of those have the chest protection turned off.
The exact message i get when i place a chest is 'Created a Private Chest successfully'.
-
View User Profile
-
Send Message
Posted Jun 23, 2012<<reply 773969="">>
@aphilosopher
it was supposed to have been fixed a version or two ago, but is definitely fixed in the latest dev builds ( http://ci.griefcraft.com/job/LWC/ ) -- they are stable
<<reply 773433="">>
@Hans6666
what's your output of
/lwc admin report? :)<<reply 774021="">>
@ray73864
are you using a plugin that gives you '' ? if you are, there is your problem ( alone is a problem in of itself). you need to set lwc.autoprotect to false
-
View User Profile
-
Send Message
Posted Jun 23, 2012I don't want chests to be automatically protected, how do i turn that off? i have autoRegister set to 'false' globally for everything and locally to chests in the config file, but it isn't doing anything.
-
View User Profile
-
Send Message
Posted Jun 23, 2012in january i posted this comment about duplication exploit with /cmagnet http://forums.bukkit.org/threads/sec-mech-lwc-v4-1-1-lightweight-protection-for-chests-furnaces-dispensers-and-more-1-2.967/page-151#post-906924
why hasnt it been fixed yet? can we please get that one fixed? i have had magnet disabled on my server because of this ever since january. my players miss it
-
View User Profile
-
Send Message
Posted Jun 23, 2012Works with R4? :D
-
View User Profile
-
Send Message
Posted Jun 23, 2012i still have some performance problems: see: http://img857.imageshack.us/img857/412/combergerkillerbukkitno.png
do you prefer any special setting to change?
edit: now the BlockRedstoneEvent caused 101.ms at 500 ticks is there also something which has to be set to "false" ? :D
-
View User Profile
-
Send Message
Posted Jun 22, 2012<<reply 771524="">>
two commands:
the quotes in the first command are preferable :) the second simply forces protections to recheck themselves in the database (so that the new owner will appear immediately)
-
View User Profile
-
Send Message
Posted Jun 22, 2012This may have been asked before, but I can not see it if it has. Is there a way to mass change one player's locks to another player besides the /lwc forceowner command, which from what I see only does one lock at a time.
-
View User Profile
-
Send Message
Posted Jun 22, 2012@AdDrumm
No, you'll want a plugin such as worldguard ;)
@Hans6666
you can disable magnet chests in magnet.yml, as @Grichecth mentioned ;)