[*:1rf8kgjx]Now open-source!
[*:1rf8kgjx]Both protections by user/group and by password
[*:1rf8kgjx]Limits of how many chests a user or group can lock
[*:1rf8kgjx]Small memory footprint (virtually none). No flatfiles. No excessive storage in memory--the protected chests are only loaded into memory temporarily when needed.
[*:1rf8kgjx]No excessive disk I/O. The only data stored on the disk is Chest locks and Limits. Everything else such as pending locks, unlocks, etc is stored in an sqlite in-memory database, which is never written to the disk.
[*:1rf8kgjx]sqlite is used--no MySQL is needed which some people can't run because it's heavy. SQLite comes with the mod, packaged with it if you will. in some cases SQLite is actually faster than MySQL. It's very fast and is very attractive for a mod such as this, where thousands of chests may be protected
Conversions
If you currently use Chest Protect, LWC includes a convenient converter. Other plugins may be supported at another time.
When you install LWC as you normally would, you can do 1 of 2 things to start the conversion process:
[*:1rf8kgjx]SSH/CMD into the plugins directory. Execute: java -cp LWC.jar CPConverter
[*:1rf8kgjx]In-game as an LWC admin. Execute: /lwc convert chestprotect
Commands
[*:1rf8kgjx]/lwc....
[*:1rf8kgjx]create public - Create a public chest ANYONE can access but not lock
[*:1rf8kgjx]create password <Password> - Create a password-protected chest
[*:1rf8kgjx]create private g:admins @Hidendra EvilGuy g:mods CoolGuy - Create a protected chest. @ denotes they are a chest admin (can add/remove users)
[*:1rf8kgjx]modify -EvilGuy Hidendra -g:mods - In the last command, this one would remove Hidendra's chest admin access, remove EvilGuy's access to the chest fully and also remove the group mods from access. - denotes removing them
[*:1rf8kgjx]free chest - Remove a chest, only the chest owner and LWC Admins can do this
[*:1rf8kgjx]free modes - Remove any modes on your player. For example, command persistence
[*:1rf8kgjx]info - View info on a chest. Chest admins, LWC admins/mods will be able to see extended info using this. Without either, you only see Type+Owner
[*:1rf8kgjx]persist - Any command you use will be usable more than one time. Ie, /lwc persist, and then /lwc info will let you info >1 chest when left clicking. Use /lwc free modes to reverse this
[*:1rf8kgjx]The following commands can only be used by LWC Admins
[*:1rf8kgjx]admin limits <amount> <groups/users> - Limits the list of groups/users to only be able to create so many protected chest (Protected=public,password,private). g:group denotes groups
[*:1rf8kgjx]admin clear chests - WARNING: PERMANENTLY REMOVES EVERY CHEST! NO WARNINGS!!
[*:1rf8kgjx]admin clear limits - WARNING: PERMANENTLY REMOVES EVERY LIMIT! NO WARNINGS!!
[*:1rf8kgjx]convert <PluginName>
Example: /lwc create private Hidendra g:mods
Aliases: (don't need to add to users to use, it's a "redirect")
[*:1rf8kgjx]/cpublic - /lwc create public
[*:1rf8kgjx]/cpassword <Password> - /lwc create password <Password>
[*:1rf8kgjx]/cprivate - /lwc create private
[*:1rf8kgjx]/cinfo - /lwc info
[*:1rf8kgjx]more to come! These are not yet showed publicly in the help message (type just /lwc as always to see it)
LWC Admins
LWC admins are players with access to /lwcadmin. They can free+view+modify any chest and view extended info using /lwc info.
LWC Mods
LWC mods are players with access to /lwcmod. They can view+modify any chest* and view extended info using /lwc info. * - lwc mods cannot view or modify chests owned by an lwc admin
example help screens
Installation
Put LWC.jar into your hMod Plugins directory and add LWC to the plugins= line in your server.properties
[*:1rf8kgjx]Disregard 1.36, you NEED this if you have 1.36
1.36
[*:1rf8kgjx]bug fix for some chests not protecting, which caused the next bug:
[*:1rf8kgjx]chest owners could clash if the chest was eventually protected (using the other side of the chest usually worked)
[*:1rf8kgjx]sql performance tweak, completely removing a physical db query, which depending on server size, may be noticeable
[*:1rf8kgjx]Source and downloads moved to Github: https://github.com/Hidendra/LWC/
[*:1rf8kgjx]Creepers + TNT no longer blow up chests
[*:1rf8kgjx]Help via commands is now a lot more informative
[*:1rf8kgjx]Bug fixes. Some include protections not working (COMMAND itself, protections worked 100%) all of the time, are now fixed
[*:1rf8kgjx]LWC Mods could not open a passworded chest owned by an admin (if they knew the password). Now fixed
1.33
[*:1rf8kgjx]Important security fix for permissions when removing chests
1.32
[*:1rf8kgjx]LWC Mods now cannot view or modify chests that are owned by LWC Admins
[*:1rf8kgjx]performance tweaks, code optimization, some removal
[*:1rf8kgjx]bug fixes, I can't remember any significant ones at this moment
1.31
[*:1rf8kgjx]Changed Hook priority for BLOCK_CREATED, BLOCK_DESTROYED, COMPLEX_BLOCK_CHANGE and COMPLEX_BLOCK_SEND to Medium
1.3
[*:1rf8kgjx]Some more sql optimization
[*:1rf8kgjx]Several bug fixes, including clean deletion of chests when a protected chest is removed.
[*:1rf8kgjx]/lwc info has been extended to anyone. To non chest admins, lwc admins + mods, it will only show the owner and type of the chest (private, public, password)
[*:1rf8kgjx]LWC Mods can now view+modify any chest
[*:1rf8kgjx]/lwc persist - enable commands to persist after one action, ie /lwc info or /lwc create
[*:1rf8kgjx]Aliases! These need not be added to player's commands, it will look for the original
[*:1rf8kgjx]/cpublic - /lwc create public
[*:1rf8kgjx]/cpassword <Password> - /lwc create password <Password>
[*:1rf8kgjx]/cprivate - /lwc create private
[*:1rf8kgjx]/cinfo - /lwc info
[*:1rf8kgjx]more to come! These are not yet showed publicly in the help message (type just /lwc as always to see it)
1.1
[*:1rf8kgjx]The following commands are removed: /lock, /unlock, /free, /info, /removepending, /removechests, /removelimits, /limits
[*:1rf8kgjx]Following command replaces everything: /lwc
[*:1rf8kgjx]/lwc....
[*:1rf8kgjx]create public - Create a public chest ANYONE can access but not lock
[*:1rf8kgjx]create password <Password> - Create a password-protected chest
[*:1rf8kgjx]create private g:admins @Hidendra EvilGuy g:mods CoolGuy - Create a protected chest. @ denotes they are a chest admin (can add/remove users)
[*:1rf8kgjx]modify -EvilGuy Hidendra -g:mods - In the last command, this one would remove Hidendra's chest admin access, remove EvilGuy's access to the chest fully and also remove the group mods from access. - denotes removing them
[*:1rf8kgjx]free chest - Remove a chest, only the chest owner and LWC Admins can do this
[*:1rf8kgjx]free pending - No longer needed as of 1.1, but still here just incase (deprecated)
[*:1rf8kgjx]info - View info on a chest. Only LWC admins and Chest admins can use this on their chests
[*:1rf8kgjx]The following commands can only be used by LWC Admins
[*:1rf8kgjx]admin limits <amount> <groups/users> - Limits the list of groups/users to only be able to create so many protected chest (Protected=public,password,private). g:group denotes groups
[*:1rf8kgjx]admin clear chests - WARNING: PERMANENTLY REMOVES EVERY CHEST! NO WARNINGS!!
[*:1rf8kgjx]admin clear limits - WARNING: PERMANENTLY REMOVES EVERY LIMIT! NO WARNINGS!!
what happens if an user uses the lock on a chest which hasn't got a lock yet.
I'm not sure what you're asking. Are you asking if someone uses /lock pass and then tries to lock a chest without a lock? It'll get locked. If it truly was someone else's chest, someone with access to /lwcadmin can use /free and remove the lock on it
[size=xx-large]
Originally it was they could view them as well, but nothing stopped them from taking items (they'd regenerate as if nothing happened, which essentially duped it)
If I'm reading this correctly, you (accidentally) made a chest in which 1 item can be taken an infinite number of times?
Is this still implementable through your plugin? I'm working on a system that gives users certain resources (instead of making them hunt down certain ones --- for the Runecraft mod) and would like not to have to keep running around and re-stocking the chests...
[size=xx-large]
Originally it was they could view them as well, but nothing stopped them from taking items (they'd regenerate as if nothing happened, which essentially duped it)
If I'm reading this correctly, you (accidentally) made a chest in which 1 item can be taken an infinite number of times?
Is this still implementable through your plugin? I'm working on a system that gives users certain resources (instead of making them hunt down certain ones --- for the Runecraft mod) and would like not to have to keep running around and re-stocking the chests...
Haha, yeah.
It's not implementable right now, but I guess if it were something people wanted I could add a different locked chest type, "resource chest", which only admins could add/remove items from and then anyone could withdraw (which the items in the chest would be infinite to non admins, of course).
It's not implementable right now, but I guess if it were something people wanted I could add a different locked chest type, "resource chest", which only admins could add/remove items from and then anyone could withdraw (which the items in the chest would be infinite to non admins, of course).
If you do implement it that would be awesome, right now I'm literally building small holes under every chest with teleporters and doing resource-runs where I refill them with the needed items (really annoying with non-stackables)
Nice, I'm definitely using this. It would also be great if these unlimited chests would only give a limit to the user of each item so as to prevent stockpiling. My idea is that I want to create pvp classes in an arena and the chest will only give 1 sword.
edit. Maybe also a command /public? Which essentially would put a lock on a chest but anyone can access it, so no one can put a personal lock on it
Nice, I'm definitely using this. It would also be great if these unlimited chests would only give a limit to the user of each item so as to prevent stockpiling. My idea is that I want to create pvp classes in an arena and the chest will only give 1 sword.
That's a step further towards what I'm looking at, I'm building a Legend of Zelda style server and woudl like 1x use chests for dungeon rewards, only-x-at-a-time for blocks to solve a puzzle, and infinite-number-forever for resources like torches
Nice, I'm definitely using this. It would also be great if these unlimited chests would only give a limit to the user of each item so as to prevent stockpiling. My idea is that I want to create pvp classes in an arena and the chest will only give 1 sword.
edit. Maybe also a command /public? Which essentially would put a lock on a chest but anyone can access it, so no one can put a personal lock on it
Hmm, yeah, a public chest would be a pretty dandy idea. It'll be in the next update (today, for sure).
Quote from AshtonDurkhun »
Quote from artlis »
Nice, I'm definitely using this. It would also be great if these unlimited chests would only give a limit to the user of each item so as to prevent stockpiling. My idea is that I want to create pvp classes in an arena and the chest will only give 1 sword.
That's a step further towards what I'm looking at, I'm building a Legend of Zelda style server and woudl like 1x use chests for dungeon rewards, only-x-at-a-time for blocks to solve a puzzle, and infinite-number-forever for resources like torches
Well, the problem with a limited withdrawl chest is that it would have to only allow 1 withdrawl, then it'd just not show them the contents anymore. What about making a kit, for say torches or whatever? You can also have kits have a time limit before you can get it again (like, 10 minutes for another sword, etc).
However, for the unlimited thing, I'll see about it
My idea on the limited withdrawal thing was that if you drag an item for this type of chest, it will check to see if that item already exists in the inventory. If it does, it will refuse to provide the user with the item. I don't know how plausible that is though.
Pointless if just destroying the chest makes it empty its contents.
Users not able to access the chest can't destroy it--but no mod prevents creepers,etc from just blowing it up. As long as creepers can't get to the chest, it's safe.
Quote from artlis »
My idea on the limited withdrawal thing was that if you drag an item for this type of chest, it will check to see if that item already exists in the inventory. If it does, it will refuse to provide the user with the item. I don't know how plausible that is though.
I see, it may not be 100% plausible as the mod can't see exactly what item the player took without caching the chest's contents, and even then it isn't reliable. On some servers it would be pretty bad.
also, proposed changes to do for tomorrow. I'll also have protection by groups and/or users instead of using a password in effect as well. Effectively, /lock will be replaced with something like:
Okay, thank you everyone for your awesome patience :tongue.gif:
I think I tested everything OK, if anyone sees anything let me know and I'll get it patched up
You shouldn't lose ANY chests currently protected when upgrading. It modifies the physical table, but it will realize this if it sees that and upgrade accordingly without erasing your data :wink.gif:
1.1
[*:2mjaatvv]The following commands are removed: /lock, /unlock, /free, /info, /removepending, /removechests, /removelimits, /limits
[*:2mjaatvv]Following command replaces everything: /lwc
[*:2mjaatvv]/lwc....
[*:2mjaatvv]create public - Create a public chest ANYONE can access but not lock
[*:2mjaatvv]create password <Password> - Create a password-protected chest
[*:2mjaatvv]create private g:admins @Hidendra EvilGuy g:mods CoolGuy - Create a protected chest. @ denotes they are a chest admin (can add/remove users)
[*:2mjaatvv]modify -EvilGuy Hidendra -g:mods - In the last command, this one would remove Hidendra's chest admin access, remove EvilGuy's access to the chest fully and also remove the group mods from access. - denotes removing them
[*:2mjaatvv]free chest - Remove a chest, only the chest owner and LWC Admins can do this
[*:2mjaatvv]free pending - No longer needed as of 1.1, but still here just incase (deprecated)
[*:2mjaatvv]info - View info on a chest. Only LWC admins and Chest admins can use this on their chests
[*:2mjaatvv]The following commands can only be used by LWC Admins
[*:2mjaatvv]admin limits <amount> <groups/users> - Limits the list of groups/users to only be able to create so many protected chest (Protected=public,password,private). g:group denotes groups
[*:2mjaatvv]admin clear chests - WARNING: PERMANENTLY REMOVES EVERY CHEST! NO WARNINGS!!
[*:2mjaatvv]admin clear limits - WARNING: PERMANENTLY REMOVES EVERY LIMIT! NO WARNINGS!!
I'm having a bit of trouble with chest locking. I got a chest locked at one point and then destroyed it. Now when ever I try to make a new one it says I've exceed the limit on locked chests, even when I haven't spawned any chests.
I'm having a bit of trouble with chest locking. I got a chest locked at one point and then destroyed it. Now when ever I try to make a new one it says I've exceed the limit on locked chests, even when I haven't spawned any chests.
did you/someone else make a limit of 0 on you/your group?
It just works. This chest protection mod is different than any other: it's more flexible and secure (in a way).
Github project page: https://github.com/Hidendra/LWC
Features
[*:1rf8kgjx]Now open-source!
[*:1rf8kgjx]Both protections by user/group and by password
[*:1rf8kgjx]Limits of how many chests a user or group can lock
[*:1rf8kgjx]Small memory footprint (virtually none). No flatfiles. No excessive storage in memory--the protected chests are only loaded into memory temporarily when needed.
[*:1rf8kgjx]No excessive disk I/O. The only data stored on the disk is Chest locks and Limits. Everything else such as pending locks, unlocks, etc is stored in an sqlite in-memory database, which is never written to the disk.
[*:1rf8kgjx]sqlite is used--no MySQL is needed which some people can't run because it's heavy. SQLite comes with the mod, packaged with it if you will. in some cases SQLite is actually faster than MySQL. It's very fast and is very attractive for a mod such as this, where thousands of chests may be protected
Conversions
If you currently use Chest Protect, LWC includes a convenient converter. Other plugins may be supported at another time.
When you install LWC as you normally would, you can do 1 of 2 things to start the conversion process:
[*:1rf8kgjx]SSH/CMD into the plugins directory. Execute: java -cp LWC.jar CPConverter
[*:1rf8kgjx]In-game as an LWC admin. Execute: /lwc convert chestprotect
Commands
[*:1rf8kgjx]/lwc....
Example: /lwc create private Hidendra g:mods[*:1rf8kgjx]create public - Create a public chest ANYONE can access but not lock
[*:1rf8kgjx]create password <Password> - Create a password-protected chest
[*:1rf8kgjx]create private g:admins @Hidendra EvilGuy g:mods CoolGuy - Create a protected chest. @ denotes they are a chest admin (can add/remove users)
[*:1rf8kgjx]modify -EvilGuy Hidendra -g:mods - In the last command, this one would remove Hidendra's chest admin access, remove EvilGuy's access to the chest fully and also remove the group mods from access. - denotes removing them
[*:1rf8kgjx]free chest - Remove a chest, only the chest owner and LWC Admins can do this
[*:1rf8kgjx]free modes - Remove any modes on your player. For example, command persistence
[*:1rf8kgjx]info - View info on a chest. Chest admins, LWC admins/mods will be able to see extended info using this. Without either, you only see Type+Owner
[*:1rf8kgjx]persist - Any command you use will be usable more than one time. Ie, /lwc persist, and then /lwc info will let you info >1 chest when left clicking. Use /lwc free modes to reverse this
[*:1rf8kgjx]The following commands can only be used by LWC Admins
[*:1rf8kgjx]admin limits <amount> <groups/users> - Limits the list of groups/users to only be able to create so many protected chest (Protected=public,password,private). g:group denotes groups
[*:1rf8kgjx]admin clear chests - WARNING: PERMANENTLY REMOVES EVERY CHEST! NO WARNINGS!!
[*:1rf8kgjx]admin clear limits - WARNING: PERMANENTLY REMOVES EVERY LIMIT! NO WARNINGS!!
[*:1rf8kgjx]convert <PluginName>
Aliases: (don't need to add to users to use, it's a "redirect")
[*:1rf8kgjx]/cpublic - /lwc create public
[*:1rf8kgjx]/cpassword <Password> - /lwc create password <Password>
[*:1rf8kgjx]/cprivate - /lwc create private
[*:1rf8kgjx]/cinfo - /lwc info
[*:1rf8kgjx]more to come! These are not yet showed publicly in the help message (type just /lwc as always to see it)
LWC Admins
LWC admins are players with access to /lwcadmin. They can free+view+modify any chest and view extended info using /lwc info.
LWC Mods
LWC mods are players with access to /lwcmod. They can view+modify any chest* and view extended info using /lwc info.
* - lwc mods cannot view or modify chests owned by an lwc admin
example help screens
Installation
Put LWC.jar into your hMod Plugins directory and add LWC to the plugins= line in your server.properties
Download
https://github.com/downloads/Hidendra/LWC/LWC.jar
Changelog
1.37
[*:1rf8kgjx]Disregard 1.36, you NEED this if you have 1.36
1.36
[*:1rf8kgjx]bug fix for some chests not protecting, which caused the next bug:
[*:1rf8kgjx]chest owners could clash if the chest was eventually protected (using the other side of the chest usually worked)
[*:1rf8kgjx]sql performance tweak, completely removing a physical db query, which depending on server size, may be noticeable
1.35
[*:1rf8kgjx]Chest Protect converter
[*:1rf8kgjx]bug fixes
1.34
[*:1rf8kgjx]Source and downloads moved to Github: https://github.com/Hidendra/LWC/
[*:1rf8kgjx]Creepers + TNT no longer blow up chests
[*:1rf8kgjx]Help via commands is now a lot more informative
[*:1rf8kgjx]Bug fixes. Some include protections not working (COMMAND itself, protections worked 100%) all of the time, are now fixed
[*:1rf8kgjx]LWC Mods could not open a passworded chest owned by an admin (if they knew the password). Now fixed
1.33
[*:1rf8kgjx]Important security fix for permissions when removing chests
1.32
[*:1rf8kgjx]LWC Mods now cannot view or modify chests that are owned by LWC Admins
[*:1rf8kgjx]performance tweaks, code optimization, some removal
[*:1rf8kgjx]bug fixes, I can't remember any significant ones at this moment
1.31
[*:1rf8kgjx]Changed Hook priority for BLOCK_CREATED, BLOCK_DESTROYED, COMPLEX_BLOCK_CHANGE and COMPLEX_BLOCK_SEND to Medium
1.3
[*:1rf8kgjx]Some more sql optimization
[*:1rf8kgjx]Several bug fixes, including clean deletion of chests when a protected chest is removed.
[*:1rf8kgjx]/lwc info has been extended to anyone. To non chest admins, lwc admins + mods, it will only show the owner and type of the chest (private, public, password)
[*:1rf8kgjx]LWC Mods can now view+modify any chest
[*:1rf8kgjx]/lwc persist - enable commands to persist after one action, ie /lwc info or /lwc create
[*:1rf8kgjx]Aliases! These need not be added to player's commands, it will look for the original
[*:1rf8kgjx]/cpublic - /lwc create public
[*:1rf8kgjx]/cpassword <Password> - /lwc create password <Password>
[*:1rf8kgjx]/cprivate - /lwc create private
[*:1rf8kgjx]/cinfo - /lwc info
[*:1rf8kgjx]more to come! These are not yet showed publicly in the help message (type just /lwc as always to see it)
1.1
[*:1rf8kgjx]The following commands are removed: /lock, /unlock, /free, /info, /removepending, /removechests, /removelimits, /limits
[*:1rf8kgjx]Following command replaces everything: /lwc
[*:1rf8kgjx]/lwc....
[*:1rf8kgjx]create public - Create a public chest ANYONE can access but not lock
[*:1rf8kgjx]create password <Password> - Create a password-protected chest
[*:1rf8kgjx]create private g:admins @Hidendra EvilGuy g:mods CoolGuy - Create a protected chest. @ denotes they are a chest admin (can add/remove users)
[*:1rf8kgjx]modify -EvilGuy Hidendra -g:mods - In the last command, this one would remove Hidendra's chest admin access, remove EvilGuy's access to the chest fully and also remove the group mods from access. - denotes removing them
[*:1rf8kgjx]free chest - Remove a chest, only the chest owner and LWC Admins can do this
[*:1rf8kgjx]free pending - No longer needed as of 1.1, but still here just incase (deprecated)
[*:1rf8kgjx]info - View info on a chest. Only LWC admins and Chest admins can use this on their chests
[*:1rf8kgjx]The following commands can only be used by LWC Admins
[*:1rf8kgjx]admin limits <amount> <groups/users> - Limits the list of groups/users to only be able to create so many protected chest (Protected=public,password,private). g:group denotes groups
[*:1rf8kgjx]admin clear chests - WARNING: PERMANENTLY REMOVES EVERY CHEST! NO WARNINGS!!
[*:1rf8kgjx]admin clear limits - WARNING: PERMANENTLY REMOVES EVERY LIMIT! NO WARNINGS!!
enjoy, gentlemen
What happens if a user sets attempts to set a password on a chest with a password by another user?
Check out my Let's Play, Now in Season 2! Also, TF2 commentaries!
Awesome generated world?
viewtopic.php?f=35&t=56150
Nothing will happen.
I'm not sure what you're asking. Are you asking if someone uses /lock pass and then tries to lock a chest without a lock? It'll get locked. If it truly was someone else's chest, someone with access to /lwcadmin can use /free and remove the lock on it
If I'm reading this correctly, you (accidentally) made a chest in which 1 item can be taken an infinite number of times?
Is this still implementable through your plugin? I'm working on a system that gives users certain resources (instead of making them hunt down certain ones --- for the Runecraft mod) and would like not to have to keep running around and re-stocking the chests...
Haha, yeah.
It's not implementable right now, but I guess if it were something people wanted I could add a different locked chest type, "resource chest", which only admins could add/remove items from and then anyone could withdraw (which the items in the chest would be infinite to non admins, of course).
If you do implement it that would be awesome, right now I'm literally building small holes under every chest with teleporters and doing resource-runs where I refill them with the needed items (really annoying with non-stackables)
Thread Bookmark'd :happy.gif:
edit. Maybe also a command /public? Which essentially would put a lock on a chest but anyone can access it, so no one can put a personal lock on it
That's a step further towards what I'm looking at, I'm building a Legend of Zelda style server and woudl like 1x use chests for dungeon rewards, only-x-at-a-time for blocks to solve a puzzle, and infinite-number-forever for resources like torches
Hmm, yeah, a public chest would be a pretty dandy idea. It'll be in the next update (today, for sure).
Well, the problem with a limited withdrawl chest is that it would have to only allow 1 withdrawl, then it'd just not show them the contents anymore. What about making a kit, for say torches or whatever? You can also have kits have a time limit before you can get it again (like, 10 minutes for another sword, etc).
However, for the unlimited thing, I'll see about it
Users not able to access the chest can't destroy it--but no mod prevents creepers,etc from just blowing it up. As long as creepers can't get to the chest, it's safe.
I see, it may not be 100% plausible as the mod can't see exactly what item the player took without caching the chest's contents, and even then it isn't reliable. On some servers it would be pretty bad.
also, proposed changes to do for tomorrow. I'll also have protection by groups and/or users instead of using a password in effect as well. Effectively, /lock will be replaced with something like:
(the - denotes removing the user from access to the chest)
Thoughts? It's the best I could think up in a few minutes, I may think of something better during school tomorrow :V
I think I tested everything OK, if anyone sees anything let me know and I'll get it patched up
You shouldn't lose ANY chests currently protected when upgrading. It modifies the physical table, but it will realize this if it sees that and upgrade accordingly without erasing your data :wink.gif:
1.1
[*:2mjaatvv]The following commands are removed: /lock, /unlock, /free, /info, /removepending, /removechests, /removelimits, /limits
[*:2mjaatvv]Following command replaces everything: /lwc
[*:2mjaatvv]/lwc....
[*:2mjaatvv]create public - Create a public chest ANYONE can access but not lock
[*:2mjaatvv]create password <Password> - Create a password-protected chest
[*:2mjaatvv]create private g:admins @Hidendra EvilGuy g:mods CoolGuy - Create a protected chest. @ denotes they are a chest admin (can add/remove users)
[*:2mjaatvv]modify -EvilGuy Hidendra -g:mods - In the last command, this one would remove Hidendra's chest admin access, remove EvilGuy's access to the chest fully and also remove the group mods from access. - denotes removing them
[*:2mjaatvv]free chest - Remove a chest, only the chest owner and LWC Admins can do this
[*:2mjaatvv]free pending - No longer needed as of 1.1, but still here just incase (deprecated)
[*:2mjaatvv]info - View info on a chest. Only LWC admins and Chest admins can use this on their chests
[*:2mjaatvv]The following commands can only be used by LWC Admins
[*:2mjaatvv]admin limits <amount> <groups/users> - Limits the list of groups/users to only be able to create so many protected chest (Protected=public,password,private). g:group denotes groups
[*:2mjaatvv]admin clear chests - WARNING: PERMANENTLY REMOVES EVERY CHEST! NO WARNINGS!!
[*:2mjaatvv]admin clear limits - WARNING: PERMANENTLY REMOVES EVERY LIMIT! NO WARNINGS!!
How would one set it up so that himself and maybe 3 or 4 others on the server could access it? other than with a password
Use /lwc info and then click on your chest. When it says "Installed lock successfully" it did not fail
Say your friends were:
Bob, Jane, Alfred
You would do:
/lwc create private Bob Jane Alfred
That would also give them access to the chest
did you/someone else make a limit of 0 on you/your group?