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

    Fabis94

    Can I protect Storage carts? I'm using MinecartMania and this would be very helpful.
     
  3. Offline

    repeat

    try this (make backup)
    /lwc admin query DELETE FROM protections WHERE owner 'playername'
     
  4. Offline

    KiloWhiskey

    Nice. I'll give that a shot. Thanks.
     
  5. Offline

    RugRats

    @Hidendra
    Can you disable the lock messages at all there getting a bit spammy
     
  6. Offline

    Fabis94

    Can you make it so I can disable chests in general for specific groups, but have exceptions? So I use lwc.blockinventory, but make it so they can still use buttons for example.
     
  7. Offline

    Kingkiron

    @Hidendra
    I'm trying to use lwc and it seems to work but will never let me lock anything,

    I type /cprivate and then it says to left click a block, but thats all. Never locks it or gives confirm of lock. In console it says
    Could not pass event PLAYER_INTERACT to LWC
    java.lang.NULLpointerexception

    Also, there is no file inside my lib/native/windows/x86 folder?

    I've tried the standard build and the cutting edge one, my Bukkit was updated yesterday.

    I'm using Permissions,Iconomy,IconomyChestshop, Mobbounty, and IconomyDeath.

    My groups file reads
    ___________________________________________________________
    groups:
    Default:
    Default: true
    info:
    prefix: ''
    suffix: ''
    build: true
    inheritance:
    permissions:
    - 'iConomy.list'
    - 'iConomy.payment'
    - 'mobbounty.collect'
    - 'mobbounty.commands.mb'
    - 'lwc.protect'
    ____________________________________________________________

    and my users file
    ___________________________________________________________
    users:
    Kingkiron:
    groups:
    - Admins
    permissions:
    ______________________________________________________________

    Please help
     
  8. Offline

    spunkiie

    @Hidendra

    I've just installed 3.30 and LWC performance on my 400+ server was KILLED. 30 minutes to start the server, even after I rollback to 3.21 the server is taking AGES to start... man, I'm sad :(

    Maybe the new "expire" option is doing this ? What can I do ?
     
  9. Offline

    Messiah93

    Up...
     
  10. Offline

    dblodonut

    Maybe its cuz im sick as a dog and its late here but LWC seems to be protecting EVERYTHING i place. dirt, stone, etc anything. what is doing this i cant figure it out : /

    edit: i havnt changed any settings from when i downloaded it and im admin
     
  11. Getting frequent reports like this:

    [13:13] <Mobbed> Hey Joy, just a heads up, I destroyed a block that was beside one of my chests, and I got a message saying the chest had been unprotected. Not sure if this is a glitch, as far as I know nothing should unregister a chest unless you destroy the chest yourself, or unprotect it ect
    [13:14] <Mobbed> the message said unregistered, not unprotected*

    People just randomly getting their chests unlocked upon block placement nearby...
     
  12. Offline

    Kainzo

    @Hidendra - I'm also getting this.

    it seems that a player can put down several blocks next to the LWC and they become infected - and are locked. I'm really unsure whats causing it. It appears to be happening on 3.21 and 3.30
     
  13. Offline

    Techykid3

    When I started my server and when I place chests it just emits light (when in dark) and then it disappeared, but my main problem is I cannot make double chests! :(
     
  14. Offline

    TheGoldFish

    The French translation has errors and untranslated words, can I correct it?
     
  15. Offline

    WiktorP

    I am afraid, that in Polish translation the LWC Admin part is totally missing, if you type this command only title appears...
     
  16. Offline

    blokzeil1

    i have a problem with towny and LWC

    Code:
    2011-07-10 18:13:05 [SEVERE] Could not pass event PLAYER_INTERACT to LWC
    java.lang.NoClassDefFoundError: com/griefcraft/scripting/ModuleLoader$Event
        at com.griefcraft.listeners.LWCPlayerListener.onPlayerInteract(Unknown Source)
        at org.bukkit.plugin.java.JavaPluginLoader$10.execute(JavaPluginLoader.java:307)
        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:321)
        at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:168)
        at net.minecraft.server.ItemInWorldManager.dig(ItemInWorldManager.java:63)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:457)
        at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
        at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:84)
        at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
        at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:451)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:361)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
    
     
  17. Offline

    compwiz91

    When i add in LWC to my server i get the following error on startup


    Code:
    C:\Users\Administrator\Desktop\Test>title="MineCraft Test"
    151 recipes
    16 achievements
    21:57:00 [INFO] Starting minecraft server version Beta 1.7.2
    21:57:00 [WARNING] **** NOT ENOUGH RAM!
    21:57:00 [WARNING] To start the server with more ram, launch it as "java -Xmx102
    4M -Xms1024M -jar minecraft_server.jar"
    21:57:00 [INFO] Loading properties
    21:57:00 [INFO] Starting Minecraft server on *:25566
    21:57:00 [INFO] This server is running Craftbukkit version git-Bukkit-0.0.0-904-
    g9277096-b953jnks (MC: 1.7.2)
    21:57:01 [INFO] LWC     Loading shared objects
    21:57:01 [INFO] Cache   Protection cache: 0/10000
    21:57:01 [INFO] LWC     Native library: plugins/LWC/lib/native/Windows/amd64/sql
    itejdbc.dll
    21:57:01 [SEVERE] java.lang.IllegalAccessError: tried to access class com.nijiko
    .permissions.ModularControl$RefreshTask from class com.nijiko.permissions.Modula
    rControl
    21:57:01 [SEVERE]       at com.nijiko.permissions.ModularControl.<clinit>(Modula
    rControl.java:45)
    21:57:01 [SEVERE]       at com.nijikokun.bukkit.Permissions.Permissions.setupPer
    missions(Permissions.java:184)
    21:57:01 [SEVERE]       at com.nijikokun.bukkit.Permissions.Permissions.onLoad(P
    ermissions.java:139)
    21:57:01 [SEVERE]       at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftS
    erver.java:121)
    21:57:01 [SEVERE]       at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer
    .java:89)
    21:57:01 [SEVERE]       at net.minecraft.server.ServerConfigurationManager.<init
    >(ServerConfigurationManager.java:51)
    21:57:01 [SEVERE]       at net.minecraft.server.MinecraftServer.init(MinecraftSe
    rver.java:132)
    21:57:01 [SEVERE]       at net.minecraft.server.MinecraftServer.run(MinecraftSer
    ver.java:335)
    21:57:01 [SEVERE]       at net.minecraft.server.ThreadServerApplication.run(Sour
    ceFile:422)
    21:57:01 [SEVERE] [Permissions] Unable to load permission data.
    21:57:01 [SEVERE] [Permissions] Shutting down Permissions due to error(s).
    21:57:01 [INFO] [Permissions] (Yeti) was initialized.
    21:57:01 [INFO] Preparing level "world"
    21:57:01 [INFO] Preparing start region for level 0 (Seed: 7718630408448783751)
    21:57:02 [INFO] [BBROTHER] ------------------------------------
    21:57:02 [INFO] [BBROTHER] Hello, and thank you for using the TESTING version of
     BigBrother!
    21:57:02 [INFO] [BBROTHER] Please note that, since this is far from complete, th
    ere will be many bugs.
    21:57:02 [INFO] [BBROTHER] IF YOU FIND ANY BUGS, PLEASE REPORT THEM ON http://bu
    gs.nexisonline.net/bb
    21:57:02 [INFO] [BBROTHER] Please stay tuned in irc.esper.net #bigbrother for up
    dates and build notifications.
    21:57:02 [INFO] [BBROTHER] ------------------------------------
    21:57:02 [INFO] [BBROTHER] BBData MySQL Driver r1 loaded!
    21:57:02 [INFO] [BBROTHER] Permissions plugin found but disabled. Enabling 'Perm
    issions' (v3.1.5).
    21:57:02 [INFO] [Permissions] (Yeti) disabled successfully.
    21:57:02 [INFO] [BBROTHER] Permissions enabled using: Permissions v3.1.5
    21:57:02 [INFO] [BBROTHER] Help plugin detected but disabled. Enabling plugin 'H
    elp' (v0.2).
    21:57:02 [INFO] [HELP] 0 extra help entries loaded
    21:57:02 [INFO] [HELP] Permissions enabled using: Permissions v3.1.5
    21:57:02 [INFO] [HELP] Help 0.2 enabled
    21:57:02 [INFO] [BBROTHER] 'Help' support enabled
    21:57:02 [INFO] [BBROTHER] BigBrother 1.9.1-SNAPSHOT (build #581) enabled!
    21:57:03 [INFO] [ColorMe] v2.2 has been enabled.
    21:57:03 [INFO] [iConomy] Logging is currently disabled.
    21:57:03 [INFO] [iConomy] v5.01 (Eruanna) loaded.
    21:57:03 [INFO] [iConomy] Developed by: [Nijikokun]
    21:57:03 [INFO] [ColorMe] hooked into iConomy.
    21:57:03 [INFO] LWC     Loaded 134 locale strings (0 overrides)
    21:57:03 [INFO] [Permissions] (Yeti) disabled successfully.
    21:57:03 [INFO] LWC     Using Permissions API...
    21:57:03 [INFO] LWC     Loading SQLite
    21:57:03 [INFO] SQLite  Using: Native
    21:57:03 [INFO] LWC     At version: v3.11
    21:57:03 [INFO] [MineBackup] 1 worlds loaded.
    21:57:03 [INFO] [MineBackup] version 0.3.1 ready
    21:57:03 [INFO] [MYHOME]: 0 homes loaded
    21:57:03 [INFO] [MYHOME] Permissions enabled using: Permissions v3.1.5
    21:57:03 [INFO] [MYHOME] 'Help' support enabled.
    21:57:03 [INFO] [MYHOME] MyHome 1.9.5 enabled
    21:57:03 [INFO] [MYWARP] [MYWARP]: 0 warps loaded
    21:57:03 [INFO] [MYWARP] Permissions enabled using: Permissions v3.1.5
    21:57:04 [INFO] [MYWARP] 'Help' support enabled.
    21:57:04 [INFO] [MYWARP] MyWarp 2.0 enabled
    21:57:04 [INFO] [Permissions] (Yeti) disabled successfully.
    21:57:04 [INFO] WorldEdit 4.6 enabled.
    21:57:04 [INFO] WorldEdit: Permissions plugin detected! Using Permissions plugin
     for permissions.
    21:57:04 [INFO] WorldGuard: Permissions plugin detected! Using Permissions plugi
    n for permissions.
    21:57:04 [INFO] WorldGuard: (world) Single session is enforced.
    21:57:04 [INFO] WorldGuard: (world) TNT ignition is PERMITTED.
    21:57:04 [INFO] WorldGuard: (world) Lighters are PERMITTED.
    21:57:04 [INFO] WorldGuard: (world) Lava fire is blocked.
    21:57:04 [INFO] WorldGuard: (world) Fire spread is UNRESTRICTED.
    21:57:04 [INFO] WorldGuard: Loaded configuration for world 'world"
    21:57:04 [INFO] WorldGuard 5.2.2 enabled.
    21:57:04 [INFO] [Permissions] (Yeti) disabled successfully.
    21:57:04 [INFO] WorldEdit: Permissions plugin detected! Using Permissions plugin
     for permissions.
    21:57:04 [INFO] WorldGuard: Permissions plugin detected! Using Permissions plugi
    n for permissions.
    21:57:04 [INFO] WorldEdit: Permissions plugin detected! Using Permissions plugin
     for permissions.
    21:57:04 [INFO] WorldGuard: Permissions plugin detected! Using Permissions plugi
    n for permissions.
    21:57:04 [INFO] [dynmap] Using environment as template: normal
    21:57:04 [INFO] [dynmap] Configuration of world world
    21:57:04 [INFO] [dynmap] center: org.dynmap.ConfigurationNode@1afecda0
    21:57:04 [INFO] [dynmap] enabled: true
    21:57:04 [INFO] [dynmap] title: world
    21:57:04 [INFO] [dynmap] maps: [{class=org.dynmap.flat.FlatMap, name=flat, title
    =Flat, prefix=flat, colorscheme=default, textured=smooth}, {class=org.dynmap.kze
    dmap.KzedMap, renderers=[{class=org.dynmap.kzedmap.DefaultTileRenderer, name=sur
    face, title=Surface, prefix=t, maximumheight=127, colorscheme=default}, {class=o
    rg.dynmap.kzedmap.CaveTileRenderer, name=cave, title=Cave, prefix=ct, maximumhei
    ght=127}]}]
    21:57:04 [INFO] [dynmap] name: world
    21:57:04 [INFO] [dynmap] Loading maps of world 'world'...
    21:57:04 [INFO] [dynmap] Loading renderers for map 'class org.dynmap.kzedmap.Kze
    dMap'...
    21:57:04 [INFO] [dynmap] Loaded 2 renderers for map 'class org.dynmap.kzedmap.Kz
    edMap'.
    21:57:04 [INFO] [dynmap] Loaded 2 maps of world 'world'.
    21:57:04 [INFO] [dynmap] Loaded 8 components.
    21:57:04 [SEVERE] [dynmap] Failed to start WebServer on null:8123!
    21:57:04 [INFO] [dynmap] version 0.19 is enabled
    21:57:04 [INFO] [iChat] Permissions plugin not found or wrong version. Disabling
    
    21:57:04 [INFO] [iChat] iChat Disabled
    21:57:04 [INFO] Done (0.294s)! For help, type "help" or "?"
    21:57:07 [INFO] [BBROTHER] Removed 0 old records because of age in 0h00m00s.
    >
    Im currently running the following plugins, Big Brother, ColorMe, dynmap, Help, iChat, iConomy, LWC, MineBackup, MyHome, MyWarp, Permissions, WorldEdit and World Guard.

    If i remove Dynmap everything works fine...not sure if this error belongs to LWC or dynamap. Any help would be greatly appreacited. If you need more of the startup log i can post the rest.
     
  18. Offline

    Messiah93

    Please help, all players unsecure my chest by /cremove and steal my objects.

    RB 953 & LWC 3.30
     
  19. Offline

    Incendia

    Apparently this isn't secure anymore?
     
  20. Offline

    pomo4ka

    Hi @Hidendra please add a link to the first post zip archive. I have no internet on the machine where there is a server, and I can not download the configuration to the plugin, every time I update the plugin. Thank you.
     
  21. Offline

    Birdie

    Hi, we have a mysql table with limits for our donators, is there a way to automatically convert these to the new limits.yml file?

    Lol, just checked the file, it automatically converted them! THANKS! :D

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

    Bhikku

    OpenAndClose with intervall 3 doesnt work or? Wooden Door never close after xxx time period. hmm just why? Mysql is correct configureded. So?
     
  23. Offline

    monir

    After uppdating i have this problem on my server that items just disapers from chests and its a problem! today a guy loosed everything in his 13 chests :/
    what can be the problem? have anybody heard about this? it have nothing to do with lwc when protecting chests? some bug or maby its some other plugin that id doing this.
     
  24. Offline

    Hidendra

    Yes.

    Are you using the "bukkitbug656workaround"? There is a known bug with said workaround at the moment that causes an infinite amount of blocks in one single direction to show up as protected (/cc: @morganm )

    In plugins/LWC/core.yml, showNotices and showMyNotices are what you are looking for :D

    A password chest? It tells you when you attempt to open it -- /cunlock <pass> (after attempting to open it)
    To remove a chest, simply use /cremove and then hit the chest

    please try deleting your core.yml in plugins/LWC/ and then restarting the server (it will be regenerated)

    I'm pretty sure you're using the wrong chest... Do not use "Locked Chest" id 95 (i think), that chest is no longer in use and was a joke. Use id 54 "chest"

    I will look into it

    Could you verify your Permissions files are configured correctly? You could try renaming the Permissions folder and seeing if default works okey

    please post the full exception if possible. As for the error, please try placing this file into that x86 folder:
    http://griefcraft.com/bukkit/shared/lib/native/Windows/x86/sqlitejdbc.dll

    Do you have ignoreBlockDestruction: true under doors in plugins/LWC/core.yml?

    Are they Ops? Please post your groups.yml for Permissions, something is wrong in it. Check for lwc.admin or lwc.admin.remove that are connected to your players in any way

    What OS are you running? (unless you're using MySQL?)

    It sounds like you are affected by a Bukkit bug -- http://leaky.bukkit.org/issues/656
    LWC's current workaround is not working fully but it helps most of the time, you could try it if you wish. In plugins/LWC/core.yml, under core:, add:
    Code:
        bukkitBug656workaround: true
    
    openAndClose does not properly work at the moment :)

    It is secure on the plugin side.

    The only current way around LWC protections that I know of (by means of no user error giving access to lwc.admin/lwc.mod) is a bukkit related bug that affects every plugin, and is not easily in LWC's control.

    If I understood correctly, I do not believe it is possible at the moment, unless you were to disable the ability to protect buttons.

    If you think you can improve it, you are more than free to :) The translations are done by you guys - the community.
     
  25. Offline

    Messiah93

    No, they aren't Ops. I don't have groups.yml, I'm using authx and LWC only.
     
  26. Offline

    Ratchet

    @Hidendra

    protections:
    denyRedstone: true
    autoRegister: off
    ignoreBlockDestruction: false
    ignoreLeftClick: false
    ignoreRightClick: false
     
  27. Offline

    thehutch

  28. Offline

    Messiah93

  29. Offline

    Hidendra

    I'll look into it -- thanks
    Are you using LWC 3.30? Please post your core.yml (if using MySQL, please remove your password.)

    please copy the whole protections block, not just the beginning.



    BTW: griefcraft.com is being transferred to a different registrar as we speak, a mirror for LWC.jar will be up in the mean time. You can access it directly here:
    http://24.222.251.55:8080/job/LWC/promotion/latest/LWC/artifact/build/LWC.jar
     
  30. Offline

    Gules1

    I'm having a problem with "public" command.
    I'm the adming, and furnace autoregister as mine.
    I use "/cremove" command to remove the protection, and it works, anyone can use it.
    But when I use "/cpublic" or "/private Group", the plugin register whatever I click as mine and no one else can use it.

    [​IMG]

    why is it locked? how do I unlock something that doesn't have a password?


    this is my core.yml:

    Code:
    core:
        locale: en
        autoUpdate: false
        flushInterval: 10
        cacheSize: 10000
        defaultMenuStyle: basic
        showNotices: true
        showMyNotices: false
        verbose: false
        opIsLWCAdmin: true
    
    database:
        adapter: sqlite
        path: plugins/LWC/lwc.db
        host: localhost
        database: lwc
        username:
        password:
        prefix:
    
    protections:
        denyRedstone: false
        autoRegister: off
        ignoreBlockDestruction: false
        ignoreLeftClick: false
        ignoreRightClick: false
        blocks:
            chest:
                enabled: true
                autoRegister: private
            furnace:
                enabled: true
                autoRegister: private
            dispenser:
                enabled: true
                autoRegister: private
            sign:
                enabled: true
                autoRegister: private
            wooden_door:
                enabled: true
                autoRegister: off
            iron_door:
                enabled: true
                autoRegister: off
            trap_door:
                enabled: true
                autoRegister: off
    
    modes:
        droptransfer:
            enabled: true
        persist:
            enabled: true
    
     
  31. Offline

    alfskan

    Code:
    doors:
        # Enable the opening of Iron Doors when you click on them
        enabled: true
    
        # If true, double doors will open, presuming they are both protected
        # and you can access both
        doubleDoors: true
    
        # Actions:
        #        toggle: the door will just open if it's closed, or close if it's opened. Will not auto close.
        #  openAndClose: the door will automatically close after <interval>. If it was already opened, it will NOT re-open.
        #
        action: openAndClose
    
        # The amount of seconds after opening a door for it to close. No effect if openAndClose action is not being used.
        interval: 3
    this is mt config.

    but when I open my locked door, it doesnt close after 3secs.

    can you help me?
     

Share This Page