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 have absolutly no clue how to charge people for locking chests..... Is it even possible anymore? :3 Or am I just completely blind
@Nivek71Minecraft
I am fully aware of the /cmodify command.
I'd like to add a function that doesn't require that command, which is the reason for the question. Though considering I see no information anywhere for other developers, I am led to believe LWC wasn't exactly made to be expandable from an outside source.
@sakura_blades
There's always the /cmodify command. I suppose you could have a dev write a quick fix-up, where when a user is added to your friend list, it'll add them to the access. Not really sure, though.
Is there a way to expand on LWC?
Say I wanted to add a feature to my plugin that created personalized groups "friends lists" is it possible to automatically cause these friend groups to be able to use/edit LWC protections?
Perhaps an API or hook that my plugin can connect to, to speak to LWC that these 'friends' have certain permissions to a player's locks?
How to add protection of mod blocks in core.yml by using block name?
I add block id to core.yml and success, but in 1.8, block id is not been supported.
Block name with 'minecraft' works.For example, to protect minecraft:chest, add "chest" to core.yml and it works. But for example, I want to portect "Thermalexpansion:strongbox",I try to add "Thermalexpansion:strongbox" or "Thermalexpansion_strongbox" or "strongbox" and all failed.
Getting this error quite often. Is this a big deal?? http://pastebin.com/ARywmp0W
I can't reach the LWC Jenkins server at http://ci.griefcraft.com/
It shows me this:
Error 522 Ray ID: 1c060a95a263168e
Connection timed out
Have tried 5 times the past hour, is anyone else getting this?
EDIT:
Seems to be back up now :)
http://puu.sh/gcf21/0520bc2986.jpg
Err this keeps popping up and there is no console error.
Hello I am having an error loading LWC, It is because something is already loading the sqlite native. Is there some way to fix this?
Is this useful for factions or not ?
Adding the block you're looking at to the protection list with just a small /cadd command would be great if possible...
Mainly since modded servers use this awesome plugin as well.
Is there any way to give players possibility to blockade only for password? Without a permanent blockade?
That would be really great to give players chance to hack into a private house
Hello all im here to save the day with recent name changes. Download and use SQLITE open your database file and go to 'Execute SQL' tab. Run the command below to update all old names to new names for anyone who updates.
users cant open chests after name changes! lease fix! thank you for the awesome plugin!
Now that username changes are available people have been changing names.
When a name is changed the locked chest doesn't update to the new name so the player can't access his/her chest and has to lock a new one.
Hi. i dont think UUID support has even been implemented yet. When is it going to be implemented or has it been implemented?
I'm trying to track down a semi-frequent server lockup on a large (50-100 players online) server, and I'm not sure the cause- could you please tell me if this stack trace comes from LWC?
Ugh, that's hard to read- well mainly it looks like two threads deadlocked, and the culprit came from
com.griefcraft.modules.credits.CreditsModule$CreditsTask.run(CreditsModule.java:110)
But I can't quite figure out where that code comes from.
Here is the full crash report from the server logs:
http://pastebin.com/wFp7Pcxg
Thank you for any help you can provide!
@MedicOP123
Scratch that, I see that UUID support has not been implemented yet. When will it be implemented?
craftbukkit/spigot 1.7.9-R0.2 after starting server none of the files even attempt to load. If i remove the plugin it runs just fine. But server will not start it just hangs while attempting to load. Any suggestions??
Edit:nvm forced closed added more ram from 16G to 32gig and now it works...I guess the cache was so large it just needed more ram to compile it all...-_-
Also, having 42 plugins installed doesn't help either...lol