Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Most players will only need to know the basic functions of LWC. That is, protecting blocks and managing said protections.
There are 3 protection types in LWC:
|Public||Anyone can access the protection, but no one can protect it for themselves. Mainly useful for community chests that store items for anyone to use (or a chest in a Factions' Faction for any faction member to use)|
|Private||By default, only you can access the protection. You can also add other players and groups to the protection so that they, too can access it. So your chest and doors can only let in your close friends and those you choose to add to it.|
|Password||The protection has a set password and you need to enter it each time you login. This can of course be shared with other players -- they will be able to access the protection until they log out (after that they will need to re enter it)|
Note: Most servers will protect blocks to 'Private' when you place them. This is the default behaviour in LWC. If you want a password chest and it's already protected, simply use the command
/cremove and then hit your chest to remove the protection first.
Ok great, but how do I create a protection?
Is what you would use for a basic private protection. Password protection is the same deal.
Now pay attention to what happens in the chat box once you hit enter:
Hit your chest and you'll have a protection!
Viewing protection info
As a user or owner of a protection, you can use
/cinfo on a protection which will let you view information on a protection. An example of this command is below.
Or a private protection, which you own:
You'll probably notice this has an 'Access Control List' (or ACL for short) under it. This is covered more in the next section.
If you're an OP or have
lwc.admin, you'll usually see something like this (the extra info is just incase! It's never all that useful in practice)
Private protections - ACLs
Private protections can have various 'ACLs', or who exactly can access the protection. The owner is considered just that - the owner - and cannot be removed from the protection, only by using
/cremove on it.
You can add (and remove) ACLs from a protection both when creating it and after you create it. If you wanted to add your friends at the same time you used
/cprivate you'd use something like:
/cprivate player1 player2 .. and then hit your protection. You'll get something like:
Adding ACLs afterwards is done with
Removing ACLs / players from a protection is as easy as prepending
And finally, entire permission groups (defined in your perms plugin) can be granted to a protection by prepending g:->
(You can combine both player and group additions in the same command!)
(Note: Towny users can grant access to town residents by prepending town: to the town name. example: /cprivate town:Smithtown )
You can grant an ACL entity (a player or group) "admin" access to the protection. This means that they can use
/cmodify (but not
/cremove) to edit the protection. They will NOT be able to remove the owner (as the owner is outside the bounds of ACL) and thus can only add or remove other players.
This is done by prepending
Additionally, admins will show up in
/cinfo as an admin.
Finally, they can be removed just like any other group/player by prepending