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 IamYourDoodie IamYourDoodie May 19, 2015 at 19:20 UTC - 0 likes

    @IamYourDoodie: Go

    Ah never mind what I said below. Build#938 doesn't seem to work on frames and armor stands =/ Well, 1.8.3 isn't that ;)

  • Avatar of IamYourDoodie IamYourDoodie May 19, 2015 at 03:24 UTC - 0 likes

    @Bronzeteufel: Go

    I was wondering the same thing. Ended up trying a Jenkins development build #938 and is working great with Spigot 1.8.4 so far. Good luck!

  • Avatar of Bronzeteufel Bronzeteufel May 18, 2015 at 18:51 UTC - 0 likes

    Is there support for spigot 1.8.4 right now?

  • Avatar of frizzbee30 frizzbee30 May 17, 2015 at 08:20 UTC - 0 likes

    @alteropa: Go

    I think you seriously need to grow up. The plugin works, yes it does need some updating.

    People running servers with such an immature attitude is what gives the server owner/admin community a bad name.

    By the way, are you paying for this plugin via licensing for full time support? Is it costing you $20,000 plus per annum contract negotiated?

    Something you need to consider before posting comments like that.

    KB Craft multiworld server
    Server mc2.fadehost.com:25655 New players always given a warm welcome!

  • Avatar of markdf markdf May 14, 2015 at 07:56 UTC - 1 like

    @alteropa: Go

    Works fine for me, must be your 'shit' server setup thats causing the problem.



  • Avatar of sakura_blades sakura_blades May 14, 2015 at 02:45 UTC - 1 like

    @alteropa: Go

    This "shit" still works...
    And try to be a little "kinder" for "shit" you need. Can't say it makes it sound like you're overly appreciative when you use the term "shit" in reference to something...
    How rude..

    And if you're finding that release builds on this page aren't working... Try looking at development builds. -.- Do some homework and you'll find it'll work just fine..

    @Bronzeteufel: Go

    Delete and allow your config to reload. There should be support for Armor Stands if I recall

  • Avatar of alteropa alteropa May 13, 2015 at 11:20 UTC - 0 likes

    Update this shit!

    i need this!!!

  • Avatar of Bronzeteufel Bronzeteufel May 13, 2015 at 09:27 UTC - 1 like

    Would be nice if there were support for armor stands :)

  • Avatar of thequestingbeast thequestingbeast May 12, 2015 at 09:05 UTC - 1 like

    I am getting reports that locks placed on the new doors are spotty at best. They may be locked one time, then unlocked, and then locked the next.

    ZBDH9ae079b012063fbc53e4c7e6fb4bf3e5 Myraeon

  • Avatar of Braytography Braytography May 08, 2015 at 00:06 UTC - 1 like

    Can you possibly add the option to only tell admins the name of the owner and not the UUID? Its a really long an obnoxious message with the UUID.



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