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

 

It's not possible to see what password a protection uses - it's hashed so it's not easy to get the real password. If you have the lwc.admin permission node or OP, you can use /cremove on the door to remove it if you wanted to do that.

It's a bukkit bug.

It sounds like you're using an old version of LWC. Updating it will fix the error LWC is throwing.

That is not an LWC bug or issue - it's related to your Permissions plugin.

(hint: you're trying to use PermissionsSql AND SuperpermsBridge, AND PermissionsEx)

Try using the command

Code:

/lwc debug

Is it saying you have lwc.admin? If not, please post your permissionsbukkit config, you mayh ave made a small mistake

In the latest dev builds LWC no longer uses implementation-specific methods for checking permissions: it strictly relies on Superperms if available (so, theoretically drops Perms 2/3 support unless a) Permissions 3 adds superperms support b) the server uses Superpermsbridge). Now implementation-specific methods are only used for getting what groups a player is in.

I didn't want to merge it to the main 3.x branch because it causes issues for those without SuperpermsBridge + Permissions 2/3. If you want, you can update to 4.0.0-alpha2 and you should not experience any problems (latest one: http://ci.griefcraft.com/job/LWC/218/)

What is the output of /lwc admin report ? Using it in-game will also throw it into the console.

by the way, if you hop into the irc / live-chat we could probably talk much faster if it's convenient for you.. your issue sounds like a rare one and it sounds like it's being caused by something else, but I'm not sure yet (it is the first time I heard about it)

 

