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


    2.0 coming today right? What time?
  3. Offline


    Oh right, i got the development build. Works.
    Any way to disable SQL database use? I don't have one.
  4. Offline


    You can't. LWC automatically downloads SQLite, a standalone database.

    Yes, although I'm not sure of an exact time :)
  5. Offline


    I mean i dont have any SQL database installed on my computer. I would like LWC to store information in file instead.
  6. Offline


    It does :p

    It uses plugins/LWC/lwc.db
  7. Offline


    I know you said you only go by the latest recommended builds, but could you add a separate download for builds 561+? Some of us (me) would appreciate it much. :D
  8. Offline


    So wtf is this:
    21:40:56 [SEVERE] no !/ in spec
    21:40:56 [SEVERE] at<init>(Unknown Source)
    21:40:56 [SEVERE] at<init>(Unknown Source)
    21:40:56 [SEVERE] at<init>(Unknown Source)
    21:40:56 [SEVERE] at com.griefcraft.sql.Database.connect(
    21:40:56 [SEVERE] at com.griefcraft.lwc.LWC.load(
    21:40:56 [SEVERE] at com.griefcraft.lwc.LWCPlugin.onEnable(
    21:40:56 [SEVERE] at
    21:40:56 [SEVERE] at
    21:40:56 [SEVERE] at org.bukkit.plugin.SimplePluginManager.enablePlugin(
    21:40:56 [SEVERE] at org.bukkit.craftbukkit.CraftServer.loadPlugin(
    21:40:56 [SEVERE] at org.bukkit.craftbukkit.CraftServer.loadPlugins(
    21:40:56 [SEVERE] at net.minecraft.server.MinecraftServer.e(
    21:40:56 [SEVERE] at net.minecraft.server.MinecraftServer.a(
    21:40:56 [SEVERE] at net.minecraft.server.MinecraftServer.d(
    21:40:56 [SEVERE] at
    21:40:56 [SEVERE] at
  9. Offline


    did you change your config file for LWC at all? what OS are you on?

    At the initial release of 2.00, it will only be the previous builds. Once released I will do the changes necessary for 561+ to be supported (looking at it, it is a fairly major build upgrade and looks like has a bunch of stuff fixed, so cool beans!)
  10. Offline


    Could you possibly add a command to unlock all chests within a selectable radius? Maybe also auto remove protection entries when a chest isnt actually there anymore? (would help to clean out entries for chests removed with worldedit) We use a plot system and every time time I need to reassign a plot, I need to go hunting for chests to make sure nobody has left a locked one in there.
  11. Offline


    You mean 'lwc.db' and ''? I needed to create them myself, because LWC didn't and always throwed an IO exception.
    As i created the empty '' and started the server, LWC filled in the default settings.
  12. Offline


    does bukkit not have write permissions to that folder or something?
  13. Offline


    It has. Other plugins doesn't have any problems.
  14. Offline


    Ah, so 1.66 does (but it created them fine, I just had to restart). Does plugins/LWC/lib/sqlite.jar exist?

    2.00 will include the command "/lwc admin cleanup" which does the latter :). as for removing chests in a radius, I don't see why not, either in this build or the next. LWC actually already supports it, I would just need to make it remove all of the protections found in said radius.
  15. Offline


    i dont know if this a bug, but if I enter /lwc -i it show only one owner

    oh, i didnt see the /lwc -o command
  16. Offline


    It exists. Windows natives exists too.
  17. Offline


    Weird. Try 2.00, [coming out momentarily]
  18. Offline


    Why didn't I get a .jar file when I downloaded? =/ and the file for editing.... I believe they are .yml.... doesn't look editable.
    EDIT: Also, now everybody joining my server is an admin O.O
  19. Offline


    It is a jar file. I'm not sure what you mean by the rest, did you post in the wrong thread? D:

    2.00 represents the largest update for LWC ever. I hope you enjoy it and all the new features and fixes it brings.

    Thank you to everyone who helped test the 2.00 pre-release, and also to everyone else for your support (and bickering, when I accidentally break things :D)
    2.00 was made possible by all of you

    LWC 2.00

    • Aside setting up your MySQL host data, the conversion between SQLite and MySQL is seamless and automatic. You most likely will need to change the following in
      • database (to mysql),
      • mysql-user,
      • mysql-pass, and
      • mysql-database
    • You may also need to change mysql-port or mysql-host
    • Lastly, run your server as normal. LWC will detect the old sqlite database and will rename it to lwc.db.old after it has finished converting to MySQL

    • LWC's output can now be very customized. This can be utilized to translate LWC to your native language, or even if you just want to change messages for fun.
    • Locale override files are placed in the plugins/LWC/locale folder, named, locale being the locale value in By default, it is en, so you would use You do not have to copy the whole default locale file into here, but you can if you want. Any values not found in your locale file will instead use the default.
    • You can view the default locale file at the LWC wiki

    • LWC now has Basic and Advanced help menus. Basic is the default (which can be changed in, default-menu-style). It only shows commands that have aliases, and uses those. Advanced is basically the same as pre-2.00! Switch using /lwc menu <basic|advanced>. LWC will also use your chosen menu style where applicable (i.e /lwc -m will show up as /cmodify anywhere it's used)
    • Various menus tweaked to be more concise

    • Almost all /lwc admin commands can be used via the console to allow easier administration
    • World cleanup: LWC can search all protections and cleanup protections with no block in the real world or where one protection has more than one registration, i.e conversion from another plugin that protected both sides of a Double Chest (/lwc -a cleanup)
    • All protections created by a player can be found with /lwc -a find <player>
    • Any protection with an inventory can be opened anywhere, anytime provided you have the ID (/lwc -i or /lwc -a find). Use /lwc -a view <id> to open up the inventory. This does support live changes!
    • The owner of a chest can be overridden to another player. Note that the new owner's name is case sensitive, use /lwc -a forceowner <player> and then left click the protection.

    • will now sort itself alphabetically
    • Protections are now flagged using the world they are located in and are bound to that world
    • Drop transferring is once again working, and works with chests and double chests, and will return items that did not fit in the chest
    • Information on chests (/lwc -i) is updated to give lwc admins everything (barring the hashed password for password protections) known about the protection
    • Block destroy protection can be disabled in for specialized servers that have a need for this (most will NOT)
    • /cmodify will now work correctly again
    • Various bug fixes

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


    Well, 2.0 just came out(love the new updates! :D). Not trying to rush you or anything, but could you now add support for 561+?
  21. Offline


  22. Offline


    Still isn't working. When I download it, I just get a zipped folder. I unzip it and there is a .yml plugin file, a com folder, a META-INF folder, and 2 text documents titled lwc_de and lwc_default. There is no executable jar file to make the plugin work on my server. When I load my server it doesn't say anything about LWC.
  23. Offline


    Don't unzip it. It's a jar file, it's just showing up as a zip file for you for some reason? Is the extension literally ".zip"? (the file it downloads is LWC.jar)

    I will soon, I just want to make sure I don't suddenly hear I missed something bad :p

    Is there something critical in 561+? Or just that you want to be at the latest :p
  24. Offline


    561 changes the interact hooks and the block placed hooks in order to fix that ghost block bug that was screwing up so many plugins. so the error on start up is simple cant pass hook bla to lwc. Should not take you long to swap them over.
  25. Offline


    Still isn't working. Not sure how to change the .zip folder into a .jar.
  26. Offline


    Try just copying it to your plugin folder. Make sure you're using "save-as" not "open". It IS a jar file.

    Hi, please download the development build here:

    i have also added a note to the first post linking to the download for 561+
  27. Offline


    Not sure if this is a falsy or what but:

    Also, my LWC recently broke for no reason, same with a couple other plugins.
  28. Offline


    That exploit detected is related to website "drive by" applets -- quoted from MS
    So, I would believe that it is a false positive :)

    when you say a "couple of other plugins", my first instinct would be that perhaps you have something wrong with your Permissions plugin? Are you getting console errors? Could you post them?
    Or, did you recently update to a Craftbukkit build >= 561?
  29. Offline


    [SEVERE] Connection timed out: connect
    [SEVERE] at Method)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at<init>(Unknown Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at Source)
    [SEVERE] at com.griefcraft.util.Updater.getLatestSQLiteVersion(
    [SEVERE] at com.griefcraft.util.Updater.update(
    [SEVERE] at com.griefcraft.lwc.LWCPlugin.loadDatabase(
    [SEVERE] at com.griefcraft.lwc.LWCPlugin.onEnable(
    [SEVERE] at
    [SEVERE] at
    [SEVERE] at org.bukkit.plugin.SimplePluginManager.enablePlugin(
    [SEVERE] at org.bukkit.craftbukkit.CraftServer.loadPlugin(
    [SEVERE] at org.bukkit.craftbukkit.CraftServer.loadPlugins(
    [SEVERE] at net.minecraft.server.MinecraftServer.e(
    [SEVERE] at net.minecraft.server.MinecraftServer.a(
    [SEVERE] at net.minecraft.server.MinecraftServer.d(
    [SEVERE] at
    [SEVERE] at
    Looks like LWC is trying and failing to update sqlite? I have auto-update off in properties even.
  30. Offline



    I think LWC destroyed my mysql 'users' table.

    Can you add an option to specify the table structure?
  31. Offline


    Can it convert back to sqlite - say if for some reason I needed to?

Share This Page