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


    How to protect other blocks with LWC ?
  3. Offline



    I know this is probably impossible, but...

    Can you make 'lwc admin purge' drop not only the user protection but COMPLETELY ERASE his protected blocks from 'world' as well ? :D

  4. Offline


    Im kind of having the same problem as iStormUK. im pre-build a part of my server so people can jump in and begin playing instead of waiting to build the first town, but im having to create a lot of signs and things for various buildings so new people know what to do. And i turned all the auto-registers to false but they keep auto-registering.

    I saw that devatrox had them set to "off" in his config file at post #2907 and i was wondering if thats how we are supposed to turn them off?
  5. Offline


    The one thing my server really wants is more granular permissions. A node for each protection command (public, private, password, remove) would be nice, and a node to see who locked a block, among others. I don't like that the plugin developer decides what my mods should get to do.
  6. Offline


    That's strange... I was just about to say the same thing. I want to give my mods "lwc.admin.purge" and some others but can't which is a bit of an annoyance.
  7. Offline


    The above was PM'd to me this morning, this is with LWC v3.06 and Notch's version of the nether. Has anyone else experienced this problem?
  8. Offline



    Sorry, but I know I mentioned this before, and you told me its all in limits.yml now, but.....

    Why remove /lwc admin limits # PLAYER or /lwc admin limits # g:GROUP ???

    So instead, I just have to manually do it inside limits.yml now?


  9. Offline


    Is it possible to customize prices for LWC per world?
  10. Offline


    After some test it's the mysql prefix that make ingame commands to not work.

    If prefix is leave empty all ingame commands works fine.
  11. Offline


    14:53:25 [SEVERE] Could not pass event PLAYER_INTERACT to LWC
    com.griefcraft.scripting.ModuleException: LWC Module threw an uncaught exception! LWC version: v3.11
            at com.griefcraft.scripting.ModuleLoader.dispatchEvent(Unknown Source)
            at com.griefcraft.listeners.LWCPlayerListener.onPlayerInteract(Unknown Source)
            at org.bukkit.plugin.RegisteredListener.callEvent(
            at org.bukkit.plugin.SimplePluginManager.callEvent(
            at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(
            at net.minecraft.server.ItemInWorldManager.interact(
            at net.minecraft.server.NetServerHandler.a(
            at net.minecraft.server.Packet15Place.a(SourceFile:57)
            at net.minecraft.server.NetworkManager.b(
            at net.minecraft.server.NetServerHandler.a(
            at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
            at net.minecraft.server.MinecraftServer.h(
    Caused by: java.lang.NullPointerException
            at com.griefcraft.lwc.LWC.getProtectionSet(Unknown Source)
            at com.griefcraft.modules.doors.DoorsModule.onProtectionInteract(Unknown Source)
            ... 15 more
    This popped up in the server log, CB 860, LWC 3.11
  12. Offline


    Thanks for the information, turned off the prefix and it started working fine! - However an offical fix would still be much appreciated as prefixes make my Minecraft DB look far tidier. :3

    While it's probably not my place to comment I'd just like to point out that this is not 'your mod', you have not contributed (significantly) to it's creation, as the plugin developer has. The plugin developer has very likely made this for his/her own benefit and releasing it into the public domain is a exetremely generous act on their behalf, these things don't just make themselves, they take hours upon hours of hard work. Making suggestions is fine and dandy, but implying that it is 'your mod' and the person who is doing the hard work should not be able to choose how it works is simply asinine.

    Just my two cents on the matter.

    EDIT: Also, this plugin is distributed under the GPL so you could make it 'your mod' in part by forking it and doing the work required to make it function the way you want.
    HawnSolo likes this.
  13. Offline


    I'm having a little trouble setting up LWC limits after upgrading to 3.11. It converted the old SQL db into the limits.yml file, and the settings look correct, but every group is getting the default limit of 25. Any player who is explicitly set as having more protections IS getting the correct number.

    Here is the limits.yml:
    limits.yml (open)
        limit: 25
        type: default
        chest: unlimited
        furnace: unlimited
        dispenser: unlimited
        wooden_door: unlimited
        iron_door: unlimited
            limit: 0
            type: custom
            chest: 5
            furnace: 2
            dispenser: 1
            limit: unlimited
            limit: 40
            type: default
            limit: 50
            type: default
            limit: 30
            type: default
            limit: 35
            type: default
            limit: 40
            type: default
            limit: 50
            type: default
            limit: 30
            type: default
            limit: 35
            type: default
            limit: unlimited
            limit: 60
            type: default
            limit: 100
            type: default

    I don't see a guide to the limits.yml, but it seems mostly straightforward. What am I doing wrong?

    We're running Permissions 2.7.2, LWC 3.11 and a whole bunch of plugins that have never caused any problems with LWC before.

    Also I've noticed:
    /lwc admin reload - disables and then enables the LWC plugin. But it doesn't remove the old listeners, and when it re-enables, it registers them again. this results in protection notice messages repeating as many times as you have reloaded the config. Also I'm not sure if this will reload the 'modules' configs (like 'limits')?

    No way to edit users/groups protection limits ingame. This was nice :( the only thing I didn't like about the old way was being unable to view the current limits ingame. I like that the /climits command in v3 can take an argument of a player's name :)

    EDIT: Turns out it was a case sensitivity issue. LWC created the limits.yml from the old DB info, and left the group names lowercase. Permissions was trying to match it to a group name with capitals in it. Thanks for the help on IRC Hidendra!
  14. Offline



    I use LWC very small on my server. I use it ONLY for admins to use on Chests and Doors to certain structures. Right now my players cant even place signs because it doesnt allow them to.. Also ANYTHING I place is automatically Locked. How can I configure this to not allow players ANY thing, and how to allow them to place signs normally? Im quite confused by this update cause these problems are all new as of upgrading to 1.6.6 from the 1.5 version
  15. Offline



    As we discussed in IRC the other night, I've created a version of LWC, forked from 3.11, which applies LWC protections at a given X,Y,Z coords regardless of the block type, which is done as a work around to Bukkit Bug 656. I've deployed this version to my server and am testing it out now, if I find it to be in good working order I'll push a gitdiff to you so you can incorporate it upstream if you like.

    It has the "bukkitBug656workaround" flag in core.yml as discussed, so for anyone not having the issue, the flag defaults to false and "normal" LWC behavior applies. For those of us affected by the bug, flipping this flag on enables the workaround code.

    I'll let you know how it goes in a day or two.
  16. Offline


    for some reason when people place chests there locked automatically and this stops my players from being able to open there own chests... people with lwc.admin can open em fine..?


    *and when its unlocked they just dont open fully stop.. not even a message.*
  17. Offline


    Good Plugin but a Simple Pressure Plate open all Doors. Please Fix it.

    Hf Doppelkeks
  18. Offline


    If i use Mysql i cant Protect -.-
  19. Offline


  20. Offline


    Why does LWC display messages in Dutch, even though I used "eng" in the configuration?
        locale: eng
        autoUpdate: false
        flushInterval: 10
        cacheSize: 10000
        defaultMenuStyle: basic
        showNotices: true
        showMyNotices: true
        verbose: false
        opIsLWCAdmin: true
  21. Offline


    Hello. Im running CB 860, Debian linux. I'm getting this error:
    2011-06-20 23:00:42 [INFO] LWC    Loading shared objects
    2011-06-20 23:00:42 [INFO] Cache    Protection cache: 0/10000
    2011-06-20 23:00:42 [INFO] LWC    Native library: plugins/LWC/lib/native/Linux/amd64/
    2011-06-20 23:00:43 [SEVERE] java.lang.IllegalAccessError: tried to access class com.nijiko.permissions.ModularControl$RefreshTask from class com.nijiko.permissions.ModularControl
    2011-06-20 23:00:43 [SEVERE]     at com.nijiko.permissions.ModularControl.<clinit>(
    2011-06-20 23:00:43 [SEVERE]     at com.nijikokun.bukkit.Permissions.Permissions.setupPermissions(
    2011-06-20 23:00:43 [SEVERE]     at com.nijikokun.bukkit.Permissions.Permissions.onLoad(
    2011-06-20 23:00:43 [SEVERE]     at org.bukkit.craftbukkit.CraftServer.loadPlugins(
    2011-06-20 23:00:43 [SEVERE]     at net.minecraft.server.MinecraftServer.e(
    2011-06-20 23:00:43 [SEVERE]     at net.minecraft.server.MinecraftServer.a(
    2011-06-20 23:00:43 [SEVERE]     at net.minecraft.server.MinecraftServer.init(
    2011-06-20 23:00:43 [SEVERE]     at
    2011-06-20 23:00:43 [SEVERE]     at
    2011-06-20 23:00:43 [SEVERE] [Permissions] Unable to load permission data.
    2011-06-20 23:00:43 [SEVERE] [Permissions] Shutting down Permissions due to error(s).
    2011-06-20 23:00:43 [INFO] [Permissions] (Yeti) was initialized.
    This is not problem of LWC, other plugins have problems with DB connection too.. :(
  22. Offline


    ummmmmm it probably just my version being out of date but does lwc do hatches??? and if i update will i have to relock everything or is it fine cuz the jar is the only thing changing and not the logs? or does the new version read the logs differently?
  23. Offline


    Not sure if this has been reported before or not, but locked doors can be bypassed by putting a pressure plate down. Is there a fix to this?
    clitcomander likes this.
  24. Offline


    yeah buttons, plates , and switches all bypass lwc....only thing i know that i did was worldedit region protect the area
  25. Offline


    If i make /cprivate i cant protect :(
  26. Offline



    Just an update: I've been running with my Bukkit Bug 656 workaround now for a few days and it's working great. I've not had a single report of any chests being broken into. I have, however, confirmed that the Bukkit bug has reared it's head and Bukkit has reported "Air" instead of a given chest, but with the workaround in place the chest was still protected anyway.

    I'm not pushing it to you just yet (assuming you do want to incorporate upstream) because when I setup this version, I knew I setup a condition whereby some blocks would get "locked" forever (until next reboot), such as in the case of double chests. I've added some code to deal with this situation but can't test it just at the moment. Once I get this tested and confirmed to be working, I'll gitpush you the changes so that anyone else experiencing Bug 656 can use these changes also to have LWC functioning at full capacity despite the Bukkit bug.

  27. Offline


    my friend made a private furnace and im admin so i destroyed it but whenever i place it back it says its locked by him.
  28. Offline


    Good news, then! It'd be lovely to have it in upstream -- I know a few people who this bug has effected and it would help them very much to have it (especially since it's just toggleable)

    What version of LWC are you using?

    Do you have Permission to do that?

    /credstone on
    HIt the door. :D

    /credstone on
    Hit the door. :D

    You can make hatches protectable yourself. In plugins/LWC/core.yml, find

        denyRedstone: false
        autoRegister: off
        ignoreBlockDestruction: false
        ignoreLeftClick: false
        ignoreRightClick: false
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: off
                enabled: true
                autoRegister: off
    Add this below it:
                enabled: true
                autoRegister: off
    Are you using Essentials?

    Also, are you using any other Permissions plugins other than Permissions itself? e.g Essentials

    Use en instead :)

    Is it configured correctly and starts fine? (No errors.)

    /credstone on
    Hit the door.

    In plugins/LWC/core.yml, replace all instances of
    autoRegister: private
    autoRegister: off
    Anytime, good sir :D

    As of right now - no.

    A similar command will be added at some point, yes. limits.yml allows more complex limits that some servers had wanted (e.g a limit of 5 chests, 2 furnaces, 1 dispenser, and 0 doors was not possible before.)

    Indeed the prefix will indeed be fixed.

    The good thing is, the surprise is "LWC actually does this," not "Thanks for the idea, I'll add it to the list!" There are lots of quirky features that are undocumented, or buried in the changelog.



    You can :)
    Most people like simple permissions -- so lwc.protect is the default.

    All permissions
    lwc.protect essentially is equal to these:
    You can give individual admin permissions, too.
    lwc.admin = Essentially, owner of ALL protections, access to ALL commands
    lwc.admin.* = ALL admin commands, you ARE NOT THE OWNER of any chests but your own.
    lwc.admin.COMMAND is the node prefix. Too many to list!
    e.g lwc.admin.find is the /lwc admin find command, which lets you find protections created by a player.
  29. Offline

    Dakotah Lucas

    i dropped the LWC.jar into my plugins folder, restarted the server and LWC made a folder with the following directories... but there is no other files in the folders... just folders enclosing folders...

    Ive tried reinstalling a few times and it always creates the same thing


    any help is appreciated =D Look forward to using this plugin
  30. Offline

    Thomas Carlsen

  31. Offline


    im using the latest; i think

Share This Page