Inactive [SEC/MECH] LWC v4.1.1 :: Lightweight Protection for Chests, Furnaces, Dispensers, and more! [1.2]

Discussion in 'Inactive/Unsupported Plugins' started by Hidendra, Jan 17, 2011.

  1. Offline


    LWC v4.1.1 3/1/2012
    [​IMG] Download
    [​IMG] Bleeding-edge builds
    [​IMG] Feature requests, Suggestions and Issues
    [​IMG] IRC - Live Chat ( #LWC )
    [​IMG] github
    [​IMG] wiki (not fully up to date yet, sorry!)
    [​IMG] Donate

    Using LWC

    [​IMG] Modules
    Modules are seperate plugins much like LWC but extend LWC in some way, usually by giving extra functionality. While there may be more than already listed here, these modules are ones that are officially supported by LWC and maintained by the same author (Hidendra).

    [​IMG] LWC-Economy 1.30 - [​IMG] Download
    Configuration file: plugins/LWC/iconomy.yml

    LWC-Economy allows players to buy protections with economy money. At the moment, iConomy, BOSEconomy and Essentials are supported (have an Econ plugin that you want supported? PM me!) It can be configured on a per-user and per-group basis. It does not use Register.

    Aside from purchasing, when a user removes a protection, they will also be refunded what they initially paid for the protection.

    Discounts can also be given to each individual group, player, or by default. A discount is defined by giving X amount of protections for Y price, e.g 5 protections for free (0). After getting 5 protections for free, they pay full price again. They cannot get another discount again unless one of the following becomes true: a. an admin manually resets them b. the discounted amount of protections is increases (e.g increasing from 5 to 6 will mean said player gets 1 more for free) or c. the discount price itself changes (which means they will again get 5 protections for the new price.)

    What can be protected?
    • Chests
    • Dispensers
    • Furnaces
    • Doors
    • Signs
    • Trap doors
    • Anything else! Protections can be customized to anything you wish.

    • Plug 'n play! LWC handles all dependency resolution -- you just put LWC.jar in your plugins directory
    • Has reached a level where its routinely safe and stable.
    • Protections can be: Public, Password, and Private (by User and/or Groups)
    • If the block has a persistent inventory (ex. chest), LWC can protect it! (Unless the server owner disabled the protection of a specific block!)
    • Limits of how many protections a user or group can lock
    • Small memory footprint. No flat files.
    • For chests, only 1 side of the chest needs to be protected. The plugin saves space by dynamically linking connected chests as protected
    • Much, much more. This post would be extremely long if I were to post every feature LWC has to offer.


    If your server would benefit more from a version of LWC in your native tongue, or you just want to do it because LWC is awesome, I'm open to allow translations to (almost any) language. Almost all LWC messages are editable.
    Locale files can be UTF-8, but are limited by Minecraft's charset (Latin-1.)

    The current and latest English locale can be found here:

    Currently, the following languages are officially bundled with LWC:
    • German - de - @Dawodo
    • Polish - pl - @Geoning @dudsonowa and @andrewkm
    • French - fr - @Cehel
    • Dutch - nl - @MadZero & @aoa2003
    • Czech - cz - @hofec
    • Swedish - sv - @christley
    • Russian - ru - @IlyaGulya - requires a Cyrillic font mod for the MInecraft client
    • Spanish - es - Raul " @RME " Martinez & David " @DME " Martinez
    • Danish - da - @TCarlsen

    Changelog (open)

    LWC 3.54
    • FIX: Exploit related to Showcase & LWC
    • /lwc admin report has been fixed

    LWC 3.53
    • FIX: All Permission plugins will now work as they should. In SuperPerms, lwc.protect will default to true. if you are using Permissions 2/3/GroupManager/etc, lwc.protect will default to false

    LWC 3.52
    • FIX: Permissions 2/3 stopped working correctly in 3.51

    LWC 3.51
    • lwc.protect has been changed to be default false again in SuperPerms

    LWC 3.50
    • Remove the permission metadata from defined commands so the endless onslaught of "LWC throwing Dave error !" stops

    LWC 3.49
    • FIX: Double console output

    LWC 3.48
    • 3.48 and 4.00 alphas can now be interchanged without receiving errors.
    • FIX: lwc.protect now defaults to true for SuperPerms, so Permissions 2/3 can be used without receiving Dave errors

    LWC 3.47
    • NEW: iConomy 6 support. LWC-Economy does not need to be updated, only LWC.jar

    LWC 3.46
    • FIX: The Redstone event was not being propagated via the new events

    LWC 3.45
    • FIX: plugins/LWC/locale/ (Locale override) could not create new key values such as grass, stone, etc.
    • Feature: The "nospam" mode now hides notices.
    • Feature: Double wooden doors will now also auto open when opening them. They must both be protected.

    LWC 3.44
    • FIX: LWC would not auto reconnect to MySQL after sitting idle for a few hours

    LWC 3.43
    • NEW: Native PermissionsEx (PEX) support
    • NEW: /lwc admin purgebanned can now take -remove as an argument to also remove the removed blocks & item contents (e.g: /lwc admin purgebanned -remove)
    • FIX: An exception would be thrown when using /lwc admin cleanup while using SQLite
    • FIX: A Bukkit bug would throw an exception when a block was pushed above a chest via piston
    • FIX: The /permissions command on PermissionsBukkit 1.2 (not 1.1) was not working correctly.
    • The Polish localization has been updated courtesy of @Geoning

    LWC-Economy 1.30
    • NEW: Native Essentials Econ support
    • NEW: type: has been added to discounts (very latest iconomy.yml) to allow you to revert to the old way of how discounts were given (default: EXACT, old way: TOTAL)
    • NEW: Refunds can now be disabled by making iConomy.refunds false

    LWC 3.42
    • The flag "EXEMPTION" has been added to allow you to exempt flags from commands such as ADMIN PURGE and ADMIN EXPIRE; it prevents the protection from being removed unnecessarily. It can only be activated by LWC admins. Use /cexempt on or the usual /lwc flag exempt on
    • FIX: Some servers were experiencing a freezing issue on startup which is now fixed
    • FIX: Disabled modes were not properly disabled, despite being told the mode was disabled.

    LWC-Economy 1.21
    • FIX: On some servers LWC-Economy would not bootstrap itself into LWC correctly
    • LWC is unaffected, but due to how automatic provisioning works, the binary will be different from the last due it modifying the build number in /lwc admin version

    • FIX: Servers with autoUpdate set to true would find 3.40 would crash all of the time due to a stackoverflow exception.
    • FIX: PermissionsBukkit /permissions command was unusable due to LWC making it load when the server first started, not when it normally would.

    LWC-Economy 1.20
    • LWC-iConomy.jar has now become LWC-Economy.jar -- please update accordingly.
    • BOSEconomy is now supported alongside iConomy. No extra setup is necessary for either!
    • Money paid for protections can now be refunded when you destroy the protection, even if the person who paid (the owner) is offline.
    • Discounts now give out the exact amount of protections for the discounted price. For example, if 'newCharge' is set to 0 and 'amount' is set to 5, a player will be able to create 5 protections for free after it takes effect.

    LWC 3.40
    • Almost all current LWC Module events have been deprecated. They have been replaced with events such as: `onProtectionInteract(LWCProtectionInteractEvent event)`
    • Fixed PermissionsBukkit compatibility: some commands did not work correctly
    • `/lwc admin cleanup` has accelerated to warp 5
    • Servers without any Permissions plugin would find anyone would have LWC Admin access
    • The mode "nospam" has been added to prevent protection creation messages from popping up (e.g "created protection successfully.") Use /cnospam or /lwc mode nospam, which toggles it on and off.
    • Protection history. LWC now logs all protection creations/destructions -- in the future, this may log chest access, but if it happens it will be a separate plugin such as LWC-Economy
    • -remove flags have been added to `/lwc admin expire` and `/lwc admin purge <player>` to remove the associated protection block. For example, if you use `/lwc admin purge -remove Hidendra`, it will remove all protections by Hidendra, and also all of the blocks protected in the world, along with any chest contents.
    • If LWC loses connection to MySQL, LWC will prevent access to chests until the connection is regained. This is to prevent stealing from chests if the connection is somehow lost and cannot be immediately regained.
    • Pistons can no longer destroy protected doors and so on.
    • Multitude of bug fixes and minor corrections
    • Minor optimizations

    • PermissionsBukkit is now officially supported. LWC will still work on builds pre-1000
    • lwc.blockinventory has been renamed to lwc.deny - please take note
    • Fixed a bug where protections would be loaded from any world
    • Fixes to the Danish translation

    • Added core.ignoreExplosions to core.yml to allow an admin to allow creeper explosions / TnT to destroy protections
    • Protections will now keep track of the last time they were interacted with
    • Added the command /lwc admin expire to allow you to expire protections that have not been used in so long. Example: /lwc admin expire 2 weeks
    • Added the command /lwc admin purgebanned to remove protections of every played in banned-players.txt
    • Added the command /lwc admin query to allow raw queries on the physical database
    • Drop transferring could not be disabled, it is now fixed.
    • Various bug fixes

    • Fix "fetch size" error
    • Removed the auto-removal of the very old players table


    • Very important bug fix for those who are using MySQL and prefixes. Prefixes will now work correctly and any issues arisen from MySQL usage should now be resolved
    • Fixed lang-defined block names being used in core.yml - protections instead of the english variant, otherwise all protections are broken.

    • It's not all about me! I've tried my hardest and /lwc credits was the result. It turns out there is a lot more people I am extremely thankful to than can fit on one chat page, so instead it scrolls.
    • Many, many people helped with LWC in vastly different ways and it's impossible to credit every single person accurately, thus I missed a few people.

    This update introduces three more languages: Russian, Spanish, and Dutch.
    • Russian - @IlyaGulya - requires a Cyrillic font mod for the Client
    • Spanish - Raul " @RME " Martinez
    • Spanish - David " @DME " Martinez
    • Dutch - @Tcarlsen

    Chunk corruption workaround
    • Have you ever noticed, when you /cinfo'd something, it said "That air is not registered"? Or when chests randomly stop working? If you get this a lot, you are most likely affected by an issue in Bukkit where chunks will mysteriously report Air (or some other block) for each block in the chunk. Please refer to this bug report on Leaky Bukkit:
    • @morganm graciously found a way to workaround this issue, and it involves forcing every single protection to be cached and some other magical tidbits (without getting too technical.) To enable this, open up plugins/LWC/core.yml and then change bukkitBug656workaround to true. If you don't see it under core:, add it:
          bukkitBug656workaround: true

    • Trap doors are now available as a default protection for any new configurations: they will not automatically add themselves to existing LWC configurations
    • The default value for magnet.yml - perSweep has been changed from 20 to 40
    • The command /lwc debug has been added to test your permissions and show you precisely what you have access to
    • LWC now displays the git commit and Jenkins build ( in version strings (e.g /lwc admin version or /lwc admin report).

    • Translation: Swedish! Thank you @christley!
    • Bug fix for block placement

    • Translation: Czech! Thank you @hofec
    • The default value for core.showMyNotices has been changed to false (does not affect current installs.)
    • Burning furnaces have been fixed
    • Iron doors have been fixed
    • Redstone fix
    • Fixed auto register allowing registrations without having lwc.protect
    • Feature: auto openable Iron Doors. On by default -- iron doors (including double doors) will open (or close) when you click them provided they are both protected and you have access to them. "openAndClose," which closes the door automatically after x seconds (3 by default) is available but currently may not work as expected (works oppositely for doors facing North or South; doors will stay open.)
    • Trap doors (aka hatches) have been added to the default protection list. However, if you have an existing core.yml, and want trap doors, you either need to delete core.yml and restart the server (thus redownloading it) or adding trap_door to protections.blocks, e.g
                  enabled: true
                  autoRegister: off

    • Sign names have been normalized to "Sign" (e.g Wall sign and Sign post are shown as just Sign)
    • Added locale values for "you" and block names (chest, furnace, dispenser, wooden_door, iron_door, and so on.) Custom block names can be defined if you have custom protections.
    • Dutch translation -- thank you to @MadZero and @aoa2003

    • Notices will be shown correctly to admins when showMyNotices is disabled.

    • Limit the amount of queries the Magnet module can use (can be changed with magnet.perSweep, default 20. Delete magnet.yml to auto-regen it). On larger worlds, this was a severe issue
    • magnet.enabled now works correctly

    • MySQL prefix is now working as it should
    • Minor fix with the cache update in 3.02

    • Cache null protections as well, to prevent massive redstone spam

    LWC 3.01

    Thank you so much to the many, many people who provided feedback and suggestions on 3.00.
    This changelog may be incomplete as I probably missed some obscure changes.

    The following languages are now available in LWC:

    Lists support
    • LWC supports the Lists plugin which allows you to create a list for your protections to use. Anyone in this list attached to the protection can access your protection
    • When modifing/creating the protection, use l:ListName or list:ListName, e.g: /cmodify l:Test or /cprivate l:Test

    • is now gone. It has been replaced by multiple .yml files, e.g core.yml, limits.yml, worldguard.yml, and so on.
    • Your old is still automatically converted.

    • The old in-database limits has been fully removed. It is replaced by an on-disk alternative, limits.yml. This very easily allows much more in-depth limits management (e.g only: 5 chests, 2 furnaces, 0 doors)

    Custom protections
    • It is now extremely easy to create your own custom protections, or remove existing ones (core.yml -> protections:). For example, this is how you would make Note Blocks protectable, and allow people to play them (But not change the note!):
                enabled: true
                ignoreLeftClick: true

    • [I hope] final major revision to the LWC Api. New additions will allow other plugins to hook into LWC much more easily and do things that were not possible before. Features can be seamlessly integrated into LWC as if they were in LWC itself.
    • PhysDB.getPrivateAccess is now deprecated -- please use protection.getAccess instead!
    • Protections can be more easily modified utilizing methods in their objects: save() (queued save), saveNow(), remove(), removeCache() (just removes the protection from the cache, not the database), and update() (just updates the cached protection, save()/saveNow() already does this)

    LWC Modules
    • Modules can be thought of as a plugin inside LWC itself -- more or less they will change LWC's behaviour in some way, depending on the module.
    • Very easily implemented by developers: cancel protection registrations, cancel that damn protection message, and way more! More info on the wiki.

    Admin customization
    • There are now a ton of permissions nodes; there is one for each admin command. For example, for every Admin command, you could use: lwc.admin or lwc.admin.*. For just "find" and "forceowner", you could give a group/player the following: lwc.admin.find and lwc.admin.forceowner. Full list on the wiki.
    • Please note that lwc.admin.* only grants all Admin commands; lwc.admin still has a higher authority over the former (e.g, lwc.admin is considered the owner of any protection, while lwc.admin.* is not !!)

    Player customization
    • Like the admin commands, the main LWC commands can now be customized via permissions. lwc.protect still functions the same (all functionality); some examples of new nodes are: lwc.create or lwc.create.* (create anything), lwc.create.private (only be able to create private protections), (/cinfo), lwc.modify (/cmodify), lwc.unlock (/cunlock), and so on. Full list on the wiki.
    • Please note that without lwc.protect, you need to manually assign flags. E.g: lwc.flag.* or / lwc.flag.magnet

    Magnet flag
    • The chest will act as a magnet and suck up nearby items (within a 3 block radius.) This can be very useful for automatic farms (e.g animals or crops.) It is compatible with double chests.
    • Can also specify items that these special chests will not pick up (in magnet.yml)
    • Compatible with Double Chests

    • It is now possible to sell protections with the fully optional LWC-iConomy bridge module. You just throw LWC-iConomy.jar into your plugins folder and then edit iconomy.yml in plugins/LWC/ when it's generated on the next startup!
    • You can also allow players to have a certain amount of protections at a reduced price (or even free) e.g free protections while you have less than 5 (but regular price after that.)

    • LWC now does major caching of protections in memory. Previously, LWC hit the database everytime a protection is opened; now they are routinely stored in cache without a huge hit on memory usage (very minimal.) It can be increased from the default of 10000 if you wish in core.yml (core.cacheSize). More will most likely be cached in the future
    • Access rights are now stored with Protections (for the curious, it uses an OUTER JOIN, so just 1 query.)
    • Protections are precached (as many as possible) when the server is started
    • Lots of bug fixes (mostly miscellaneous.)

    • MySQL prefix can now be configured (if you change it with an existing MySQL install, it will fix that automatically, don't worry!)
    • /cpersist or /lwc mode persist now acts as a toggle for the mode
    • Added the following aliases: /cpersist , /cdroptransfer , /cmagnet , and /cadmin
    • /climits displays your protection limit and how many protections you have protected.
    • Minor changes all around


    • Security bugfix regarding an issue in minecraft itself (thanks sycot)

    • Native German translation! If you wish to use LWC in German, please change "locale" in to de. Many thanks to @Dawodo for doing the translation!
    • /lwc admin cleanup will now show the correct values instead of variable names when outputting results
    • enforce-worldguard-regions is now compatible with WorldGuard 5.x
    • Redstone is now changed again. All set redstone flags are reset. Redstone will obey the deny-redstone config value (which is false by default), meaning if it is set to false, you need to explciitly set the flag to disable redstone (/lwc flag redstone on), and if it is set to true, all doors prevent redstone by default so you need to set the flag to allow redstone.

    • Minor bug fixes

    • By default, redstone WILL NOT open doors (at the moment, it appears dispensers are unaffected, hopefully they will be fixed in CraftBukkit). In order to allow redstone to open your door, you need to issue this: /lwc flag redstone on. Using /lwc flag will show you the available protection flags -- these are "switches", only on/off (only redstone flag exists at the moment)
    • Bug fix: Protections will auto protect themselves again when being placed

    • Official support for RB builds >600 now that I am back home
    [hit max thread length]

    enjoy, gents
  2. Offline


    Ah that could explain that then, is there an LWC reload command? I couldn't find one in the command list.
  3. Offline


    i need help befor the update it all worked fine now it works kinda you cand you commands like /cprivate or /cremove or any of that
  4. Offline


    Doesnt work at UNRECOMMEND build 1137 + permissions 3x it says no permissions BUT IM OP AND ALL PERMISSIONS in permissions 3x
  5. Offline


    Are you using 3.50?

    Are you using 3.50?
  6. Offline


    i did but now i updated to unrecommend build of lwc that u made, it seems to work fine :)
  7. @Hidendra Any chance that LWC stores locks by IP address? I ask because on my server, many people have others in their household that play with them, and players with the same IP as others have access to the locks made by them.

    Er, that's a bit confusing. Here:
    Player A and Player B have the same IP address. Player C has his own.

    Player A uses /cprivate on a door.
    Player B can open the door, but still receives the message that it's owned by Player A.
    Player C cannot open the door.
  8. Offline


    dose it have trouble running on mac because every time i lock a chest my friend can open it it just says this chest is locked by jjoonn222 and then he can take all of the stuff in it
  9. Offline


    how can i make it to where it dose not lock the item right away when someone placesit they have to lock it manuly
  10. Offline


    I cant get lwc to protect glass pane ... tried glass_pane and Glass_Pane .. Not sure of the id to go that route. Not in items.csv

    Thanks for any help.

    NM lwc calls it thin glass.. found id also is 102..

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 18, 2016
  11. Offline


    When I updated my server to CB 1129 (Minecraft 1.8) locking no longer worked. The plugin was there and it loaded up and even myself (admin) couldn't lock anything it just said:
    I'm sorry Dave, I can't let u do that
    Yeah..... so wtf Please help. I'm admin and I have every permission so its not that I have to wrong nodes. Plz fix, massive stealing riots have started XD lol

    Is LWC Version 4.00 out for download even though its not recommended?

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 18, 2016
  12. Offline


    I found nothing about redstone triggers.
    How can i protect levers or buttons?
  13. Offline


    He has access to lwc.admin in permissions or is an OP. If you don't want Ops to be LWC Admins (access to everything), in plugins/LWC/core.yml, change opIsLWCAdmin to false

    You are using an outdated Permissions plugin, that does not support Bukkit.... however, update to LWC 3.50..

    In plugins/LWC/core.yml, replace every autoRegister: private to autoRegister: off - there is more than one occurrence.

    Many IPs are dynamic. This would not work well when your IP changes, no?

    If players want to share locks, they should use /cprivate OtherPlayerName to give them access, or /cmodify OtherPlayerName to add them in. Or, protect the door using a password (which when you unlock it, it gives you access until you log out.)

    You can disable redstone on a door with /credstone on.

    If you want levers/buttons to be protected, you need to add them in plugins/LWC/core.yml -- scroll down to where you see chest: , etc. You will need to copy the one block and make the level/button
            enabled: true
            enabled: true
    And so on. If you want it to be auto protected, you'd need to do the autoRegister: private like the others do.

    Yeah. The central server that manages connections to my build server is down at the moment, so I can't get you a link. if you hop in IRC whenever you're on I could get a build to you.

    Download server is down, yet again. I'm going to talk to the company that provides it and may need to move. A few generous gentlemen had offered things in the past so I may need to take one of them up on their offer..
  14. Offline


    2011-09-18 12:49:30 [SEVERE] Error occurred while enabling LWC v3.5 (Is it up to date?): null
        at java.util.Locale.toLowerCase(Unknown Source)
        at java.util.Locale.convertOldISOCodes(Unknown Source)
        at java.util.Locale.<init>(Unknown Source)
        at java.util.Locale.<init>(Unknown Source)
        at com.griefcraft.lwc.LWCPlugin.onEnable(
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(
        at org.bukkit.craftbukkit.CraftServer.loadPlugin(
        at org.bukkit.craftbukkit.CraftServer.enablePlugins(
        at net.minecraft.server.MinecraftServer.e(
        at net.minecraft.server.MinecraftServer.a(
        at net.minecraft.server.MinecraftServer.init(
    running - CB1149 , yes i know its NOT a recommended build but i thought i would tell you about this error.
  15. Offline


    Unusual, I'm running 3.49 (b247) on CB1149 without any issues.
  16. Offline


    In plugins/LWC/core.yml, is locale set to null?
  17. Offline


    well the odd thing is there is no /LWC/core.yml. the only thing i have is\LWC\lib\native\Windows\amd64
  18. Offline


  19. Offline


    very nice! thanks :D i believe the issue started since your site is down, it didnt download all the files. no big-e its all fixed :D
  20. Offline


    I miss the bleeding-edge dev page, it's giving me one less thing to troll for updates. :(
    LoL, it's rather upsetting to realise how much I love looking for updates.
  21. Offline


    best chest protection ever.
  22. Offline


    When it's back up, you can (as of alpha4) use /lwc admin version to check for updates if you wanted to ;)

    /lwc admin update was redone by default updates to the latest dev build currently. Wwhen it's fully released, you'll be able to either a. stay up to date to the stable branch, b. stay up to date to the maybe less stable branch, but has more features (e.g alpha1, then when alpha2 is released, it updates to that), and c. bleeding edge (which is what it's set to right now), it keeps up to date to the latest LWC Jenkins build

    thank you :)
    544nick101 and khamseen_air like this.
  23. Offline


    hi,help plz.
    When some player type /cprivate and private his chest/door another player can open his door/chest,but if user with admin permissions private doors/chest all ok.I have permissions plugin 3.6 and lwc 3.50.Need help,its very important!
  24. Offline


    its set to off on mine and it still is auto protect
  25. Offline


    do you a link for permissions? the link on front page doesnt work, 404 error
  26. Offline


    Don;t worry I
    Don't worry I went onto and found build #257 and that works for me even though its bleeding-edge
  27. Offline


    could I bother to poke you for the 4.0 build also? want to poke around with the towny feature on my test server :)
  28. Offline


    Just LWC.jar ;). In core.yml, change core.townyBorders to true
  29. Offline


    thank you :)
    maybe I'm missing something?

    replaced jar, deleted my entire LWC folder, started server...but dont see a core.townyborders option.
    here is the core.yml
    # Core configurable options for LWC
        # The language LWC will use, specified by the shortname. For example, English = en, French = fr, German = de,
        # and so on
        locale: en
        # If set to true, LWC will automatically download new updates as they become available
        autoUpdate: false
        # How often updates are batched to the database (in seconds). If set to a higher value than 10, you may have
        # some unexpected results, especially if your server is prone to crashing.
        flushInterval: 10
        # LWC regularly caches protections locally to prevent the database from being queried as often. The default is 10000
        # and for most servers is OK. LWC will also fill up to <precache> when the server is started automatically.
        cacheSize: 10000
        # How many protections are precached on startup. If set to -1, it will use the cacheSize value instead and precache
        # as much as possible
        precache: -1
        # The default menu style presented to players. Possible options are basic and advanced. Basic prefers to use
        # aliases such as /cprivate over its advanced counterpart, /lwc -c private or /lwc create private
        defaultMenuStyle: basic
        # If true, players will be sent a notice in their chat box when they open a protection they have access to, but
        # not their own unless <showMyNotices> is set to true
        showNotices: true
        # If true, players will be sent a notice in their chat box when they open a protection they own.
        showMyNotices: false
        # If true, ops will be considered LWC admins (e.g with a Permissions plugin, considered to have lwc.admin) and thus
        # will have very destructive LWC commands.
        opIsLWCAdmin: true
        # If true, LWC will not log history about protections. If you are using LWC-Economy and this is disabled, you will
        # NOT receive refunds for purchased protections
        disableHistory: false
        # If you're having an issue where chest locks randomly stop working, and if you type '/lwc -o' and hit
        # one of these "not workin" chests and see something like 'That Air is not registered!', you may be
        # experiencing bukkit bug #656:
        # If so, set this flag to true, and to avoid a performance hit, be sure to set 'cacheSize' above to
        # more than whatever number of active protections you have.  LWC will cache all protections in memory
        # and protect any x,y,z registered block, regardless of if Bukkit says it's something else (like Air).
        bukkitBug656workaround: false
    # Database information for LWC
        # The database adapter to use, for example sqlite (default) or mysql
        adapter: sqlite
        # This is strictly for SQLite only and should be left alone. When changing to MySQL and this is left intact,
        # LWC will automatically convert your protections from SQLite to MySQL
        path: 'plugins/LWC/lwc.db'
        # The MySQL host. You can specify a non-default port (3306) by adding :port, e.g host: 'localhost:3307'
        host: 'localhost'
        # The database LWC should use to store data (not necessary for SQLite)
        database: 'lwc'
        # The username LWC should use to connect to the server with (not necessary for SQLite)
        username: ''
        # The password LWC should use to connect to the server with (not necessary for SQLite)
        password: ''
        # The prefix for LWC tables. For example, a prefix of 'lwc_' will make
        # the protections table show up as lwc_protections
        prefix: 'lwc_'
    # The protections nodes allows you to define, remove and modify which blocks LWC is allowed to protect
    # This means that you could make any block you want protectable, or remove existing protectable blocks
    # (e.g trap doors, etc.)
        # These values serve as default values for the protections defined under blocks
        # If true, the default behaviour will be to BLOCK redstone to protections, and /credstone on (Protection Flag)
        # will ALLOW redstone to the protection
        # If false, the default behaviour will be to ALLOW redstone to protections, and /credstone on will
        # BLOCK redstone to the protection
        denyRedstone: false
        # Settable to private, public, or off. It defines what protections are registered as when you place them on
        # the ground
        autoRegister: off
        # Used in very specific use-cases: makes LWC ignore block destruction for the given block or all blocks, allowing
        # players to remove the block and resulting protection.
        ignoreBlockDestruction: false
        # If left clicking should be ignored by LWC. An example of this would be to add ignoreLeftClick under a note block
        # protection to allow players to play the note block's note, but not change the note (which is done via right click,
        # which would be blocked by LWC.)
        ignoreLeftClick: false
        # If right clicking should be ignored by LWC.
        ignoreRightClick: false
        # If LWC should ignore explosions to the protection. For example, you could allow Doors to be blown by explosions,
        # but not chests.
        ignoreExplosions: false
        # Current and custom protections are defined here by their block name or id
        # If you use the Id, you MUST encase it in quotes, for example (chest):
        # '54':
        #     enabled: true
        # The custom protection must also have enabled: true under it for it to function in the world
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: private
                enabled: true
                enabled: true
                enabled: true
            enabled: true
            enabled: true
    if it suppose to be there and not generating it no rush on it, since it is a pre-release build I'm pestering you about :p
  30. Offline


    It won't be added automatically (may fix that in the future ;))

    # Core configurable options for LWC
        # Shazzam!
        townyBorders: true
        # The language LWC will use, specified by the shortname. For example, English = en, French = fr, German = de,
        # and so on
        locale: en
  31. Offline


    ahhh silly me..thanks for replying. ignore my ignorance and lack of reading skills and carry on :p

Share This Page