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

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

DevBukkit

• Overview: http://dev.bukkit.org/server-mods/lwc/
• Forum: http://dev.bukkit.org/server-mods/lwc/forum/

Using LWC

• Installation
• Commands
• Permissions
• MySQL

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).

LWC-Economy 1.30 - 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) Changelog (close)

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:

• Polish -- a thank you to @Geoning @dudsonowa and @andrewkm !!
• French -- a thank you to @Cehel !!

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

 

I know! happens to me to! i need help! D:

 

i am not admin , op
but open chest

 

What's also strange about that, is it's a double chest, yet the chest inventory is only displaying as a single chest.

 

When i do "/LWC admin cleanup" I get the following errors "Error: The world test does not exist!". I know that world does not exist anymore but shouldn't it cleanup that protection entry??

 

yer im getting same issues, i have PEX and added the lwc.protect to my builders but they still can access to their own chests. It even says, this chest is protect by you. But they still cant get in...lol

 

Can you please update the wiki page for this plugin? or is there a link that explains configuration?

 

having a mayor problem with lwc, chests keep losing their protection for some reason

 

[BUG in 3.5.3]
@Hidendra It seems like the command /lwc -o no longer shows the person that created the private protection of a chest oder door ect.
The protection is active, but it only lists additionally added players or groups with access.
E.g. if player "Progamer" uses "/cprivate Nooby", it only lists Nooby.

Another thing:
It would be handy to have a permission node to show the info who owns a protected chest or block.
There is currently only a global switch for it (ShowNotices & ShowMyNotices) in the core.yml.
Because as admin its very handy to see that by just klicking a chest. But members complain about those messages.

 

Is there a way to change the protection on a chest from public to private (or vice versa) without destroying and replacing the chest?

Second question, can you set individual costs for protections on different types of blocks?

 

Are we allowed to protect/private fence gates yet? If so, what's the name so I can add it to the blocks.

 

@Hidendra

Probably CB issue but here goes -> http://pastie.org/2609088

 

i am useing #1185
and this plugin don't protect chest
it can steal chset
please test

 

Yes, simply unprotect the chest using '/cremove' then use the public or private command to lock it again.

 

The only problem with that method is if you use economy costs with no refund they still have to pay again to change the lock type. But to be fair, you did answer my question exactly as asked.

I guess I should have asked more specifically if there was a way to switch the protection types without removing it.

 

I'm using Lwc 3.52 and CB 1185

None of these seem to work for me?? I placed iron doors last night and couldn't open them.. Also both doors didn't open with red stone either.

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
    double Doors: true

Now do i have this set right to auto close?

Code:

# 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.
    #
    name: openAndClose

Is this in minutes, seconds or what? cause it doesn't seem to be working for me either?

Code:

 # The amount of seconds after opening a door for it to close.
No effect if openAndClose name is not being used.
    interval: 1

Thanks,

 

I believe the command in the advanced menu is /lwc -m <private/public>

The "m" stands for modify, and all you do is punch the chest you want to change.

 

All -m can do is add players or groups to the list of allowable players.

"/lwc -m public" for example would attempt to add the player "public" to the list of those allowed access.

 

hey,
we using permissions 2 and set the lwc.mod flag.
but the mods doesnt have access to the /cremove command
same with the lwc.admin flag on our semiadmins, lwc says "access denied"
where is the problem?

Code:

    Mod:
        default: false
        info:
            prefix: ''
            suffix: ''
            build: true
        inheritance:
        permissions:
            - 'logblock.tool'
            - 'lwc.protect'
            - 'lwc.mod'
            - 'towny.town.claim'
            - 'towny.town.resident'
            - 'towny.town.toggle.*'
            - 'town.plot'
            - 'towny.spawntp'
            - 'towny.publicspawntp'
            - 'SpawnControl.spawn.use'
            - 'ChestShop.shop.create'
            - 'ChestShop.shop.buy'
            - 'ChestShop.shop.sell'
            - 'commandbook.say.me'
            - 'commandbook.msg'
            - 'commandbook.kick'
            - 'commandbook.bans.ban'
            - 'commandbook.bans.unban'

 

What is the benefit of using MySQL instead of SQLLite?

 

when ever someone trys to break there chest it says internal error report to admin :BLOCK BREAK

Code:

7:30:00 [SEVERE] java.sql.SQLException: NYI

