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

    andune

    I've seen various people complaining about issues in the 818+ series and LWC 3.00-rc1, which had kept me away from trying it. However, since I did finally try it I wanted to add my (positive) experience here so others know it DOES work.

    I was using v2.31 on 818+ (updated 819, then 820, now 823) and it was inconsistent. Sometimes the locks wouldn't be there at all, sometimes they would, sometimes players could create new locks, sometimes they couldn't. Since I run a chest/sign shop, I had to close the shop b/c I couldn't trust that the market chests would be locked to prevent people from just taking what they wanted.

    I was using SQLLite, but wanted to move it into MySQL (already have a DB I use for LogBlock, and MySQL will be faster and more efficient than SQLLite anyway). People were reporting issues w/ 3.0 and MySQL, so to be safe, I performed the upgrade on v2.31 by changing the config to MySQL and letting 2.31 convert the DB. That part worked flawlessly.

    After letting that run for a day to make sure it was stable with MySQL, I then dropped in the 3.00-rc1 update and restarted. That was a few days ago and things have been working fine ever since - no more random LWC failures like I was having on 2.31.

    So, in summary, Bukkit #823, LWC 3.00-rc1 and MySQL: works great!

    Looking forward to the 3.00 Wiki updates so I can take advantage of some of the new features.
     
  3. Offline

    spunkiie

    Hey, how do I enable: /lwc mode persist on 3.0 RC1 ? There's no 'permission' option for this command, and when my normal players tries to use it, LWC says its 'disabled'.

    BTW: Have more than 30k protected blocks running just FINE with LWC. I love this plugin :)
     
  4. Offline

    Vhab

    I'm preparing our server to upgrade to Permissions 3.
    Is this plugin compatible with the new Permissions version?
    (there are some changes in the API regarding groups that can cause issues on plugins assuming 2.7)
     
  5. Offline

    spunkiie

    REQ: Well, now that we are protecting way more things than chests/doors, it become impossible to use /lwc admin find to identify users chests :(

    Please make a switch or a new command to return ONLY chests/doors if possible.

    Thank you Hidendra.
     
  6. Offline

    flozza83

    Hi

    For me, running on CB818 with permissions 3.1.2, the 3.00 RC1 working. But when there is a lot of players, some protected chests loose their protection, and cant recreate one on it. Only after server restarted, the protection re-appear.... Is this because im using sqlite for database ?
    if yes, can you explain me how to transfer my sqlite db in mysql ? there are explications only for the 2.x version, please ?

    The translation in french locale is nice! I pointing the underline on some yaml restrictions bypassing with that plugin.. Très appréciable ! ;)

    thanks you
     
  7. Offline

    Vhab

    Agreed. I'd love to see an option to restrict the blocks that can be protected with this plugin.
     
  8. Offline

    woodzy

    @ Hidendra
    there seems to be a tad of lag when locking chests useing the AUTO lock in 3.00 (laged out today just 2 players) i was alost placeing like 10 large chests

    but not i cant get it to not auto lock :eek:
     
  9. Offline

    cartman-2000

    3.00 for me spams the DB server with queries when I use it.

    13:17:18 [INFO]
    13:17:18 [INFO] + Engine: MySQL
    13:17:18 [INFO] + Date: Mon Jun 06 13:17:18 PDT 2011
    13:17:18 [INFO] + Time: 57656 seconds
    13:17:18 [INFO] + Players: 1
    13:17:18 [INFO] + Protections: 885
    13:17:18 [INFO] + Cache: 83/10000
    13:17:18 [INFO]
    13:17:18 [INFO] - Physical database
    13:17:18 [INFO] + Queries: 828218
    13:17:18 [INFO] + Average: 14.364818926044125 /second
    13:17:18 [INFO]
    13:17:18 [INFO] - Memory database
    13:17:18 [INFO] + Queries: 24001
    13:17:18 [INFO] + Average: 0.41627931178021366 /second
    13:17:18 [INFO]


    I don't see anything on my maps that could generate that many queries, one thing that could is if someone made a redstone powered set of doors with a rapid pulser, that could spam the DB with atleast 5-10k queries per minute, enough to lag the server.
     
  10. Offline

    spunkiie

    : + Engine: MySQL
    : + Date: Mon Jun 06 18:40:53 BRT 2011
    : + Time: 3532 seconds
    : + Players: 292
    : + Protections: 252493
    : + Cache: 10000/10000
    :
    : - Physical database
    : + Queries: 764719
    : + Average: 216.5116081540204 /second
    :
    : - Memory database
    : + Queries: 453610
    : + Average: 128.4286523216308 /second


    Is this speed good ?

    3.0

    I have lots of RAM and lots of users aswell. What's the best 'cache' configuration for this scenario ?

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

    Rick

    Will this be updated to 818? or is it abandoned?
     
  12. Offline

    Hidendra

    Check out core.yml -- under the protections header you can very easily disable protectable objects :)

    The wiki will be updated to include all of these obscure features.

    3.00-rc1 is working fine for me on 818 builds, I have no plans to abandon LWC.

    The default is fine and should work in all scenarios -- the cache uses a very trivial amount of RAM (especially when you consider the speed increase it can give you, especially on SQLite.)

    Haha, nice. That isn't necessarily the speed, but that sure is a lot of protections and players!

    Yeah, I did think of that when doing the redstone (spamming the DB), but if LWC is protecting this and you don't want redstone using it, it's sadly needed. If it were to become a problem, I'm sure there would be ways around it (filters on LWC's end), or if you don't really even protect doors at all, you could disable them (to be protectable.)

    Oops, looked like it disappeared from core.yml. Add this to your core.yml:

    Code:
    modes:
        droptransfer:
            enabled: true
        persist:
            enabled: true
    
    Sounds like you have another permissions plugin -- e.g groupmanager or essentials group manager.

    Thank you :)

    I believe I'm starting the wiki updates/changes tonight, and then hopefully finishing them tomorrow (depending on how much work my teachers decide to pile unto me.)
     
  13. Offline

    spunkiie

    3.0

    Hidendra: Is there a way to enable normal users to see that his blocks are protected (just like when an admin right click a block and it shows: Notice: that private block is locked by ...) ?

    TIA
     
  14. Offline

    DivineKyuuji

    So I made a shop, destroyed the shop, and when my friend places chests there it says that its still under my protection, how do i get my protection off of that spot?
     
  15. Offline

    Runelynx

    Any tips of what might be going wrong if LWC worked fine before now... but now on 818 + 3.00rc1 it creates a 5-second lag on the server? I really like LWC but if it's working fine for everyone else (though I still dont see replies to the posts saying its making thousands of unnecessary DB queries...) I guess I need to move to another plugin :(
     
  16. Offline

    hutchpe

    No I was testing on a new server with no other plugins running except LWC.
     
  17. Offline

    PhotonLance

    works on trapdoors???
     
  18. Offline

    Freakdk

    Hello.

    I've tried installing LWC, and it's working "fine". I'm getting no error logs, or anything.
    I did have a few errores to start with, but I browsed through the thread and found a lot of your comments usefull @Hidendra (thanks!), so I was able to fix those.

    Anyways there's only one thing left.
    All the commands are "working"
    I can use for instance; /lwc admin cleanup
    Also the command itself, /cprivate is working - BUT when the command is executed, it tells me to left click the block I want to be locked, I do it - And nothing happens.
    I can't see it in the logs, and when I use /lwc i it's not registered.

    I tried looking for the answer in the thread, but I couldn't seem to find it.
    Hope you've got a solution, I really like this plugin!

    EDIT:
    Sudenly I do get an error report top line says;

    Code:
    20:01:15 [SEVERE] Could not pass event BLOCK_PLACE to LWC
    com.griefcraft.scripting.ModuleException: LWC Module threw an uncaught exception
    !
            at com.griefcraft.scripting.ModuleLoader.dispatchEvent(Unknown Source)
            at com.griefcraft.listeners.LWCBlockListener.onBlockPlace(Unknown Source
    )
            at org.bukkit.plugin.java.JavaPluginLoader$26.execute(JavaPluginLoader.j
    ava:419)
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav
    a:58)
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j
    ava:310)
            at org.bukkit.craftbukkit.event.CraftEventFactory.callBlockPlaceEvent(Cr
    aftEventFactory.java:84)
            at org.bukkit.craftbukkit.event.CraftEventFactory.callBlockPlaceEvent(Cr
    aftEventFactory.java:68)
            at net.minecraft.server.ItemSign.a(ItemSign.java:57)
            at net.minecraft.server.ItemStack.placeItem(ItemStack.java:56)
            at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.j
    ava:217)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:535)
            at net.minecraft.server.Packet15Place.a(SourceFile:57)
            at net.minecraft.server.NetworkManager.a(NetworkManager.java:196)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:75)
            at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
            at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:377)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:292)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:394)
    Caused by: java.lang.NullPointerException
            at com.griefcraft.modules.limits.LimitsModule.mapProtectionLimit(Unknown
     Source)
            at com.griefcraft.modules.limits.LimitsModule.onRegisterProtection(Unkno
    wn Source)
            ... 18 more
    20:03:51 [SEVERE] Could not pass event BLOCK_PLACE to LWC
    com.griefcraft.scripting.ModuleException: LWC Module threw an uncaught exception
    !
            at com.griefcraft.scripting.ModuleLoader.dispatchEvent(Unknown Source)
            at com.griefcraft.listeners.LWCBlockListener.onBlockPlace(Unknown Source
    )
            at org.bukkit.plugin.java.JavaPluginLoader$26.execute(JavaPluginLoader.j
    ava:419)
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav
    a:58)
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j
    ava:310)
            at org.bukkit.craftbukkit.event.CraftEventFactory.callBlockPlaceEvent(Cr
    aftEventFactory.java:84)
            at org.bukkit.craftbukkit.event.CraftEventFactory.callBlockPlaceEvent(Cr
    aftEventFactory.java:68)
            at net.minecraft.server.ItemSign.a(ItemSign.java:57)
            at net.minecraft.server.ItemStack.placeItem(ItemStack.java:56)
            at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.j
    ava:217)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:535)
            at net.minecraft.server.Packet15Place.a(SourceFile:57)
            at net.minecraft.server.NetworkManager.a(NetworkManager.java:196)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:75)
            at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
            at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:377)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:292)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:394)
    Caused by: java.lang.NullPointerException
            at com.griefcraft.modules.limits.LimitsModule.mapProtectionLimit(Unknown
     Source)
            at com.griefcraft.modules.limits.LimitsModule.onRegisterProtection(Unkno
    wn Source)
            ... 18 more
    And this is not when the server starts up.
    I think I read your answer to a guy who had the same problem.. Will just check the thread again :)
     
  19. Offline

    spunkiie

    @Hidendra

    As you could see a few post above, I have a very large server with many protections under LWC. Today I noticed a randomly 4s delay on block break/catch-from-the-ground. Inspecting my (linux) proccess I saw that Mysql (only used by LWC) was using 100% CPU for a few seconds than it drops to normal CPU usage.

    So my BIG LWC database with mysql is killing my server performance. What can I do ? Maybe enabling InnoDB would help ? If so how can I use LWC with a Mysql InnoDB database ? (tried to simple enable InnoDB under my.cnf) but LWC could not start then.

    Would sqlite perform better (I doubt). If so, is it possible to convert from Mysql to SQLITE ?

    Again, does a tweak in core.yml (cache/bd flush) could help ? BTW: Before LWC I used PreciousStones and the plugin works throwing all the protect block database in RAM while starting up. (Yeap, I have 16GB RAM exclusively for my Bukkit server). So If no core.yml/mysql tweak help, there's a chance of LWC support this "all-in-ram" feature in the future ?

    Thank you again :D
     
  20. Offline

    MiiMiiX

    Hello there, i just configured my own server for the first time, with absolutely no problems! II'm here because i got a question: Is it possible for LWC to lock Buttons/Levers/pressure plates?
    Thanks, for that AWSOME plugin :)
     
  21. Offline

    Hidendra

    Did you modify limits.yml in plugins/LWC/? Could you post the content of it?

    Code:
    /lwc admin cleanup
    
    Could you post the results of:
    Code:
    /lwc admin report
    
    (if you use it in-game, it also prints to the console!)

    Ah, snap.. I see -- the new release version will be out today, I'm just plugging away at the final features. Mostly minor things such as showing notices for your own protections, precaching, individual LWC permissions (e.g lwc.admin.find, lwc.admin.*, or lwc.create , lwc.unlock etc) and some other things that are done

    You can add trapdoors yourself to be protectable in 3.00 -- the wiki will be updated sometime today with how to.

    You can add it to core.yml under protections manually if you so wish, yes.

    My current build has precaching in it -- good idea! It'll be out soon today.

    Could you post the results of
    Code:
    /lwc admin report
    
    ? It will appear in the console.
     
  22. Offline

    spunkiie

    @Hidendra

    I posted yesterday my report, here's it again:

    : + Engine: MySQL
    : + Date: Mon Jun 06 18:40:53 BRT 2011
    : + Time: 3532 seconds
    : + Players: 292
    : + Protections: 252493
    : + Cache: 10000/10000
    :
    : - Physical database
    : + Queries: 764719
    : + Average: 216.5116081540204 /second
    :
    : - Memory database
    : + Queries: 453610
    : + Average: 128.4286523216308 /second


    My server is really big :D

    FYI: Just converted back from Mysql to SQLite for testing purpose. This make my server UNPLAYABLE. Had to go back to Mysql.

    Can't wait for today release.. having 300+ users complaining about block lag is just not fun :D
     
  23. Offline

    Freakdk

    @Hidendra

    Yes I did edit my limit.yml

    Code:
    # type:
    #    default = LIMIT counts ALL default protections (IGNORES chest:, furnace:, Etc)
    #    custom   = LIMIT becomes a default PER-BLOCK limit, while chest:, furance:, etc is the PER-BLOCK limit (e.g 0 protected furnaces, 2 chests)
    
    # chest: unlimited, etc is just shown in master block to make it
    # clear they can be used here
    master:
        limit: unlimited
        type: custom
        chest: unlimited
        furnace: unlimited
        dispenser: unlimited
        wooden_door: unlimited
        iron_door: unlimited
    
    # Overrides for Permissions groups
    groups:
        # Gives the group Example limits of 5 chests, 2 furnaces, and 1 dispenser, and 0 of everything else
        Member:
            limit: unlimited
            type: unlimited
            chest: unlimited
            furnace: unlimited
            dispenser: unlimited
        Mod:
            limit: unlimited
            type: unlimited
            chest: unlimited
            furnace: unlimited
            dispenser: unlimited
        Admin:
            limit: unlimited
            type: unlimited
            chest: unlimited
            furnace: unlimited
            dispenser: unlimited
     
    players:
        # Gives Notch unlimited protections
        Notch:
            limit: unlimited
     
  24. Offline

    bigggan

    Hello

    When i try to run the server this error comes:
    Code:
    [SEVERE] Could not load 'plugins\LWC.jar' in folder 'plugins': 
    java.util.zip.ZipException: error in opening zip file
        at java.util.zip.ZipFile.open(Native Method)
        at java.util.zip.ZipFile.<init>(Unknown Source)
        at java.util.jar.JarFile.<init>(Unknown Source)
        at java.util.jar.JarFile.<init>(Unknown Source)
        at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:59)
        at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:194)
        at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:117)
        at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:103)
        at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:232)
        at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:219)
        at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:146)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:285)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
     
  25. Offline

    Hidendra

    Right, I see. and yeah -- with that many protections, SQLite will be laggy.

    Have you tried increasing the cache? 10k protections uses about 3 MB (which is a rough guess), so even 100k would only use about 30 MB (it may help, or if you wanted to use even more memory squeezing all 252k protections into the cache.)

    How big is LWC.jar? Sounds like it is corrupted?

    You have type: set to unlimited -- it needs to be either 'custom' or 'default'

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

    bigggan

    134,54 KB

    It dont install the folder LWC either.
     
  27. Offline

    Hidendra

    What version?
     
  28. Offline

    spunkiie

    @Hidendra:

    Yeap, already tried raising the cache to even: 10000000. Same block lag.

    I think the only solution will be putting all protections in RAM just as PS does. BTW: I had over 4 million protection ons under PS :D
     
  29. Offline

    bigggan

  30. Offline

    Hidendra

    try replacing it with this:
    <Edit by Moderator: Redacted mediafire url>

    Yup, I'm just testing everything now
     
    Last edited by a moderator: Dec 15, 2016
  31. Offline

    spunkiie

Share This Page