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

    Hidendra

    When you protect a chest, even though it only protects one side, LWC will protect both sides of a double chest. Meaning if you remove one side as the owner, it will remove the protection. I guess I imagine this is probably unexpected but at the moment that is how it works -- in a later version I'll probably fix it so it only unregisters when both blocks are removed

    http://griefcraft.com/bukkit/lwc/development/LWC.jar

    That one will work with Permissions .. but not groupmanager as of yet ('til it's updated I can't push that to release, else I get even more people asking why it doesn't work)

    If you use Permissions 2.4, you can configure permissions per-world ;)

    Permissions 2.4 is supported in the dev build
    http://griefcraft.com/bukkit/lwc/development/LWC.jar

    as TJ8 said, you are not using 1.57

    Edit: I really shouldn't post while sleeping. The update that fixes permissions will be in the release channel later on.
     
  3. Offline

    Vaupell

    +1, same and using recomended build by bukkit team 440

    Except mine is not related to anjo permissions, dont have it installed..
    Code:
    2011-02-28 11:08:10 [SEVERE] Could not pass event BLOCK_DAMAGED to LWC
    java.lang.NullPointerException
     at com.griefcraft.sql.PhysDB.registerProtectedEntity(PhysDB.java:912)
     at com.griefcraft.listeners.LWCBlockListener.blockTouched(LWCBlockListener.java:597)
     at com.griefcraft.listeners.LWCBlockListener.onBlockDamage(LWCBlockListener.java:126)
     at org.bukkit.plugin.java.JavaPluginLoader$23.execute(JavaPluginLoader.java:242)
     at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:59)
     at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:225)
     at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:346)
     at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
     at net.minecraft.server.NetworkManager.a(SourceFile:230)
     at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:70)
     at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
     at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:338)
     at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:253)
     at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    
     
  4. Offline

    M1sT3rM4n

    This one worked fine on the latest CB build with Permissions 2.4. Maybe it's because I am not using GroupManager
     
  5. Offline

    Hidendra

    Yeah, the 1.57 with working permissions 2.4 is up now (I posted not too long after waking up, so wasn't thinking :D) (instead of just that link you used)

    Have you tried http://ci.bukkit.org/job/package-CraftBukkit/?
     
  6. Offline

    matfoy

    I LOVE this plugin, probably the most useful and my favourite one.

    Keep up the good work! :)
     
  7. Offline

    Zeta

    I'm running craftbukkit 432, the latest groupmanagers and latest LWC as of this moment. I have nothing in the groupmanagers permissions for LWC permissions, leaving all commands to only admins.

    I'm still getting the error where protection of chests isn't working. I want private chests, so I set them up properly, and it says they're registered to the given players, but anyone can open and break them.

    I've tested this myself by removing myself from ops.txt and groupmanager and I lose all admin functionality but can still open any chest I want to even when it's supposed to be protected.

    I'm not getting any errors, however, and even more perplexing, password protected chests successfully stop a chest from being broken, but nobody can use the password command (and I don't want password chests anyway).

    Any idea what's going on?
     
  8. Offline

    Hidendra

    Have you tried a more up to date Bukkit build?
     
  9. Offline

    Vaupell

    Yes, well the craftbukkit team encurages people to only use recomended builds. that way all the plugin developers
    can make a working plugin for that build, and dosent have to update their plugins everyday!
    Atleast not until another recomended build is released. that way you get more for less.

    But then some plugin devs go out on their own and release those plugins for "not-recomended builds" and if
    i just get the last build then LWC might work, but 5 others will be broken cause they develop release for
    recomended builds, or both.. :(

    Sorry but im just following the recomendations of the craftbukkit dev team.
    ill guess ill be using another mod until lwc matches up with next reconmended build.
     
  10. Offline

    zingzam

    The jar isnt in the zip D:
     
  11. Offline

    stkeroro

    lwc -a doesn't work on permissions 2.4, inside lwc.jar command doesn't exist
     
  12. Offline

    Zeta

    Not yet, but it did this same thing on an older build, and since LWC's title says it's 432+ it must have been tested against this build and should be working, especially since this was one of the reccomended builds

    I'm pretty sure just updating craftbukkit isn't going to fix the issue given this, as much as I'd like it to
     
  13. Offline

    Plasmius

    Well i have the latest craftbukkit and lwc build no errors but when i lock a chest everyone can open it
    here is config file anything wrong with it?
    groups:
    Def:
    default: true
    info:
    prefix: '&8'
    suffix:
    build: true
    inheritance:
    permissions:
    - 'lwc.protect'

    Moderator:
    default: false
    info:
    prefix: '&2'
    suffix:
    build: true
    inheritance:
    permissions:
    Admins:
    default: false
    info:
    prefix: '&4'
    suffix:
    build: true
    inheritance:
    permissions:
    - '*'
    - 'lwc.admin'
    - 'lwc.blockinventory'
    - 'lwc.protect'


    Owner:
    default: false
    info:
    prefix: '&d'
    suffix:
    build: true
    inheritance:
    permissions:
    - '*'
    - 'lwc.admin'
    - 'lwc.blockinventory'
    - 'lwc.protect'

    ##
    # DarkGrave has control over all commands.
    # sk89q can use /spawn & /time
    ##
    users:
    nate629:
    group: owner
    permissions:
    darthderp:
    group: Admin
    permissions:
    deathbelcher:
    group: Admin
    permissions:
    mjcuevasii:
    group: Def
    permissions:
    Tehmon:
    group: Def
    permissions
     
  14. Offline

    wootalyzer

    Any news on making /reload not completely crash this plugin? It's almost like it doesn't shutdown cleanly, then kills itself when it comes back up.
     
  15. Offline

    Hidendra

    Are you using 1.57?

    are they ops?

    redownload 1.57

    i have just tried build 440 and everything works just fine for me.

    Is it being caused by something specific? i.e only in a specific world? Does plugins/LWC/lwc.db exist? If it doesn't, does db-path in lwc.properties say plugins/LWC/lwc.db? If it refers to another file, does that file exist? If not, perhaps the folder is not writable?
     
  16. Offline

    Plasmius

    only first 3 are rest are not
     
  17. Offline

    strupan

    CB 440
    LWC 1.57
    Permissions 2.4

    I don't have any permissions added for the default group but yet they can still lock chests in game?
     
  18. Offline

    Moo Master

    Code:
    
    2011-03-01 18:44:03 [SEVERE] java.lang.NullPointerException
    2011-03-01 18:44:03 [SEVERE] at com.griefcraft.sql.MemDB.getActions(MemDB.java:108)
    2011-03-01 18:44:03 [SEVERE] at com.griefcraft.listeners.LWCBlockListener.blockTouched(LWCBlockListener.java:291)
    2011-03-01 18:44:03 [SEVERE] at com.griefcraft.listeners.LWCBlockListener.onBlockDamage(LWCBlockListener.java:127)
    2011-03-01 18:44:03 [SEVERE] at org.bukkit.plugin.java.JavaPluginLoader$23.execute(JavaPluginLoader.java:242)
    2011-03-01 18:44:03 [SEVERE] at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:59)
    2011-03-01 18:44:03 [SEVERE] at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:225)
    2011-03-01 18:44:03 [SEVERE] at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:346)
    2011-03-01 18:44:03 [SEVERE] at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
    2011-03-01 18:44:03 [SEVERE] at net.minecraft.server.NetworkManager.a(SourceFile:230)
    2011-03-01 18:44:03 [SEVERE] at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:70)
    2011-03-01 18:44:03 [SEVERE] at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
    2011-03-01 18:44:03 [SEVERE] at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:338)
    2011-03-01 18:44:03 [SEVERE] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:253)
    2011-03-01 18:44:03 [SEVERE] at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    2011-03-01 18:44:04 [SEVERE] java.lang.NullPointerException
    2011-03-01 18:44:04 [SEVERE] at com.griefcraft.sql.MemDB.getActions(MemDB.java:108)
    2011-03-01 18:44:04 [SEVERE] at com.griefcraft.listeners.LWCBlockListener.blockTouched(LWCBlockListener.java:291)
    2011-03-01 18:44:04 [SEVERE] at com.griefcraft.listeners.LWCBlockListener.onBlockDamage(LWCBlockListener.java:127)
    2011-03-01 18:44:04 [SEVERE] at org.bukkit.plugin.java.JavaPluginLoader$23.execute(JavaPluginLoader.java:242)
    2011-03-01 18:44:04 [SEVERE] at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:59)
    2011-03-01 18:44:04 [SEVERE] at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:225)
    2011-03-01 18:44:04 [SEVERE] at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:346)
    2011-03-01 18:44:04 [SEVERE] at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
    2011-03-01 18:44:04 [SEVERE] at net.minecraft.server.NetworkManager.a(SourceFile:230)
    2011-03-01 18:44:04 [SEVERE] at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:70)
    2011-03-01 18:44:04 [SEVERE] at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
    2011-03-01 18:44:04 [SEVERE] at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:338)
    2011-03-01 18:44:04 [SEVERE] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:253)
    2011-03-01 18:44:04 [SEVERE] at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    
    Im getting this in console litteraly about twice a second. and i belive it might be on the fact that i just installed greifalertr reborn and it might be conflicting since it never happened before.

    Craftbukkit build 450.

    Note: Occurs when someone right clicks a chest, workbench, etc.
     
  19. Offline

    wootalyzer

    Yep, the problem isn't very reliable though. If I cause the problem with a /reload, I can typically get it to start behaving again with another /reload or two.
     
  20. Offline

    Hidendra

    If you disable the griefalert plugin, does it stop occurring?

    Ah.

    Redownload 1.57

    ok, are they in the Moderator group now? Moderators have "*". perhaps try redownloading LWC -- maybe you got a bad build or it was fixed in a later 1.57
     
  21. Offline

    wootalyzer

    It looks like it's crashing while closing the database, thus breaking the entire reload process. When you run reload a second time, it doesn't try to shutdown again (the plugin is already unloaded), so it continues to load successfully. Looks like the shutdown code is bugged.

    Edit: Hold that thought. This might be a plugin conflict.
     
  22. Offline

    Moo Master

    When i disable griefalertr it still goes, but as soon i transfered maps it went back to normal. Could it of been a database error?
     
  23. Offline

    msleeper

    I think that limits in relation to Groups may need to be revisited. Maybe I'm missing something, but I had a hell of a time setting up what I would think is a common setup.

    My "Default" group is only allowed 5 protections. My "VIP" group, however, is allowed unlimited protections. In order to make this work properly, I had to add the limit of the VIP group (and any other groups that have limits), and then add the Default group last. My VIP limit is set to -1, which is unlimited right? I'm pretty sure because it works for me.

    Is there any way to fix group limit permissions, so that if in the future I have to add another group with limits, I don't have to re-do the entire list of limits? I'm not sure if the group permission re: limits is not being inherited properly, or if the "Default" group is taking precedence for some reason (ASC vs. DESC sorting?), but it would be awesome if this wasn't so fragile.

    Thanks again for the awesome plugin, Hidendra!
     
  24. Offline

    Hidendra

    It could have been, yes

    Alright

    talking to you on irc
     
  25. Offline

    mutiny

    Build 482 lwc 1.57

    I realize this is not a recommended build however my users were experiencing a bug where certain chests were unlockable, as in not receiving any message upon hitting the chest. Verified this. Using lwc -i it gives message this 'air' block is not protected. No errors on console, unsure of issue.
     
  26. Offline

    undefinedarray

    hello, im have a problem, lwc commands dont work or show up

    i typed /lwc - and no commands showed, i looked in console, and it said unknown command, type help....

    i have LWC enabled and loaded, i have the commands in my permissions and yet i cant figure out the problem

    permissions 2.4 config below:

    http://pastebin.com/BQZECuqx
     
  27. Offline

    DanDaMan

    Thanks for making and maintaining such a great and important plugin for all of us!!! :)
     
  28. Offline

    Hidendra

    I can only assume it's a problem with the build you have :)
    Have you tried the CB package? It is updated much less often, so should be more stable -- http://ci.bukkit.org/job/package-CraftBukkit/

    Redownload LWC.

    ^_^
     
  29. Offline

    undefinedarray

  30. Offline

    silentdojo

    @mutiny I am also experiencing the same isssue. Although the already locked chest are protected. Making new protections do not work for non admin players. Using CB 484.

    @Hidendra I know this is not a Recommended build though it is very stable for all of my other plugins and has helped with the tp/warp bug with loading chunks initially. Everyone on the server loves your plugin and we appreciate the time you spend making this. I'll just rollback to another CB build in the meantime.
     
  31. Offline

    murphmaster01

    Is there any ways you can make it so the creator of a password protected chest isn't required to enter the password when they open the chest?

    Sorry if this has already been addressed I wasn't up to the task of reading 41 pages.
     

Share This Page