7:30:00 [SEVERE]       at org.sqlite.Conn.prepareStatement(Conn.java:217)
7:30:00 [SEVERE]       at com.griefcraft.sql.Database.prepare(Database.java:282

7:30:00 [SEVERE]       at com.griefcraft.sql.PhysDB.saveHistory(PhysDB.java:956

7:30:00 [SEVERE]       at com.griefcraft.model.History.saveNow(History.java:314

7:30:00 [SEVERE]       at com.griefcraft.model.Protection.saveNow(Protection.ja
a:620)
7:30:00 [SEVERE]       at com.griefcraft.model.Protection.remove(Protection.jav
:537)
7:30:00 [SEVERE]       at com.griefcraft.modules.destroy.DestroyModule.onDestro
Protection(DestroyModule.java:51)
7:30:00 [SEVERE]       at com.griefcraft.scripting.ModuleLoader.dispatchEvent(M
duleLoader.java:187)
7:30:00 [SEVERE]       at com.griefcraft.listeners.LWCBlockListener.onBlockBrea
(LWCBlockListener.java:143)
7:30:00 [SEVERE]       at org.bukkit.plugin.java.JavaPluginLoader$39.execute(Ja
aPluginLoader.java:511)
7:30:00 [SEVERE]       at org.bukkit.plugin.RegisteredListener.callEvent(Regist
redListener.java:58)
7:30:00 [SEVERE]       at org.bukkit.plugin.SimplePluginManager.callEvent(Simpl
PluginManager.java:338)
7:30:00 [SEVERE]       at net.minecraft.server.ItemInWorldManager.c(ItemInWorld
anager.java:195)
7:30:00 [SEVERE]       at net.minecraft.server.ItemInWorldManager.dig(ItemInWor
dManager.java:92)
7:30:00 [SEVERE]       at net.minecraft.server.NetServerHandler.a(NetServerHand
er.java:497)
7:30:00 [SEVERE]       at net.minecraft.server.Packet14BlockDig.a(SourceFile:43

7:30:00 [SEVERE]       at net.minecraft.server.NetworkManager.b(NetworkManager.
ava:226)
7:30:00 [SEVERE]       at net.minecraft.server.NetServerHandler.a(NetServerHand
er.java:92)
7:30:00 [SEVERE]       at net.minecraft.server.NetworkListenThread.a(SourceFile
108)
7:30:00 [SEVERE]       at net.minecraft.server.MinecraftServer.h(MinecraftServe
.java:464)
7:30:00 [SEVERE]       at net.minecraft.server.MinecraftServer.run(MinecraftSer
er.java:374)
7:30:00 [SEVERE]       at net.minecraft.server.ThreadServerApplication.run(Sour
eFile:417)
7:30:00 [SEVERE] com.griefcraft.scripting.ModuleException: LWC Module threw an
ncaught exception! LWC version: 3.53 (b294)
7:30:00 [SEVERE]       at com.griefcraft.scripting.ModuleLoader.dispatchEvent(M
duleLoader.java:204)
7:30:00 [SEVERE]       at com.griefcraft.listeners.LWCBlockListener.onBlockBrea
(LWCBlockListener.java:143)
7:30:00 [SEVERE]       at org.bukkit.plugin.java.JavaPluginLoader$39.execute(Ja
aPluginLoader.java:511)
7:30:00 [SEVERE]       at org.bukkit.plugin.RegisteredListener.callEvent(Regist
redListener.java:58)
7:30:00 [SEVERE]       at org.bukkit.plugin.SimplePluginManager.callEvent(Simpl
PluginManager.java:338)
7:30:00 [SEVERE]       at net.minecraft.server.ItemInWorldManager.c(ItemInWorld
anager.java:195)
7:30:00 [SEVERE]       at net.minecraft.server.ItemInWorldManager.dig(ItemInWor
dManager.java:92)
7:30:00 [SEVERE]       at net.minecraft.server.NetServerHandler.a(NetServerHand
er.java:497)
7:30:00 [SEVERE]       at net.minecraft.server.Packet14BlockDig.a(SourceFile:43

7:30:00 [SEVERE]       at net.minecraft.server.NetworkManager.b(NetworkManager.
ava:226)
7:30:00 [SEVERE]       at net.minecraft.server.NetServerHandler.a(NetServerHand
er.java:92)
7:30:00 [SEVERE]       at net.minecraft.server.NetworkListenThread.a(SourceFile
108)
7:30:00 [SEVERE]       at net.minecraft.server.MinecraftServer.h(MinecraftServe
.java:464)
7:30:00 [SEVERE]       at net.minecraft.server.MinecraftServer.run(MinecraftSer
er.java:374)
7:30:00 [SEVERE]       at net.minecraft.server.ThreadServerApplication.run(Sour
eFile:417)
7:30:00 [SEVERE] Caused by: java.lang.NullPointerException
7:30:00 [SEVERE]       at com.griefcraft.sql.PhysDB.saveHistory(PhysDB.java:959

7:30:00 [SEVERE]       at com.griefcraft.model.History.saveNow(History.java:314

7:30:00 [SEVERE]       at com.griefcraft.model.Protection.saveNow(Protection.ja
a:620)
7:30:00 [SEVERE]       at com.griefcraft.model.Protection.remove(Protection.jav
:537)
7:30:00 [SEVERE]       at com.griefcraft.modules.destroy.DestroyModule.onDestro
Protection(DestroyModule.java:51)
7:30:00 [SEVERE]       at com.griefcraft.scripting.ModuleLoader.dispatchEvent(M
duleLoader.java:187)
7:30:00 [SEVERE]       ... 14 more
7:30:00 [SEVERE] java.sql.SQLException: NYI
7:30:00 [SEVERE]       at org.sqlite.Conn.prepareStatement(Conn.java:217)
7:30:00 [SEVERE]       at com.griefcraft.sql.Database.prepare(Database.java:282

7:30:00 [SEVERE]       at com.griefcraft.sql.PhysDB.saveHistory(PhysDB.java:956

7:30:00 [SEVERE]       at com.griefcraft.model.History.saveNow(History.java:314

7:30:00 [SEVERE]       at com.griefcraft.model.Protection.saveNow(Protection.ja
a:620)
7:30:00 [SEVERE]       at com.griefcraft.model.Protection.remove(Protection.jav
:537)
7:30:00 [SEVERE]       at com.griefcraft.modules.destroy.DestroyModule.onDestro
Protection(DestroyModule.java:51)
7:30:00 [SEVERE]       at com.griefcraft.scripting.ModuleLoader.dispatchEvent(M
duleLoader.java:187)
7:30:00 [SEVERE]       at com.griefcraft.listeners.LWCBlockListener.onBlockBrea
(LWCBlockListener.java:143)
7:30:00 [SEVERE]       at org.bukkit.plugin.java.JavaPluginLoader$39.execute(Ja
aPluginLoader.java:511)
7:30:00 [SEVERE]       at org.bukkit.plugin.RegisteredListener.callEvent(Regist
redListener.java:58)
7:30:00 [SEVERE]       at org.bukkit.plugin.SimplePluginManager.callEvent(Simpl
PluginManager.java:338)
7:30:00 [SEVERE]       at net.minecraft.server.ItemInWorldManager.c(ItemInWorld
anager.java:195)
7:30:00 [SEVERE]       at net.minecraft.server.ItemInWorldManager.dig(ItemInWor
dManager.java:92)
7:30:00 [SEVERE]       at net.minecraft.server.NetServerHandler.a(NetServerHand
er.java:497)
7:30:00 [SEVERE]       at net.minecraft.server.Packet14BlockDig.a(SourceFile:43

7:30:00 [SEVERE]       at net.minecraft.server.NetworkManager.b(NetworkManager.
ava:226)
7:30:00 [SEVERE]       at net.minecraft.server.NetServerHandler.a(NetServerHand
er.java:92)
7:30:00 [SEVERE]       at net.minecraft.server.NetworkListenThread.a(SourceFile
108)
7:30:00 [SEVERE]       at net.minecraft.server.MinecraftServer.h(MinecraftServe
.java:464)
7:30:00 [SEVERE]       at net.minecraft.server.MinecraftServer.run(MinecraftSer
er.java:374)
7:30:00 [SEVERE]       at net.minecraft.server.ThreadServerApplication.run(Sour
eFile:417)
7:30:00 [SEVERE] com.griefcraft.scripting.ModuleException: LWC Module threw an
ncaught exception! LWC version: 3.53 (b294)
7:30:00 [SEVERE]       at com.griefcraft.scripting.ModuleLoader.dispatchEvent(M
duleLoader.java:204)
7:30:00 [SEVERE]       at com.griefcraft.listeners.LWCBlockListener.onBlockBrea
(LWCBlockListener.java:143)
7:30:00 [SEVERE]       at org.bukkit.plugin.java.JavaPluginLoader$39.execute(Ja
aPluginLoader.java:511)
7:30:00 [SEVERE]       at org.bukkit.plugin.RegisteredListener.callEvent(Regist
redListener.java:58)
7:30:00 [SEVERE]       at org.bukkit.plugin.SimplePluginManager.callEvent(Simpl
PluginManager.java:338)
7:30:00 [SEVERE]       at net.minecraft.server.ItemInWorldManager.c(ItemInWorld
anager.java:195)
7:30:00 [SEVERE]       at net.minecraft.server.ItemInWorldManager.dig(ItemInWor
dManager.java:92)
7:30:00 [SEVERE]       at net.minecraft.server.NetServerHandler.a(NetServerHand
er.java:497)
7:30:00 [SEVERE]       at net.minecraft.server.Packet14BlockDig.a(SourceFile:43

7:30:00 [SEVERE]       at net.minecraft.server.NetworkManager.b(NetworkManager.
ava:226)
7:30:00 [SEVERE]       at net.minecraft.server.NetServerHandler.a(NetServerHand
er.java:92)
7:30:00 [SEVERE]       at net.minecraft.server.NetworkListenThread.a(SourceFile
108)
7:30:00 [SEVERE]       at net.minecraft.server.MinecraftServer.h(MinecraftServe
.java:464)
7:30:00 [SEVERE]       at net.minecraft.server.MinecraftServer.run(MinecraftSer
er.java:374)
7:30:00 [SEVERE]       at net.minecraft.server.ThreadServerApplication.run(Sour
eFile:417)
7:30:00 [SEVERE] Caused by: java.lang.NullPointerException
7:30:00 [SEVERE]       at com.griefcraft.sql.PhysDB.saveHistory(PhysDB.java:959

7:30:00 [SEVERE]       at com.griefcraft.model.History.saveNow(History.java:314

7:30:00 [SEVERE]       at com.griefcraft.model.Protection.saveNow(Protection.ja
a:620)
7:30:00 [SEVERE]       at com.griefcraft.model.Protection.remove(Protection.jav
:537)
7:30:00 [SEVERE]       at com.griefcraft.modules.destroy.DestroyModule.onDestro
Protection(DestroyModule.java:51)
7:30:00 [SEVERE]       at com.griefcraft.scripting.ModuleLoader.dispatchEvent(M
duleLoader.java:187)
7:30:00 [SEVERE]       ... 14 more

 

Come chunks won't protect chests, then the chunk beside it locks chests, what can fix this?

 

hello, can i set LWC with all protections for different worlds?

ex: world have LWC with full protections
nether not have LWC

ty

 

That depends on your permissions manager and whether or not it has multi-world support. (Though I think they all support multiple worlds now at this point.)

Using your example, you can set things up so players only get the 'lwc.protect' permission in your main world. When they travel to the nether, they no longer have that permission and so they can't use LWC.

 

yep nice idea, im very stupid. Tyvm. But for delete the function chests already protected?

 

Is there any reason why we cant lock buttons/levers with signs anymore?
Running LWC v3.53

 

I have this plugin and people can't open my (admin) chests but they can open chests from other which are locked by /cprivate
Why is this? Please help me!

 

I have one Question : Why Should I move to MySQL with my plugins : What it will do , Will it reduce RAM and CPU usage ? ( I know how to set it up ) I want to know what it will bring to me

 

I want that my Users only can lock chests and furnances, nothing other, how i can do that?

 

is there any way we can prevent users from opening doors with redstone stuff?

 

Hi, sorry if this has been answered before or something.

I just installed LWC, and it's great and all (much better then the other way I was using to protect chests on my server)

but I have one problem.

I started protecting some of my chests in my house on my server, just to test it out. Got the hang of it quickly, it's easy.

But now ALWAYS, whenever I put down a sign, or anything, it creates it as a private sign, etc.

It's like I can't touch anything now or put anything down that can be locked, without it being locked, even without me locking it in the first place.

I'll put a chest down, and it'll say in the chat "successfully created private chest" or whatever.

Is there something i'm missing, or is this a bug, or..?

Some help would be great ^^;

Peace,
Danke,
-Lukis