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


    Spout lwc plz give us spot lwc gui
  3. Offline


    My friend got a problem, he wants to create a public furnace room. The problem is when he puts a furnace down it automaticly his. How do he change this?
  4. Hi there, ive got a problem, i run a small MC Server just 8 slots, and because i dont undestand how to configure permissions (i just dont get it, and i tried it many times) i use OP instead along with PermissionsEX to make plugins running that absolutly needs a permissions plugin to work, my problem is that if i protect a chest with LWC the other players still can open it and take items or put some in or even destroy the chest, is there a solution to take LWC admin rigths away from OP´s ? I´ve seen there is an "opIsLWCAdmin" option, allthough i set it to false it still doesnt take away the rights from the op´s. did i make something wrong here ? pls help out.

    I did use lockette before there were two options to take admin rights away from op´s : 1st: "allow-admin-snoop (true/false)" 2nd: "allow-admin-bypass (true/false)" when i set these two to false even the op´s couldnt look into chests anymore or destroy them...
  5. I've set up a new server with minimal plugins. Currently just using:
    Simple Server

    With this setup everything works fine. Ops are ops and players can play.
    I then add:


    Then set up config.yml (just using the standard config except changing the admin user name).

    Admin can access /perm and ops/players are fine.

    As soon as I add LWC things go squiffy.

    Nobody can do anything except ops. I saw the option to auto lwc admin ops so simply removed the users from ops.txt rather than mess with the default LWC files.

    Situation now:

    guest, user and admins cannot create or destroy or open anything. Get a you cannot build here (or similar) message.
    Interestingly admins can't use /perm any more.

    So, as soon as I add LWC nobody can do anything (apart from ops).
    I'm assuming Simple Server has nothing to do with it as it's just a wrapper (but will try without it this evening).
    I have found posts in this thread (and elsewhere) with people with the exact same problem but it's never followed up or resolved.
    To re-iterate, I'm not using "Permissions", just PermissionsBukkit. I've seen config.yml samples where some use SuperPermBridge for LWC and some don't. Nobody has said what's wrong or right.
    I'm at work atm and can't real off version numbers off my head :) however, all plugins and simple server wrapper were downloaded within the last few days.

    I've been banging my head on the wall for days now. I can get all plugins working together (it seems) but as soon as I add LWC, even to a clean setup, it stop building/access/destroying.

    Any obvious "gotchas" for setting up LWC?
    All config files for LWC are default. config.yml just has a username changed (just letters so catching me out on wrapping it in quotes etc.)
    (every group has " true" apart from default that's set to false).

    Anyone any ideas what's happening?

    Does anyone have a "simple" config.yml that they can confirm works with a clean install? ie a default, user and admin group with a user for each group with LWC permissions.

    I'll post versions and config files when I get home.

  6. Offline


    Anything else ?? Sorry i did not understand this Part, so it means it is possible to protect Minecarts ??
    Or, is it possible to protect them ??

    Like a door cmodify *player* so just this player can drive your own cart,
    or to make them public so all can drive but not destroying.
  7. Offline

    Cosmic Break

    there is support for double doors, only if both doors are protected. there is an option to disable the messages when clicking on your own protections. there is an option to auto close protected doors.

    this is all in the config. just take a look
  8. Offline


    Please Help! When I use this plugin it will not let me place items. And when I try and use the /lwc commands it says "An internal error occurred while trying to perform this command"
    Please help!
  9. Offline

    Cosmic Break

    thats a problem with your mysql. get a better connection to the db or switch to sqlite

    make sure you set up permissions.

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

    11:45:55 [SEVERE] Could not pass event BLOCK_PISTON_EXTEND to LWC
    java.lang.ClassCastException: org.bukkit.material.MaterialData cannot be cast to org.bukkit.material.PistonBaseMaterial
            at org.bukkit.event.block.BlockPistonEvent.getDirection(
            at com.griefcraft.listeners.LWCBlockListener.onBlockPistonExtend(
            at org.bukkit.plugin.RegisteredListener.callEvent(
            at org.bukkit.plugin.SimplePluginManager.callEvent(
            at net.minecraft.server.BlockPiston.g(
            at net.minecraft.server.BlockPiston.doPhysics(
            at net.minecraft.server.World.k(
            at net.minecraft.server.World.applyPhysics(
            at net.minecraft.server.BlockRedstoneWire.g(
            at net.minecraft.server.BlockRedstoneWire.doPhysics(
            at net.minecraft.server.World.k(
            at net.minecraft.server.World.applyPhysics(
            at net.minecraft.server.World.update(
            at net.minecraft.server.World.setTypeIdAndData(
            at net.minecraft.server.BlockDiode.a(
            at net.minecraft.server.Chunk.flushTicks(
            at net.minecraft.server.World.j(
            at net.minecraft.server.World.doTick(
            at net.minecraft.server.MinecraftServer.h(
  11. Offline


    You can try and download a updated version :D
  12. Offline


    why don't you use that the people can subscribe to updates via e-mail?
  13. Offline


    com.griefcraft.scripting.ModuleException: LWC Module threw an uncaught exception! LWC version: 3.31-git-LWC-b9ea01e8c2f66480ada443ba9084dfbe9832f06e-b81jnks at com.griefcraft.scripting.ModuleLoader.dispatchEvent( at com.griefcraft.listeners.LWCPlayerListener.onPlayerInteract( at$10.execute( 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( at at Caused by: com.griefcraft.scripting.ModuleException: LWC Module threw an uncaught exception! LWC version: 3.31-git-LWC-b9ea01e8c2f66480ada443ba9084dfbe9832f06e-b81jnks at com.griefcraft.scripting.ModuleLoader.dispatchEvent( at com.griefcraft.modules.create.CreateModule.onBlockInteract( at com.griefcraft.scripting.ModuleLoader.dispatchEvent( ... 14 more Caused by: java.lang.NullPointerException at com.griefcraft.modules.limits.LimitsModule.mapProtectionLimit( at com.griefcraft.modules.limits.LimitsModule.onRegisterProtection( at com.griefcraft.scripting.ModuleLoader.dispatchEvent( ... 16 more

    LWC is telling me this in the console, whats wrong?
  14. Offline


    Right, because i need a better connection than it residing on the same machine the server is running on. A quad core i7 with 16GBs of ram.
  15. Offline


    I've found that if u place a lever next to a door, you can open the door. Its a pain sometimes
  16. Offline


    i have a problem we have 66.000 locked chests on our server most of them are old how can i remove them or can i do something with them it cant be god to have that much or?
  17. Offline


    Not able to update LWC.jar. It seems there no file-Uploads at
  18. Offline


    I didn't take this screenshot, but I realized how people can use LWC to annoy people.

  19. Offline


    Sorry to bother you developer, but I was wondering if in the near future you will add it so when signs get broken that are protected the text doesn't get messed up? Quote me back please!
  20. Offline

    Emiya Shirou

    This plugin is the best protection I've found out there, is there a way to use it as cuboid protection as well? (for all the house for example)
  21. Offline


    I'm getting the internal error thing when I try to run /lwc admin cleanup. I saw someone else post about this, but couldn't find the solution. Has one been found yet?
  22. Offline

    Emiya Shirou

    After updating from 3.31 to 3.42 through /lwc admin update I see this error when trying /lwc admin cleanup

    03.09 04:14:12 [Server] SEVERE     at
    03.09 04:14:12 [Server] SEVERE     at
    03.09 04:14:12 [Server] SEVERE     at net.minecraft.server.MinecraftServer.h(
    03.09 04:14:12 [Server] SEVERE     at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
    03.09 04:14:12 [Server] SEVERE     at org.getspout.spout.SpoutNetServerHandler.a(
    03.09 04:14:12 [Server] SEVERE     at net.minecraft.server.NetServerHandler.a(
    03.09 04:14:12 [Server] SEVERE     at net.minecraft.server.NetworkManager.b(
    03.09 04:14:12 [Server] SEVERE     at net.minecraft.server.Packet3Chat.a(
    03.09 04:14:12 [Server] SEVERE     at net.minecraft.server.NetServerHandler.a(
    03.09 04:14:12 [Server] SEVERE     at
    03.09 04:14:12 [Server] SEVERE     at net.minecraft.server.NetServerHandler.handleCommand(
    03.09 04:14:12 [Server] SEVERE     at org.bukkit.craftbukkit.CraftServer.dispatchCommand(
    03.09 04:14:12 [Server] SEVERE     at org.bukkit.command.SimpleCommandMap.dispatch(
    03.09 04:14:12 [Server] SEVERE     at org.bukkit.command.PluginCommand.execute(
    03.09 04:14:12 [Server] SEVERE     at com.griefcraft.lwc.LWCPlugin.onCommand(
    03.09 04:14:12 [Server] SEVERE     at com.griefcraft.scripting.ModuleLoader.dispatchEvent(
    03.09 04:14:12 [Server] SEVERE     at com.griefcraft.modules.admin.AdminCleanup.onCommand(
    03.09 04:14:12 [Server] SEVERE     at com.griefcraft.modules.admin.AdminCleanup$
    03.09 04:14:12 [Server] SEVERE     at org.sqlite.Stmt.setFetchSize(
    03.09 04:14:12 [Server] SEVERE     at org.sqlite.RS.setFetchSize(
    03.09 04:14:12 [Server] SEVERE java.sql.SQLException: fetch size -2147483648 out of bounds 0
    03.09 04:14:09 [Server] INFO [AuthMe] Player Emiya_Shirou logged in!
    and also this in game
  23. Offline


    It's just client sided - log out and in ;)

    Use this build:

    At the moment, no ;)
    LWC isn't exactly intended for that purpose and as such internally supports single block protection. Some servers opt to auto protect most blocks (such as wood, fences, wool, brick, etc etc.)

    It is indeed a problem but not something I don't think is in within LWC's scope. I am aware people could also build houses out of protected furnaces (Heh), but when you put a protected block over someone's chest, it makes it obvious who the perpetrator is, right?

    /lwc admin  cleanup
    Will remove any protections that no longer have an associated block with them in the world :)

    Some servers have millions of protections, so if you're using MySQL, 66k is perfectly OK :D

    Could you quote your plugins/LWC/limits.yml?

    Please use this build :) I will push the update tomorrow since it seems a lot of people are using SQLite and cleanup!

    It has been fixed in the latest LWC dev builds. It's actually a bug on Bukkit's end, not LWC's, but LWC is working around it.

    I will be :) I just haven't had a lot of time these past few days to finish it to get it approved.

    Thank you

    At the moment the workaround is buggy. In future updates it will be seamless and LWC will use necessary measures on its own and not need to be manually turned on.

    Check out plugins/LWC/limits.yml -- it should layout how to. As for lwc.mod.. you are aware that allows them to view inside anyone's chest, correct?

    Either /cremove it (you can remove multiple protections with /cpersist, then use /cremove and hit all of the blocks) OR in plugins/LWC/core.yml, find the furnace: section and change autoRegister: private to autoRegister: off

    It should automatically remove the protection when they remove the block or sign.

    It will be looked into
  24. Offline


    Maybe it is when we just rollback with bigbrother, we are hoping they add sign support like hawkeye does.
    Emiya Shirou likes this.
  25. Offline

    Emiya Shirou

    I wrote that because there really isn't any good cuboid plugins out there :/ I might just put all the building materials into LWC auto protection but that will be troublesome when 2 people want to live in one house D:
  26. Offline


    I see LWC is in multiple languages, can I maybe help you translate it to Dutch?
  27. Hello again @Hidendra
    CB1068 and upwards causes commands to be denied due to failing permissions, even if you have '*'. Tested with LWC v3.31 and v342 together with Permissions 3.1.6. Would it be possible to make it work with the later non-RB builds? :)

    CB1068 Changes:
    Commands are now "bukkit.command.x" instead of "craftbukkit.command.x", added legacy perms for compat
  28. Offline


    I get server crash when typing /lwc admin cleanup
  29. Offline


    Use this LWC.jar :)

    During startup, does LWC say somewhere LWC: Permissions API: NijiPermissions ? It will be near the bottom of the startup log, most likely.

    There is already a Dutch translation but if you feel it can be improved upon, please do so :)

    Ah, I see.

    That would indeed explain it :)

    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

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

    2011-09-03 12:35:28 [INFO] LWC: Loaded 137 locale strings (0 overrides)
    2011-09-03 12:35:29 [INFO] LWC: Permissions API: ^[[31mNijiPermissions^[[0m
    2011-09-03 12:35:29 [INFO] LWC: Currency API: ^[[31miConomyCurrency^[[0m
    2011-09-03 12:35:29 [INFO] LWC: Loading SQLite^[[0m
    2011-09-03 12:35:29 [INFO] LWC: Using: Native^[[0m
    2011-09-03 12:35:29 [INFO] LWC: Precached 2564 protections.
    2011-09-03 12:35:29 [INFO] LWC: At version: 3.42 (b154)
  31. Offline


    I am getting this error when I did a fresh install of LWC-Economy 1.30

    2011-09-04 00:14:51 [SEVERE] Error occurred while enabling LWC-Economy v1.3 (Is it up to date?): null
        at com.griefcraft.bukkit.LWCEconomyPlugin.init(
        at com.griefcraft.bukkit.LWCEconomyPlugin.onEnable(
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(
        at org.bukkit.craftbukkit.CraftServer.loadPlugin(
        at org.bukkit.craftbukkit.CraftServer.enablePlugins(
        at net.minecraft.server.MinecraftServer.e(
        at net.minecraft.server.MinecraftServer.a(
        at net.minecraft.server.MinecraftServer.init(

Share This Page