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.
I am getting reports that locks placed on the new doors are spotty at best. They may be locked one time, then unlocked, and then locked the next.
Can you possibly add the option to only tell admins the name of the owner and not the UUID? Its a really long an obnoxious message with the UUID.
I just notice in my LWC database, i have a few 1000 protections still using player_names in the owner field while the rest are using UUIDs. Is there a way to convert those?
Hi i keep getting this logs about LWC
http://pastebin.com/CDrrMTLy
i don't know what they are
can someone help me please ?
i'm on CraftBukkit 1.7.9
thanks
How do i make this plugin become compatible with Tekkit Items ids example, RedStone Furnace, Item ID: 924
How do I get this plugin to work with all types of doors?
Question, So im trying to change the prefix, the way it looks when you lock something using /lock to a different colour instead of just the green, How would I do that, I can't find it in the config file?
@silentspectr
Set chest autoRegister in the config to false and they won't automatically lock anymore.
@ThoLav
thank you
do you know how i do put this by default in the config ?
@silentspectr
Use /unlock and click it.
Hi when i place a chest, it register automatically as a private chest so i can't put a password to it because it says that i have already registerde the chest.
how do i unregister it ? have have it unregistered by default when i place a chest
thanks
@twixi007
Please use pastebin, you've just filled a massive part of the thread with console spam.
My server MCPC 1.4.7 forge 6.6.1 on all versions LWC its error:
[SEVERE] Error occurred while enabling LWC v4.4.0 (b881) (July 11, 2013) (Is it up to date?) java.lang.NoSuchFieldError: HOPPER at com.griefcraft.sql.PhysDB.performDatabaseUpdates(Unknown Source) at com.griefcraft.sql.PhysDB.load(Unknown Source) at com.griefcraft.lwc.LWC.load(Unknown Source) at com.griefcraft.lwc.LWCPlugin.onEnable(Unknown Source) at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:217) at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:427) at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:381) at org.bukkit.craftbukkit.v1_4_R1.CraftServer.loadPlugin(CraftServer.java:289) at org.bukkit.craftbukkit.v1_4_R1.CraftServer.enablePlugins(CraftServer.java:271) at org.bukkit.craftbukkit.v1_4_R1.CraftServer.<init>(CraftServer.java:225) at gm.<init>(ServerConfigurationManager.java:121) at hn.<init>(DedicatedPlayerList.java:19) at ho.c(DedicatedServer.java:148) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:724) at fy.run(ThreadMinecraftServer.java:16)
help lpese its plugin - the best...
Anyone hosting the database externally via MySQL? I can convert from SQite, it populates the host tables, but then changing the type to mysql it then throws a wobbler saying it needs converting to MySQL! It seems like it is only targeted to use localhost.
@Syhedghog
Simple fix with 2 options.
Players unlock everything they have then change their name
or
/lwc admin purge oldplayername
then they lock everything again.
Edit: This was because of another plugin.
Recently updated to spigot 1.8.3
We are having a very odd bug, where some chests, will kick you when you try opening them. Break it, and you and anyone near you, will be kicked and not be allowed to return to the server. Even after a restart.
Here is the message you get upon login.
The only visible console error is a nullpointer error.
People are able to change names now and lwc locks to the name not the uuid
@NickGamerGR
I'm also having this problem. I'm on spigot 1.8.3 tho.