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 GumbyDammit GumbyDammit Jan 17, 2014 at 17:58 UTC - 0 likes

    I did a profile of my server with NoLagg /examine and it showed that LWC was chewing up a significant amount of processing time. During the snapshot, most of my plugins take between 1 - 125ms. LWC takes 1056ms. The event that take sup all the cycles in LWC is BlockRedstoneEvent. Could you look into this please?

  • Avatar of Maximvdw Maximvdw Jan 16, 2014 at 19:05 UTC - 0 likes

    @mike1360: Go

    Try using a development build. (Jenkins). Make sure your SQL or MySQL configuration is correct

  • Avatar of mike1360 mike1360 Jan 16, 2014 at 03:41 UTC - 0 likes

    Got an error whenever a new block is attempted to get locked. It says

    [LWC] Internal Error. Notify an admin immediately. :PLAYER_INTERACT

    The error in console is this http://pastebin.com/WyGhDNeh

    Craftbukkit 1.7.2 beta and LWC 4.4.0

  • Avatar of CaniCraft CaniCraft Jan 15, 2014 at 22:48 UTC - 0 likes

    @XztriggerhappyzX: Go

    use this it should work

    player: default: false permissions: - some.perm - some.perm1 - -lwc.protect inheritance: - somegroup info: prefix: '&1[&9player&1]&b' build: true suffix: '&3'

    this should disallow people in this groups not too be able to use LWC hope it helped ;)

    Last edited Jan 15, 2014 by CaniCraft: fixing up the group


  • Avatar of XztriggerhappyzX XztriggerhappyzX Jan 15, 2014 at 01:55 UTC - 0 likes

    Is there a way to disable this plugin per world? i have a survival world that uses this plugin but i also have a raiding world but don't want lwc to be in this world. I have ruled out having another server due to my computer not being powerful enough. i use groupmanager for my permissions and have set it to per world permissions. i've given the "player" group (lowest rank) the permission node - -lwc.* but this doesn't seem to do the trick. is there any other way to disable the use to create a protected chest, door, hopper esc. apon placement? thanks - Trigger

  • Avatar of frol1 frol1 Jan 14, 2014 at 03:30 UTC - 0 likes

    Is this working with 1.7.2?

  • Avatar of MrCobayo MrCobayo Jan 12, 2014 at 13:10 UTC - 1 like

    Hello! For open door with password, you can add the option for only write the password in the chat and it work? not with for example /cpassword holahola. Only with /holahola.

    Or with one command more small, for example /cp or /o (open)

  • Avatar of dermarionator dermarionator Jan 11, 2014 at 20:41 UTC - 0 likes

    There is a Translation mistake in the German translation.

    Change: Diese Schild gehört dir nicht! in Dieses Schild gehört dir nicht!


  • Avatar of IPFaNbg IPFaNbg Jan 11, 2014 at 15:50 UTC - 0 likes
  • Avatar of ultima84 ultima84 Jan 10, 2014 at 04:41 UTC - 0 likes

    In that case it is not working for me, and I need to make a ticket.
    When the server loses it's MySQL connection, LWC doesn't reconnect and stops working.


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