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

    Noxes

    Here ya are, installed, same prob

    Its prob a simple mistake on my end; dunno
     

    Attached Files:

  3. Offline

    Hidendra

    Try replacing your config.yml with this:

    Code:
    # Supports "Default" and "GroupUsers"
    plugin:
        permissions:
            system: default
    
    ##
    # Groups can contain inheritance.
    #   To make a group inherit the permissions from another 
    #   group simply place the groups name in the "inheritance:" 
    #   field seperated by commas.
    #
    #   Example: inheritance: Default,Admins,
    ##
    #   All permissions including the asterisks must be placed in single quotes.
    #   like so:
    #
    #       - 'general.spawn'
    #
    #   Otherwise errors will happen!
    ##
    #   Globalized Permission settings:
    #
    #       If a permission contains periods (.) you can denote a globalized parameter:
    #
    #           - 'general.*'
    #
    #       This will allow you to use all general commands.
    #
    ##
    #
    #   Single Asterisk denotes all commands:
    #
    #       - '*'
    ##
    groups:
        Default:
            default: true
            info:
                prefix: 
                suffix:
                build: false
            inheritance: 
            permissions:
                - 'general.spawn'
    
        Builder:
            default: false
            info:
                prefix: '&1'
                suffix:
                build: true
            inheritance:
                - Default
            permissions:
                - 'general.time'
                - 'general.teleport'
                - 'general.teleport.here'
                - 'general.player-info'
                - 'mywarp.*'
                - 'myhome.*'
                - 'essentials.kit.*'
                - 'lwc.protect'
    
        Admins:
            default: false
            info:
                prefix: '&4'
                suffix:
                build: true
            inheritance:
                - Builder
            permissions:
                - '*'
    
    
    ##
    # DarkGrave has control over all commands.
    # sk89q can use /spawn & /time
    ##
    users:
        Noxes:
            group: Admins
            permissions:
        Vetrina:
            group: Admins
            permissions:
        Deathmaaka:
            group: Admins
            permissions:
    #
        TehNyss:
            group: Admins
            permissions:
        Vidari:
            group: Builder
            permissions:
        R3mix3d:
            group: Builder
            permissions:
        ~bcwfs:
            group: Builder
            permissions:
        leelee:
            group: Builder
            permissions:
    
     
  4. Offline

    Noxes

    Lol that sure clears up a lot of my permissions.yml lol...

    However the problem still occurs :/
     
  5. Offline

    4o66

    *** Critical Issue ***

    I checked the last few pages and din't see this mentioned. Sorry if it is a repeat.

    An LWC protected door can be opened by an unauthorized user by using levers, buttons, pressure plates, or redstone.
     

  6. Thank you!
     
  7. Offline

    AntonyDream

    234 kb

    Now I have this
    Code:
    LWC     [1,491] Loaded command: /lwc -admin
    LWC     [1,491] Loaded command: /lwc -create
    LWC     [1,491] Loaded command: /lwc -free
    LWC     [1,491] Loaded command: /lwc -info
    LWC     [1,491] Loaded command: /lwc -p
    LWC     [1,491] Loaded command: /lwc -modify
    LWC     [1,491] Loaded command: /lwc -unlock
    LWC     [1,491] -> PLAYER_QUIT
    LWC     [1,491] -> ENTITY_EXPLODE
    LWC     [1,491] -> BLOCK_INTERACT
    LWC     [1,491] -> BLOCK_DAMAGED
    LWC     [1,491] Dev mode: FALSE
    LWC     [1,491] Using Nijikokun's permissions plugin for permissions
    06.02.2011 20:16:42 org.bukkit.craftbukkit.CraftServer loadPlugins
    SEVERE: com/nijikokun/bukkit/Permissions/Permissions (Is it up to date?)
    java.lang.NoClassDefFoundError: com/nijikokun/bukkit/Permissions/Permissions
            at com.griefcraft.lwc.LWC.load(LWC.java:291)
            at com.griefcraft.lwc.LWCPlugin.onEnable(LWCPlugin.java:292)
            at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:135)
            at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader
    .java:384)
            at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManage
    r.java:175)
            at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:64)
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:45)
            at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:156)
            at net.minecraft.server.MinecraftServer.c(MinecraftServer.java:143)
            at net.minecraft.server.MinecraftServer.d(MinecraftServer.java:104)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:186)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:512)
    Caused by: java.lang.ClassNotFoundException: com.nijikokun.bukkit.Permissions.Pe
    rmissions
            at java.net.URLClassLoader$1.run(Unknown Source)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.net.URLClassLoader.findClass(Unknown Source)
            at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.
    java:30)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            ... 12 more
     
  8. Offline

    Hidendra

    Forgot to edit my post. 254 seems to be working fine for me with everything I've tested

    is Permissions corrupt?

    At the moment there isn't an exactly simple way to find who used redstone to open a door. I'm still looking for a valid solution

    Weird. Are you using a version at least version 232 of CraftBukkit?
     
  9. Offline

    JakeSheppard

    hey,

    i am the chest password guy... i mean can you automaticly unlock all the chests with the same passwort when i enter the /lwc -u passwort comamnd...
     
  10. Offline

    Hidendra

    Ah. at the moment it isn't possible.


    PS: You can now view who has access to a chest if you download the latest release, which is still 1.491. It's still fairly basic, but the command is /lwc -o or /lwc -owners. it will probably change to something that sounds better.

    If you happen to have more than 15 people on a protection, you can view the next page with /lwc -o [page], ie /lwc -o 2
     
  11. Offline

    darknesschaos

    Can I request a toggleable function that with certain settings you can go around locking multiple chests with that one command? (I usually have many chests to lock)
     
  12. Offline

    Zayadaslaya

    Thanks a TON for the plugin, it's so helpful to me and my players in every way all the time, but I recently ran into a problem.

    After updating to the most recent bukkit build, I got this error. Now nobody (including me, the owner) can use any /lwc commands. Please help! I really do appreciate your time.

    I will also post my permissions file if needed.

    Code:
    2011-02-06 13:39:36 [INFO] Starting minecraft server version Beta 1.2_01
    2011-02-06 13:39:36 [INFO] Loading properties
    2011-02-06 13:39:36 [INFO] Starting Minecraft server on *:25565
    2011-02-06 13:39:36 [INFO] Preparing level "New Map"
    2011-02-06 13:39:36 [INFO] Preparing start region
    Preparing spawn area: 40%
    Preparing spawn area: 60%
    Preparing spawn area: 93%
    [ArrowTurrets] Config loaded!
    2011-02-06 13:39:39 [INFO] [General] version [2.0] (Mafia) loaded
    2011-02-06 13:39:39 [INFO] [Healthy] version [1.0] (Apple) loaded
    2011-02-06 13:39:39 [INFO] [iChat] version [1.3] (Jack Frost) loaded
    2011-02-06 13:39:39 [INFO] [iConomy] version [2.2] (Aime) loaded
    LWC     [1.491] Loading shared objects
    Config  [1.491] Loaded 10 config entries
    Feb 6, 2011 1:39:39 PM org.bukkit.plugin.SimplePluginManager loadPlugins
    SEVERE: Could not load plugins\LWC.jar in plugins: null
    org.bukkit.plugin.InvalidPluginException
            at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.j
    ava:83)
            at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.
    java:117)
            at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager
    .java:82)
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:43)
            at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:153)
            at net.minecraft.server.MinecraftServer.c(MinecraftServer.java:140)
            at net.minecraft.server.MinecraftServer.d(MinecraftServer.java:104)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:177)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:512)
    Caused by: java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou
    rce)
            at java.lang.reflect.Constructor.newInstance(Unknown Source)
            at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.j
    ava:81)
            ... 8 more
    Caused by: java.lang.NoSuchMethodError: com.griefcraft.util.Updater.getOSSpecifi
    cFolder()Ljava/lang/String;
            at com.griefcraft.lwc.LWCPlugin.<init>(LWCPlugin.java:94)
            ... 13 more
     
  13. I have a problem with LWC (installed ALL plugins new tonight)

    Running Permissions 2.0 and latest LWC

    I can access the lwc command and put a protection on a chest.
    If I do '/lwc -i' the results are

    ID: 1
    Type: Private
    Owner: ElgarL
    Location: {24, 63, -236}
    Date created: 2011-02-06 18:52:25.593

    The problem is everyone can access it. Even people who are not able to access the /lwc command.
    There's no errors on the server start up, or during it's operation.

    EDIT:
    Just to point out, Thsi is my first time ever of getting a minecraft server running with bukkit.
    Working plugins I'm certain of so far are :-

    Essentials
    Whitelist

    My Permission config.yml is as follows
    Code:
    # Supports "Default" and "GroupUsers"
    plugin:
        permissions:
            system: default
    
    ##
    # Groups can contain inheritance.
    #   To make a group inherit the permissions from another
    #   group simply place the groups name in the "inheritance:"
    #   field seperated by commas.
    #
    #   Example: inheritance: Default,Admins,
    ##
    #   All permissions including the asterisks must be placed in single quotes.
    #   like so:
    #
    #       - 'general.spawn'
    #
    #   Otherwise errors will happen!
    ##
    #   Globalized Permission settings:
    #
    #       If a permission contains periods (.) you can denote a globalized parameter:
    #
    #           - 'general.*'
    #
    #       This will allow you to use all general commands.
    #
    ##
    #
    #   Single Asterisk denotes all commands:
    #
    #       - '*'
    ##
    groups:
        Default:
            default: true
            info:
                prefix:
                suffix:
                build: true
            inheritance:
            permissions:
                - 'general.spawn'
                - 'lwc.protect'
                - 'essentials.*'
        Moderator:
            default: false
            info:
                prefix: &1
                suffix:
                build: true
            inheritance:
                - Default
            permissions:
                - 'general.time'
                - 'general.teleport'
                - 'general.teleport.here'
                - 'general.player-info'
        Admins:
            default: false
            info:
                prefix: &4
                suffix:
                build: true
            inheritance:
                - Moderator
            permissions:
                - '*'
    
    ##
    # DarkGrave has control over all commands.
    # sk89q can use /spawn & /time
    ##
    users:
        elgarl:
            group: Admins
            permissions:
        sk89q:
            group: Default
            permissions:
                - 'general.time'
     
  14. Offline

    Hidendra

    You can :D
    Code:
    /lwc -p persist
    
    then just use whatever command and you can use it over and over (for example, could then use /lwc -c private then click all your chests)

    Update your plugins as well. Most specifically, BigBrother if you have it (to 1.5). Yes, that IS why you're getting the error.

    Are you using the latest LWC and latest CraftBukkit?
     
  15. Yep, latest downloaded minutes ago.
    --- merged: Feb 6, 2011 7:42 PM ---
    Fixed. I just noticed the players who we're testing we're ops.
     
  16. Offline

    AntonyDream

    I don't think so, other plugins works fine with permissions, but when I put LWC in plugins folder I get this error..
     
  17. Offline

    Hidendra

    Are you using the latest version? If so, try 1.9, maybe I'm the one who is outdated
     
  18. Offline

    Zydox

    Could you add the abillity to lock Jukeboxes as well?
     
  19. Offline

    darknesschaos

    @Hidendra I think I love you for that <3
     
  20. Offline

    megabytes

    Would it be possible to add the item/block ID to the database? We had our server running for a few days with an older copy of the config without signs/doors blacklisted and a few added protections to their signs/doors. I tried to manually remove the protections from the DB, but couldn't find anything referencing the block type.
     
  21. Offline

    Hidendra

    Perhaps

    In (or probably before, to get it prepared) 1.5 the block ID will be stored in the database.
     
  22. Offline

    megabytes

    Sounds great! Will missing block IDs be filled in once its implemented?
     
  23. Offline

    Hidendra

    Yup. I'll need them for the web panel
     
  24. Offline

    feverdream

    I'm officially requesting a "BAN_THE_THIEF" type chest that bans anybody attempting to take from it that is unauthorized. Looking at the code, it would not be hard to add to this plugin.
     
  25. Offline

    AntonyDream

    1.9 doesn't help :<
     
  26. Offline

    diegokilla

    update: i finally got it to work after i set autoupdate=true, even though i had reDL derictly from here a couple times thanks again for the sweet mod hidendra :D

    edit: however i havent tested using grps from permissions yet, gonna get rite on it tho
     
  27. Offline

    Hidendra

    A cool idea, but still limited by the weakest link ,, bukkit does not yet (officially) have inventory transaction hooks

    What other plugins are you using?

    Good to hear :)
     
  28. Offline

    diegokilla

    @Hidendra: Is there anyway to remove protections that are over the limit for a user?
    ie: after i got limits implemented (as well as worldguard adherence) any chests that were already locked stayed locked, which is nice and saves me the headache of crybaby users, however i am giving my users a few days to clear out there over the limit chests before i go through torching all the over the limit/outside worldgurad ones. is there any ways to go and get rid of thes protections without getting rid of ALL protections?

    sry if that was a bit rambly :p
     
  29. Offline

    AntonyDream

    Plugins: ARC Teleport, Authorization, BigBrother, BorderGuard Lite (Round), Essentials, HeroBounty, iConomy, LightVote, LoginMessage, Permissions, PlantSpreader, SpawnHealth, TreeHugger, WarpGate, WorldEdit, WorldGuard
     
  30. Offline

    Hidendra

    Well, in LWC via the server? No. Using a SQL query on the database yourself? With a little bit of work (a lot less than manually checking people and you won't get as many complaints as removing everyone's protections), yeah.

    If you have Shell access to the server in question, I could type something up, it'd only take a few minutes to remove protections that are over the limit.
    If you're on linux, make sure you have "sqlite3", and if you're on windows, you may need some kind of sqlite tool, I'm not sure of any off the top of my head, I know cygwin would work fine if you happen to have it.

    @AntonyDream Does LWC start fine if you have just Permissions and LWC in the folder?
     
  31. Offline

    Josch

Share This Page