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 saturnux saturnux Apr 23, 2014 at 09:34 UTC - 0 likes

    you can ignore this.

    the url of build has moved (i think) or has unreachable.

    normaly this error cause no other problem in game.

    you can try dev build, but i have the same issue for 1.7.2

  • Avatar of kristijan260393 kristijan260393 Apr 23, 2014 at 00:09 UTC - 0 likes

    eror [01:58:54] [Craft Scheduler Thread - 6/INFO]: [LWC] [LWC] The updater ran into a minor issue: http://update.griefcraft.com/lwc/branch/stable/LATEST [01:58:54] [Craft Scheduler Thread - 6/INFO]: [LWC] [LWC] This can probably be ignored. [01:58:54] [Craft Scheduler Thread - 6/WARN]: Exception in thread "Craft Scheduler Thread - 6" [01:58:54] [Craft Scheduler Thread - 6/WARN]: org.apache.commons.lang.UnhandledException: Plugin LWC v4.4.0 (b881) (July 11, 2013) generated an exception while executing task 8 at org.bukkit.craftbukkit.v1_7_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.NullPointerException at com.griefcraft.util.Updater$1.run(Updater.java:81) at org.bukkit.craftbukkit.v1_7_R1.scheduler.CraftTask.run(CraftTask.java:58) at org.bukkit.craftbukkit.v1_7_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) ... 3 more

    [01:58:54] [Craft Scheduler Thread - 0/WARN]: Exception in thread "Craft Scheduler Thread - 0"

  • Avatar of PrimoHighDefinition PrimoHighDefinition Apr 22, 2014 at 10:04 UTC - 1 like

    I agree with bobeeb and Schneidertm, Thanks @Hidendra <33

  • Avatar of Schneidertm Schneidertm Apr 21, 2014 at 12:01 UTC - 0 likes

    I agree with bobeeb. Thanks @Hidendra for working on a UUID update

  • Avatar of bobeeb bobeeb Apr 21, 2014 at 11:00 UTC - 1 like

    thanks for the uuid update hidendra

  • Avatar of Ar7ific1al Ar7ific1al Apr 21, 2014 at 06:40 UTC - 0 likes

    @Max633: Go

    It might be helpful to post more information than just a crash log. What version of LWC are you using? What version of Bukkit/Spigot/etc? What other plugins are running? When does this error occur? Stuff like that would help others help you quite a lot. :)


  • Avatar of Max633 Max633 Apr 20, 2014 at 10:05 UTC - 0 likes



    Help me please.....

    Server french

  • Avatar of JrdMorell JrdMorell Apr 19, 2014 at 20:06 UTC - 0 likes

    @Hisendra we detected the following bugs in the last version of your plugin:

    • You can cancel the protection of a chest by putting a protected sign next to it and destroying it.
    • You can open other people's protected doors by putting a button, a lever or a pressure plate to it.
  • Avatar of glen3b glen3b Apr 17, 2014 at 23:55 UTC - 1 like

    @Hidendra will this plugin be updated to support UUIDs? If not, I cannot use it, but if it will I can plan on using it.

    Dat dev


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