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

    MrDynamo

    All plugins are creating files fine, other then LWC.
     
  3. Offline

    andune

    Spunkiie, I know Hidendra added the core.precache variable for trimming down the precache amount and that helped. I'm looking at the code and I think I can do some tuning to help it load faster, can you export your LWC tables and make them available somewhere so I can load it up as test data?

    There are 3 options I see:
    1. Direct performance tuning. I think there are some gains to be made here, it's possible we could get 6mil queries down to not much more than the time it takes MySQL to spit them out. I was able to dump my 9million row LB table in 10 seconds and that's 542MB of data. I think it's reasonable we could get LWC precache to perform in that range (10-30 seconds) with some work.
    2. Immediate fix: tune your 'core.precache' to be something really low like 10k. Your server should startup immediately and instead of having all 6mil Protections in memory, they'll be spot-loaded from the DB as needed. This, naturally, will be a little bit slower than having them in memory, but I'm assuming you have a beefy box and MySQL is no slouch when it comes to performance, so I'm willing to bet your server will startup right away and you'll see very little performance hit run-time.
    3. Offload pre-caching to another thread. This would make LWC start up instantaneously while the precache was going on in the background. Any player interactions while the precache was still going on would result in a DB hit, which coupled with the pre-cache going on simultaneously, might mean LWC locks would seem a little bit sluggish when first booting until the pre-cache completes, but that's better than waiting for an 8-20 min to boot where the server isn't available at all. :p
    Ideally I'd like to implement a combination of #1 and #3. But I need some test data to work with. And who knows, @Hidendra might already be hot on the case.
     
  4. Offline

    spunkiie

    @morganm

    Please check your inbox.
     
  5. Offline

    Zalastri

    Still really hoping for a configurable (and optional) last-usage based LWC lock expiration. I have SOO many old protections on my map. :[
     
  6. Offline

    Ratchet

    I'm switching to LWC over from Lockette, but what my players really like about Lockette is that they can put a sign on the chest and use them to label what's inside, would it be too much trouble to add that functionality to LWC? Just making it so you can place signs on chests?

    I would rather not have to install another separate plugin just for this small feature :(
     
  7. Offline

    spunkiie

    @morganm

    Your second tip didn't work in the past (mysql always using 100% CPU). BTW: That's why i've suggested 'all-in-ram' feature to Hidendra.

    FYI: My server is an i7 2600k@4.9Ghz, 16 GiB G.Skill 2.133 RAM, and SSD disk.
     
  8. Offline

    IlyaGulya

    Yep,that's would be really nice!

    Can somebody help me with my problem?
    My players can't /cprivate more. I've updated LWC from 3.06 to 3.11

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

    spunkiie

    HAPPY UPDATE!!!!!

    Tried to set core.cache = 1 and it took several minutes to start the server.. hmm
    So I tried to set it to 0 (zero) and it took 3 seconds to start oO

    I still can't believe.

    Here's the error LWC gives on start with (0 cache):

    2011-06-26 02:23:51 [SEVERE] java.lang.NumberFormatException: For input string: "3.11-dev"

    The funny thing is that even with the start-up error, all protections are working OK (with 120 players online) and the old mysql problem (before pre-caching) using 100% of CPU has GONE.

    Well, obviously Hidendra has changed (tweaked/optimized) something in the test version he gave me. So, yes @Hidendra, you win again, cuz with your test version pre-cache is totally unneeded.

    BTW: Mysql is using VERY little CPU/RAM.. The server is running very, very smooth.

    Let's see tomorrow with 300+ players how mysql will behave.

    As a REQ: Please make possible to completety disable caching in core.yml.

    Thank you again @Hidendra and @morganm

    :)
     
  10. Offline

    andune

    Glad to hear it. The error can be ignored, it has to do with LWC trying to set it's numerical version (which is choking on the "-dev" part), which it uses to look for an update if auto updating is turned on. Shouldn't be a problem with production versions, though it should probably be cleaned up anyway.

    I'm glad setting pre-cache to 0 worked well. I don't know what Hidendra has changed since you last tried, but current LWC code will hit the DB once and then cache that Protection for all future queries. With the server spec you listed, I'm sure MySql has it's entire DB sitting in memory so you're probably getting some great performance assuming indexes and queries in LWC are all setup right (and from your experience, it sounds like they are).

    I may still play with the pre-cache tuning but it seems like you're out of the woods for now. :)
     
  11. Offline

    NeatMonster

    Solved.
     
  12. Offline

    Thomas Carlsen

    having some problems whit droptransfer. it only works for me and not my users so i guess its a permissions error?
    my users have lwc.protect and i cant find anything on the wiki about a speciel mode (droptransfer) permission but is there that? or why does users keep getting that the mode is disabled?

    modes:
    droptransfer:
    enabled: true
    persist:
    enabled: true
     
  13. Offline

    m0dulus

    Is there a way I can set so that people can only have ONE protected chest?
     
  14. Offline

    Getris

    I am currently using Permissions 3.1.5, and have just recently attempted to install LWC 3.11.
    Everything appears fine until I restart the server. LWC starts up and runs fine, however permissions then does not.
    E.g. I attempt to run /pr -reload but it is read as an unknown command.

    On server startup, LWC loads before Permissions Plugin, and sends back; "Using Permission API".
    Is this having some effect?

    Thanks in advance, G.
     
  15. Offline

    Thomas Carlsen

    had this problem whit another plugin my fix was renaming Permissions to aPermissions. that way Permissions loads before the other plugins
     
  16. Offline

    Getris

    That worked flawlessly, many thanks! :D
     
  17. Offline

    chrcms

  18. Offline

    Einschtein

    Meh. When I want to change from sqlite to MySql, fill in all the things required in the core file, save the file, use /reload in the server: it gives me an error that something bad happened when trying to convert the files.

    Halp?
     
  19. Offline

    sp1nn3y

    Currently having a problem with a random chest here and there, it seems to choose at random.. when someone clicks on the chest in any way, they crash.

    on click my console shows this
    Code:
    26.06 13:03:08 [Disconnect] User Sp1nn3y has disconnected, reason: unknown
    26.06 13:03:07 [Disconnect] User Sp1nn3y has disconnected, reason: disconnect.endOfStream
    26.06 13:03:07 [Server] INFO Connection reset
    26.06 13:03:05 [Disconnect] User Wildpawz has disconnected, reason: disconnect.endOfStream
    26.06 13:03:05 [Server] INFO Connection reset
     
  20. Offline

    maciek1o3s

    Hey, where and how can i change permissions?
     
  21. Offline

    spunkiie

    More Update:

    LWC 3.11 (dev test Hidendra)
    Players online: 320

    core.yml:
    flushInterval: 0
    precache: 0

    Rights table: Not deleted (was deleting before due to dealy starting the server)
    Start up time: 3 seconds
    Mysql: CPU: 2% / RAM: 3%
    Server runs faster than before.

    LWC ADMIN REPORT:

    :
    : + Version: 3.11-dev
    : + Engine: MySQL
    : + Date: Sun Jun 26 15:40:58 BRT 2011
    : + Time: 4020 seconds
    : + Players: 286
    : + Protections: 6723342
    : + Cache: 10000/10000
    :
    : - Physical database
    : + Queries: 157936
    : + Average: 39.27779159413081 /second
    :
    : - Memory database
    : + Queries: 268334
    : + Average: 66.73315095747327 /second


    What can I say ?

    Fuck Yeah!

    BTW: Ah, Didn't tried yet 'lwc admin cleanup'
     
  22. Offline

    Blackswordsman

    I have one player that LWC blocks access to chests and furnaces. I know it is LWC because the server does not block this player when I take LWC out of the server plugins. It tells her that the Server Admin is blocking you from opening that. I deleted all of LWC and remade everything from fresh files. Still the same thing. I know my permissions are not messed up because she is in the same group as every other normal member. I am using bukkit 860 and the Permissions and LWC from for that version.
     
  23. Offline

    MrDynamo

    Can anyone help with my problem?

    Every time I try to use any LWC commands I get 'An internal error occurred while attempting to perform this command'. I am using the latest LWC, Permissions, and Bukkit Build 860. Any help?
     
  24. Offline

    soloman981

    Polish language in lwc is total FAIL
    delete that or ask polish guy to do this
     
  25. Offline

    dslip

    Is it just me (possible) or has the commands to set limits on groups changed? I tried to check limits with command /lwc -a getlimits g:group not longer work, they just write '/lwc' to chat window.
     
  26. Offline

    emcitement

    Great plugin.

    Though, is it true that when enough chests are placed and registered on the server that they'll lag a bit?
    (Because Lockette doesn't ever.)
    On a server I used to play on, there was a slight delay upon opening chests but I figured that was normal for SMP but I'm wondering if it's from this plugin.

    Either way, I don't mind. The delay wasn't anywhere near enough to harm the gameplay at all so I'll still be using this.
     
  27. Offline

    MrOttuh

    I have a question: When i type /lwc flag magnet on it tells me to left click on whatever i want to set the flag to (in my case im trying to do it on a chest so it'll pick up items within a 10 radius) like it should. But when I click on a chest nothing happens. If i do it to a door it'll set the flag for the door (kinda weird too). Any ideas why it won't set the flag?
    p.s. yes i am an admin and i have lwc set to recognize OP as lwc admin
     
  28. Offline

    ProjectInfinity

    Is it normal that not even an OP is allowed to /cremove with LWC 3.11 on RB935? It says "punch your protection to remove the lock", and when I do nothing happens. Nor can I cmodify it to public. There is absolutely no output in the console either so I have nothing to go by.
    Edit: people cant lock them either.

    edit2: Changed everything back to SQLite again, works fine now but I want MySQL to work properly so bad.
     
  29. Offline

    Black_Jack

    When I'm have locked up y sign and then somebody tries to destroy sign, sign wont just removes. It just clearing the text. Sign still on the place, but text just fly out. Bug?
     
  30. Offline

    flozza83

    I have some ploblems with CB928
    I cant remove a protection on a chest. It said protection successfully removed, but owned by me again after. And if i brake the chest, and another person put a chest, the protection is again to me... not so good...
    lwc.admin permission on
     
  31. Offline

    dakzerox

    Lock door have bug
    other player can use swith leaver button or plate open my door
     

Share This Page