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.
Please make 1.10 version!!
In reply to Forge_User_60251221:
Hello, so I am an admin for the server and I was wondering if there was a way to toggle the "Notice: that private chest is locked by(name)" since it spams the chat quite heavily
In reply to Clammychimera6:
It's LWC plug for chests, type:
/lwc:cnospam
I'm not sure if there's a command/setting for admins so everyone on the server doesn't have to individually type it.
(This reply is for other people whom haven't figured it out, before you ask "why reply to old post)
It is possible for a player to give access to all your blocks to another player without being block a block? How?
Can admins figure out passowrds?
usually admins and OPs can open any chest if the owner of the server wants to
Is the LWCv5 the one that works with 1.11 ? Thanks for helping.
@alien12
thank you so much for trying to help ! i have tried everything and still not working, when i put LWC.jar for the first time it creates the files so now u want to change the sqlite.jar with the one 3.15.1 jar right ? also when i go to LWC\lib\native\Windows\amd64 it creates lib\native\Linux\a,d64\ not Windows this is done in the server side right ? so add the windows one ? If u have a couple of minutes could u do a step by step please ? Thank you ! Happy thanks giving to everyone !
@smmmadden
You can update the sqlite versions that the plugin is using yourself for now. Search for sqlite-jdbc, download the 3.15.1 jar file and rename it to match what is in the LWC\lib. The dll for LWC\lib\native\Windows\amd64 can be found inside the jar file (you can open it with 7zip etc).
Everything seems to be working on 1.11, obviously make a backup of your db in case anything does go wrong.
@Jabberwockie666
Wow, thanks for your guide to fixing older plugins. Great to know! Would really love to try this, but I am working in a Mac environment and fear I wont' be able to do it due to lack of tools. Could you post your updated version maybe? Would be massively appreciated. Cheers!
Hi, what is your schedule for updating LWC for 1.11. Spigot released 1.11 yesterday and LWC isn't loading properly due to the upgrade in the database drivers (java.lang.NoClassDefFoundError: org/SQLite/NativeDB
Thanks, Steve
Whatup.
My 1.10.2 server uses a remapped LWC.
Check the LWC curse download page comments for
some neat tricks how to update many plugins yourself and
a link to working ChestShop plugin I fixed using the same method.
If this or other plugins seem semi-abandoned since 1.8?
You might need to be able to update them yourself in the future.
Learn the method. Become the ninja master, not the victim.
https://mods.curse.com/bukkit-plugins/minecraft/lwc
https://dev.bukkit.org/bukkit-plugins/chestshop/#c5388
Oh, Hidendra has done a massively wonderful job of LWC
and may or may not keep it up to date in the future. Who knows.
Who cares? You can update it yourself NP. Check links.
I will never give up on this plugin.
Take care!
LWC/ChestShop MANY other discontinued plugins.
FULL 1.10 + 1.9 compatibility? You can fix them.
LWC IS NOT AT ALL DEAD FOR 1.10+
I would upload my jars but you really need to know how to do this because you can fix/rewrite other plugins using the same techniques!
It's not nearly as geeky as it looks below. Easy even. I did it on
my 1st try without even knowing a single thing about Java. If it
takes you 26 tries before you get it right? So what? 27th try is a WIN.
You will need.
Java Development Kit latest + latest Java version.
You likely will also need a Github account and unix/dos shell application BASH. Some experience working with script helper files (.sh) would also help. Get the latest "SpecialSource.jar"or an earlier version if needed.
(Latest is 5m old. Dont be worried about it's age, it fixes LOADS)
If you recently used buildtools.jar to get the latest or a specific
bukkit/spigot then you likely already have everything you need.
Just grab specialsource.jar and done.
VERY rough guide.
Get build tools.
Get SpecialSource.jar
Put your broken plugin in a folder the same as specialsource.jar.
make a text file that points to your JDK folder path and version + the .csrg file and the broken plugin by name. save the .txt as specialsource.sh Something like this.
JAVA_HOME="C:\Program Files\Java\jdk1.8.0_31" java -jar SpecialSource-2.jar map -m deprecation-mappings.csrg -i SignLogger1.0.jar -o SignLogger-1.10.jar
-i is the input jar.
-o is the new name output jar.
The above fixed an ancient 1.7 plugin to work for 1.10.2
Now just run the .sh file and depreciated mappings utility will rewrite all the broken class paths and stuff in your plugin.jar to the correct up to date paths/event names. It just outputs a new jar with all the new stuff. This has fixed many plugins for me where I would have had to let those plugins go because discontinued. Fixed LWC for 1.9.
Now I'm running 1.10.2 with LWC absolutely no issues. (Paper v897. Not spigot/bukkit) Sometimes? When devs disappear and leave plugins broke or falling behind in versions?
You may be able to update them yourself. Do the above.
It's worth the brain pain! Folks are O.o that you have working versions
of seemingly obsolete or discontinued plugins in 1.9 + 1.10.
Who's the Ninja Master! You. You can do it. Give it a go.
LWC? I'm a total Lockette dodger. LWC for life!
ALSO!
There is a .class editing .jar file at sourceforge.net.
You can to surprising degree rewrite whole plugins with this.
It's basic and not nearly as good as a source rebuild but
it does do alot to allow you to edit bukkit API paths and events.
Sometimes you can fix things that the above remapping tool will
miss like broken /APIPath/item/mob names.
"EnderDragon" > "Ender_Dragon" for an example. Cannot fix
this without actually editing the .class in the .jar
Get yourself a class editor. I recommend the one at sourceforge.
Unpack the broken/abandoned/discontinued/any plugin into
a new folder. Now you can actually edit the class files.
Backup your original jar first. Replace the .class files in your copy of the plugin's jar with your edited ones and upload to server. Start.
Fixed. You can also remake entire plugins using this cheesy cheap
but effective tool.
Mojang is at war with plugins /bukkit/spigot. It started with the EULA.
It only keeps getting more brutal.
EVERY new version comes with tons of trollfaced petty changes
to NBT / item/mobs names / events / class paths.
They are trying to bully the hell out of anyone that runs a plugins server every new update. Face the music and dance. The above methods will help you dance, and not fall over. If you are a total config dodger? Forget the above and poke your top admin to do this for the server instead.
If this post helps you? Please like the plugin +1 not the post ^^
Hidendra? I love your plugin. Even if you are no longer here to say thanks to... THANK YOU! Even if Hidendra fixed LWC for latest versions
what use would it do for your other busted plugins? Learn the above.
<3
CHESTSHOP
Using the above fixit method?
You can now download a fully working ChestShop.jar
for 1.9 + 1.10.2 at the ChestShop plugin comments.
Check out my comment and attatched .jar here
https://dev.bukkit.org/bukkit-plugins/chestshop/#c5388
Have fun you.
http://www.filedropper.com/chestshop3812
As for the SpecialSource file, not sure which server uses version 2 shown above, but with Spigot 1.11, the one I used to fix ChestShop For Iconomy 7.5 (actually v3.8.12) was using the two files from:
SpecialSource-1.7.5-SNAPSHOT-shaded.jar dated May 16, 2016
Deprecation-Mappings.csrg dated 29-Feb-2016
Other than that, it worked perfectly. :-)
+1
The method worked for some old addons I use. Fast and splended method :)
@sergehumphrey
Thank you!
Hidendra's lastet version of LWC from his GitHub. Download LWC.jar
I get some LWC errors. Can someone help me try to fix all of my errors? Maybe pm me or something. Thanks.
http://pastebin.com/gAw2e1iW