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.
Facts
- Date created
- Sep 08, 2011
- Categories
- Last update
- Mar 16, 2013
- Development stage
- Mature
- Language
- deDE
- enUS
- esES
- frFR
- itIT
- plPL
- ptBR
- ruRU
- License
- BSD License
- Curse link
- LWC
- Downloads
- 918,285
- Recent files
- B: LWC 4.3.2 Beta 3 for 1.5.0 Mar 16, 2013
- B: LWC 4.3.2 Beta 2 for 1.5.0 Mar 15, 2013
- B: LWC 4.3.2 Beta 1 for 1.5.0 Feb 04, 2013
- R: LWC 4.3.1 for 1.4.6 Nov 14, 2012
- R: LWC 4.3.0 for CB 1.4.2-R0.2 Aug 08, 2012
- Reply
- #1427
Hidendra Feb 04, 2013 at 04:36 UTC - 0 likes@fyrus12345: Go
yes. players will by default be allowed to protect blocks and ops will have admin rights. I agree with what @LiLChris06 says though, learning permissions will be an invaluable asset should you want to ever do anything simpler than 1 "group" (usually you do)
- Reply
- #1426
Hidendra Feb 04, 2013 at 04:33 UTC - 1 likeA beta build has been uploaded to the files page pending approval. Please let me know if anyone has any issues with this as this is likely a candidate for the next release.
@Zombiemold: Go
Just to confirm are you using #820? If you are could you give me the output of `/lwc admin report`?
A good thing to look for is your cache size. In the report, look at how many protections you have. You want to aim to have cacheSize (in core.yml) to be larger than this if possible. If LWC knows all protections are in the cache it never has to do a query when doing simple selections for protections.
- Reply
- #1425
LiLChris06 Feb 04, 2013 at 04:00 UTC - 1 like@fyrus12345: Go
2nd time I see you ask this in a dev page, you really should try setting up perms.
Makes a worlds difference when maintaining your server.
HTTP://WWW.LILCRAFT.NET
- Reply
- #1424
fyrus12345 Feb 03, 2013 at 21:33 UTC - 0 likesDoes this work without permissions?
- Reply
- #1423
lord0o Feb 03, 2013 at 21:14 UTC - 0 likesAll my errors seems to be fixed now. with lastest dev. Thank you.
- Reply
- #1422
StanoMalek Feb 03, 2013 at 00:05 UTC - 0 likesLastBuild
CB last.
- Reply
- #1421
Siickest Feb 02, 2013 at 16:54 UTC - 0 likesLWC was spamming my Log with errors all the time -.- Wtf
- Reply
- #1420
diannetea Feb 02, 2013 at 16:31 UTC - 0 likesLatest dev build is spamming my console with
"loadProtections() in 0ms"
www.bigturtlegames.com
- Reply
- #1419
cam246 Feb 02, 2013 at 16:22 UTC - 0 likesCould you make it so it can lock anvils and enchanting tables to. It would really help out a lot.
- Reply
- #1418
LiLChris06 Feb 02, 2013 at 15:07 UTC - 0 likesBuild #814, holy smokes look all those reverts. :o
"Donation chest support."
Hmm wonder how that works, think my players will like that.
Thanks for the new dev builds!