That is not an LWC bug or issue - it's related to your Permissions plugin.
(hint: you're trying to use PermissionsSql AND SuperpermsBridge, AND PermissionsEx)



lol my bad sorry

 

i need remove
created a private BLOCKNAME succeffuly,

 

Oh, thanks for telling me. I just installed it and it seems to work perfect. Thank you!

 

Thankyou for this plugin, I will be installing soon. If I come across any error's I'll be sure to notify you. Thanks again!

 

I'm quite certain this question has been ask a minimum of 34 times. But after searching 15+ threads <--- that way.. I figured I would ask again.

How do I fix this?
Player A places chest - /cprivate and punches chest
Player A no longer wish to have that chest placed there.... he 'breaks' the chest without /cremove first
Player B comes along... places a NEW chest/block .... says 'That XYZ is already registered'
Player B QQs to Admin/Mod.....
Admin/Mod have to type /cremove to remove the old protection

^^ Anyways to remove protection from chests once they are 'broke' by Player A?

Thanks in advance!
Eric

 

Thanks!

 

i need remove
created a private BLOCKNAME succeffuly,
And i make a translate for PORTUGUES-BRAZILIAN, how to add for lwc?

 

when i try to type a command, it comes up with red writing saying "Sorry cant do that steve".
1. my name isnt steve.
2. i don't have permissions of any kind
3. its scary...
4. nothing comes up in the cmd.

 

Cant seem to lock noteblocks? Jukebox, buttons and levers works fine. Using:

note_block:
enabled: true
ignoreLeftClick: true

 

@Hidendra
Showcase (plugin) allows items to be displayed on stone slabs without players being able to pickup and steal the items. Also, they wont despawn. But if you place a magnet chest next to it. The item will be sucked into chest repeatedly as Showcase replaces the lost item, effectively causing a dupe loop. Can this be solved by perhaps doing a check for nearby showcases before pulling in items.

 

CONSOLE: + Version:3.45 (b204)
CONSOLE: + Engine:SQLite
CONSOLE: + Date:Tue Sep 13 15:50:52 MSD 2011
CONSOLE: + Time:28185 seconds
CONSOLE: + Players:1
CONSOLE: + Protections:0
CONSOLE: + Cache:1/10000
CONSOLE:
CONSOLE: - Physical database
CONSOLE: + Queries:466
CONSOLE: + Average:0.016533617172254746 /second
CONSOLE:
CONSOLE: - Memory database
CONSOLE: + Queries:81
CONSOLE: + Average:0.0028738690792974985 /second
CONSOLE:
:S Looks like it is not saving

 

This plugin has an issue on the most recent CB builds.

Basically it causes all console commands to multiply, see this bug:
https://github.com/Bukkit/CraftBukkit/commit/776ed4a980c343a8dadc155ce80f33ab1146a1f2

I have been told it is related to using CB classes and creating new Console classes.

 

i need remove
created a private BLOCKNAME succeffuly,
And i make a translate for PORTUGUES-BRAZILIAN, how to add for lwc?

 

You can remove protections with /cremove

If you want to translate it, the English file is located here: https://raw.github.com/Hidendra/LWC/master/src/lang/lwc_en.properties

If you wanted to add it to your own LWC so you can modify messages, create the folder

Code:

plugins/LWC/locale

and then create a file named lwc.properties inside this locale folder. Copy all of the text you want to translate (or have already translated?) into it (e.g, that whole english file).
When you make changes, a server restart (or plugin reload may work just fine as well) will make the changes show up.

Fixed in the devel builds - I will look into putting out a release for it.

Try this

Code:

'25':  # Note block
    enabled: true
    ignoreLeftClick: true

What version of LWC are you using? If you aren't using the latest, please update (/lwc admin version will tell you what version you have.)

Excellent

Awfully weird!

Try adding this argument to the java arguments for the server:

Code:

-Dlwc.purejava=true

e.g it should look something like:

Code:

java -Xmx### -Dlwc.purejava=true -jar craftbukkit.jar

You could also try using MySQL if you have a mysql server installed .. although it'd be a bit much if you don't and were to install one (but that would probably work ..)

 

man i need remove a MENSAGE, all time i put a block on the chat appears
created a private BLOCKNAME succeffuly,
i need remove it

 

Is it that you don't want blocks to automatically remove? I'm sorry - I'm not sure exactly what you're asking (I had to assume a few things) - or does that message literally say 'BLOCKNAME' (I assume it's the block name, not literally that..)

 

when i put a block chat show THIS message.


sorry for a bad inglesh

when i put a block chat show THIS message.


sorry for a bad inglesh

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

I see.

So, you're wanting to remove the message, yeah? At the moment it isn't removable, however you can turn the messages on and off for yourself with the command /cnospam - however it will be disabled when you log out.

 

hm, ty, make permission node for remove this...

 

I don't even know how to instal MySQL and how it works , and How to use it , I'm new to MySQL :S ( Stupid question ) does MySQL takes more RAM or Less ? )

 

is there any way to remove all protections per world?
we use lwc with mysql.

 

I've just migrated from Permissions 2 to PermissionsBukkit and all LWC chest protections have disappeared. I've ensured that the appropriate permissions have been assigned in PermissionsBukkit, and looking at the database file for LWC I can see that it still has the data for the protections. Any ideas on what could be causing this?

 

What do you mean by disappeared? Try using

Code:

/lwc admin report

If you use it in-game, it'll also throw a report into the console as well. It'll tell you how many protections you have.

It may be that you assigned lwc.admin or lwc.mod unknowningly? Try getting a "normal" player to use /lwc debug - it'll tell them what LWC sees their permissions as.

If you configured LWC to use a prefix such as lwc_, replace protections with the prefix. e.g: lwc_protections

example:

Code:

/lwc admin query DELETE FROM lwc_protections WHERE world = 'world_nether';

Yeah, it probably wouldn't be a good idea to install MySQL.

Would I be able to hop on the server and take a peek (the mc server)? My MC username is Hidendra

 

Yes for sure , Do you want to be OP to acces the commands ?

 

Hu?
You don't have to be OP, if thats what your asking.. It supports BukkitPermissions....

 

Im sorry if I missed it, did a search of the thread and found many Towny threads but none about my question.

I see it uses worldguard zones to allow where chests can be locked. does it also use towny zones? would love to be able to have people only lock chests in towns, and not able to lock chests in towny 'wild'.

anyone know of a way to accomplish this?

 

At the moment, no. If you open up an issue on github, I can get to it when I can!

Also! LWC has been confirmed to be working A-OK on the experimental 1.8 CB build #1097. It should still work on builds past this!

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

will do, that would be amazing, that would complete our entire town/wild/village ruleset without mods having to manually unlock any chests found in the wild.