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.
01:00:58 [INFO] [Metrics] Server returned HTTP response code: 500 for URL: http://metrics.griefcraft.com/report/LWC
Where can I find latest stable LWC-Economy.jar
@Endimmion
Fix for groups limits is not 4.0.5 after some tests
I was wondering if you could please use VAULT for your permissions system instead since it supports everything, and it will be easier on you.
I have tried setting up custom limits per group using PEX but it doesnt take.. It would be great if you could use VAULT which will integrate with all of them. You only need to add 3 things.
Does 4.0.5 include the fix for groups limits for bPermissions 2.7?
I don't see any information about this in the changelog
okay sorry im late but i didnt have much time to finish it so here is the translation: http://pastie.org/3183353
Evening.
I am having troubles with a couple things and I'm wondering if you could set me straight.
First I was trying to get a basic discount working for a perms group and I have the configs set as:
limitsv2.yml:
iconomy.yml:
At first this worked but after a server reboot the discount is no longer working for some reason. It just charges the base cost. Chest limiting is working as it should.
The other issue I have is, I am trying to figure out how to have it so donor groups have a decrease in LWC costs as well as have x amount of LWC's for free but for the life of me cannot work out how to do it.
I have seen it done on other servers before so know it is possible.
For example,
and so on.
Any info on this would be much appreciated.
Thanks :D
Need any more info, just let me know.
@mike0fmikes
Still have that problem? If so, try removing your serverBankAccount: [iConomyAccountName] name from the iconomy.yml, create an account with iConomy first then add the name of the newly created account back into the serverBankAccount: [iConomyAccountName]. I am actually having no problems as far as I can see without using an account name, but I did get the same error when I first added an account name.
Although signs can be protected by default, the block underneath them isn't.
Makes it pretty easy for other players to break the sign by destroying the block underneath it.
It still works with signs placed on walls, the wall block becomes protected.
Is there any way to fix this? It still seems to work that way with doors and trapdoors.
I'd also like to protect the block under rails and redstone wire for the same reason.
Using LWC 4.0.4
Well - I want to migrate to MySQL and i followed this: http://wiki.griefcraft.com/wiki/LWC/MySQL
But the lwc plugin nevertheless uses sqllite....
No GitHub Account, so I post a little little Bug here:
In the locale: I have to use "iron" for "iron=Amboss" (iron_block/ironblock... doesn't work)
In the limitsv2.yml I have to use "iron_block" for showing "Amboss" ingame with /climits. (iron/ironblock... doesn't work)
Only with the item-ID like "42", it won't show the items with /climits.
Error :( how to fix :(
[SEVERE] Error occurred while enabling LWC v4.0.4 (b601-git-648cec22) (Is it up to date?): null java.lang.NullPointerException at com.griefcraft.util.config.ConfigurationNode.removeProperty(ConfigurationNode.java:526) at com.griefcraft.util.config.ConfigUpdater.update(ConfigUpdater.java:136) at com.griefcraft.util.config.Configuration.load(Configuration.java:138) at com.griefcraft.util.config.Configuration.load(Configuration.java:106) at com.griefcraft.lwc.LWC.<init>(LWC.java:212) at com.griefcraft.lwc.LWCPlugin.onEnable(LWCPlugin.java:234) at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:188) at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:968) at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:280) at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:186) at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:169) at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:128) at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigurationManager.java:52) at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:145) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:399) at net.minecraft.server.ThreadServerApplication.run(SourceFile:457)
@ServerFrog
Quickfix:
edit the plugin.yml in the jar and modified load: startup to
load: POSTWORLD and added depend: ['iConomy']
The reason is maybe the Plugin Vault. Vault stands for a iCon Plugin but it doesnt it! And the iCon Method useMiniDB() use a static Field that only be not null when iCon is going to be enable (onEnable() Method). Maybe it helps to develop ;) (Make maybe a Thread that Watch and wait until iCon is init! I think in the same way work Vault. It Announced it when it hooked into iCon when it loaded. Maybe this way, maybe a other :D)
@Hidendra "@derkb
They are fixed in the latest dev builds it'll be in the next official release."
Config: iConomy: true and serverBankAccount: 'Server' database is mysql on localhost and same database for both. it is maybe a iConomyBug? dsnt find anythin usefull in the Queried class on the first watch. He is checking wich database somone use(fisrt minidb then inventoryDb and then use it SQL) but when not used miniDB it returned the Method and dont use the database = iConomy.Database.getDatabase();
@saftb1
Something you'll have to set up with the permission nodes. Donors should have a different permission rank, or individual permissions, and lwc.protect should be given to the donors.
@Hidendra to bobeeb
are you using MySQL? Please drop or rename the lwc_rights table - it is no longer used as of LWC 4 and may be causing the extra lag (I won't explain it in depth why unless you want me to)//
thnx for the info, i deleted the table with a sqlite editor an the delay is gone
Hi, Is there any way to have only our donators use chest protections and default players cant?
hello is it posible you can made a permission note that lets mods open doors and trapdoors and break signs, but dont let them open chests or furnaces ? make it like lwc.mod.limited or something
Am I doing something wrong, or is it impossible since 4.0.0 to protect open trapdoors against redstone, so redstone doesn't close the trapdoor? It was possible before 4.0.0, and I really need that! At the moment it just prevents redstone from opening it... :(
Can't get LWC to charge players for some reason. Using the latest version of Vault and iConomy and LWC reports that it found and is using iConomy. In iConomy.yml I have enabled set to true and charge set to a default value of 1. No discounts are active and the player does not have any permissions except lwc.protect