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 observed that a wither was able to break locked chests and furnaces using it's ability that allows it to break all nearby blocks excluding bedrock/end portal blocks. The flags are set at default, which means they should be impervious to explosions.
Is this intended behavior?
This is bunk, If you have 1.7.2 and try using this with permissions EX they don't even work together and just error.
@harleyknd1
it does work as i have used it before plus about 24 hours after making my post i resolved my issue. also i have a permissions plugin i have setup 24 servers in the past and hadnt run accross this issue until the last update
SOLUTION:
1) Start the server if its a fresh install otherwise Delete entire LWC folder under plugins then Restart the server. 2) Open your core.yml file and proceed to step 3 3) Replace the items list starting after the last default item in the list and paste the item id's in the list provided in the pastebin below 4) http:pastebin.com/BA69esJY 5) Save your core.yml file 6) Restart your server
Now the items should now lock with LWC with FTB you have to manually add the id's
Is it possible to edit the messages or turn them off?
@Raginshunter
lwc doesn't work with ftb, cause ftb modifies the data files of containers :) also, lwc doesn't work without permissions, so you might have to install something like pex or bperms
@dsmith0996
have a negative permission node for the admins/mods in that world (aka lwc.admin -false) and grant them the lwc.unlock node allowing them to unlock password protected chests or just lwc.protect
We have a PVP world where we discovered anyone with lwc.mod and lwc.admin could create locked chests. How can we prevent this, but still be able to open any locked chest until we can remove all locked chests. I have tried adding -lwc.protect to the world, but mods and admins still created locked chests by default.
@Raginshunter
i even tried just having LWC by its self on the server with no luck after doing /cprivate and left clicking nothing happened when i left clicked
Hello i have a FTB Unleashed server launcher version 1.1.7 and minecraft version 1.5.2 with MCPC+ for version 1.5.2 which i have used before and now the issue which just started within the last week is.
i have installed the LWC plugin and its not working i can type /cprivate and it will say to left click the block to protect it but when i left click it doesnt register the block as it did before the most recent update ( even tried a older version and no luck) please help
i have not modified the files at all just a default install
any help would be awesome
@marc3108
I have the same Problem, also by automatically protection with chests
Hey,
at first sorry for my bad english.
When you will protect [Gate] Signs with the Command /cprivate there will come the Message that the protection was Successful but other player can interact with the Sign too.
Has anyone the problem too?
Critical Error: IDPlayer_Interact?
Whats the fix for this Error?
love this plugin :) stay forever please
@Matthew_Carter
in the config files under protections, change the values of autoregister from true/private to public
Hi, I am using this plugin on my server, it's very useful, except I have to keep removing protections when they are automatically protected, is there an option to not automatically create protections for a player, or even everyone? if there is, I couldn't find it, and if there isn't, please add it!
Is there maybe an option to change the type of protection created? if not, please add it!
It is very tedious to make like a room full of chests to be used as public storage, and having to
/cremove /cpublic
on each one... and the signs too -_-thanks!
@matze135
i am using bukkit (not spigot) but the 918 gives me an error message: "/plugins/LWC/lib/native/Linux/amd64/libsqlitejdbc.so: file too short" so not sure but guessing i can fix with new files ? have not tried uploading other files as LWC is supposed to be self contained
@ggincdeath:
I have Spigot 1.7.9 on my server and this LWC Version:
http://ci.griefcraft.com/job/LWC/918/
I have no problems.
Does the current version work with 1.7.2, or 1.7.9?
Hi, I was just wondering if the following is possible. A Player Bob creates a region and adds Player Fred to the regions owner list Bob places a Chest that is auto locked by LWC LWC checks the region and finds Fred's also an owner of the region so the plugin automatically adds him to the chest protection
Is this at all possible? as Ive tried many methods and none seem to work Thanks Sky
What about a disable funktion complete for lwc in worlds? So much useless options and no world disablefunktion?