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


    I cant for some reason get mine to lock dual chests (2 chests side by side) works great with single chests though
  3. Code:
    [SEVERE] Could not pass event PLAYER_INTERACT to LWC
    com.griefcraft.scripting.ModuleException: LWC Module threw an uncaught exception! LWC version: 3.21-git-LWC-2936c58564bf9d84e97a9a024af1644c8f67f269-b54jnks
    	at com.griefcraft.scripting.ModuleLoader.dispatchEvent(Unknown Source)
    	at com.griefcraft.listeners.LWCPlayerListener.onPlayerInteract(Unknown Source)
    	at org.bukkit.plugin.RegisteredListener.callEvent(
    	at org.bukkit.plugin.SimplePluginManager.callEvent(
    	at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(
    	at net.minecraft.server.ItemInWorldManager.dig(
    	at net.minecraft.server.NetServerHandler.a(
    	at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
    	at net.minecraft.server.NetworkManager.b(
    	at net.minecraft.server.NetServerHandler.a(
    	at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
    	at net.minecraft.server.MinecraftServer.h(
    Caused by: java.lang.NullPointerException
    	at org.bukkit.craftbukkit.CraftServer.getWorld(
    	at com.griefcraft.model.Protection.getBukkitWorld(Unknown Source)
    	at com.griefcraft.modules.doors.DoorsModule.onProtectionInteract(Unknown Source)
    	... 15 more

    CB 953, LWC 3.21, DB MYSQL :) hope this helps :)
  4. Offline


    It seems as if the plugin creator COMPLETELY ignored my comment about permissions for LWC not working correctly by giving me Access Denied EVERYTIME my Default, Trusted, and Moderators try to create a lock on a chest. And I put in lwc.protect in the default group so that EVERYONE can use LWC but seeing the plugin creator ignored my comment, I guess it's a problem he/she doesn't want to face. So until then, I will be using lockette.
  5. Offline


    Honestly dude, you're doing it wrong. Post your permissions config and whatnot so we can see what you're doing. LWC works fine.
  6. Offline


    Sounds like you renamed a world? If you did, and know how to execute a query on the MySQL db for lwc, do this:
    UPDATE protections SET world = 'newname' WHERE world = 'oldname';
    replace protections with your prefix + protections if applicable (e.g prefix = lwc_, table name would be lwc_protections)

    If you DO NOT know how to, please update to CI build #60:
    And then do this:
    /lwc admin query UPDATE protections SET world = 'newname' WHERE world = 'oldname'
    Double chests are working fine and have no reason not to. Are you using the latest version of LWC?

    Update to 3.21 :)

    That would be awesome! :D

    Have you created the ulfbagec_lwc database? I'm also assuming is the real ip instead?

    You could remove all protections still left in the skylands (assuming no one can protect stuff now.) First, update to this build:

    And then execute this command:
    /lwc admin query DELETE FROM protections WHERE world = 'skylands';
    if you use a prefix, prefix protections with it (lwc_ = lwc_protections). And skylands is the world name (assuming it is not skylands.)

    @spunkiie thanks

    That's where you are wrong, friend. This thread receives a staggering amount of replies/help requests and if I stop replying for even a day I get so far behind that it's difficult to even try (hence why my replies to this thread generally have 10-20 quoted posts each [including this post]). Once in a while I DO miss a post or two, and yours I must have indeed missed.

    You can also use /lwc debug to instantly verify what permission nodes you have access to for LWC.

    As @Zalastri mentioned, please post your permissions config for the world. usually it's something as little as a typo, that you may not see (because you did it.)

    PS a release or two should be coming up in the next couple of days, which'll include expiring protections and some other stuff
    Zalastri likes this.
  7. Offline


    Yes that database shall be created, and yes is replaced by the real ip that I use. It's so strange since it works for several other plugins with their databases but not this one.
  8. Offline


  9. Offline


    In my.cnf (for mysql) is bind-address set properly? If it isn't, perhaps try that?

    Also, are you able to connect using mysql -uulfbagec_Hampi90 -hyourip -p?
  10. Offline


    The swedish translation is Bad, It says:
    Notera: Att Privat Kista är låst av du.

    That in english is
    Note: That private chest is locked by yourself.

    XD It SHOULD be
    Notera: Denna privata kista är låst av dig.

    That in english is
    Note: This private chest is locked by you.

    This is correct:

    :p Hopy u change it :p
  11. Offline


    im getting Access Denied how do i fix this?
  12. Offline


    Peer review is always fantastic! I wouldn't say it is bad, each person's interpretation may be different (I'm assuming the rest is okay if you only mentioned one word, so it can't be all that bad :p)

    Thank you

    Did you add lwc.protect to the group(s) in Permissions?
  13. Offline


    yes but can you tell me if i did it right:
            default: true
                prefix: ''
                suffix: ''
                build: true
            default: false
                prefix: ''
                suffix: ''
                build: true
                - Default
                - 'warpplugin.warp'
                - 'econplugin.basic.*'
                - 'lwc.protect'
            default: false
                prefix: ''
                suffix: ''
                build: true
                - Member
                - 'modplugin.ban'
                - 'modplugin.kick'
                - 'modplugin.unban'
                - 'lwc.mod'
            default: false
                prefix: ''
                suffix: ''
                build: true
                - 'lwc.admin*'
  14. Offline


    Ok I recently switched to a multiworld setup, in one world there is no LWC access, so I did not give LWC perms, however ALL chests now say (The server admin is blocking you from opening that) unless the person themselves placed it, and there is no protection even registered to the chests, please help advise.
  15. Offline


    Well what you said now is more than I know about mysql. How can I connect using this (mysql -uulfbagec_Hampi90 -hyourip -p)?

    And where do I find my.cnf?

  16. Offline


    I've figured out how bukkit plugins are written and done dummy theft protection as a standalone plugin, now I'm trying to make an LWC module which add a new flag for this.
  17. Offline


    is there a way to make it so that people can put stuff in a chest but they cant take it out? cuz i wana make a sacrifice room where everyone has to give me stuff :D and i dont want ppl stealin from it
  18. Offline


    Can anyone help me to set up my wooden doors on server so it can be destroyed by anyone unless in protected area? ( Precious Stones )

    Thank You!

    apply "/cmagnet on" and make them throw items at chest, make chest ur own private...

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


    Sorry for my bad english but
    How can I turn that out, that I can open doors with buttons? Because i can use a button to open a door.
  20. Offline


    Yeah that's how I'm doing this now. When the chest is closed, each ItemStack which was previously in it is checked to still be in the chest. So if you take some of the diamonds it will raise an alarm. You can put extra items in chest since it's not considered a theft.

    Redstone flag.

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


    ty :)
  22. Offline


    Well it's grammatically incorrect. That's how new immigrants would say xD
  23. Offline


    I am sure this has been posted several times before, but I am having a little problem. I can get the permissions etc to work with this plugin, but after it says "Left click on the item you want to protect", nothing happens when i click the chest?

    I haven't changed the config files since it is a plug and play plugin, so maybe this is where I am going wrong?
    MrMinecraftMcGee likes this.
  24. Offline


    Hey Hiendra, im having a little issue while tryng to implement LWC with LevelCraft

    java.lang.NoClassDefFoundError: com/griefcraft/scripting/Module
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(
        at org.bukkit.plugin.SimplePluginManager.loadPlugin(
        at org.bukkit.plugin.SimplePluginManager.loadPlugins(
        at org.bukkit.craftbukkit.CraftServer.loadPlugins(
        at org.bukkit.craftbukkit.CraftServer.<init>(
        at net.minecraft.server.ServerConfigurationManager.<init>(
        at net.minecraft.server.MinecraftServer.init(
    Caused by: java.lang.ClassNotFoundException: com.griefcraft.scripting.Module
        at Method)
        at java.lang.ClassLoader.loadClass(
        at java.lang.ClassLoader.loadClass(
        ... 11 more
    Heres the simple code (cut to make it easyer to read) im tryng:

     lwc = (LWCPlugin)getServer().getPluginManager().getPlugin("LWC");
    LwcModule lwcModule = new LwcModule(this);
    lwc.getLWC().getModuleLoader().registerModule(this, lwcModule);
    Then, at my LwcModule:

    class LwcModule extends JavaModule {
            public LCThiev plugin;
            public LwcModule(LCThiev tance) {
                plugin = tance;
        // called when a player interacts with a protection
        public Result onProtectionInteract(LWC lwc, Player player, Protection protection, List<String> actions, boolean canAccess, boolean canAdmin) {
                        return DEFAULT;
                    int level = LevelFunctions.getLevel(player, plugin);
                    // wood door ou iron door 10
                    if((protection.getBlock().getType()==Material.WOODEN_DOOR || protection.getBlock().getType()==Material.IRON_DOOR )) {
                        if(!player.getInventory().contains(Material.IRON_INGOT)) {
                            player.sendMessage("Voce precisa de barras de ferro para abrir portas !");
                            return DEFAULT;
                        }  else {
                            Random rnd = new Random();
                            int n = rnd.nextInt(100);
                                n *= 1.3;
                            if(level < 10)
                                level = 10;
                            if(n < level/2) {
                                player.sendMessage("Voce astutamente abre a porta.");
                                LevelFunctions.addExp(player, plugin, 10);
                                if(n<level/5) { // acerto critico
                                   player.sendMessage("Ao abrir a porta, voce consegue quebrar a tranca !");
                                return ALLOW;
                            } else {
                                player.sendMessage("Voce falhou em abrir a porta");
                    // bau
                    if(protection.getBlock().getType()==Material.CHEST && level > 20) {
                        if(!player.getInventory().contains(Material.DIAMOND)) {
                            player.sendMessage("Voce precisa de diamantes para abrir baus !");
                            return DEFAULT;
                        } else {
                            Random rnd = new Random();
                            int r = rnd.nextInt(100);
                            int chance = 1;
                                if(level > 30) chance+=1;
                                if(level > 60) chance+=1;
                                if(level > 80) chance+=1;
                                if(level > 90) chance+=1;
                                if(level > 99) chance+=1;
                            if(chance > r) {
                                player.sendMessage("Com uma violenta diamantada voce consegue quebrar o trinco do bau !");
                                LevelFunctions.addExp(player, plugin, 20);
                            } else {
                                player.sendMessage("Voce falhou em abrir o bau !");
            return DEFAULT;
    I really would apreciate any help, my coding skills are not very good. Thanx alot.
  25. Offline


  26. Offline


    Is the server running LWC > 3.00?

    Are you trying to protect something inside of Spawn area? you will also need OP privileges if so

    A group has access to lwc.blockinventory

    At the moment, no (unless you use the magnet flag as @staniboy mentioned)

    /credstone on
    Hit the door :D

    ah, nice
  27. I am having the same problem! I have tried everything. The people on my server need a good protection system and i like this one
  28. Offline


    I have a question.
    I have converted LWC from sqlite to mysql, but now, i wil get it back, if i set it on sqlite it wil automatich convert back ore something?

    Sorry for my bad english :(
  29. Offline


    No, its not inside the spawn area, and I am an op.
    Here is my permissions file if it helps:
            system: default
            default: true
                prefix: ''
                suffix: ''
                build: false
                - ''
                - 'essentials.motd'
                - 'essentials.rules'
            default: false
                prefix: '&9'
                suffix: ''
                build: true
                - Builder
                - ''
                - 'essentials.tphere'
                - 'essentials.ban'
                - 'essentials.kick'
                - 'essentials.time'
                - 'essentials.jump'
                - 'essentials.warp'
                - 'essentials.setwarp'
                - 'essentials.item'
                - 'essentials.spawn'
                - ''
                - ''
                - 'essentials.signs.heal.use'
                - 'lwc.mod'
            default: false
                prefix: '&4'
                suffix: ''
                build: true
                - '*'
                - 'lwc.admin'
                - ''
                - 'essentials.jail.exempt'
            default: false
                prefix: '&b'
                suffix: ''
                build: true
                - '*'
            default: false
                prefix: '&2'
                suffix: ''
                build: true
                - '*'
                - 'essentials.jail.exempt'
            default: false
                prefix: ''
                suffix: ''
                build: true
                - ''
                - 'essentials.home'
                - 'essentials.motd'
                - 'essentials.rules'
                - 'essentials.sethome'
                - 'essentials.spawn'
                - ''
                - 'essentials.signs.heal.use'
                - 'essentials.warp'
                - 'lwc.protect'
                - ''
                - ''
                - ''
  30. Offline


    No, the conversion from MySQL to SQLite is not supported, and must be manually done.

    Please pm me your server IP and allow me to ahve builder privileges (my username is HIdendra)
  31. Offline


    How i need to do that?

Share This Page