Commands
Command: /lwc -info
Alias: /lwc -i, /lwci
Permission: lwc.info
Desc: Punch a protection to view information on it. For some block details you need access to the block.
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.
In the core.yml you can add custom blocks to enable the manual block protection and optional the auto protection with block place. The full instruction to the block configuration you found here. Blocks there aren't register in this config part can't protect.
All blocks you can protect with different types with various behaviors for other people there want to interact with it:
| 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 can of course be shared with other players to open it too. | /cpassword <password> |
| Public | Anyone can access the protection. | /cpublic |
| Donation | Anyone can put things into this protection, 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 define her own protection, in all types only he is the owner of the block. He and players with a staff permission can change the protection type. It's also able to define the access for other peoples.
Tipp: You can remove the protection of a block with the
/lwc -remove protectioncommand. » more infos
Note: If you protect a iron door / iron trapdoor (not dependent on the protection type) you can open and close it with right click too. By defaut, if you protect one door of a douple door, LWC will open both doors together for you. But it's saver to protect booths doors seperately. The behavior of doors / trapdoors you can configure in the
doors.yml.
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
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.
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.
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
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.
With the optional exception you add some protection exception for specific players or groups. » more infos
Command: /lwc -modify [exception]
Alias: /lwc -m, /cmodify
Permission: lwc.modify
Desc: Modify an existing protection.
With the optional exception you add some protection exception for specific players or groups. » more infos
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. |
r:<region> |
Allow all users there are member or owner of a specifically 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 to use it. |
For all listed definitions of positive accesses, with the präfix @ you can give the player / group additionally the permission to manage the access list by self for this block. They cannot disable the owner from modifying it.
For example, with @g:<group> you give these group the "protection admin" permissions for the block.
To remove players / groups (no matter the using of @) with a negative registration via -.
For example, with -g:<group> an already whitelisted group.
-
/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 may also modify the protection -
/cmodify g:vip Lola123 -Nick123- modified an exist protection: add the group "vip" and the user "Lola123" to the whitelist and remove the already defined player "Nick123" from the whitelist too.
Like you see in the examples, it's possible to attach more than one exception (or negative exception) with a blank as separator.
Command: /lwc -unlock
Alias: /lwc -u, /cunlock
Permission: lwc.unlock
Desc: Unlock a password-protected block.
Permission: lwc.remove
Command: /lwc -remove protection
Alias: /lwc -r protection, /unlock, /cremove
Desc: Removes protection from a block, no matter the type of protection there had.
Command: /lwc -remove modes
Alias: /lwc -r modes
Desc: Removes all player modes from you.
All about the Protection Flags found here.
All about the Player modes found here.
By default, the history is deactivated in the core.yml. You must activate the history to logging 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.
-
/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 there are 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, maybe you have to restart the server to update the protections. -
/lwc admin version- View the loaded LWCX version and - if exist - the latest available. -
/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 cache clear- Clear the server cache of LWCX. -
/lwc admin flush- Sync the server with the database. Use it after a cache clear. -
/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 infocommand.
All command to remove / cleanup the protections based on different conditions are described here.
