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:


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


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.


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.


  • /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 /cremove in 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.


Advanced 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.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Techmo9j Techmo9j Nov 24, 2015 at 00:05 UTC - 0 likes

    Hi. I use this to lock double iron doors but they hinge the same way, bad update maybe?

  • Avatar of roracle roracle Nov 14, 2015 at 11:13 UTC - 0 likes

    I attempted "/lwc dump local" so that I could change the "This _blank_ is locked with a magic spell" message to simply "This _blank_ is locked."

    When I run "dump local" it just says "/lwc" in the output. Then I used our friend Google and it came up with people saying it's "/lwc admin dump local" so I tried that, and no output at all and I didn't get the local files required.

    Could anyone please help me out with this? Is there another way to change the message perhaps?

    EDIT: So it's "locale" with an "e". Got it working, sorry for the bother!

    Last edited Nov 14, 2015 by roracle
  • Avatar of markdf markdf Nov 13, 2015 at 22:13 UTC - 0 likes

    @sexypotatofish: Go

    Just tried the link, your right its not working at the moment. Jenkins server appears to be offline, I'd expect it to return at some time.

    Never tried adding crafting table and torch's, so I cant tell you if it works for me. Although if it is possible to add torches, I don' think that would be a great idea as you would very quickly have thousands of database entries, mostly pointless as most torches will be placed in mines that will not be visited again. My database has 15000 protections on just doors and chests.



  • Avatar of sexypotatofish sexypotatofish Nov 13, 2015 at 21:00 UTC - 0 likes

    I added "crafting_table" and "torch" to the config file, but I still can't lock them.


    Also, I get an error when downloading the latest version via the Spigot link.

    I do have the latest build, though, since I downloaded the 1.7.9 build, which is actually a 1.8 build.

    Last edited Nov 13, 2015 by sexypotatofish
  • Avatar of markdf markdf Nov 13, 2015 at 20:43 UTC - 0 likes
  • Avatar of sexypotatofish sexypotatofish Nov 13, 2015 at 16:56 UTC - 0 likes

    Why does the 1.8 build say 1.7.9 and not 1.8?

  • Avatar of scuroK scuroK Oct 25, 2015 at 00:35 UTC - 0 likes

    PLEASE update! /lwc admin purge PLAYERNAME is broken. @Hidendra are you still alive? what about lwc??

    please answer thx

  • Avatar of kevinnatte kevinnatte Oct 19, 2015 at 16:25 UTC - 0 likes


    chestshop does remove a chet protection if you remove the sign, i recomend to chek the chestshop config!

    cant find it? pm me!

  • Avatar of tcarey2015 tcarey2015 Oct 14, 2015 at 00:23 UTC - 0 likes

    also players can somehow remove the locks only from cdonation chests.. by using chestshop then deleting the chestshop sign ..

    I tried negating the perm ^lwc.create.cdonation and players can still use it.

    Last edited Oct 14, 2015 by tcarey2015
  • Avatar of tcarey2015 tcarey2015 Oct 12, 2015 at 12:30 UTC - 0 likes

    I can't find the command to switch from sqlite to sql ?


Date created
Sep 08, 2011
Last update
Dec 10, 2014
Development stage
  • deDE
  • enUS
  • esES
  • frFR
  • itIT
  • plPL
  • ptBR
  • ruRU
BSD License
Curse link
Recent files