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


    Read not two posts above where you posted this...
  3. Offline


    Thank god this is 1.2 ready!
  4. Offline


    Hey for somereason my lwc stop working correctly limitsv2.yml its not working properly anymore :( check it out the groups setting its not overriding the defaults I never touched this and just stop working out of the blue!! please help
  5. Offline

    Emiya Shirou

    So how does the groups work in LWC? How to set them? I have a lot of chests that setting to certain players one by one will be pain in the arse so I want to set players to certain group then add access of that group to all the chests - how to do that?
  6. Offline


    morning, last week I buyed a bukkit Server from nitrado and installed LWC. For some days all works fine, but now always get the message "Notice: That private (chest) is protectet by ....." I'm op. Some pages earlier in this thread I read that I can disable this message, but I can't find the option you described. Is there still a possibility to diable this without disabling to be LWC admin? Its really annoying. I have version 4.1.1 (b645-git-b24cc99e) of LWC. hope you can help me.

  7. Offline



    I have deleted some entries in table lwc_protections and plugin stopped responding to any command starting from "c.." (cprivate, cinfo, etc.) and respond only "/lwc" for commands "/lwc admin", "/lwc menu", "/lwc flag", "/lwc mode".

    How to fix that?
  8. Offline


    Either use '/cprivate g:<groupname>' to create a private chest which a group named has access to,
    or '/cmodify g:<groupname>' to add a group to an existing private lock.
    Emiya Shirou likes this.
  9. Offline

    Emiya Shirou

    So you explained me how to add group to chest protection, now how to add users to that group? (or remove if I wish to)
  10. Offline


    That depends on your permissions plugin, each of them is slightly different so you'd have to check their instructions on groups. :)
  11. Offline

    Emiya Shirou

  12. Offline


    'Groups' are assigned by the permissions plugins, other plugins can then make use of them. Within your permissions plugin config file (usually a .YML file) you will have the option to specify 'groups', each of these groups has permission nodes assigned to it. You can also specify which group a user or users are part of. I'm not sure how pex does it exactly as I've never used that particular plugin, but there will be information on that thread about how to do it.
  13. Offline


    I run a very small server (less than 10 users), I'd like to enable protection (public) for nearly all block types. Am I missing something, because from the way I understand the config I can specify default settings for protections, but will have to individually specify each block type that they apply to. Since I basically want to automatically public protect virtually every block that building will be done with, that's a pain.
  14. Offline

    Emiya Shirou

    Here are two ranks from my permission.yml file which sits in PermissionsEX folder

            inheritance: Guest
            default: false
            - runecraft.*
            - modifyworld.*
            - lwc.protect
            - cm.init
            - heroes.classes.*
            - heroes.reset
            - templecraft.newgame
            - templecraft.join
            - templecraft.leave
            - templecraft.ready
            - templecraft.templelist
            - templecraft.gamelist
            - templecraft.playerlist
                rank: '950'
            prefix: '&7[&fPathfinder&7] &f'
            inheritance: Guest
            default: false
            - runecraft.*
            - modifyworld.*
            - lwc.protect
            - cm.init
            - heroes.classes.*
            - heroes.reset
            - templecraft.newgame
            - templecraft.join
            - templecraft.leave
            - templecraft.ready
            - templecraft.templelist
            - templecraft.gamelist
            - templecraft.playerlist
                rank: '900'
            prefix: '&9[&fAdventurer&9] &f'
    Do you call those "Groups"? If so If I set (to what should I'll set it for Adventurer rank to have access to chest? Player or Adventurer?) /cmodify g:Adventurer will all players with Adventurer rank will have access to that chest?
  15. Offline


    Those are what I mean yes, those are what we call groups. Your group with the prefix Adventurer, has the name Player. So you would use;
    /cmodify g:player
    to achieve what you want. Though it may be worth renaming the group from player to Adventurer just to avoid confusion in the future. :)
    Emiya Shirou likes this.
  16. Offline

    Emiya Shirou

    Ok thanks <3
    khamseen_air likes this.
  17. Offline


    :) Thank you one of the only plugins that has actually been updated to 1.2.
  18. Offline


    Hey, I have a problem with the newest build of LWC. I use PermissionsEx, which is my favorite permissions plugin. However, the permissions are not working on LWC. Even without "lwc.protect," players still create LWC locks when they place signs, doors, and chests. Is this a problem on my side or yours?
  19. Offline


    I have a problem using this with bPermissions 2.9.0. Whenever I place a chest or furnace, dispenser, it gives me
    [LWC] Internal error. Notify an admin immediately. PLAYER_INTERACT
    Actually it gives me that error whenever I do anything that involves the /cprivate /cpublic /lwc -c password commands. Other commands seem to work fine. Please fix it quickly! Thank you in advance.
  20. Offline


    I have a problem with LWC v.4.1.1. When I open protected chests, there appears a message "Note: This Chest is protected by ...". I looked in the config of the plugin and "showNotices" and "showMyNotices" is on "false". Please help me.

    PS: I'm playing on Craftbukkit 1.2.3 0.1RB
  21. Offline


    Got the same problem.

    my core.yml ->
  22. Offline


    I have the same problem too.
    If you are OP on your server and lock your chest you will see the notice even if they are at False in the config.
    When I de-OP myself it goes away.

    Please fix :)
  23. Offline


    That's good to know. I was wondering if that was spamming everybody or just the OPs. Can live with it until he gets a chance to fix it.
  24. Offline


    Im trying to make private doors so only certain groups can have access. So i type in /cprivate g:Builder enter and it say it worked. I i have one of my builder go to the door and it tells them they cant open the door.
    Could it be that its not reading the Essentials GroupManager

    Show Spoiler
        default: true
        - backup.notify
        - essentials.helpop
        - essentials.list
        - essentials.motd
        - essentials.rules
        - essentials.spawn
          prefix: '&e'
          build: true
          suffix: ''
        default: false
        - Guest
        - g:essentials_builder
          prefix: '&2'
          build: true
          suffix: ''
        default: false
        - worldedit.*
        - lwc.protect
        - izone.tool.define
        - izone.tool.check
        - groupmanager.manuadd
        - groupmanager.manudel
        - groupmanager.manwhois
        - groupmanager.listgroups
        - builder
        - g:essentials_moderator
        - g:bukkit_moderator
        - g:towny_moderator
          prefix: '&5'
          build: true
          suffix: ''
        default: false
        - worldguard.*
        - hawkeye.*
        - lwc.admin
        - ChestShop.*
        - Moderator
        - g:essentials_admin
        - g:bukkit_admin
        - g:towny_admin
          prefix: '&c'
          build: true
          suffix: ''
        default: false
        - '*'
        - admin
          prefix: '&4'
          build: true
          suffix: ''
  25. Offline


    Thanks you soo much!
  26. Offline


    Ooh I was just going to ask why this happened.
    Hope this will be fixed in the next version!

    NOTE: This does not only happen with OP's, but with everyone that has the permission lwc.*

    EDIT: Is it possible to give /cprivate and /cpassword seperate permission nodes?
    I want /cprivate for the normal members and /cpassword just for the donators but i'm not able to do this now.
  27. Offline


    i have an issue, whenever i destory a locked object, it does not unregister automatically. which means the block will be locked even though nothing i there, so if someone set something in that block later, they wont be able to move it...
    how do i make it auto unregister when block is destroyed?
    also, when i access a locked object (chest etc.) it tells me in the chat that "you own that private chest", both config files for shownotices and showmynotices in the core.yml is set to false, so i dont see why it is doing this?
    can anyone help me?
  28. Offline


    Ah this plugin is great ! I love it :D
    Just a Plug'n'Play-Plugin (I use MySQL so I don't "Plug'n'Play", though...).
    Great Plugin dude ;)
  29. Offline


    Is there a way to make it so that users CAN'T lock chests/doors etc. in a certain WORLD? Not WorldGuard Region? Because I have a PVP and a Non-PVP world in my server, and I only want players to be allowed to lock chests in non-pvp (raiding is allowed in pvp cuz there's factions :p). And I only gave users the permission to lock a chest in the non-pvp world, yet apparently they still can in pvp. Not sure why. Help?
  30. Offline


    Any way you could make it so only the user that places the door/furnace/chest etc. is allowed to lock it? Like, some users don't want to lock their doors, they want them to be open to everyone. But then some ppl come around and troll and lock them for them, and then they cant get in. Its a hassle. So any way that only the player that places it can change the privacy? (except of course for admins, or like users with lwc.admin. Because normal users with lwc.protect can lock other players doors for them and troll :S)
  31. Offline



    When i use any LWC command i just get "[LWC] Internal error, Notify an admin immediately" :(
    WHAT DO I DO?!??

Share This Page