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


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

    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.

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


    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:

    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)

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

    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

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

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

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

    LWC 3.49
    • FIX: Double console output

    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

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

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

    LWC 3.45
    • FIX: plugins/LWC/locale/ (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.

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

    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

    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.

    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

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

    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

    • 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

    • 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

    • Fix "fetch size" error
    • Removed the auto-removal of the very old players table


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

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

    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:
    • @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:
          bukkitBug656workaround: true

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

    • Translation: Swedish! Thank you @christley!
    • Bug fix for block placement

    • 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
                  enabled: true
                  autoRegister: off

    • 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

    • Notices will be shown correctly to admins when showMyNotices is disabled.

    • 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

    • MySQL prefix is now working as it should
    • Minor fix with the cache update in 3.02

    • Cache null protections as well, to prevent massive redstone spam

    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.

    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

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

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

    • [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), (/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.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

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

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

    • 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


    • Security bugfix regarding an issue in minecraft itself (thanks sycot)

    • Native German translation! If you wish to use LWC in German, please change "locale" in 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.

    • Minor bug fixes

    • 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

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

    enjoy, gents
  2. Offline


    ah ok thaks
  3. Offline



    v3.05, bukkit #857 (will be on RB #860 later today, but I expect behavior to be the same since this has been a consistent issue since RB #818)

    I'm still having the issue where locks quietly disappear after the server has been up for some time. Again the scenario: I run a sign/chest-based marketplace, and LWC protects the chests. After a fresh server restart, I can run around the market and left-click on the chests and see that they are all locked by their owners (so the protection data in the DB is good).

    After some time of the server running (a few hours, half a day, w/e), when I do the same thing, the chests are no longer showing their owners when I left-click on them. When I '/lwc -o' one of the said chests, it reports 'That Air is not registered!'. Of course having market chests unlocked and open to the world is not a good thing! So I keep having to close my market and it's been over a week and a half now (since my LWC 3.0 upgrade) and players are wondering if I'm ever going to re-open it. :p

    I have a duplicate test world of my original, so I'd be happy to show you this first-hand on a fresh restart (test server) vs. up for a few hours (prod server), if that would aid in debugging any.
  4. Offline


    Isnt compatible with movecraft ... it save the items while you move with a Movecraft craft :( ...:
    Start a Aircraft with a protectet LWC chest . Move it took out of the chest 1 item than move and the item is double themselv .. in your item the one and in the chest ...
  5. Offline


    I've an issue with protection. When an place a chest it create a protected chest. My core is : autoRegister: false and i don't understand why
  6. Offline


    a question is this possible?
        denyRedstone: false
        autoRegister: false
                enabled: true
                autoRegister: false
        allowBlockDestruction: false
  7. Offline


    I would really appreciate it if you post some sort of version history for LWC. I need to acquire the last v2.x jar. Otherwise I love what you have done with this great plugin.
  8. Offline


    Hey guys! :)
    Just stopping by to let you know this is working good (LWC 3.05) on my CB #860!
    Keep up the great work guys!
    All protections are good to go! :D

    Hmm, for some reason after i just went to CB #860
    Magnet chests are lagging VERY BAD. Meaning the items get sucked up after like...... 20 seconds... Please check if you have the same issue.

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


    : + Version: v3.05
    : + Engine: MySQL
    : + Date: Sat Jun 11 15:15:20 BRT 2011
    : + Time: 6082 seconds
    : + Players: 329
    : + Protections: 1454141
    : + Cache: 1558491/100000000
    : - Physical database
    : + Queries: 262831
    : + Average: 43.2074634226533 /second
    : - Memory database
    : + Queries: 516182
    : + Average: 84.85648528686504 /second


  10. Offline


    Where do I download LWC-iconomy.jar?
    Edit: Found it.
    However, it seems like it charges every time I place a chest/furnace down, not just when I want to lock one. Help?
    Edit: Found it in core.yml
  11. Offline


    Uhh.. How do I enable the magnet flag? It's enabled in it's config yet it doesn't appear in the list of flags.
  12. Offline


    hey nice plugin but i ran into some trouble with multiple groups per player

    after reading your src i found the problem ... idk if its a permissions 3.0 feature but you should rather use this for groupchecking
    for(String groupname : permissions.getGroups(player.getWorld().getName(), playerName)) {
       if (protection.getAccess(AccessRight.GROUP,  groupname) >= 0) {
         return true;
    EDIT: another bug... the "@" flag for Admins doesnt affect groups even if lwc outputs it
    EDIT2: ok located it in the src you check for isMod and isAdmin only for online players so only if the Admin is online the Mod cannot enter the lock
    EDIT3: use
    public boolean isAdmin(String player, String world) {
            Player p = plugin.getServer().getPlayer(player);
            if (p != null && p.isOp()) {
                    if (configuration.getBoolean("core.opIsLWCAdmin", true)) {
                        return true;
            if(permissions != null) {
                if (permissions.has(world, player, "lwc.admin")) {
                    return true;
            return false;
    public boolean canAccessProtection(Player player, Protection protection) {
            if (protection == null || player == null) {
                return true;
            // call the canAccessProtection hook
            Result canAccess = moduleLoader.dispatchEvent(Event.ACCESS_PROTECTION, player, protection);
            if (canAccess != Result.DEFAULT) {
                return canAccess == Result.ALLOW;
            if (isAdmin(player.getName(), protection.getWorld())) {
                return true;
            if (isMod(player)) {
                if (!isAdmin(protection.getOwner(), protection.getWorld())) {
                    return true;
  13. Offline


    Tons of my users are confirming the insane lag of the magnet flag in #860. :(
    The items take forever to go in, 20-30 seconds ++++++ and sometimes they just dont :(
  14. Offline



    Please make possible to add protections by ID. I'm trying to add Moss Stone without success.

    Tried many different names, LWC doesn't understand it.
  15. Offline


    @Hidendra yup, confirmed super lag with magnet flag...
    Were at 50-60 online now, and its lagging hard now, 30+ seconds to go into chest. (Over 10 users confirmed it)
    Before 860 we had about 50-60 online and it had no lag going in.
  16. Offline


    In magnet.yml, try increasing perSweep value (if you don't see it, here's the default magnet.yml)

    # Magnet module
        enabled: true
        # The radius around containers that they will suck up
        radius: 3
        # How many items to check per sweep (per world)
        # It is HIGHLY UNRECOMMENDED to use a very high value
        perSweep: 20
        # A blacklist of items that will NOT be picked up
        # Item names usually work, but be careful
            - 500
    perSweep is how many dropped items LWC loops through each time it checks. Be warned that if you increase this dramatically (e.g to 50000), you may see severe lag. A value of 100-400 should be safe, depending on your server specs (and perhaps even higher.)

    You can use the Id already :)

    It does not appear in /lwc flag yet. I'm looking into a better solution of how that command works, because the current way isn't very good at all.

    Yes. You may need to use trap_door instead, or just use the block Id if it does not work.

    is autoRegister set to false under chest: as well?

    May be an issue with movecraft itself -- I'll look

    I would prefer not to drop Permissions <3 support yet -- I'd rather not force people to upgrade from 2.7.4 to 3.0+ just yet.

    This is a long recurring issue with CraftBukkit itself. It has existed since the 1.3 or 1.4 builds (and maybe even earlier.) I believe it is an issue with chunk caching and at the moment there isn't any immediate fixes on LWC's end (it will happen to any plugins that have you interact with blocks, such as McMMO.)

    3.06 is mainly a maintenance update for some outstanding issues!

    LWC 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
    X-Stef likes this.
  17. Offline


    Cheers, thanks, I love you. Went to translate into Russian =)
  18. Offline


    I'm trying a clean install of LWC v3.05 with bukkit 860 and Permissions 3.1.5. I'm using MySQL as a backend for configuration of both permissions and LWC.

    When I issue a "/lwc -c private" command I get the expected dialog asking me to left click on a chest, but when I do left-click nothing happens. I've confirmed LWC can read/write from/to the database as "/lwc menu <basic | advanced>" writes to the database as expected so I think the configuration options are right... perhaps I've missed something.

    I've enabled the verbose option in core.yml hoping to see some errors in the server log, but there isn't anything. Do you all have some additional debugging ideas I can try or has anyone seen this problem before and have a solution?

  19. Offline


    By any chance are you not an OP and are trying to protect something inside of spawn? :)

    Awesome :D My apologies again for the wait!
  20. Offline


    That would be too easy. I am an op, but I'm well outside of the spawn zone. I have also produced the aforementioned results using an unprivileged (non-admin, non-op) user.

    limts.yml: (default)
    Startup log (just updated to 3.06, problem still happening and no error):

    And here's the permissions for the non-privileged user:
    >pr g:Default perms list
    20:49:01 [INFO] [Permissions] No world specified. Defaulting to default world.
    20:49:01 [INFO] [Permissions] Permissions: iConomyChestShopw.command.iteminfo, essentials.nick,,, essentials.home, essentials.compass, essentials.sethome, lwc.protect,, essentials.getpos, essentials.helpop, essentials.rules, essentials.msg, iConomy.list, essentials.whois, essentials.warp, essentials.kit.*,, essentials.list, iConomy.access, iConomy.rank, iConomy.payment, essentials.kit, craftbook.mech.*, essentials.spawn, essentials.motd
    Thank you for such a fast reply
  21. Offline


    Could you do this for each value individual posts?
    1. chest=Chest
    2. furnace=Furnace
    3. dispenser=Dispenser
    4. sign=Sign
    5. wooden_door=Wooden Door
    6. iron_door=Iron Door
    7. trap_door=Trap Door
    Like this:
    1. protection.chest.notice.protected=%red%Notice: %white%That %red%%type% Chest%white% is locked by%yellow% %owner%.
    2. protection.furnace.notice.protected=%red%Notice: %white%That %red%%type% Furnace%white% is locked by%yellow% %owner%.
    3. protection.dispenser.notice.protected=%red%Notice: %white%That %red%%type% Dispenser%white% is locked by%yellow% %owner%.
    4. protection.sign.notice.protected=%red%Notice: %white%That %red%%type% Sign%white% is locked by%yellow% %owner%.
    5. protection.wooden_door.notice.protected=%red%Notice: %white%That %red%%type% Wooden Door%white% is locked by%yellow% %owner%.
    6. protection.iron_door.notice.protected=%red%Notice: %white%That %red%%type% Iron Door%white% is locked by%yellow% %owner%.
    7. protection.trap_door.notice.protected=%red%Notice: %white%That %red%%type% Trap Door%white% is locked by%yellow% %owner%.
  22. Offline


    At the moment, no - if you looked at the protected notice, it is:
    protection.general.notice.protected=%red%Notice: %white%That %red%%type% %block%%white% is locked by%yellow% %owner%.
    %block% is the transformed name of the block (e.g a Chest looks up the "chest" locale value.)

    What you're proposing there would also not work for custom protections, among other things D:
  23. Offline


    Just in the Russian language word meanings are different. For example I need to make it (this), and (this), the first and second word in brackets are different, but in English they are the same :(
  24. Offline


    Ah, I see. I was thinking it was related to that :(

    Are they different for each protection, or does the adjective (e.g Wooden) change it?

    P.S, an open question to anyone -- is anyone absolutely against having hatches/trap doors protectable? I've lost count how many times I've gotten that question, and am thinking they should just be added to default (keeping in mind that anyone can still remove them from the "protectable" list.)
    edit: It most likely will not auto add itself to existing core.ymls, it would just be default to new installs of LWC.
    pomo4ka likes this.
  25. Offline


    Not against it.
  26. Offline


    Yes, different. So do not get to translate :)
  27. Offline


    I'm trying to update LWC to the lastest version (3.06), but each time I start the server I get an error with the MySQL Engine.

    06:07:10 [INFO] LWC     Loaded 125 locale strings (0 overrides)
    06:07:10 [INFO] LWC     Using Permissions API...
    06:07:10 [INFO] LWC     Loading MySQL
    06:07:10 [GRAVE] java.lang.NullPointerException
    06:07:10 [GRAVE]        at java.util.Hashtable.put(Unknown Source)
    06:07:10 [GRAVE]        at com.griefcraft.sql.Database.connect(Unknown Source)
    06:07:10 [GRAVE]        at com.griefcraft.lwc.LWC.load(Unknown Source)
    06:07:10 [GRAVE]        at com.griefcraft.lwc.LWCPlugin.onEnable(Unknown Source)
    06:07:10 [GRAVE]        at
    06:07:10 [GRAVE]        at
    06:07:10 [GRAVE]        at org.bukkit.plugin.SimplePluginManager.enablePlugin(
    06:07:10 [GRAVE]        at org.bukkit.craftbukkit.CraftServer.loadPlugin(
    06:07:10 [GRAVE]        at org.bukkit.craftbukkit.CraftServer.loadPlugins(
    06:07:10 [GRAVE]        at org.bukkit.craftbukkit.CraftServer.reload(
    06:07:10 [GRAVE]        at org.bukkit.command.SimpleCommandMap$ReloadCommand.execute(
    06:07:10 [GRAVE]        at org.bukkit.command.SimpleCommandMap.dispatch(
    06:07:10 [GRAVE]        at org.bukkit.craftbukkit.CraftServer.dispatchCommand(
    06:07:10 [GRAVE]        at net.minecraft.server.MinecraftServer.b(
    06:07:10 [GRAVE]        at net.minecraft.server.MinecraftServer.h(
    06:07:10 [GRAVE]        at
    06:07:10 [GRAVE]        at
    06:07:10 [INFO] Patcher ######################################################
    06:07:10 [INFO] Patcher ######################################################
    06:07:10 [INFO] Patcher SQLite to MySQL conversion required
    06:07:10 [INFO] Patcher Loading SQLite
    06:07:10 [INFO] Patcher SQLite is good to go
    06:07:10 [INFO] Patcher #### SEVERE ERROR: Something bad happened when converting the database (Oops!)
    06:07:10 [GRAVE] java.lang.NullPointerException
    06:07:10 [GRAVE]        at com.griefcraft.migration.MySQLPost200.checkDatabaseConversion(Unknown Source)
    06:07:10 [GRAVE]        at com.griefcraft.lwc.LWC.load(Unknown Source)
    06:07:10 [GRAVE]        at com.griefcraft.lwc.LWCPlugin.onEnable(Unknown Source)
    06:07:10 [GRAVE]        at
    06:07:10 [GRAVE]        at
    06:07:10 [GRAVE]        at org.bukkit.plugin.SimplePluginManager.enablePlugin(
    06:07:10 [GRAVE]        at org.bukkit.craftbukkit.CraftServer.loadPlugin(
    06:07:10 [GRAVE]        at org.bukkit.craftbukkit.CraftServer.loadPlugins(
    06:07:10 [GRAVE]        at org.bukkit.craftbukkit.CraftServer.reload(
    06:07:10 [GRAVE]        at org.bukkit.command.SimpleCommandMap$ReloadCommand.execute(
    06:07:10 [GRAVE]        at org.bukkit.command.SimpleCommandMap.dispatch(
    06:07:10 [GRAVE]        at org.bukkit.craftbukkit.CraftServer.dispatchCommand(
    06:07:10 [GRAVE]        at net.minecraft.server.MinecraftServer.b(
    06:07:10 [GRAVE]        at net.minecraft.server.MinecraftServer.h(
    06:07:10 [GRAVE]        at
    06:07:10 [GRAVE]        at
    06:07:10 [GRAVE] Error occurred while enabling LWC v3.05 (Is it up to date?): null
            at com.griefcraft.migration.MySQLPost200.checkDatabaseConversion(Unknown Source)
            at com.griefcraft.lwc.LWC.load(Unknown Source)
            at com.griefcraft.lwc.LWCPlugin.onEnable(Unknown Source)
            at org.bukkit.plugin.SimplePluginManager.enablePlugin(
            at org.bukkit.craftbukkit.CraftServer.loadPlugin(
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(
            at org.bukkit.craftbukkit.CraftServer.reload(
            at org.bukkit.command.SimpleCommandMap$ReloadCommand.execute(
            at org.bukkit.command.SimpleCommandMap.dispatch(
            at org.bukkit.craftbukkit.CraftServer.dispatchCommand(
            at net.minecraft.server.MinecraftServer.b(
            at net.minecraft.server.MinecraftServer.h(
    If I use the SQLlite Engine, I don't get any error. Here is my core.yml file, I didn't modified anything in the other yml files :

        locale: fr
        autoUpdate: false
        flushInterval: 10
        cacheSize: 10000
        defaultMenuStyle: basic
        showNotices: true
        showMyNotices: true
        verbose: false
        opIsLWCAdmin: true
        adapter: mysql
        path: plugins/LWC/lwc.db
        host: localhost
        database: minecraft
        username: root
        denyRedstone: false
        autoRegister: off
        ignoreBlockDestruction: false
        ignoreLeftClick: false
        ignoreRightClick: false
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: off
                enabled: true
                autoRegister: off
            enabled: true
            enabled: true
    I use my local webserver to test the update of my MC Server before to upload it. Thanks :)
  28. Offline


    The development build should now have this working. You won't see it in the locale file -- protection.general.notice.protected acts as a catch-all, and is overrided like so:
    protection.chest.notice.protected=Chest message
    protection.wooden_door.notice.protected=Wooden door message
    And so on.
    It is here:

    That looks like 3.05 (it says 3.05.) Did you do a fresh restart or a /reload?
    pomo4ka likes this.
  29. Offline


    You have already done this? I myself need to add a message?
  30. Offline


    Yessir :)

    What you pasted a few posts up should be what you just need to use, and should work fine. The current way (with %block) will still remain, it can just be overridden.

    p.s another obscure feature, if for example you did this:
    chest=Modified Chest Name
    to modify the notice, you'd have to instead use
  31. Offline


    Thank you very much. I hope in the future you add them in the main release :)

Share This Page