LWC or LightWeight Chest Protection is service that allows players to control access to their "usable" containers, like chests, furnaces, and hoppers, and also to who can open movable object like doors. The most common application is to lock a container against being opened (by a thief). The command may also be used to set permissions that allow only certain user(s) or groups to access it, or even be set to require a password to open.
A registered MCO player can set two containers to be protected by LWC. With higher levels of donation the number of protected objects grows.
- /lwc - is the primary command of the Lightweight Chest Protection service. The options given with the command determine what it does
Note that in this context "create" means "apply permissions", it does not create the container. Note also that if the container is a chest that it may be a one or two block version but still count as just one locked object. It is also okay to apply permissions to a single block chest and later add a second second chest to make it a double .. the permissions remain attached to the double chest.
The player using the lwc command to create a protected object is the owner of that protection and will always be able to modify or remove access permissions on it.
Permissions are applied to the block, not the object itself, so if you protect a chest and then break the chest, the permissions remain set on the empty blocks. It is possible to remake the chest, or whatever, in that same location and it will still be under LWC protection.
- /lwc -create <access level> [<user list>] - sets the container for access by you alone.
- /lwc -c <access level> [<user list>] - Alias for the "-c private" command.
- /cprivate <access level> [<user list>] - Another alias for the "-c private" command.
where <access level> may be "public", "private", or "password"
Public access means that anyone can access the protected block, and that it cannot be protected by anyone. Anything in the object can be taken by anyone, and anyone can deposit things into it.
Private access, with a list of users means that only those users, and the object owner, can access the contents of the object, or use it in the case of doors etc. However, be careful when using this option if you would change your username in the future, because as for now, LWC is uses your current username and not your UUID.
Password access does not use a list of users, but only those that can give the password can unlock the protected object.
LWC provides Access Control List (ACL) options that restrict container access to only specified 'users', or groups. Users may be just mentioned by name. Group names are denoted by prefixing g: before the name. @ denotes the named user(s) or group(s) is to have admin powers on the container and so can add or remove users.
For Instance: /lwc create private g:admins @Hidendra EvilGuy g:mods CoolGuy means:
- members of the "admins" group can access the container, but are not admins for it.
- user Hidendra has access and admin powers on the container
- user EvilGuy has only access permissions, even if he(she) is a member of the admins group
- members of the "mods" group also have access
- CoolGuy has access too
Existing permissions may be modified, new ones added, or existing ones removed or changed.
- /lwc -modify <list of names>
- /cmodify Alias of -modify command
- /lwc -m Another Alias of -modify
Modification commands use the same syntax as Create commands for applying special permissions, with the addition of a minus sign, '-', as a prefix before a User or Group name that has the effect of removing a permission
- /lwc -m -g:Members - removes access to the block for everyone in the Members group
- /cmodify -User1 @someguy
- remove access to the block for User1
- give SomeGuy admin privileges on the block
With reference to the previous ACL example:
- /lwc -modify -EvilGuy Hidendra -g:mods
- remove Hidendra's admin access, making him a regular user of the container
- EvilGuy loses all access
- the "mods" group loses its "only access" permisison
Remove a Protection
when you need to remove the protection from a block you give one of the following command and then punch the object, with default controls that means you left-click it.
- /lwc -remove <object type> then left click the container you want to remove protections from
- /lwc -r <object type> alias for the remove command
where <object type> is one of "chest", "furnace", or other object name.
to obtain information about a proetected object bove this command and then punch (left-click with default controls) the object.
- /lwc -info
- /lwc -i Alias for lwc -info.
- /cinfo - Alias for lwc -info.
Admins or high level donors can use this command to know where your chests are use this command
- /wherearemychests - Reports the coordinates of all your protected objects.
- /lwcwhere - alias for the above.
To wipe out all of your protections use this command
- /lwc admin limits amount groups/users - Sets chest protection limits for users or groups (protected=public,password,private).
- /lwc admin clear limits - unsets all limits.
- /lwc admin clear chests - clears all chests, equivalent to deleting lwc.db (pretty extreme).
- Players who have Registered may protect up to two containers.
- Every donation level adds an additional container to the player's limit:
- Wood donors may protect three containers.
- Stone four containers.
- Iron five containers.
- Gold six containers.
- Diamond seven containers.
- Obsidian eight containers.
- Nether nine containers.
- Aether ten containers.
- God donors may protect up to thirty containers (but they don't really need chests anyway).