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/cremovein 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.
-
View User Profile
-
Send Message
Posted Aug 7, 2013@Usa_Rox_All
How did you find those percentages? :S Can you monitor the performance of plugins somehow? I have looked around so long for something like that :O
-
View User Profile
-
Send Message
Posted Aug 7, 2013How can I improve the french translation ?
-
View User Profile
-
Send Message
Posted Aug 6, 2013Why does my server take a while to do this, and what is it doing?
-
View User Profile
-
Send Message
Posted Aug 6, 2013@mike136032
per world - lwc.deny ? maybe? :D
-
View User Profile
-
Send Message
Posted Aug 6, 2013I have multiple worlds and one world is a pvp world. In this world, i only want blocks to be locked when the player is online. I want chests to be locked 24/7 in all other worlds. How can i do this? is there a specific node i can give or take away for certain world(s)?
-
View User Profile
-
Send Message
Posted Aug 6, 2013All users have all permissions without putting it in PEX... how to manage permissions for LWC please... I used this plugin a lot in the past, without any problem...
-
View User Profile
-
Send Message
Posted Aug 5, 2013hi please fix so whe can lock horse's i have tried myhorse but that doesn't work so good !
-
View User Profile
-
Send Message
Posted Aug 5, 2013@PocK123
I'll tell you the same, because it is listed very clearly in the wiki! https://github.com/Hidendra/LWC/wiki/Configuration
The option is under "modes:" in your Plugins\LWC\core.yml file..
-
View User Profile
-
Send Message
Posted Aug 5, 2013@little_dude187
Assuming you have already check the wiki which you can find the link to at the top of this page, I will give you a quick example since you obviously have read the wiki but still don't understand it. Because of course you checked the wiki before asking basic questions that is very clearly shown in the wiki right? ^^
The following line is added under the "protections:" line in Plugins\LWC\core.yml
'117':
enabled: true
autoRegister: private
"117" is the ID for the block you want to protect.
the next line is called "enabled:" you want to put in "true" if you want people with permissions to type /lock to lock it.
"autoRegister:" is the last option, in here you can write "public" or "private", or you can not add it if you don't want to automaticly lock it.
Hope it helps! But really, at least take a peek at the wiki before asking :P
-
View User Profile
-
Send Message
Posted Aug 5, 2013Hi !
How do i disable 'cdroptransfer' for LWC ?
-
View User Profile
-
Send Message
Posted Aug 4, 2013@ShawnPR1
Are you using LWC 4.4.0? It should protect registered chests from hoppers extracting items by default. ( /chopper needed to allow it )
@flip284
In your core.yml go down to where it says chest and remove this line:
autoRegister: private
-
View User Profile
-
Send Message
Posted Aug 3, 2013@TungstenKnight
Thanks a bunch ... but it doesn't work at all :/
I know how to do config so I didn't make any parse errors. Everything is aligned the way it's meant to be aligned (I use notepad for easy configuration).
Any other ideas??
-
View User Profile
-
Send Message
Posted Aug 3, 2013@ShawnPR1
Shawn, under optional in your "core.yml" make sure that:
blacklistedBlocks: - '166' - '154'
exists. It'll prevent hoppers from touching chests.
-
View User Profile
-
Send Message
Posted Aug 3, 2013@ShawnPR1
Maybe have users protect the region that they place their chests in? Try worldguard.
-
View User Profile
-
Send Message
Posted Aug 3, 2013as an OP on my server, every time I create a chest it automatically becomes protected. How do I turn this off? It is VERY annoying and I never get a response.
-
View User Profile
-
Send Message
Posted Aug 3, 2013Alright, this is a really big issue you HAVE to look into, please:
When you declare a chest as private, nobody can open it (obviously), but there is a way to bypass the lock ... You simply place a hopper under the chest and all of it's content will get removed.
Seeing my server has a lot of people who know about this trick, things are bound to get messy. Merely telling them not to use the glitch isn't enough.
PLEASE FIX THIS!!
- other than that : Great plugin! A must-have for all Minecraft servers
-
View User Profile
-
Send Message
Posted Aug 1, 2013Please take a look at my pull request when you get a sec. It fixes an issue where the attached block to a lever or button isn't protected. It was implemented but the flags were never updated. I updated it and submitted a patch for merge. It has been tested already.
https://github.com/Hidendra/LWC/pull/686
-
View User Profile
-
Send Message
Posted Jul 31, 2013I made this LWC core.yml configuration for modpack FTB Unleashd. This block all itens IDs from 1 to 31999. Download: http://is.gd/Ixxk6v
-
View User Profile
-
Send Message
Posted Jul 31, 2013@Hidendra Have you looked into the "InventoryMoveItemEvent" issue? I haven't tried removing lwc on my server yet, but we are experiencing a lot of lag almost regulary. It starts of with a few spikes after a restart before it grows slowly with more and more lag.
Plugins list: http://blacksheep.gaming.multiplay.co.uk/file/Plugins.html
This issue has been brought up many times in this comment field: http://dev.bukkit.org/bukkit-plugins/lwc/?comment=1905 http://dev.bukkit.org/bukkit-plugins/lwc/?comment=1912 http://dev.bukkit.org/bukkit-plugins/lwc/?comment=1917 http://dev.bukkit.org/bukkit-plugins/lwc/?comment=1944
@pyro56808
There is already a ticket about protection of leads: https://github.com/Hidendra/LWC/issues/658
The way I understand it, LWC is not designed to protect entities, only blocks. You are probably better off with one of the horse-protection plugins, or do like me: I am using precious stones on my server, in player-placed city protection fields, only the owner of the field and allowed people can break leads on fenceposts.
@toxicscopesMC
I am not sure about this, but if you are using a permission plugin using groups, you can /cmodify [groupname]
Like i said though, I'm not sure about this :)
@Ianhalmond
I just tested this on my 1.6.2 server with LWC version 4.4.0 and it didn't happen. When you run 4.4.0 for the first time on your bukkit server, LWC will add another line in it's core.yml: denyHoppers: true
This means that ever protection created after the update, will not allow hoppers to take items from the protected block. Be aware that this also includes hoppers that are placed by the owner. If you want to enable hoppers on a protection, write /chopper off and punch the protected block you want to enable hopper on.
Hope this helps!
BTW, have anyone tried KodekPL's fixed .jar file? His comment: http://dev.bukkit.org/bukkit-plugins/lwc/?page=2#c1927
-
View User Profile
-
Send Message
Posted Jul 31, 2013LWC seems to drop my TPS down. Everytime I place a sigh down it takes around 3-5 seconds for it to show up and drops my TPS from 20 to down to 18 or 16.