Commands

Info

Command: /lwc -info

Alias: /lwc -i, /lwci

Permission: lwc.info

Desc: Click a block to view information about it's protection. For some details you need access to the block.

Limits

Command: /lwc -info limits

Alias: /lwc -i limits, /climits

Desc: View the number of protections you own, and the number you are allowed to create.

Create A protection

Basic Command: /lwc -create

Basic Permission: lwc.create

In the core.yml you can add custom blocks for which you want to enable the manual block protection and optionally activate automatic protection on block placement. The full instruction to the block configuration are found here. Blocks there aren't listed in this config part can't be protected.

All available blocks can be protected with various protection-types. All of these types have different interaction restrictions for other people.

Protection	Description	one of the Commands
Private	Only you can access the protection.	/cprivate
Password	The protection has a set password. You need to enter it each time you log in. This password can be shared with other players, so they can use the block as well.	/cpassword <password>
Public	Anyone can access the protection, but no one can protect it for themselves.	/cpublic
Donation	Anyone can put things into the protected block, but won't be able to take anything out.	/cdonation
Display	The contents of the protection may be viewed by others, but they will not be able to put anything in or take anything out.	/cdisplay

If a player defines a block protection, he is in all protection types the only owner of the block. The owner, as well as players with a staff permission, can change the protection type and the access for other peoples.

Tipp: You can remove the protection of a block with the /lwc -remove protection command. » more infos

Note: If you protect a iron door / iron trapdoor (not dependent on the protection type) you can open and close by right clicking. If one of the two doors of a double door is protected, by default LWCX will open both at the same time. But it's saver to protect booths doors seperately. The behavior of doors / trapdoors can be configured in doors.yml.

Private protection

Command: /lwc -create private [exception]

Alias: /lwc -c private, /lock, /cprivate

Permission: lwc.create.private

Desc: Create a private protection: only you are able to access the block.

With the optional exception you add some protection exception for specific players or groups. » more infos

Password protection

Command: /lwc -create password <password>

Alias: /lwc -c password, /cpassword

Permission: lwc.create.password

Desc: Create a password protection: every time you log in you need to unlock the block with /cunlock and the password. Anyone who knows the password can access the protection.

Public protection

Command: /lwc -create public

Alias: /lwc -c public, /cpublic

Permission: lwc.create.public

Desc: Create a public protection: anyone can use a public protection, but no one can unlock it except for the owner.

Donation protection

Command: /lwc -create donation [exception]

Alias: /lwc -c donation, /cdonation

Permission: lwc.create.donation

Desc: Create a donation protection: anyone can put items inside the protection, but they cannot be taken back out.

With the optional exception you add some protection exception for specific players or groups. » more infos

Display protection

Command: /lwc -create display [exception]

Alias: /lwc -c display, /cdisplay

Permission: lwc.create.display

Desc: Create a display protection: anyone can view the protection's contents, but cannot modify them.

You can optionally make exceptions for specific players or groups. » more infos

Modify

Command: /lwc -modify [exception]

Alias: /lwc -m, /cmodify

Permission: lwc.modify

Desc: Modify an existing protection.

You can optionally make exceptions for specific players or groups. » more infos

Protection Exception / Access Control List

Positive Access

You can add players / groups to a protection, to give him the access to interact with the block.

Syntax	Description
<playername>	Add a player to the block-whitelist.
g:<group>	Add a group to the block-whitelist.
region:<region> or r:<region>	Allow all users who are members or owners of a specific WorldGuard region. No matter of the block is inside this region or not. (This feature must be to activate in the worldguard.yml of LWCX.)
town:<town> or t:<town>	Allow all users who are added in a Towny region. No matter of the block is inside this town or not.

Positive Access + Admin Permission

With the präfix @ in front of the player / group, you can give the player / group additionally the permission to manage the access list for this block. They cannot disable the owner from modifying it.

For example, with @g:<group> you give a group the "protection admin" permissions for the block.

Negative Access

You can remove players / groups (ignoring @) by using -.

For example, with -g:<group> you remove the access for an already added group.

More Examples:

• /cprivate Hidendra g:moderator - creates a private protection for yourself, the player "Hidendra", and the group "moderator".
• /lwc -c private @pop4959 - creates a private protection for yourself, and the player "pop4959", who can also modify the protection.
• /cmodify g:vip Lola123 -Nick123 - modifies an exist protection: it adds the group "vip" and the user "Lola123" to the whitelist and removes the already allowed player "Nick123" from the whitelist.

Tip: Like you see in the examples, it's possible to attach more than one exception (or negative exception) with a blank as separator.

Unlock

Command: /lwc -unlock

Alias: /lwc -u, /cunlock

Permission: lwc.unlock

Desc: Unlocks a password-protected block.

Remove

Permission: lwc.remove

Remove Protection

Command: /lwc -remove protection

Alias: /lwc -r protection, /unlock, /cremove

Desc: Removes a protection from a block, no matter the type of protection.

Remove Player Modes

Command: /lwc -remove modes

Alias: /lwc -r modes

Desc: Removes all player modes from you.

Protection Flags

All about the Protection Flags found here.

Player modes

All about the Player modes found here.

History

By default, the history is deactivated in the core.yml. You must activate it, if you want to log new protections and to get result with the history commands:

    # If true, LWC will not log history about protections. If you are using LWC-Economy and this is disabled, you will
    # NOT receive refunds for purchased protections
    disableHistory: false

• /lwc history <player> - Search the LWCX history.
• /lwc details <history ID> - Display details from "History ID" obtained from /lwc history.

Admin Commands

Basic Commands

• /lwc admin view <protection ID> - View a protected inventory using the protection's ID, if you're standing beside it.
• /lwc admin find <player> [page] - Get a list with all protections that have been created by a player.
• /lwc admin forceowner <new player> [protection ID] - Change the owner of a protection.
• /lwc admin forceownerall <old player> <new player> - Change the owner of all of a player's protections. After these command, you may have to restart the server to update all the protections.
• /lwc admin version - View the loaded LWCX version and - if not already exist - the latest available version.
• /lwc admin update - Update to the latest version of LWCX if it's newer than the installed version.
• /lwc admin report - View the LWCX performance / analyze report.
• /lwc admin flush - Save all unsaved data manually. (It's the same flush that happens when you shut down the server.)
• /lwc admin cache clear - Clear the server cache of LWCX manually. (Use it after the flush command.)
• /lwc admin convert - Convert another plugin's database to LWCX.

Tipp: One way to get the ID of a speficically protection is to use the /lwc admin find <player> [page] or /lwc info command.

Protection Cleanup

All command to remove / cleanup the protections based on different conditions are described here.