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

    flametornado

    Hi,

    I was wonder why you have a Jobs table in your database.
     
  3. Offline

    nepal7

    Hi, this plugin is very nice but I noticed that when I use pressure plates, button and lever the doors the protected doors can be opened by everyone :(
    is there anything to prevent this?
    thanks for answer.

    PS: sorry, my english is a little bit crappy...
     
  4. Offline

    fitzpatrick123

    sure
    Code:
    # System is no longer used, but may become used in the future
    # Copies is for multiple-world support
    #   Put the name of the world you wish for it to be a clone of, otherwise leave it empty.
    #   If this file is for your default world (the one in server.properties) then you must
    #   leave copies blank.
    #  Example: copies: Derp    -  This will clone the permissions of the world Derp
    #
    # Make sure to rename this file to the name of the world that is in sever.properties under
    # level-name.  So if it is level-name: world  then this should be world.yml and in the 
    # plugins/Permissions directory (ie. plugins/Permissions/world.yml)
    #
    # NOTE: Do not use tabs while editing this document.  Use only spaces.  A good way to avoid
    # doing this is to use Notepad++ and replace the tab with 4 spaces.
    plugin:
        permissions:
            system: default
            copies: 
    
    ##        
    # AntiBuild is included with this.  To disable a group from being able to build then
    # set the build: flag to false (build: false).  If you want a group to be able to build
    # then set it to true. 
    ##
    # Groups can contain inheritance.
    #   To make a group inherit the permissions from another
    #   group simply place the groups name in the "inheritance:" like so:
    #
    #   Example:
    #       inheritance:
    #           - Default
    ##
    #   All permissions including the asterisks must be placed in single quotes.
    #   like so:
    #
    #       - 'foo.bar'
    #
    #   Otherwise errors will happen!
    ##
    #   Globalized Permission settings:
    #
    #       If a permission contains periods (.) you can denote a globalized parameter:
    #
    #           - 'foo.*'
    #
    #       This will allow you to use all general commands.
    #
    ##
    #   Single Asterisk denotes all commands:
    #
    #       - '*'
    #   If you give a group this permissions, do not have the group inherit any permissions
    #   from other groups.  Any users assigned to this group should NOT be given any additional
    #   permissions either.
    ##
    #   To exempt a node use the - prefix like so:
    #       - '-foo.bar'
    ##
    #   prefix: and suffix: do not do anything on their own.  You need another outside plugin
    #   such as iChat or HeroChat in order for these to do anything.
    groups:
        Default:
            default: true
            info:
                prefix: ''
                suffix: ''
                build: false
            inheritance:
            permissions:
                - 'foo.bar'
                - 'lwc.protect'
        Moderator:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
                - Default
            permissions:
                - 'bar.foo'
        Admin:
            default: false
            info:
                prefix: '&cAdmin'
                suffix: 'Admin'
                build: true
            inheritance:
            permissions:
                - '*'
    ##
    # Users denote which users are included in which group.
    # TheNo1Yeti is in the Admin group
    # Herpina is a member of the Moderator group but also has access
    # to the herp.derp permissions
    # Derpina is a member of the admin group but does not have access
    # to the derp.derp permission node
    # Users can also have a prefix and suffix as seen with Herpina
    ##
    users:
        fitzpatrick123:
            group: Admin
            info:
                prefix: ''
                suffix: ''
            permissions:
                - 'lwc.*'
        allemeinentchen:
            group: Admin
             info:
                prefix: ''
                suffix: ''
            permissions:
                - 'lwc.admin'
    
    
    
    
     
  5. Offline

    Mayban36

    On the groupmanager folder, the group YML have this:
    Code:
    groups:
      Default:
        default: true
        permissions:
        - essentials.help
        - essentials.home
        - essentials.motd
        - essentials.sethome
        - essentials.spawn
        inheritance: []
        info:
          prefix: ''
          build: false
          suffix: ''
      SemiAdmin:
        default: false
        permissions:
        - +groupmanager.mandemote
        - +groupmanager.manpromote
        - -groupmanager.*
        - '*'
        inheritance:
        - moderator
        info:
          prefix: '&c'
          build: true
          suffix: SemiAdmin
      RedFaction:
        default: false
        permissions: []
        inheritance:
        - peasant
        info:
          prefix: '&c'
          roles-category: faction
          build: true
          suffix: Red
      Farmer:
        default: false
        permissions:
        - essentials.kit
        - essentials.kit.farmer
        - essentials.spawnmob
        inheritance: []
        info:
          roles-requirement:
          - BlueFaction
          - RedFaction
          prefix: ''
          roles-category: job
          build: false
          suffix: ''
      Healer:
        default: false
        permissions:
        - essentials.kit
        - essentials.kit.healer
        - essentials.heal
        inheritance: []
        info:
          roles-requirement:
          - BlueFaction
          - RedFaction
          prefix: ''
          roles-category: job
          build: false
          suffix: ''
      Fighter:
        default: false
        permissions:
        - essentials.kit
        - essentials.kit.fighter
        inheritance: []
        info:
          prefix: ''
          roles-category: skill
          build: false
          suffix: ''
      Admin:
        default: false
        permissions:
        - '*'
        inheritance:
        - semiadmin
        info:
          prefix: ''
          build: true
          suffix: ''
      Miner:
        default: false
        permissions:
        - essentials.kit
        - essentials.kit.miner
        - flashlight.regular
        inheritance: []
        info:
          roles-requirement:
          - BlueFaction
          - RedFaction
          prefix: ''
          roles-category: job
          build: false
          suffix: ''
      FlyingMan:
        default: false
        permissions:
        - nocheat.moving
        inheritance: []
        info:
          roles-requirement: Fighter&SuperCart
          prefix: ''
          roles-category: skill
          build: false
          suffix: ''
      Peasant:
        default: false
        permissions:
        - roles.joinrole
        - roles.leaverole
        - roles.myroles
        inheritance:
        - default
        info:
          prefix: '&e'
          build: true
          suffix: Peasant
      BlueFaction:
        default: false
        permissions: []
        inheritance:
        - peasant
        info:
          prefix: '&d'
          roles-category: faction
          build: true
          suffix: Blue
      Railer:
        default: false
        permissions:
        - essentials.kit
        - essentials.kit.railer
        inheritance: []
        info:
          roles-requirement: Miner
          prefix: ''
          roles-category: subjob
          build: false
          suffix: ''
      SuperCart:
        default: false
        permissions:
        - minecartmania.*
        inheritance: []
        info:
          roles-requirement: Railer
          prefix: ''
          roles-category: skill
          build: false
          suffix: ''
      Moderator:
        default: false
        permissions:
        - essentials.tp
        - essentials.tphere
        - essentials.item
        - essentials.give
        inheritance:
        - default
        info:
          prefix: '&c'
          build: true
          suffix: Mod
     
  6. Offline

    Hidendra

    could you pm me your server IP?

    Are you trying to give a group LWC protection powers? Or specific players? I don't see lwc.protect in your groups.yml

    Code:
    /lwc flag redstone on
    
    Then click your door :)

    It is deprecated and scheduled to be removed in 3.00 along with the tables inventory, players, and limits (along with other unused things)

    The jobs table was originally designed to execute actions remotely (e.g for a web panel that was done, have the ability to dispense a dispenser, change sign text, open a door, destroy a block to remove a protection, and so on).
    It was a good idea and worked very well, but I believe I do not want to contract myself to a larger scope than I envision LWC being.

    I've just did this and it's working great in the 3.00-alpha2 build -- I can fire it your way if you wish?

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

    d00ba

    Hi Hidendra,

    This Plugin is fantastic, thank you!

    Just wondering if you have any intention of allowing users to protect blocks anytime in the future?

    Regards,

    d00ba
     
  8. Offline

    Hidendra

    At the moment I have no plan to. LWC does one thing (generally) and it does it well -- I wouldn't want to force block protection down people's throats :)

    In 3.00, you will be able to create custom blocks that can be protected. While it won't be regions, it will still be just 1 block (Useful for diamond blocks? I don't know. Perhaps note blocks and other blocks). You would need to edit the new LWC config file to do so then -- no new blocks are added in 3.00 by default that can be protected.
     
  9. Offline

    Drei Gyuu

    Has anyone ever had a problem with the liquids in the game not flowing properly while using this mod?

    Any fix for it?

    It starts out fine for me, and then after a while the water will not flow properly anymore. like you put down water and even after you kill the source you still see the water that flow from the source still there sitting on the ground. and they wont go away. Normally water goes away after you kill the source.

    I always have to restart my server to fix this issue but it always comes back.
     
  10. Offline

    RustyDagger

    @Drei Gyuu I noticed the same problem the other day i doubt it is linked to LWC in any way Iv not had the problem since a restart.

    LWC From what i can tell dose not effect or touch water handling in any way.


    @Hidendra That would be awsome if ya could :)
     
  11. Offline

    andrewkm

    All is well here on latest RB [766] Thanks!
     
  12. Offline

    fitzpatrick123

    i started a seperate conversation with you i need your ingame name for the whitelist
     
  13. Offline

    Mayban36

    When I Put in permissions lwc.protect of any group, all lwc commands broke and doesnt work in all groups, the chat say: Internal error the commands doesnt work.
     
  14. Offline

    Drei Gyuu

    Apparently in my case the problem was because I lock the time, so the liquids in the game wont flow. It does make perfect sense. Just sharing the solution for those who had the same issue. and it has nothing to do with this plugin.
     
  15. Offline

    Hidendra

    Look in your console -- there's an error there waiting for you ;)

    Okay, will shoot you a PM now
     
  16. Offline

    Jaxter

    Guys, I was using LWC and it broke and people are breaking into others chests... Literally the protections just stop being there, or stop protecting chests and then if I restart server it'll be protected again. It then turns off after server's been on for a little while. I've checked server.log and I have 0 errors or anything on there and its starting to really freak me out to as to why this should ever happen!

    Like sometimes, when it'll stop working, all locked chests/doors wont be locked anymore and if I try to lock any it literally acts like the plugin isn't even there and the commands dont work. THEN I restart server and it is back again.

    I tried removing all plugins and trying just LWC and it still has issues. It is thee most frustrating thing I've ever seen. It didn't happen until just recently. It happens on any latest version of Bukkit, been running 740, tried 755 and 766 and both were the exact same. I dont know whats wrong with this :(.

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

    Hidendra

    Very sadly it is an issue in CraftBukkit (or even possibly Minecraft), and affects a lot of other plugins as well because of it.
     
  18. Offline

    Whitellama

    I am having the same problem as he/she is, where protection remains, but typing any LWC command in chat results in that standard internal error message. When you type commands, like /lwc in the console, the console responds perfectly, exactly like it should in game.

    When the server restarts, and when it gives an error to players in game, there is absolutely no error in the console. I am sure. If you want the logs, I can give them to you, but I just thought I might say I too am having this problem, and it's troubling the server.

    Thank you.
     
  19. Offline

    Gull06

    Is there a magic wand that can be used to create private permissions you click with it? If not can this be implemented in the next update because I have a crap load of chests and signs to protect haha.
     
  20. Offline

    MisanthropX

    @Hidendra
    Good morning, I really love this plugin and I like what you can do with it, but a huge issue is that people do not want to close everything, especially for doors.

    The Issue is that Some people make other doors private while they are offline,.. and then the admins have to go and unlock for them ._.

    I would like to have permission nodes for every single thing:

    • Chests
    • Dispensers
    • Furnaces
    • Doors
    • Signs
    thanks in advance
     
  21. Offline

    Mayban36

    Sorry, here are the error when i write /cprivate, /cremove or something:
    Code:
    19:29:35 [GRAVE] null
    org.bukkit.command.CommandException: Unhandled exception executing command 'cpri
    vate' in plugin LWC v2.31
            at org.bukkit.command.PluginCommand.execute(PluginCommand.java:37)
            at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:85
    )
            at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:2
    55)
            at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.
    java:677)
            at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:640)
    
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:634)
            at net.minecraft.server.Packet3Chat.a(Packet3Chat.java:32)
            at net.minecraft.server.NetworkManager.a(NetworkManager.java:195)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:74)
            at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
            at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:370)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:285)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:394)
    Caused by: java.lang.NullPointerException
            at org.anjocaido.groupmanager.permissions.NijikoPermissionsProxy.permiss
    ion(NijikoPermissionsProxy.java:241)
            at com.griefcraft.lwc.LWCPlugin.onCommand(LWCPlugin.java:199)
            at org.bukkit.command.PluginCommand.execute(PluginCommand.java:35)
            ... 12 more
    >
     
  22. Offline

    Whitellama

    :confused:

    I got 0 errors whatsoever, maybe there's a debug mode you activate for this stuff or something?
     
  23. I would like to request SQL table prefixing, lwc_actions, and so forth.
     
  24. Offline

    jamescosten

    Link to command wiki is broken :( So i dont even know how to use this lol
     
  25. Offline

    axeblade346

    The links are correct the wiki is just Offline atm.
    Its a wonderful plugin so I would like you to be able to use it.
    So the time being use the Google cache of the wiki pages.
    Get is by Google searching the full website name and clicking on cached.

    [​IMG]

    Install: http://webcache.googleusercontent.com/search?q=cache:qwPUHktcwhEJ:wiki.griefcraft.com/wiki/LWC/Installation http://wiki.griefcraft.com/wiki/LWC/Installation&cd=1&hl=en&ct=clnk&gl=za&source=www.google.co.za
    Commands: http://webcache.googleusercontent.com/search?q=cache:rDco69kBdogJ:wiki.griefcraft.com/wiki/LWC/Commands cache http://wiki.griefcraft.com/wiki/LWC/Commands&cd=1&hl=en&ct=clnk&source=www.google.com
    Permissions:http://webcache.googleusercontent.com/search?q=cache:cLIK-WHvc08J:wiki.griefcraft.com/wiki/LWC/Permissions http://wiki.griefcraft.com/wiki/LWC/Permissions&cd=1&hl=en&ct=clnk&source=www.google.com
    MySQL:http://webcache.googleusercontent.com/search?q=cache:Co1D65EbUagJ:wiki.griefcraft.com/wiki/LWC/MySQL http://wiki.griefcraft.com/wiki/LWC/MySQL&cd=1&hl=en&ct=clnk&source=www.google.com

    Hope this helps you figure out the plugin.

    On another note can someone please make use a banner for LWC
    here is my Bad version : <Edit by Moderator: Redacted mediafire url>

    I want to make an banner list of all the plugins we use on our server.
     
    Last edited by a moderator: Dec 15, 2016
  26. Offline

    irononreverse

    Hi, we've been using this plugin on our server and it has been working perfectly. I was just wondering if there was a way of restricting the area that lwc is active in. Our server has an area outside of the mainland where anything goes, griefing, PVP, stealing etc. Having LWC active out here kind of ruins the dangerous experience out there
     
  27. Offline

    spunkiie

    +1 to this. I'm currently using PreciousStone for block protection, and always wondered WHY it's not stable as LWC.

    If LWC starts supporting block protection I will for sure use instead of PreciousStone.

    BTW: Is there a download link for 3.0 alpha ?
     
  28. Offline

    Kingadams

    Running 2.31 and my console is spamming this...

    Im running essentials worldguard worldedit and falsebook
     
  29. Offline

    axeblade346

    Just for pure interest check your plugins/LWC/lwc.properties
    and make sure the Redstone deny is set to False or True
     
  30. Offline

    Phinary

    Im having a problem. Some areas of my map when you try to lock something, you type /cprivate then click it and nothing happens. I have a big map over 1 GB. Any suggestions?
     
  31. Offline

    Hidendra

    I finally got around to moving the wiki to the same server as the main griefcraft.com site -- it should be back up soon

    If you use WorldGuard -- yes !
    You can specify regions that only protections can be created in (they can even be a blank region with no flags), and it will only allow protections to be created in those.
    Just change enforce-worldguard-regions to true and change worldguard

    Is it happening when your server is turning off?

    Are there errors in the console?
    If you type /cinfo and click that block, does it say "that air is not registered" ?

    http://griefcraft.com/bukkit/lwc/alpha/LWC.jar

    In core.yml, scroll down to the protections: block and it explains how to add custom protections (ala block protection)[/b]
     

Share This Page