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


    heres the thing though, im the admin, in fact, im a user whose the sole member of a group called "SheepRock" who can do anything apperantly because of the '*' in my permissions, so i get everything anyway regardless of inheritances?

    brb changing what you mentioned....
  3. Offline


    That isn't the point. Because the groups your group inherit do not exist, IT WILL throw an error. Yaml isn't as free willed as hMod's permissions, if something is wrong it will complain about it.
  4. Offline


    it worked because of what you mentioned. my lack of plurals all the way down the chain seems to have been the problem. thank you sir!
  5. Offline

    Cosmic Break

    What can be protected?

    • Chests
    • Dispensers
    • Furnaces
    • Doors
    • Signs
    i love you now
  6. I wish there was a way, to make it so that chests, can only be protected in specific area :(
  7. Offline


    Hey I want to start off by saying I like this plugin alot.

    However, it seems to use up ALOT of memory on my server. I did a test on a fresh world on my server. First I logged in and ran around with just craftbukkit. Then with just LWC. Then with all my mods. Then with all my mods but LWC. and then again with just craftbukkit.

    Adding LWC into the mix (on a fresh map with no chests locked) used up an extra 200mb on average. With LWC (either by itself or with all my plugins) used up 550mb on startup and 800mb after exploration. Without LWC I was at 350 on startup and around 600 after exploration.

    I went through this twice, and the numbers were consistent. Any ideas why this is happening, or is this expected?

    edit: Also, I would really like to see a chest limit implemented for groups. I understand that I can add it per user, but it would be really great to be able to /lwc admin limits 1 g:Default
  8. Offline


    Well, at the moment the only way would be to make enforce-worldguard-regions true if you have WorldGuard. It disallows new protections in areas where people cannot build

    No, it's not expected. I'll take a peek.
  9. Offline


    hey thanks for the fast response, I will keep checking this forum for a bit so if there is anything you need to know just ask
  10. Well that wont really work since I want it so LWC cna only be used in protected towna. People need to be able to build outside towns :p
    But thanks for responding :)
  11. Offline


    My findings

    - Each trial has a newly generated world
    - Each trial was timed for 2 minutes -- always running forward
    Trial 1 - no LWC
    Initial memory: 580 M
    After 2 minutes: 798 M
    Trial 2 - LWC loaded
    Initial memory: 585 M
    After 2 minutes: 780 M

    What does this mean? Well, it means that worlds are highly variable ;). LWC alone is not going to consume any more memory if you run for 1 minute vs 10 hours -- it will remain the same if you don't use LWC at all. It will only increase if you begin using LWC, ie chests, commands, where it will fill up its own cache.

    I can start minecraft with -Xmx256m -Xms256m and it will still happily let LWC run and many other plugins (170M usage). LWC by itself is not a memory hog

    Edit: If it still happens to be doing it, what OS are you on?
  12. Offline


    hey thanks for doing this. The server is running centos 5.5

    I am surprised by how high your memory use is without lwc. Maybe you are right and this number doesn't mean as much as I thought, I havn't had any lag yet, although I havn't tested it with more than one person :s
  13. Offline


    How to do:

    Now I know, /lwc admin limits

    Other question.
    I think door lock dont work.
    It lock from move through door or from open by button?
  14. Offline


    thanks for the nice Plugin Hidendra, but i can't get it to work for me :(
    I am using the latest craftbukkit and the some plugins (authorize, permissions, guardian, guardian and general)
    When i start the server i get the following:

    LWC     [v1,47Loading shared objects
    [v1,47Loaded 8 config entries
    [v1,47Creating folder lib
    [v1,47Need to download 2 object(s)
    Updater [v1,47]  - Downloading file
    [v1,47]   + Download complete
    [v1,47]  - Downloading file
    [v1,47]   + Download complete
    -01-30 16:31:25 [INFO] [Permissionsversion [1.9] (Handlerloaded
    -01-30 16:31:25 [INFO] [Authorization1 user registrations loaded
    -01-30 16:31:25 [INFO] [AuthorizationAuthorization plugin build 10 is enab
    [v1,47Loaded command: /lwc -admin
    [v1,47Loaded command: /lwc -create
    [v1,47Loaded command: /lwc -free
    [v1,47Loaded command: /lwc -info
    [v1,47Loaded command: /lwc -p
    [v1,47Loaded command: /lwc -modify
    [v1,47Loaded command: /lwc -unlock
    [v1,47] -> PLAYER_COMMAND
    [v1,47] -> PLAYER_MOVE
    [v1,47] -> PLAYER_QUIT
    [v1,47] -> ENTITY_EXPLODE
    [v1,47] -> BLOCK_INTERACT
    [v1,47] -> BLOCK_DAMAGED
    [v1,47Dev modeFALSE
    [v1,47Using Nijikokun's permissions plugin for permissions
    LWC     [v1,47] Loading SQLite
    java.lang.ClassNotFoundException: org.sqlite.JDBC
            at$ Source)
            at Method)
            at Source)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            at java.lang.Class.forName0(Native Method)
            at java.lang.Class.forName(Unknown Source)
            at com.griefcraft.sql.Database.connect(
            at com.griefcraft.lwc.LWC.load(
            at com.griefcraft.lwc.LWCPlugin.onEnable(
            at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManage
            at org.bukkit.craftbukkit.CraftServer.loadPlugin(
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(
            at net.minecraft.server.MinecraftServer.e(
            at net.minecraft.server.MinecraftServer.c(
            at net.minecraft.server.MinecraftServer.d(
    2011-01-30 16:31:26 [INFO] Done! For help, type "help" or "?"
    what is the problem?
  15. Offline


    Maybe add block protection, so users can protect XX blocks, other users cant build on them or destroy them.

    XX -> Number of Blocks that a Player can Protect.

    if a block is getting destroyed by the owner -> remove the protection.

    Also add a command to remove all protected Blocks.

    That would be awsum...
    --- merged: Jan 30, 2011 4:39 PM ---
    i found a bug, if u protect a door and if the state of the door is open, no user can enter or exit my house, it keeps saying me "This wooden door is locked...".

    so if its possible, remove the protection if the door is open, and re-enable it if the door is closed.
    --- merged: Jan 30, 2011 4:40 PM ---
    You can also destroy the Block of the door, fix that also please. :)
  16. Offline


    I have new Bukkit, new LWC and now i can't create a chest-log ...
    Plugin is Loadet, config. Chests are Locket, but new Chest's I can't lock..
    When I write . /cprivate MiniKahn
    when i LEFT_KLICK on this Chest nothing happens...
  17. Offline


    Is there a .lib file and sqlite.jar in the lib folder in your minecraft folder?

    I do not plan to expand LWC to block protection.

    It isn't a bug at the moment.

    If you want to remove every single protection, there already is a way. /lwc -a clear protections

    At the moment until the right events are implemented, doors prevent people without access from walking through.

    Heh, on an existing world it's only 350-400M on start. That would be probably where your errors came in, if you tried LWC first on a fresh map, did you then clear the map? ;)
  18. Offline


    yes, there is the sqlite.jar is 1125kb and the win-x86.lib 376kb
    i also deleted them serveral times and let them redownload, but it never worked for me :(

    the lwc.db also exists in the /plugins/LWC/ folder and is the one you provided somewhere in this thread.
  19. Offline


    Try redownloading LWC.jar
  20. Offline


    did aliases stop working?
    /lwc itself works as expected but /cprivate does not..
  21. Offline


    the following error persists
    LWC     [v1,47] Loaded command: /lwc -admin
    LWC     [v1,47] Loaded command: /lwc -create
    LWC     [v1,47] Loaded command: /lwc -free
    LWC     [v1,47] Loaded command: /lwc -info
    LWC     [v1,47] Loaded command: /lwc -p
    LWC     [v1,47] Loaded command: /lwc -modify
    LWC     [v1,47] Loaded command: /lwc -unlock
    LWC     [v1,47] -> PLAYER_COMMAND
    LWC     [v1,47] -> PLAYER_MOVE
    LWC     [v1,47] -> PLAYER_QUIT
    LWC     [v1,47] -> ENTITY_EXPLODE
    LWC     [v1,47] -> BLOCK_INTERACT
    LWC     [v1,47] -> BLOCK_DAMAGED
    LWC     [v1,47] Dev mode: FALSE
    LWC     [v1,47] Using Nijikokun's permissions plugin for permissions
    LWC     [v1,47] Loading SQLite
    java.lang.ClassNotFoundException: org.sqlite.JDBC
            at$ Source)
            at Method)
            at Source)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            at java.lang.Class.forName0(Native Method)
            at java.lang.Class.forName(Unknown Source)
            at com.griefcraft.sql.Database.connect(
            at com.griefcraft.lwc.LWC.load(
            at com.griefcraft.lwc.LWCPlugin.onEnable(
            at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManage
            at org.bukkit.craftbukkit.CraftServer.loadPlugin(
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(
            at net.minecraft.server.MinecraftServer.e(
            at net.minecraft.server.MinecraftServer.c(
            at net.minecraft.server.MinecraftServer.d(
  22. Offline


    Is a plugin interfering? Does /cprivate work in-game but just says unknown console command in console? (it will)

    Sounds like your sqlite.jar is too small. Use this one
    <Edit by Moderator: Redacted mediafire url>
    Last edited by a moderator: Dec 15, 2016
  23. Offline


    Last edited by a moderator: Dec 15, 2016
  24. Offline


    Hello i had a question, i was wondering if LWC "Frees up memory" when someone logs out ive been getting this in my terminal (Debian 64bit) and its causing extraaaaaa lag on log out for the whole server when 1 player logs out or relogs because it sits there and processes how much memory to free up.

    2011-01-30 13:57:01 [INFO] xxxxx lost connection: disconnect.quitting
    2011-01-30 13:57:08 [INFO] Freed 2497.466766357422 MB.
  25. Offline


    hm maybe i should have explained what i did better. I basically made a fresh map, then restarted my server like 10 times, going through the plugin arrangements twice. On each load, I would just check the memory used, and it would go like this.

    [memory use on load -> memory use after running for a bit]

    1.) no plugins - 350 -> 660
    2.) all plugins - 550 -> 800
    3.) all plugins but lwc - 350 -> 660
    4.) just lwc - 550 -> 800
    5.) no plugins - 350 -> 660

    These aren't the exact numbers, but they're actually really close. I wrote them down last night but then didn't save it.

    I actually don't know that "memory use" matters. I am using McMyAdmin, and I am just looking at the memory use on the control panel, trying to get things setup before I consider invited people in to test or play here. (And the server hasn't lagged with just me on it.)
  26. Offline


    lwc info command does not work on my server.
    Bukkit build: 179
    OS: CentOS 5.5

    Does not work AT ALL with 181 build.
  27. Offline


    /lwc works but says unknown in console #179

    /cprivate (v1,47) collides with Calander v1.01.

    Show Spoiler

    2011-01-30 22:46:06 [INFO] Anoniempje issued server command: lwc
    2011-01-30 22:46:06 [INFO] Unknown console command. Type "help" for help.
    30-jan-2011 22:46:21 org.bukkit.plugin.SimplePluginManager callEvent
    SEVERE: Could not pass event PLAYER_COMMAND to Calendar
    java.lang.ArrayIndexOutOfBoundsException: 1
    at com.bukkit.Multimac.Calendar.CalendarPlayerListener.onPlayerCommand(C
    at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav
    at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j
    at net.minecraft.server.NetServerHandler.c(
    at net.minecraft.server.NetServerHandler.a(
    at net.minecraft.server.Packet3Chat.a(SourceFile:24)
    at net.minecraft.server.NetworkManager.a(SourceFile:232)
    at net.minecraft.server.NetServerHandler.a(
    at net.minecraft.server.NetworkListenThread.a(SourceFile:104)
    at net.minecraft.server.MinecraftServer.h(
    2011-01-30 22:46:21 [WARNING] Can't keep up! Did the system time change, or is t
    he server overloaded?
  28. Offline


    How do we remove "locks" from doors and signs?
  29. Offline


    change them to public with /cpublic

    also i cant seem to walk through doors after i updated to #182
  30. Offline


    Were they protected?

    The same way as any other ;). /lwc -r protection. Unless that didn't work?

    It's not LWC, it is a different plugin :p

    err.. well since that made me curious, it is the Essentials plugin.

    I can't help you if you don't help me. If you're using the Permissions plugin, I am going to wager a guess that you don't have it setup correctly (if that is the case, players that are allowed to protect stuff need lwc.protect)

    I can replicate it on arch linux. I will look into it. I may look into converting the nested db driver over to the native one, which is supposedly 20x faster, and should use less memory as well
  31. Hello,

    I have given this the god ole' college try to figure this out on my own, but I am at a loss. The plugin is working perfectly (v1.46) on CraftBukkit v137 with one exception. I cannot get the admin functions to work. I have gone through this thread and checked my settings and can't seem to find the issue. I have Permissions setup as well as I am listed in ops.txt. Neither myself (Admin) or my mods can access these functions. A pastebin of my config is below. Any thoughts?

Share This Page