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

    mazzaman

    Okay im having a few problems.
    The main one is that my public members are (in permission) not allowed to use lwc, this is a higer group ability.
    New players are set as default for the group with no lwc nodes in groups file.
    The players keep getting an "Access Denied" error output in chat when they try to place blocks down (chests and wood plands etc)
    It seems like an auto lock on new blocks placed by user but i dont know how to disable it.

    (permission node 'lwc.protect' is enabled for the next group up from public and then is inherited from then upto admin)
    Server is working okay had a quick look through the server log and couldnt see anything really related to lwc not working :/



    Version info:
    Permissions 3.1.6 (current release)
    Craftbukkit 953 (1.7.2 current release)
    And your Lwc plugin which is up to date (as in i downloaded it yesterday)

    I have other plugins installed on this server i can output a list just ask.

    Any ideas how to fix this
    (i have also searched and most of the replys for "Access Denied" are Whats you version of permissions. ^^
     
  3. Offline

    Dimochka

  4. Offline

    Hidendra

    No problem :D

    I do not know, it is an interesting problem so I may have to do something else (not the way I wish to, but it would temporarily fix it)

    So your only issue is "Access denied" being sent when the player really doesn't have access to it anyway (when placing a chest etc) ?

    It is fixed in CI build #60 - thank you. http://ci.griefcraft.com/job/LWC/60/artifact/build/LWC.jar
     
    Dimochka likes this.
  5. Offline

    Dimochka

    Is it possible to prevent taking items from chest without making it private?
    Or, even better, to execute command whenever public chest contents is changed by anyone but its owner? It's quite needed for RP.
    I know that BigBrother plugin is capable of tracking chest deltas.
     
  6. Offline

    MutinyMC

    Well the LordOfTheCraft server seems to have it working fine, why dont you contact him on his twitter maybe he can give you the version he got that is fixed up
     
  7. Offline

    monir

     
  8. Offline

    Hidendra

    It half works -- for doors facing East and West it will work fine. north and south doors are reversed.

    I may look into supporting BukkitContrib with "donation" chests. Executing a command whenever contents are changed is an interesting idea.

    Looks ok. are you sure the user/pass is correct? Please take a look at the first errors that are out of view.

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

    monir

    Yes im 100% sure becouse i use mcmmo and logblock to mysql i dont have password and user is root

    [​IMG]
    [​IMG]
     
  10. Offline

    Ratchet

    @Hidendra I enabled the fix to stop chests being wiped but it's still happening, 4 players today had some of their chests entire contents wiped
     
  11. Offline

    Dimochka

    d
    This would be so great if you implemented this allowing macro expansion for player's name and/or position when executing command. Also execute it not just from player who peeked into chest but ephemerous LWC account so that custom permissions for him could be set. This way it will be possible to automatically imprison overly curious players using some jail plugin.

    Signs maybe used to set the commands for execution in-game like CommandSigns plugin does, although it may be time-taking when you want to set up a lot of similar protection on numerous chests like public chests in some RP area.
    Maybe you can allow setting up custom flags through configuration files.

    Like that:
    Code:
    jail:
      enabled: true
      # Flag effect conditions:
      # change -- when player changes chest contents
      # hit -- when player attempts to destroy chest
      # open -- when player opens chest contents
      condition: change
      effects:
        # user who will run the command
        command-user: LWC
        # <Name> is substituted with username of player who interacted with the chest
        command: '/jail <Name>'
    And then you do '/lwc flag jail' on chests you want to protect with this flag.

    etc.
     
  12. Offline

    mazzaman

    Did that, stopped the server and then reload.

    Feedback from the members say that it worked straight away.

    Many thanks for the help and quick reply.
    Good plugin :)
    +Cookie
     
  13. Offline

    Hidendra

    @spunkiie There isn't really a way go get all 10 million protections at once easily to cache them all, but I'll look into making cleanup run in the background so it doesnt affect server performance at all.

    Excellent :D

    try using
    Code:
    password: ''
    
    instead of just password:

    Nice, yes. Currently you can create honeypot LWC protections, but it's a very obscure feature that is not even listed in any current documentation. It allows you to kick someone with a reason, or ban them via mcbans (local ban) for a reason

    It requires lwc.admin to create the current honeypots
    Code:
    /lwc create trap kick Uh oh, why'd you go and do that :3
    /lwc create trap ban Indeed!
    
    Cool idea, though, for creating custom flags.. ;)
     
  14. Offline

    Zalastri

    Wow, mind blown.

    EDIT: I just asked basically asked for honeypots with arbitrary commands too. +1 for that!
     
  15. Offline

    monir

    Code:
    password: ''
    
    Thank you it works gr8 now!
    you really are doing a great job this is easily the most imortant plugin nodoubt about it!
     
  16. Offline

    odielag

    I operate a server that has two very different worlds... one that's pvp/factions/skylands, and one that's pve/protected/world.

    Is there any way to disable lwc on all chests in skylands and/or enable anyone in skylands to delete other's lwc protections? So far I just gave everyone in skylands the lwc.mod node but it doesn't allow them to destroy chests in skylands, and I don't want them to touch other's chests in the normal world.

    I thank anyone for constructive input in response to this.
     
  17. Offline

    Hidendra

    Can you not just remove the lwc.protect node from players for the world skylands? :)

    Awesome, good to know :D

    Aye
     
  18. Offline

    odielag

    I tried that but I still can't destroy a death chest made by another player... it says... "This chest is locked with a magical spell."

    So basically I removed all permission nodes with "lwc" in them from the world's group file in the permissions plugin folder. I also did "pr -reload all" in the console afterwards.

    Are there any other ideas?
     
  19. Offline

    Hampi90

    I updated this plugin to the latest version, after that my server has started to lag when I use sqlite, so I thought I could give it a go and try mysql since that works very well with many other plugins I use.

    It loads succesfully, but then I get this error:
    Show Spoiler
    Code:
    2011-07-07 16:22:17 [SEVERE] com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
    
    The last packet successfully received from the server was 42,416 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago.
    2011-07-07 16:22:17 [SEVERE] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    2011-07-07 16:22:17 [SEVERE] at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    2011-07-07 16:22:17 [SEVERE] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
    2011-07-07 16:22:17 [SEVERE] at java.lang.reflect.Constructor.newInstance(Unknown Source)
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.Util.handleNewInstance(Util.java:407)
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1116)
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3082)
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2968)
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3516)
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1986)
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2140)
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2626)
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2111)
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2273)
    2011-07-07 16:22:17 [SEVERE] at com.griefcraft.sql.MemDB.getActions(MemDB.java:120)
    2011-07-07 16:22:17 [SEVERE] at com.griefcraft.listeners.LWCPlayerListener.onPlayerInteract(LWCPlayerListener.java:122)
    2011-07-07 16:22:17 [SEVERE] at org.bukkit.plugin.java.JavaPluginLoader$10.execute(JavaPluginLoader.java:307)
    2011-07-07 16:22:17 [SEVERE] at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
    2011-07-07 16:22:17 [SEVERE] at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:321)
    2011-07-07 16:22:17 [SEVERE] at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:168)
    2011-07-07 16:22:17 [SEVERE] at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.java:210)
    2011-07-07 16:22:17 [SEVERE] at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:552)
    2011-07-07 16:22:17 [SEVERE] at net.minecraft.server.Packet15Place.a(SourceFile:57)
    2011-07-07 16:22:17 [SEVERE] at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
    2011-07-07 16:22:17 [SEVERE] at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:84)
    2011-07-07 16:22:17 [SEVERE] at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
    2011-07-07 16:22:17 [SEVERE] at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:451)
    2011-07-07 16:22:17 [SEVERE] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:361)
    2011-07-07 16:22:17 [SEVERE] at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
    2011-07-07 16:22:17 [SEVERE] Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost.
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:2529)
    2011-07-07 16:22:17 [SEVERE] at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2979)
    2011-07-07 16:22:17 [SEVERE] ... 22 more


    Here's my config file:
    Show Spoiler
    Code:
    core:
    
        locale: en
        autoUpdate: false
        flushInterval: 10
        cacheSize: 100000
        defaultMenuStyle: basic
        showNotices: true
        showMyNotices: false
        verbose: false
        opIsLWCAdmin: true
    
    database:
        adapter: mysql
        path: plugins/LWC/lwc.db
        host: 0.0.0.0 (I use to have my host ip here but I removed it now)
        database: ulfbagec_lwc
        username: ulfbagec_Hampi90
        password: **********
        prefix:
    
    protections:
        denyRedstone: true
        autoRegister: off
        ignoreBlockDestruction: false
        ignoreLeftClick: false
        ignoreRightClick: false
        blocks:
            chest:
                enabled: true
                autoRegister: off
            furnace:
                enabled: true
                autoRegister: off
            dispenser:
                enabled: true
                autoRegister: off
            sign:
                enabled: true
                autoRegister: off
            wooden_door:
                enabled: true
                autoRegister: off
            iron_door:
                enabled: true
                autoRegister: off
            trap_door:
                enabled: true
                autoRegister: off
    
    modes:
        droptransfer:
            enabled: true
        persist:
            enabled: true
     
  20. Offline

    spunkiie

    @Hidendra

    FYI:

    MySQL Connector/J 5.1.17, a maintenance release of the production 5.1 branch has been released.
    Connector/J is the Type-IV pure-Java JDBC driver for MySQL.

    Version 5.1.17 is suitable for use with any MySQL version including MySQL-5.1 or MySQL-5.5.

    It is now available in source and binary form from the Connector/J download pages at

    http://dev.mysql.com/downloads/connector/j/5.1.html

    and mirror sites as well as Maven-2 repositories.

    As always, we recommend that you check the "CHANGES" file in the download
    archive to be aware of changes in behavior that might affect your application.

    We welcome and appreciate your feedback, bug reports, bug fixes, patches etc.:

    http://forge.mysql.com/wiki/Contributing

    MySQL Connector/J 5.1.17 includes the following general bug fixes and improvements:

    - Fix for Bug#61332 - LIKE not optimized in server when run against I__S tables and no
    wildcards used. Databases/tables with "_" and/or "%" in their names (escaped or not)
    will be handled by this code path, although slower, since it's rare to find these
    characters in table names in SQL. If there's a "_" or "%" in the string, LIKE will
    take care of that, otherwise we now use = . The only exception is information_schema
    database which is handled separately. Patch covers both getTables() and getColumns().

    - Fix for Bug#61150 - First call to stored procedure fails with "No Database Selected".
    The workaround introduced in DatabaseMetaData.getCallStmtParameterTypes to fix the
    bug in server where SHOW CREATE PROCEDURE was not respecting lower-case table names
    is misbehaving when connection is not attached to database and on non-casesensitive OS.

    - Fix for Bug#61105 - Avoid a concurrent bottleneck in Java's character set
    encoding/decoding when converting bytes to/from Strings.
    * IMPORTANT NOTE *
    No longer use String.getBytes(...), or new String(byte[]...), use the StringUtils
    method instead.
     
  21. Offline

    Dimochka

    It's nice but too cruel and not good for RP servers.
    DO WANT arbitary commands with stooffs here.
    Keep up your great work!
     
  22. Offline

    Jonny Dennis

    I can translate the plugin into portugese
     
  23. Offline

    andune

    Odd. I use this on my server and it's quite effective, I've not had a single issue of a chest being emptied/stolen since I put it into place. We should probably add a startup INFO message to indicate that the bug656 workaround is in effect, who knows it could be a simple typo in the config.
     
  24. Offline

    Bashoogers

    yey! Trapdoors :D
    Is it possible to disable the "Notice" of who protect it?
    Notice: That private <ITEM> is locked by <name>
    That must be disable, is that possible? :D
    Only the messages btw
     
  25. Offline

    Dimochka

    see core.yml config
    Code:
        showNotices: true
        showMyNotices: false
     
  26. Offline

    Bashoogers

    YAY!
    TY :)


    I hope that LWC can protect Pistons comming soon, Buttons, Levers and more :))
     
  27. Offline

    shauwk

    hey is there a way to configure lwc so that when someone breaks a protected door, chest or whatever and puts it back.... it wont have protection? because we keep having problems with people building in old places and their items automatically gets locked by whoever protected the item that used to be there. and i have to keep using /cremove. if someone knows how to change this it will be very appreciated ^^
     
  28. Offline

    Zalastri

    The problem is you're removing old protections with something like worldedits super pick, which just replaced the block with air, it doesnt actually trigger the block broken event so LWC cant pick up on it.

    What you CAN do is do /lwc admin cleanup and it will purge non-existant (like that) protections. What a great plugin :D
     
    shauwk likes this.
  29. Offline

    supre

    i'd like my moderators to have the /cremove
    but not have full access to admin
    adding the permissions - 'lwc.admin.remove'

    doesnt work for me?
    is it different to how i've put it
     
  30. Offline

    skeletonofchaos

    on every start up of my server i get
    21:26:17 [SEVERE] java.sql.SQLException: fetch size -2147483648 out of bounds 0
    21:26:17 [SEVERE] at org.sqlite.RS.setFetchSize(RS.java:167)
    21:26:17 [SEVERE] at org.sqlite.Stmt.setFetchSize(Stmt.java:295)
    21:26:17 [SEVERE] at com.griefcraft.sql.PhysDB.precache(Unknown Source)
    21:26:17 [SEVERE] at com.griefcraft.lwc.LWC.load(Unknown Source)
    21:26:17 [SEVERE] at com.griefcraft.lwc.LWCPlugin.onEnable(Unknown Source)
    21:26:17 [SEVERE] at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:126)
    21:26:17 [SEVERE] at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:857)
    21:26:17 [SEVERE] at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:264)
    21:26:17 [SEVERE] at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:151)
    21:26:17 [SEVERE] at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:136)
    21:26:17 [SEVERE] at org.bukkit.craftbukkit.CraftServer.reload(CraftServer.java:358)
    21:26:17 [SEVERE] at org.bukkit.command.SimpleCommandMap$ReloadCommand.execute(SimpleCommandMap.java:281)
    21:26:17 [SEVERE] at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:129)
    21:26:17 [SEVERE] at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:290)
    21:26:17 [SEVERE] at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:480)
    21:26:17 [SEVERE] at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:465)
    21:26:17 [SEVERE] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:361)
    21:26:17 [SEVERE] at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
    Lwc works fine even with this error any ideas?
     
  31. Offline

    shauwk

    ohhh thanks u SO much i didnt know that!!! LIKE :D
     

Share This Page