LWC
- Download
- NOTE!: Development builds for LWC can be found at the below Jenkins server. These builds have not been approved by the BukkitDev staff and may not have gone through any QA processes. Use them at your own risk!
- Development builds (Jenkins)
- Feature requests, Suggestions and Issues
- IRC - Live Chat ( irc.esper.net #LWC )
- github
- wiki
- Donate
LWC is the longest-lived single block protection plugin that protects both the block itself and contents of Chests, Furnaces, and Dispensers. It can also protect any other blocks, and by default will also protect Doors (Wooden + Iron), Signs and Trap Doors.
Blocks can be protected with three basic protection types:
Private
By default, only you can access this protection. You can also modify it (or specify when creating) to add other players or groups to the protection, so they can access it. Say you wanted Notch and Hidendra to both access the protection. When creating the protection, you could do /cprivate Notch Hidendra
or if it already exists /cmodify Notch Hidendra
. If you wanted to remove Hidendra from the private protection, you can use /cremove -Notch
Password
A password is set on the protection and anyone that knows the password can open it. You yourself also need this password each time you log in.
Public
Mainly targeted at community chests, a Public chest means just that: anyone can access it, but no one can protect it which makes it advantageous because it cannot be made private by someone else.
Commands
/lwc
- The LWC command for everything, however aliases are available to make some commands shorter. Type /lwc in-game for more detailed help./cprivate
- The alias of /lwc create private (or /lwc -c private), it creates a private protection./cpassword <password>
- The alias of /lwc create password <password>, it creates a passworded protection./cpublic
- The alias of /lwc create public, it creates a public protection/cremove
- Allows you to remove a protection you own (or if you're an LWC admin, any protection) - you must click on the protection after using/cremove
in order to remove it./cunlock <password>
- Allows you to attempt to gain access to a passworded protection after LWC tells you you attempted to open a password protection.... more!
There are aliases for all major used commands and every alias is not listed here.
Permissions
Basic permissions:
lwc.protect
- Allows the player to create and manage their own protections. It also allows them to use enabled modes and flags.lwc.mod
- Allows the player to open any chest, but not remove them.lwc.admin
- Gives the player absolute power to LWC - this node should be considered dangerous if used incorrectly as this node essentially gives you the right to destroy every protection (and even the block & inventory contents associated with it) in one command!lwc.deny
- Prevents players with this node from interacting with anything LWC can protect. For example, from opening or destroying protected and unprotected chests, furnaces, etc if protectable.
@x8105
Hi @x8105, that is indeed a problem. Removing lwc.protect would temporarily solve the issue (lwc.deny is disabled by lwc.protect). If you could hop in live chat (IRC) I will fix it as soon as I get home.
Thanks!
Scenerio found by our biggest pain and biggest fan, Player Enables LWC Droptransfer in main world and hops over to a creative world, with the ability to dump D-Blocks to his chest. We added the permissions to lwc.deny to his group and to the test account group / world, but still has the ability to droptransfer chest.
Multiverse latest, Multi Inv latest.
ALSO, MagnetChest, we are using Phat loots and Magnet Chest as a means of collecting player drops in our dungeons, Would it be possible in near future builds to configure a variable ranges and block types per chest? Chest 1, Important valuable loot range 128, Chest2 not so valuable common loot range 75, and Chest3 Misc Crap range 50.... ect. Default group, no permissions, Lower classranks, 10 block range, Higher class ranks 25 block range,
<<reply 408463="">>
@robxu9:
sounds like another plugin is failing and breaks LWC. e.g Permissions. Check for Yaml errors near the top of the server log
<<reply 407987="">>
@shinji257:
I marked the issue as appropriate on the git and am looking into it now. I could simply fix it but I'm looking into making the protection matcher easier to use and maintain anyway.
@Hidendra:
And I take that back DX
2011-10-19 14:48:23 [SEVERE] Could not pass event PLAYER_QUIT to LWC com.griefcraft.scripting.ModuleException: java.lang.NullPointerException at com.griefcraft.sql.Database.printException(Database.java:144) at com.griefcraft.sql.MemDB.unregisterPlayer(MemDB.java:818) at com.griefcraft.listeners.LWCPlayerListener.onPlayerQuit(LWCPlayerListener.java:194) at org.bukkit.plugin.java.JavaPluginLoader$2.execute(JavaPluginLoader.java:251) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:339) at net.minecraft.server.ServerConfigurationManager.disconnect(ServerConfigurationManager.java:159) at net.minecraft.server.NetServerHandler.disconnect(NetServerHandler.java:127) at org.getspout.spout.SpoutNetServerHandler.disconnect(SpoutNetServerHandler.java:507) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:365) at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:618) at net.minecraft.server.Packet10Flying.a(SourceFile:126) at net.minecraft.server.NetworkManager.b(NetworkManager.java:226) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:92) at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:500) at net.minecraft.server.NetworkListenThread.a(SourceFile:108) at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:471) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:374) at net.minecraft.server.ThreadServerApplication.run(SourceFile:417) Caused by: java.lang.NullPointerException at com.griefcraft.sql.MemDB.unregisterPlayer(MemDB.java:813) ... 17 more
And it can't pass any event...
I added buttons (stone_button) and levers (lever) to the list. It works fine as those that are not supposed to interact with it can't but I found that if you destroy the block they are attached to then it drops the item. Is it possible to protect the block they are on as well like you do for doors already?
@Hidendra
...You know, whenever devs respond to my inquiries, the thing starts working all of a sudden... Seems like CB 1240 fixed this problem...
@Endimmion: just add
type: default
@Hidendra
I've got some problems with the limits setting.
I'm using Craftbukkit Build 1317, LWC 3.53 and bPermissions.
My master config in limits.yml is that:
Below I've config that:
But I still receive warning that I've got too many protections and cannot protect chests or other things anymore.
<<reply 405939="">>
@robxu9:
what is the error you are receiving?
@Hidendra
I did... and everything came out correctly >_<
EDIT: Config below:
The only thing different is the wooden door. And that threw an exception >>;
I don't want to register for GitHub so yeah I have this problem and I recently updated my craftbukkit. Have any idea what this means?
<<reply 394773="">>
How long the server has been running for ;) In 4.0.0 it is displayed as a more friendly time (e.g xx hours xx minutes xx seconds)
<<reply 394942="">>
Much obliged ;)
<<reply 402011="">>
Paste your config file into this page: Yaml Parser
It will tell you your errors more easily ;)
Hi,
Whenever I modify even the slightest change in config.yml, it throws an exception about parsing YAML... Did something break?
Thank you for the awesome plugin! Just donated 10 USD!
-CKM Gaming!
http://ckmgaming.net
@Hidendra
works fine thx. With /lwc admin report I see "Time: 6816 seconds", what is that?
@dumle29
First off, default protections are configurable in lwc's config.yml
Secondly, you can use /cremove to remove the protection, much easier than /lwc -r protection.
<<reply 388919="">>
/lwc admin cleanup
;)Dont want to register at github so ill just post the ticket here
What is the enhancement in mind? How should it look and feel?
when a block is placed, it automaticaly gets a private protection, however to do the command /cpublic on a private block you first need to do /lwc -r protection, and that is pretty anoying.
so any new lock type, overrides the previous
Please provide any additional information below.