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 Dec 06, 2013 at 15:56 UTC - 0 likes

    @Keepoladon: Go

    Thanks, I'll give that a try this weekend.

  • Avatar of Keepoladon Keepoladon Dec 04, 2013 at 23:05 UTC - 0 likes

    @GumbyDammit: Go

    Go into the core config file and remove the part where it says "autoRegister: private" under sign. Should end up looking like this.

    sign: enabled: true

  • Avatar of Dobsonium Dobsonium Dec 04, 2013 at 23:00 UTC - 0 likes

    Double Wooden Doors

    Previously If one placed two wooden doors side by side (left first,then right), one could "/cpublic" them, and then "/lwc flag autoclose on", so when ever a player opened one door both would open.

    Now I have noticed that this has stopped working, When I open one door I hear the double door opening sound, but only a single door opens.

    I am wondering if any else has noticed/experienced this.

    The server is running 1.7.2 and lwc ver 4.4.0 (b903), plus a few other plugins

    update on the above, It appears to have been a problem with one of the Spigot releases, as the problem has resolved itself with the latest Release.

    Last edited Dec 18, 2013 by Dobsonium: Problem resolved
  • Avatar of GumbyDammit GumbyDammit Dec 04, 2013 at 21:46 UTC - 0 likes

    Small issue with LWC and HerobrineAI. Herobrine places signs that nobody but me can break because LWC appears to be protecting them.

  • Avatar of usercoolbeans usercoolbeans Dec 03, 2013 at 20:46 UTC - 0 likes

    i have a problem =/ i have lwc on my server and people can open chests with my clickwarp item wich is another plugin =/


  • Avatar of Baybeehxliciouz Baybeehxliciouz Dec 03, 2013 at 16:43 UTC - 0 likes

    What is that?

    [WARNING] [LWC] Task #7 for LWC v4.4.0 (b881) (July 11, 2013) generated an exception com.griefcraft.scripting.ModuleException: com.griefcraft.scripting.ModuleException: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

    after this message... my server is immediately stopped... :-(

    best regards


  • Avatar of lipe124 lipe124 Dec 03, 2013 at 00:04 UTC - 0 likes

    @z1haze: Go

    Use /chopper or /lwc flag hopper on It's in the wiki.

    @Jacold: Go

    Have you checked that its not the magnet option? I played with the before and it uses a ton of resources, try disabling the magnet feature in the config.

  • Avatar of z1haze z1haze Dec 02, 2013 at 21:30 UTC - 0 likes

    @hunted2: Go

    yea i have an issue having to unlock chests before hoppers work with him.. is there a fix for this?

  • Avatar of Aqelius Aqelius Dec 02, 2013 at 15:29 UTC - 0 likes

    Когда новая версия будет? 4.4.0 выдаёт ошибку на версии 1.6.4 R2.1

    2013-12-02 16:26:13 [SEVERE] Exception in thread "pool-1-thread-3" 
    2013-12-02 16:26:13 [SEVERE] org.apache.commons.lang.UnhandledException: Plugin LWC v4.4.0 (b881) (July 11, 2013) generated an exception while executing task 9
    at org.bukkit.craftbukkit.v1_6_R3.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: com.griefcraft.scripting.ModuleException: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
    The last packet successfully received from the server was 123,691 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.
    at com.griefcraft.sql.Database.printException(Database.java:199)
    at com.griefcraft.sql.PhysDB.fetch(PhysDB.java:126)
    at com.griefcraft.sql.PhysDB.getProtectionCount(PhysDB.java:146)
    at com.griefcraft.lwc.LWC$2.getValue(LWC.java:1469)
    at com.griefcraft.util.Metrics.postPlugin(Metrics.java:393)
    at com.griefcraft.util.Metrics.access$400(Metrics.java:57)
    at com.griefcraft.util.Metrics$1.run(Metrics.java:223)
    at org.bukkit.craftbukkit.v1_6_R3.scheduler.CraftTask.run(CraftTask.java:53)
    at org.bukkit.craftbukkit.v1_6_R3.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
    ... 3 more
    Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
    The last packet successfully received from the server was 123,691 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
    at com.mysql.jdbc.Util.handleNewInstance(Util.java:407)
    at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1116)
    at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3082)
    at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2968)
    at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3516)
    at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1986)
    at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2140)
    at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2626)
    at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2111)
    at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2273)
    at com.griefcraft.sql.PhysDB.fetch(PhysDB.java:116)
    ... 10 more
    Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost.
    at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:2529)
    at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2979)
    ... 18 more
    Last edited Dec 02, 2013 by Aqelius
  • Avatar of hunted2 hunted2 Dec 01, 2013 at 07:40 UTC - 0 likes
    I have only ask, not bash. This plugin reach high timings with 12,5k protections. I have only enabled chest protecting. I have noticed lower performance whed I updated LWC to version for 1.5. I think problem is with hoppers.

    I have found lately that my TPS has been dropping horribly. Installed nolagg and did /nolagg examine. LWC is using 90% of the cycles that's taking my server down to 4TPS. Chestshop was using 10-20% also.

    Any chance you are running Chestshop?

    Raistlinhunted, Minecraft Omega, Forums: www.minecraftomega.com, Server: server.minecraftomega.com, www.minecraftomega.com


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