LWC

LWC

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:

Private

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

Password

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.

Public

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.

Commands

  • /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.

Permissions

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 phillipkdick phillipkdick Dec 09, 2013 at 19:53 UTC - 0 likes

    When i tried to pass my 1.6.4 server to 1.7.2 and put lwc, have some critical errors to out of memory and PermGen fail...

    i use this plugin since when i create my server, its the best plugin for protect chest and now... i'm very worried about the way is taking...

    i tried to mount my server plugin by plugin and the most critical plugin for me is LWC, and i have more to 60 plugins...

    fix it for 1.7.2 please

  • Avatar of kristijan260393 kristijan260393 Dec 09, 2013 at 18:14 UTC - 0 likes

    whwn I run comand /cremoveall and /lwc confirm my server shut dowen

  • Avatar of ThoLav ThoLav Dec 09, 2013 at 08:17 UTC - 0 likes

    @Dr_Bunsen: Go

    Hi,

    yes you can. Edit core.yml.

    If I had helped you, a like would be nice. Thank you.

    Have a nice day,
    Thomas

  • Avatar of Dr_Bunsen Dr_Bunsen Dec 09, 2013 at 08:13 UTC - 0 likes

    Could itemframes also be protected? People are breaking my map room stuff, and in my storing facility they are stealing the diamond blocks on the item frames. And I know there is a plugin to protect itemframes, but that just weird, having 2 plugins basicly giving the same functions but just with different blocks/items.

    [EDIT]: I noticed that when I was editting or placing protections, bukkit will lagg the hell out, I removed 4 signs, we had 12 seconds of lagg "Can't keep up! Did the system time change, or is the server overloaded? Running 11046ms behind, skipping 220 tick(s)" I thought you may wanted to know

    Last edited Dec 09, 2013 by Dr_Bunsen
  • Avatar of ThoLav ThoLav Dec 08, 2013 at 16:59 UTC - 0 likes


    Hi,

    we have a problem. We use SignEditor http://dev.bukkit.org/bukkit-plugins/signeditor/ and also LWC. When someone tries to edit a protected sign, LWC protects the sign, but also deletes the entire text on that sign!

    I tested it with pex, lwc and signeditor, no other plugins else. Please fix that!

    Last edited Dec 08, 2013 by ThoLav
  • Avatar of mmuziek mmuziek Dec 08, 2013 at 10:58 UTC - 0 likes

    it seems lwc is not saving all protections anymore on restart when using bukkit 1.7.2

    so please make a update :)

  • Avatar of TomXPro TomXPro Dec 07, 2013 at 08:56 UTC - 0 likes

    Hey!

    Thanks for this really helpful plugin! I'm just wondering if LWC 4.3.2 Beta 3 is the latest release working on 1.5.2?

    Greetings Tom

  • 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

Facts

Date created
Sep 08, 2011
Categories
Last update
Jul 11, 2013
Development stage
Mature
Language
  • deDE
  • enUS
  • esES
  • frFR
  • itIT
  • plPL
  • ptBR
  • ruRU
License
BSD License
Curse link
LWC
Downloads
1,530,514
Recent files

Authors