Inactive [SEC/MECH] LWC v4.1.1 :: Lightweight Protection for Chests, Furnaces, Dispensers, and more! [1.2]

Discussion in 'Inactive/Unsupported Plugins' started by Hidendra, Jan 17, 2011.

  1. Offline

    Hidendra

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


    DevBukkit
    Using LWC

    [​IMG] Modules
    Modules are seperate plugins much like LWC but extend LWC in some way, usually by giving extra functionality. While there may be more than already listed here, these modules are ones that are officially supported by LWC and maintained by the same author (Hidendra).

    [​IMG] LWC-Economy 1.30 - [​IMG] Download
    Configuration file: plugins/LWC/iconomy.yml

    LWC-Economy allows players to buy protections with economy money. At the moment, iConomy, BOSEconomy and Essentials are supported (have an Econ plugin that you want supported? PM me!) It can be configured on a per-user and per-group basis. It does not use Register.

    Aside from purchasing, when a user removes a protection, they will also be refunded what they initially paid for the protection.

    Discounts can also be given to each individual group, player, or by default. A discount is defined by giving X amount of protections for Y price, e.g 5 protections for free (0). After getting 5 protections for free, they pay full price again. They cannot get another discount again unless one of the following becomes true: a. an admin manually resets them b. the discounted amount of protections is increases (e.g increasing from 5 to 6 will mean said player gets 1 more for free) or c. the discount price itself changes (which means they will again get 5 protections for the new price.)


    What can be protected?
    • Chests
    • Dispensers
    • Furnaces
    • Doors
    • Signs
    • Trap doors
    • Anything else! Protections can be customized to anything you wish.

    Features
    • Plug 'n play! LWC handles all dependency resolution -- you just put LWC.jar in your plugins directory
    • Has reached a level where its routinely safe and stable.
    • Protections can be: Public, Password, and Private (by User and/or Groups)
    • If the block has a persistent inventory (ex. chest), LWC can protect it! (Unless the server owner disabled the protection of a specific block!)
    • Limits of how many protections a user or group can lock
    • Small memory footprint. No flat files.
    • For chests, only 1 side of the chest needs to be protected. The plugin saves space by dynamically linking connected chests as protected
    • Much, much more. This post would be extremely long if I were to post every feature LWC has to offer.

    Translations

    If your server would benefit more from a version of LWC in your native tongue, or you just want to do it because LWC is awesome, I'm open to allow translations to (almost any) language. Almost all LWC messages are editable.
    Locale files can be UTF-8, but are limited by Minecraft's charset (Latin-1.)

    The current and latest English locale can be found here:
    https://raw.github.com/Hidendra/LWC/master/src/lang/lwc_en.properties

    Currently, the following languages are officially bundled with LWC:
    • German - de - @Dawodo
    • Polish - pl - @Geoning @dudsonowa and @andrewkm
    • French - fr - @Cehel
    • Dutch - nl - @MadZero & @aoa2003
    • Czech - cz - @hofec
    • Swedish - sv - @christley
    • Russian - ru - @IlyaGulya - requires a Cyrillic font mod for the MInecraft client
    • Spanish - es - Raul " @RME " Martinez & David " @DME " Martinez
    • Danish - da - @TCarlsen

    Changelog (open)

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

    9/22/2011
    LWC 3.53
    • FIX: All Permission plugins will now work as they should. In SuperPerms, lwc.protect will default to true. if you are using Permissions 2/3/GroupManager/etc, lwc.protect will default to false

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

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

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

    9/16/2011
    LWC 3.49
    • FIX: Double console output

    9/15/2011
    LWC 3.48
    • 3.48 and 4.00 alphas can now be interchanged without receiving errors.
    • FIX: lwc.protect now defaults to true for SuperPerms, so Permissions 2/3 can be used without receiving Dave errors

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

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

    9/10/2011
    LWC 3.45
    • FIX: plugins/LWC/locale/lwc.properties (Locale override) could not create new key values such as grass, stone, etc.
    • Feature: The "nospam" mode now hides notices.
    • Feature: Double wooden doors will now also auto open when opening them. They must both be protected.

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

    9/3/2011
    LWC 3.43
    • NEW: Native PermissionsEx (PEX) support
    • NEW: /lwc admin purgebanned can now take -remove as an argument to also remove the removed blocks & item contents (e.g: /lwc admin purgebanned -remove)
    • FIX: An exception would be thrown when using /lwc admin cleanup while using SQLite
    • FIX: A Bukkit bug would throw an exception when a block was pushed above a chest via piston
    • FIX: The /permissions command on PermissionsBukkit 1.2 (not 1.1) was not working correctly.
    • The Polish localization has been updated courtesy of @Geoning

    LWC-Economy 1.30
    • NEW: Native Essentials Econ support
    • NEW: type: has been added to discounts (very latest iconomy.yml) to allow you to revert to the old way of how discounts were given (default: EXACT, old way: TOTAL)
    • NEW: Refunds can now be disabled by making iConomy.refunds false

    8/28/2011
    LWC 3.42
    • The flag "EXEMPTION" has been added to allow you to exempt flags from commands such as ADMIN PURGE and ADMIN EXPIRE; it prevents the protection from being removed unnecessarily. It can only be activated by LWC admins. Use /cexempt on or the usual /lwc flag exempt on
    • FIX: Some servers were experiencing a freezing issue on startup which is now fixed
    • FIX: Disabled modes were not properly disabled, despite being told the mode was disabled.

    8/26/2011
    LWC-Economy 1.21
    • FIX: On some servers LWC-Economy would not bootstrap itself into LWC correctly
    • LWC is unaffected, but due to how automatic provisioning works, the binary will be different from the last due it modifying the build number in /lwc admin version

    8/25/2011
    3.41
    • FIX: Servers with autoUpdate set to true would find 3.40 would crash all of the time due to a stackoverflow exception.
    • FIX: PermissionsBukkit /permissions command was unusable due to LWC making it load when the server first started, not when it normally would.

    8/25/2011
    LWC-Economy 1.20
    • LWC-iConomy.jar has now become LWC-Economy.jar -- please update accordingly.
    • BOSEconomy is now supported alongside iConomy. No extra setup is necessary for either!
    • Money paid for protections can now be refunded when you destroy the protection, even if the person who paid (the owner) is offline.
    • Discounts now give out the exact amount of protections for the discounted price. For example, if 'newCharge' is set to 0 and 'amount' is set to 5, a player will be able to create 5 protections for free after it takes effect.

    LWC 3.40
    • Almost all current LWC Module events have been deprecated. They have been replaced with events such as: `onProtectionInteract(LWCProtectionInteractEvent event)`
    • Fixed PermissionsBukkit compatibility: some commands did not work correctly
    • `/lwc admin cleanup` has accelerated to warp 5
    • Servers without any Permissions plugin would find anyone would have LWC Admin access
    • The mode "nospam" has been added to prevent protection creation messages from popping up (e.g "created protection successfully.") Use /cnospam or /lwc mode nospam, which toggles it on and off.
    • Protection history. LWC now logs all protection creations/destructions -- in the future, this may log chest access, but if it happens it will be a separate plugin such as LWC-Economy
    • -remove flags have been added to `/lwc admin expire` and `/lwc admin purge <player>` to remove the associated protection block. For example, if you use `/lwc admin purge -remove Hidendra`, it will remove all protections by Hidendra, and also all of the blocks protected in the world, along with any chest contents.
    • If LWC loses connection to MySQL, LWC will prevent access to chests until the connection is regained. This is to prevent stealing from chests if the connection is somehow lost and cannot be immediately regained.
    • Pistons can no longer destroy protected doors and so on.
    • Multitude of bug fixes and minor corrections
    • Minor optimizations

    3.31
    • PermissionsBukkit is now officially supported. LWC will still work on builds pre-1000
    • lwc.blockinventory has been renamed to lwc.deny - please take note
    • Fixed a bug where protections would be loaded from any world
    • Fixes to the Danish translation

    3.30
    • Added core.ignoreExplosions to core.yml to allow an admin to allow creeper explosions / TnT to destroy protections
    • Protections will now keep track of the last time they were interacted with
    • Added the command /lwc admin expire to allow you to expire protections that have not been used in so long. Example: /lwc admin expire 2 weeks
    • Added the command /lwc admin purgebanned to remove protections of every played in banned-players.txt
    • Added the command /lwc admin query to allow raw queries on the physical database
    • Drop transferring could not be disabled, it is now fixed.
    • Various bug fixes

    7/5/11
    3.21
    • Fix "fetch size" error
    • Removed the auto-removal of the very old players table

    7/4/11
    3.20

    • Very important bug fix for those who are using MySQL and prefixes. Prefixes will now work correctly and any issues arisen from MySQL usage should now be resolved
    • Fixed lang-defined block names being used in core.yml - protections instead of the english variant, otherwise all protections are broken.

    Credits
    • It's not all about me! I've tried my hardest and /lwc credits was the result. It turns out there is a lot more people I am extremely thankful to than can fit on one chat page, so instead it scrolls.
    • Many, many people helped with LWC in vastly different ways and it's impossible to credit every single person accurately, thus I missed a few people.

    Translations
    This update introduces three more languages: Russian, Spanish, and Dutch.
    • Russian - @IlyaGulya - requires a Cyrillic font mod for the Client
    • Spanish - Raul " @RME " Martinez
    • Spanish - David " @DME " Martinez
    • Dutch - @Tcarlsen

    Chunk corruption workaround
    • Have you ever noticed, when you /cinfo'd something, it said "That air is not registered"? Or when chests randomly stop working? If you get this a lot, you are most likely affected by an issue in Bukkit where chunks will mysteriously report Air (or some other block) for each block in the chunk. Please refer to this bug report on Leaky Bukkit: http://leaky.bukkit.org/issues/656
    • @morganm graciously found a way to workaround this issue, and it involves forcing every single protection to be cached and some other magical tidbits (without getting too technical.) To enable this, open up plugins/LWC/core.yml and then change bukkitBug656workaround to true. If you don't see it under core:, add it:
      Code:
          bukkitBug656workaround: true
      

    Behaviour
    • Trap doors are now available as a default protection for any new configurations: they will not automatically add themselves to existing LWC configurations
    • The default value for magnet.yml - perSweep has been changed from 20 to 40
    • The command /lwc debug has been added to test your permissions and show you precisely what you have access to
    • LWC now displays the git commit and Jenkins build (ci.griefcraft.com) in version strings (e.g /lwc admin version or /lwc admin report).

    6/16/11
    3.11
    • Translation: Swedish! Thank you @christley!
    • Bug fix for block placement

    6/16/11
    3.10
    • Translation: Czech! Thank you @hofec
    • The default value for core.showMyNotices has been changed to false (does not affect current installs.)
    • Burning furnaces have been fixed
    • Iron doors have been fixed
    • Redstone fix
    • Fixed auto register allowing registrations without having lwc.protect
    • Feature: auto openable Iron Doors. On by default -- iron doors (including double doors) will open (or close) when you click them provided they are both protected and you have access to them. "openAndClose," which closes the door automatically after x seconds (3 by default) is available but currently may not work as expected (works oppositely for doors facing North or South; doors will stay open.)
    • Trap doors (aka hatches) have been added to the default protection list. However, if you have an existing core.yml, and want trap doors, you either need to delete core.yml and restart the server (thus redownloading it) or adding trap_door to protections.blocks, e.g
      Code:
              trap_door:
                  enabled: true
                  autoRegister: off
      

    6/11/11
    3.06
    • Sign names have been normalized to "Sign" (e.g Wall sign and Sign post are shown as just Sign)
    • Added locale values for "you" and block names (chest, furnace, dispenser, wooden_door, iron_door, and so on.) Custom block names can be defined if you have custom protections.
    • Dutch translation -- thank you to @MadZero and @aoa2003

    6/08/11
    3.05
    • Notices will be shown correctly to admins when showMyNotices is disabled.

    6/08/11
    3.04
    • Limit the amount of queries the Magnet module can use (can be changed with magnet.perSweep, default 20. Delete magnet.yml to auto-regen it). On larger worlds, this was a severe issue
    • magnet.enabled now works correctly

    6/07/11
    3.03
    • MySQL prefix is now working as it should
    • Minor fix with the cache update in 3.02

    6/07/11
    3.02
    • Cache null protections as well, to prevent massive redstone spam

    6/07/11
    LWC 3.01

    Thank you so much to the many, many people who provided feedback and suggestions on 3.00.
    This changelog may be incomplete as I probably missed some obscure changes.

    Translations
    The following languages are now available in LWC:

    Lists support
    • LWC supports the Lists plugin which allows you to create a list for your protections to use. Anyone in this list attached to the protection can access your protection
    • When modifing/creating the protection, use l:ListName or list:ListName, e.g: /cmodify l:Test or /cprivate l:Test

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

    Limits
    • The old in-database limits has been fully removed. It is replaced by an on-disk alternative, limits.yml. This very easily allows much more in-depth limits management (e.g only: 5 chests, 2 furnaces, 0 doors)

    Custom protections
    • It is now extremely easy to create your own custom protections, or remove existing ones (core.yml -> protections:). For example, this is how you would make Note Blocks protectable, and allow people to play them (But not change the note!):
    Code:
            note_block:
                enabled: true
                ignoreLeftClick: true
    

    API
    • [I hope] final major revision to the LWC Api. New additions will allow other plugins to hook into LWC much more easily and do things that were not possible before. Features can be seamlessly integrated into LWC as if they were in LWC itself.
    • PhysDB.getPrivateAccess is now deprecated -- please use protection.getAccess instead!
    • Protections can be more easily modified utilizing methods in their objects: save() (queued save), saveNow(), remove(), removeCache() (just removes the protection from the cache, not the database), and update() (just updates the cached protection, save()/saveNow() already does this)

    LWC Modules
    • Modules can be thought of as a plugin inside LWC itself -- more or less they will change LWC's behaviour in some way, depending on the module.
    • Very easily implemented by developers: cancel protection registrations, cancel that damn protection message, and way more! More info on the wiki.

    Admin customization
    • There are now a ton of permissions nodes; there is one for each admin command. For example, for every Admin command, you could use: lwc.admin or lwc.admin.*. For just "find" and "forceowner", you could give a group/player the following: lwc.admin.find and lwc.admin.forceowner. Full list on the wiki.
    • Please note that lwc.admin.* only grants all Admin commands; lwc.admin still has a higher authority over the former (e.g, lwc.admin is considered the owner of any protection, while lwc.admin.* is not !!)

    Player customization
    • Like the admin commands, the main LWC commands can now be customized via permissions. lwc.protect still functions the same (all functionality); some examples of new nodes are: lwc.create or lwc.create.* (create anything), lwc.create.private (only be able to create private protections), lwc.info (/cinfo), lwc.modify (/cmodify), lwc.unlock (/cunlock), and so on. Full list on the wiki.
    • Please note that without lwc.protect, you need to manually assign flags. E.g: lwc.flag.* or lwc.flag.redstone / lwc.flag.magnet

    Magnet flag
    • The chest will act as a magnet and suck up nearby items (within a 3 block radius.) This can be very useful for automatic farms (e.g animals or crops.) It is compatible with double chests.
    • Can also specify items that these special chests will not pick up (in magnet.yml)
    • Compatible with Double Chests

    iConomy
    • It is now possible to sell protections with the fully optional LWC-iConomy bridge module. You just throw LWC-iConomy.jar into your plugins folder and then edit iconomy.yml in plugins/LWC/ when it's generated on the next startup!
    • You can also allow players to have a certain amount of protections at a reduced price (or even free) e.g free protections while you have less than 5 (but regular price after that.)

    Performance
    • LWC now does major caching of protections in memory. Previously, LWC hit the database everytime a protection is opened; now they are routinely stored in cache without a huge hit on memory usage (very minimal.) It can be increased from the default of 10000 if you wish in core.yml (core.cacheSize). More will most likely be cached in the future
    • Access rights are now stored with Protections (for the curious, it uses an OUTER JOIN, so just 1 query.)
    • Protections are precached (as many as possible) when the server is started
    • Lots of bug fixes (mostly miscellaneous.)

    Other
    • MySQL prefix can now be configured (if you change it with an existing MySQL install, it will fix that automatically, don't worry!)
    • /cpersist or /lwc mode persist now acts as a toggle for the mode
    • Added the following aliases: /cpersist , /cdroptransfer , /cmagnet , and /cadmin
    • /climits displays your protection limit and how many protections you have protected.
    • Minor changes all around

    Cheers

    4/18/11
    2.31
    • Security bugfix regarding an issue in minecraft itself (thanks sycot)

    4/09/11
    2.30
    • Native German translation! If you wish to use LWC in German, please change "locale" in lwc.properties to de. Many thanks to @Dawodo for doing the translation!
    • /lwc admin cleanup will now show the correct values instead of variable names when outputting results
    • enforce-worldguard-regions is now compatible with WorldGuard 5.x
    • Redstone is now changed again. All set redstone flags are reset. Redstone will obey the deny-redstone config value (which is false by default), meaning if it is set to false, you need to explciitly set the flag to disable redstone (/lwc flag redstone on), and if it is set to true, all doors prevent redstone by default so you need to set the flag to allow redstone.

    4/06/11
    2.21
    • Minor bug fixes

    4/06/11
    2.20
    • By default, redstone WILL NOT open doors (at the moment, it appears dispensers are unaffected, hopefully they will be fixed in CraftBukkit). In order to allow redstone to open your door, you need to issue this: /lwc flag redstone on. Using /lwc flag will show you the available protection flags -- these are "switches", only on/off (only redstone flag exists at the moment)
    • Bug fix: Protections will auto protect themselves again when being placed

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


    enjoy, gents
     
  2. Offline

    diegokilla

    Every single word in that post was WAY over my head :p It's np though, my users have been doing it themselves without too many complaints :D
     
  3. Offline

    Hidendra

    Haha, alright :)
     
  4. Offline

    JakeSheppard

    Hey,

    your plugin needs to be updated to the newest bukkit version (after update i get this message):

    Code:
    Feb 7, 2011 1:04:10 PM org.bukkit.plugin.SimplePluginManager callEvent
    SEVERE: Could not pass event BLOCK_INTERACT to LWC
    java.lang.NoClassDefFoundError: com/nijiko/permissions/PermissionHandler
            at com.griefcraft.lwc.LWC.isAdmin(LWC.java:401)
            at com.griefcraft.lwc.LWC.canAccessChest(LWC.java:869)
            at com.griefcraft.lwc.LWC.enforceAccess(LWC.java:159)
            at com.griefcraft.listeners.LWCBlockListener.onBlockInteract(LWCBlockLis
    tener.java:68)
            at org.bukkit.plugin.java.JavaPluginLoader$21.execute(JavaPluginLoader.j
    ava:225)
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav
    a:60)
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j
    ava:214)
            at net.minecraft.server.BlockFurnace.a(BlockFurnace.java:76)
            at net.minecraft.server.ItemInWorldManager.a(ItemInWorldManager.java:121
    )
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:483)
            at net.minecraft.server.Packet15Place.a(SourceFile:57)
            at net.minecraft.server.NetworkManager.a(SourceFile:232)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:71)
            at net.minecraft.server.NetworkListenThread.a(SourceFile:104)
            at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:310)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:225)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:512)
     
  5. Offline

    Hidendra

    No, on the latest version it is fine (for me, anyway?). Is your Permissions plugin out of date?
    --- merged: Feb 8, 2011 5:37 AM ---
    Anyone want to shed their opinion?:

    http://lwc.griefcraft.com
    Username is admin and the password is also admin. Not all the current features are there, just the gist of them ;). Finally got to work on it more! All of it is actual data from my local MC server

    If you notice, when viewing inventories you can click on them and the slot will turn to red. I'm going to work it probably tomorrow so that it will actually be possible to remove specific items from an inventory. It disappears, essentially!

    Dispensers also won't appear there. Inventories aren't supported for dispensers in Bukkit yet, however I did put a pull request (irrelevent for you guys though given that it isn't released :p)
     
  6. Offline

    Etalyx

    Clearly I am doing something incorrectly because I installed this plugin like every other and cannot get a single command to work. I have v254 and Permissions 2.0 set up as I believe it should be but I cannot get any of the /lwc commands to work. None of them do a thing except say that I attempted to use a command in the console. Not even denied. Thanks for any help.
     
  7. Offline

    Hidendra

    Do you have lwc.protect added to the groups that should be able to protect with the Permissiosn plugin?
     
  8. Offline

    Etalyx

    Code:
        Members:
            default: false
            info:
                prefix:
                suffix:
                build: true
            inheritance:
                - Default
            permissions:
                - 'essentials.whois'
                - 'essentials.realname'
                - 'essentials.compass'
                - 'essentials.msg'
                - 'essentials.mail'
                - 'essentials.mail.send'
                - 'lwc.mod'
                - 'lwc.protect'
    I'm the admin so I have the appropriate inheritance and also the '*' permission. Thanks for your quick response.
     
  9. Offline

    ben62224

    There is a problem you can open the door secures with the redstone
     
  10. Offline

    feverdream

    But you can detect if they try to tell them something is private, or locked, etc.. looking at the code you have everything you need to detect intent to look in a chest that is not theirs.
     
  11. Offline

    sicksurfer123

    When i try to do this on my server and type /lwc it will say you do not have permission but i am the admin and i have all commands with the ' *' or whatever it is but i also gave myself all three permissions and it still doesnt work
     
  12. Offline

    holyurethra

    hey guys! i need some help, i just downloaded the most current version of bukkit today, and I downloaded this from this page. I put the .jar file into my plugins folder, and it doesn't work! any help would be greatly appreciated!
     
  13. Offline

    GEN3RIC

    What's the point when they can just break the chest? It does keep them from getting into it though.
     
  14. Offline

    Hidendra

    They can't. Are they doing something to break it? Another plugin, perhaps?

    Why? Are there errors in the console?

    Are you using the permissions plugin? What does your config.yml for it look like?

    But it seems sort of harsh to just outright ban them if they open the chest, no?
     
  15. Offline

    feverdream

    Not at all. And as the owner of a server, I want that power. If somebody is so dishonest that they are willing to go into other peoples houses when the server rules say not to, and look in other peoples chests when the server rules say not to, I want a way to enforce these rules and punish the person breaking them... even if I only have one chest on the entire server that is rigged this way as a decoy, sitting next to spawn. After all, we criminalize breaking and entering into somebody's home in real life, why cant I do it in minecraft?
     
  16. Offline

    GEN3RIC

    Hmm. If they aren't supposed to be able to, I've got some sort of issue with CB. I'm going to try some other builds and see what happens.
     
  17. Offline

    Nakin

    Hello,
    Sorry for my English, I'm French.
    I installed the plugin and I put in my plugin folder.
    I also have the plugin permissions which I am admin.
    The plugin have to start since I have access to any commands.
    I then slaps /cpassword test and make a left click on a box.
    The success message is displayed correctly and the information by typing /lwc info.
    But anyone can open the safe in question without typing the password.
    I myself disconnected / reconnected, I have no problem opening the trunk.
    I tried reinstalling. Reboot server. Nothing helps. The chest is still open access.
    Can you help me?
    Thank you in advance.
    PS: Other recent walk plugin: McBane, Myhome, General, Permissions, MsgReply.
     
  18. Offline

    Hidendra

    Fair enough. Then I don't see why not, I'll do it tomorrow

    Alright

    Are the others that are trying to open the chest an lwc admin (aka have * perms, lwc.admin perms, or even an OP)? If they are, they won't be asked for the password
     
  19. Offline

    GEN3RIC

    Just thought I'd update you, I went to b288 and it does not allow them to break them. That is how I expected it to work and I'm sorry I didn't know any better earlier! Good job on the plugin.
     
  20. Offline

    Josch

    Could you implement a message if a Admin opens a protected chest? Just a short "Chest protected" or something like that popping up.
     
  21. Offline

    Nakin

    Thank you very much, it works for normal players. But is it possible for these
    players (no ops, no admins) to have a private safe even for admins / ops?
     
  22. Offline

    scar413

    i also would love to see this.

    btw, is it possible that all chests are by default private protected? i mean, if you put a chest down, its automaticlly private to you?
     
  23. Offline

    DelaDrago

    hey

    i got a question about settings groups with /lwc -c private g:groupname

    i use permission mod on my server so i set some user groups like Member so i did /lwc -c private g:Member but people wich are in this permission group cant open the door. did i make something wrong?

    sorry for that bad english im from germany

    greetz drago
     
  24. Offline

    errdivideby0

    I know this probably isn't the best place to be asking this, but since it pertains to the installation of the plugin I'll go ahead and as it here. My server doesn't have sqlite or mysql installed on it but I want to use this plugin. I'm running a linux server, how would I go about installing sqlite so I can use this?
     
  25. Offline

    Ugarte

    Is there a permission to grant players the ability to unlock password chests but not create them?
    I know in hMod I could accomplish this with a limits command, and set the chest limit of groups to 0.
     
  26. Offline

    Hidendra

    /lwc -a limits 0 -global

    You don't need to do anything. SQLite is standalone and LWC will literally do everything for you. All you do is put it in the plugins folder and [re]start the server

    Seems i forgot to add groups for protection rights. It'll be in the next version

    I don't see why not. I'll add a config option next release for that (and it will most likely default to do this by default)

    The only solution I can see is don't give lwc.protect to admins and change op-is-lwcadmin to false. If you're using permissions, then manually give just you (or a group that is meant to do anything) lwc.protect

    PS Death Note is awesome :)

    Noted for the next version

    Alright, great news :D
     
  27. Offline

    feverdream

    Looking forward to the update, if there is anything I can do to help just ask.
     
  28. Offline

    ganzor

    Strange, users on my server were randomly starting on fire while underground when this plugin was enabled. I was running LWC 1.491 with CraftBukkit #289 - disabling LWC gets rid of the problem.
     
  29. Offline

    tygreen19

    can you please explain how groups work? i have tried creating groups but it seems like they dont really do anything? am i missing something?
     
  30. Offline

    generalmek

    1)how i can disable pass protection on server? i want make only private or free.
    2) any can destroy my chests with tnt :(
    3) ppls hate wright commands for every self chests, can you add function into properties fail all chests who install them is private by default?

    thank you. but 1 problem ppls don't want and dont want know commands
     
  31. Offline

    Hidendra

    LWC cannot start fires. ;)
    Perhaps you have an outdated version of CB?

    The "group" is the group in the Permissions plugin.

    1. At the moment not possible, at some point there will be something in place
    2. Is your CraftBukkit outdated? Try updating. I just tried and I can't destroy chest with TNT, it's an issue with your CB
    3. The next version will have this
     

Share This Page