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 Wind1000100 Wind1000100 Mar 21, 2014 at 06:16 UTC - 0 likes

    Could you please add a permission like lwc.lock.door (and more) so you can give players only perms to lock a certain kind of thing? Thanks!

  • Avatar of Baffu Baffu Mar 20, 2014 at 19:59 UTC - 0 likes

    Had exploit where hacker accessed locked chests.

  • Avatar of KatranLife KatranLife Mar 20, 2014 at 17:10 UTC - 1 like

    pls update!

  • Avatar of Rouchesta Rouchesta Mar 19, 2014 at 13:50 UTC - 1 like

    Please need an update ;-)

  • Avatar of drikraft drikraft Mar 19, 2014 at 11:50 UTC - 1 like

    Please update!

  • Avatar of LHammonds LHammonds Mar 18, 2014 at 15:25 UTC - 1 like

    LWC 4.4.0 Build 886 works in CraftBukkit 1.7.2-R0.3 and Spigot 1.7.2-R0.4 with Java 1.7.0_51 (64-bit).

    I have been using this particular build since it was compiled on Aug 26, 2013 with the current version of CraftBukkit back then and every version since then.

    I also use LWC-Economy B84 and LWCTweaks 3.3.0


    Last edited Mar 18, 2014 by LHammonds

    Website: HammondsLegacy.enjin.com

    Minecraft Server: HammondsLegacy.com

  • Avatar of TheKyle27 TheKyle27 Mar 17, 2014 at 18:14 UTC - 0 likes

    Do any of the dev builds work with 1.7.2? This is the only plugin I'm waiting on.

    G4m.es Minecraft Server

  • Avatar of BucketFreak BucketFreak Mar 16, 2014 at 15:18 UTC - 0 likes

    Help! My players have permission "lwc.protect" but can (sometimes) open all chests, even the one I created...

    I am running bukkit 1.7.2-R0.2-15 / API 1.7.2-R0.3-SNAPSHOT...

  • Avatar of Aqelius Aqelius Mar 16, 2014 at 14:51 UTC - 0 likes
    [18:41:10] [pool-3-thread-21/INFO]: [LWC] [LWC] The updater ran into a minor issue: http://update.griefcraft.com/lwc/branch/stable/LATEST
    [18:41:10] [pool-3-thread-21/INFO]: [LWC] [LWC] This can probably be ignored.
    [18:41:10] [pool-3-thread-21/WARN]: Exception in thread "pool-3-thread-21" 
    [18:41:10] [pool-3-thread-21/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:53)
    	at org.bukkit.craftbukkit.v1_7_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
    	... 3 more
  • Avatar of Wbfw Wbfw Mar 16, 2014 at 06:03 UTC - 0 likes

    Why private or public piston doesn't work on redstone? Like door, How does piston work well on redstone with private or public protect?

    Last edited Mar 16, 2014 by Wbfw


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