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

    Hidendra

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


    DevBukkit
    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.

    Features
    • 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.

    Translations

    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:
    https://raw.github.com/Hidendra/LWC/master/src/lang/lwc_en.properties

    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)

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

    9/22/2011
    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

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

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

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

    9/16/2011
    LWC 3.49
    • FIX: Double console output

    9/15/2011
    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

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

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

    9/10/2011
    LWC 3.45
    • FIX: plugins/LWC/locale/lwc.properties (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.

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

    9/3/2011
    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

    8/28/2011
    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.

    8/26/2011
    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

    8/25/2011
    3.41
    • 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.

    8/25/2011
    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

    3.31
    • 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

    3.30
    • 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

    7/5/11
    3.21
    • Fix "fetch size" error
    • Removed the auto-removal of the very old players table

    7/4/11
    3.20

    • 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.

    Credits
    • 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.

    Translations
    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: http://leaky.bukkit.org/issues/656
    • @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:
      Code:
          bukkitBug656workaround: true
      

    Behaviour
    • 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 (ci.griefcraft.com) in version strings (e.g /lwc admin version or /lwc admin report).

    6/16/11
    3.11
    • Translation: Swedish! Thank you @christley!
    • Bug fix for block placement

    6/16/11
    3.10
    • 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
      Code:
              trap_door:
                  enabled: true
                  autoRegister: off
      

    6/11/11
    3.06
    • 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

    6/08/11
    3.05
    • Notices will be shown correctly to admins when showMyNotices is disabled.

    6/08/11
    3.04
    • 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

    6/07/11
    3.03
    • MySQL prefix is now working as it should
    • Minor fix with the cache update in 3.02

    6/07/11
    3.02
    • Cache null protections as well, to prevent massive redstone spam

    6/07/11
    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.

    Translations
    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

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

    Limits
    • 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!):
    Code:
            note_block:
                enabled: true
                ignoreLeftClick: true
    

    API
    • [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), lwc.info (/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.redstone / 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

    iConomy
    • 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.)

    Performance
    • 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.)

    Other
    • 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

    Cheers

    4/18/11
    2.31
    • Security bugfix regarding an issue in minecraft itself (thanks sycot)

    4/09/11
    2.30
    • Native German translation! If you wish to use LWC in German, please change "locale" in lwc.properties 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.

    4/06/11
    2.21
    • Minor bug fixes

    4/06/11
    2.20
    • 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

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


    enjoy, gents
     
  2. Offline

    KiloWhiskey

    Build 493 is now the recommended CB build version. Please kick out an update to let us now it's fully functioning.
     
  3. Offline

    Hidendra

    I tried it yesterday with another guy -- 1.57 is working just fine on 493.

    Try redownloading LWC. Do you have the latest permissions (2.5.1)?

    Also, are you using Permissions, but still have FakePermissions.jar in your plugins directory? That would be a problem if so!

    lwc.blockinventory blocks access to any inventory whether protected by LWC or not.

    Perhaps try redownloading LWC -- you may have an old version of 1.57 where Permissions didn't work as expected.


    P.s to everyone, sorry I can't give more specific answers to you guys with problems with Permissions -- everything I've tried is working just fine on build #493 of craftbukkit and even others, so it's hard for me to help with that said ;)
     
  4. Offline

    Rilly

    so, it requires the permissions plugin? I haven't installed any permissions plugins

    (I am using MyMcAdmin if that matters)

    and I'm new to the use of Bukkit.... trying to move over from hMod

    edit: And I just downloaded it today.. so I have the latest version
     
  5. Offline

    GameFAQsRolo

    I updated my server today and am running into the following error when someone uses anything that LWC can protect. The error appears in the console regardless of the item being protected or not. I don't know whether this is something that needs to be updated on LWC or if there's a problem with the latest update of GM?

    CB #493
    GroupManager 1.0 a3
    LWC 1.57
    Code:
    20:59:38 [SEVERE] Could not pass event BLOCK_INTERACT to LWC
    java.lang.NoSuchMethodError: org.anjocaido.groupmanager.GroupManager.getPermissi
    onHandler()Lcom/nijiko/permissions/PermissionHandler;
            at com.griefcraft.listeners.LWCBlockListener.onBlockInteract(LWCBlockLis
    tener.java:100)
            at org.bukkit.plugin.java.JavaPluginLoader$23.execute(JavaPluginLoader.j
    ava:237)
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav
    a:59)
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j
    ava:225)
            at net.minecraft.server.BlockFurnace.a(BlockFurnace.java:75)
            at net.minecraft.server.ItemInWorldManager.a(ItemInWorldManager.java:160
    )
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:482)
            at net.minecraft.server.Packet15Place.a(SourceFile:57)
            at net.minecraft.server.NetworkManager.a(SourceFile:230)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:75)
            at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
            at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:357)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:272)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    --- merged: Mar 4, 2011 5:23 AM ---
    Well, nvm. I re-downloaded 1.57 and saw it was new version of 1.57. Updating existing versions and keeping the same version number is really confusing. :confused: Is it possible to use a supplemental version identifier for small updates? Maybe 1.5.7.1 or 1.5.7a or something?
     
  6. Offline

    D-Kalck

    Same thing here I had the same problem with the 1.57, redowload (thanx to you), I now it works, so I agree that small update should change the version number.
     
  7. Offline

    Rilly

    I had downloaded the LWC 1.57 just last night from this thread for the first time, and I do not have the permissions plugin installed (is it required?). Anything else to look at?
     
  8. Offline

    Prime

    OS: Windows XP SP3 (Windows 7)
    Architecture: x64
    Bukkit Build: 458
    Plugins:
    • AppleTree
    • Deathchest
    • DeathTPPlus
    • Essentials
    • HeroSneak
    • iChat
    • Jail
    • LWC (The plugin that is causing the error, see log below.)
    • MagicCarpet
    • MobileAdmin
    • Mob Rider
    • MyHome
    • Permissions (2.5.2)
    • Stargate
    • WarnFreeze
    • Whitelist
    • WorldEdit
    • WorldGuard

    Issue: I'm having a problem when loading the server. I do and do not understand exactly what the problem is. This is not halting use of LWC, I'm just that kind of person that hates to see errors anywhere even if it works correctly. Sorry if this post is lacking any information beside the following:

    Log:
    Code:
    2011-03-04 15:54:02 [INFO] LWC  [v1.57] Native library: lib/native/Windows/x86/s
    qlitejdbc.dll
    2011-03-04 15:54:02 [SEVERE] Could not load plugins\mysql-connector.jar in plugi
    ns: null
    org.bukkit.plugin.InvalidPluginException
            at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.j
    ava:56)
            at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.
    java:129)
            at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager
    .java:94)
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:58)
            at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:187)
            at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:174)
            at net.minecraft.server.MinecraftServer.d(MinecraftServer.java:120)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:227)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    Caused by: java.io.FileNotFoundException: Jar does not contain plugin.yml
            ... 9 more
    2011-03-04 15:54:02 [WARNING] Using the stupidly long constructor com.nijikokun.
    bukkit.Permissions.Permissions(PluginLoader, Server, PluginDescriptionFile, File
    , File, ClassLoader) is no longer recommended. Go nag the plugin author of Permi
    ssions to remove it! (Nothing is broken, we just like to keep code clean.)
    Thanks in advance!
     
  9. Offline

    flatd

    If your having problems download IZarc and convert the .zip to .jar
     
  10. Offline

    Techcuron

    Make a new version. My other mods need the newest version of craftbukkit, and your LWC can't run on the newest craftbukkit.
     
  11. Offline

    sumTard

    Anyone else having issues with chests being detected as "air" by lwc in certain areas of the map? It wont let us lock chests in this area, and it just happens to be in the middle of a city :/

    No console errors, nothing. CB 478, and using the latest 1.57
     
  12. Actually that's not a good idea. Plugins should ideally be built against the newest "reccommended" build of Bukkit, which could be up to 2 weeks old. It's 493 at the moment, and was 440 before that. This means that people can always have a more or less "stable" build.
     
  13. Offline

    Xphome

    I had a problem with Permissions 2.5.2, try 2.5.1
     
  14. Offline

    XeoVegaS

    Hello, firstly, you have done a very good job ! I have a little problem with LWC 1.57, I have the latest craftbukkit version, I have writen this in permissions config :
    - 'lwc.admin' for the admins but they can't open chest and doors of others players.
     
  15. Offline

    qwrrty

    We have been using LWC 1.491 successfully with Bukkit #440, but when I updated Bukkit to #493, it threw a NoSuchMethodException when trying to load LWC. Here's the stack trace:

    Code:
    2011-03-05 09:19:08 [SEVERE] Could not load plugins/LWC.jar in plugins: null
    org.bukkit.plugin.InvalidPluginException
            at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:80)
            at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:129)
            at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:94)
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:59)
            at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:204)
            at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:191)
            at net.minecraft.server.MinecraftServer.d(MinecraftServer.java:131)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:246)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    Caused by: java.lang.NoSuchMethodException: com.griefcraft.lwc.LWCPlugin.<init>()
            at java.lang.Class.getConstructor0(Class.java:2706)
            at java.lang.Class.getConstructor(Class.java:1657)
            at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:75)
            ... 8 more
    
    I upgraded LWC to 1.57, but Bukkit #493 throws the same exception. The only other plugins we are running are RegexFilter and Teleport, which seem unaffected. I thought the problem must be the changes Seph warned about in this post, but if other people are running LWC successfully with build 493 then that seems unlikely.

    Has anyone else seen this kind of failure with LWC?
    --- merged: Mar 5, 2011 4:56 PM ---
    Update: after downloading build #493 again and running it with LWC v1.57, it seems to work fine. I don't know what I did wrong the first time around.
     
  16. Offline

    nukeade

    Thanks, that fixed it! Seems to be working just fine on CB#493 with the setup I described earlier.
     
  17. Offline

    HawnSolo

    Has LWC been updated and built against 493 yet? If not, may we please have new version that works properly with it?
     
  18. Offline

    _Oni_

    LWC 1.57 works with CD #493. What the problem with this?
     
  19. Offline

    Dev

    So I have a very humble request. Would you please add the ability to edit the message it spits out to users when they try to open something that is locked?

    Right now it says something about a magic spell protecting it, which I think is inappropriate for anything other than an rpg type server.

    At the very least, make it say something more generic, such as "this door is locked."
     
  20. Offline

    flatd

    i don't know whats wrong with yours but mines the newest version and I get No errors
     
  21. Offline

    trivials

    Same here. It comes you cannot protect air :(
    I need help. Much players have the problem.
     
  22. Offline

    Lokykun

    Same here with no console errors.
     
  23. Offline

    maxsteele

    Is it possible to remove all chest protections from a single user?

    I'm running into what I believe is a bug. We have a protection limit of 10 in place.

    I'm having a player say that they destroyed chests they had protected, it said that the protection was removed, but now they're trying to protect a chest and it's telling them they've exceeded their limit for protection.

    I would like to be able to remove all established protections that a single user might have, thus resetting just them and allowing them to re-protect anything up to their limit, but it looks like LWC thinks they have chests / doors / furnaces protected out there when they do not.
     
  24. Offline

    Skate

    can someone help me i am getting "internal error while trying to use that command" when i do /lwc
     
  25. Offline

    Techcuron

    Well I have Craftbukkit build 495
    And it still won't work for me.
     
  26. Offline

    Hidendra

    /lwc -a purge <user>
    example: /lwc -a purge Hidendra

    What is the error in the console?

    LWC is working just fine with CB #493 (I have witnessed it on a live server) and pretty much any latest build. There is something wrong on your end, not mine ;)

    Perhaps you tried /reloading LWC, and not a fresh reboot? however, given that the error you're getting was fixed a couple versions ago, it is weird indeed

    You haven't updated your CraftBukkit -- that is your problem ;)

    What is "the newest version of CraftBukkit"? LWC works just fine on any update I try, including #496 (the latest as of this post).

    The problem you're experiencing cannot be on LWC's end if you downloaded it correctly.

    I was thinking about this just two or three days ago! Actually, it was for language files (to allow translations, there are quite a few german servers), which that would allow just that.
     
  27. Offline

    sumTard

    I think there really needs to be a version change each time anything is updated, even if its just a small bug. I'm using CB478 and did not think I needed to update because the title clearly says 432+, and the version hadn't changed either.
     
  28. Offline

    Hidendra

    Indeed, I'll change it to the recommended build.

    Generally the version in the title is the version I built the initial LWC build against. In 478's case, it was unpredictable that there would be a bug let through that registered all clicks as air (or even that build that gave everyone OP status).
     
  29. Offline

    sumTard

    Thank you :)

    Other than that, working great.
     
  30. Offline

    SimplisticBeing

    No matter.. If given the lwc.protect permission..they can peak inside and remove and add items to admin chests as they please.. Only way to keep out was to block from looking in.. But I wanted to give them protection commands.. All plugins 493 steady.. Will wait for next recommended build unless I missed something..
     
  31. Offline

    Hidendra

    Are you sure you didn't give them lwc.admin or lwc.*? Are they OPs?

    Also, if it's of any use to anyone, I'm keeping a spreadsheet as of a couple days ago for new versions of features that I confirmed are 100% working, and on what CB build. It also serves as a feature list (I don't think I missed anything). At the moment it has 1.57 listed

    https://spreadsheets.google.com/ccc...ktOWDNrOW9FLVlRYl9ablE&hl=en&authkey=CPOXh9UC
     

Share This Page