Skip to content

Permissions

RedstoneFuture edited this page Mar 10, 2023 · 32 revisions

Note: All modern permission plugins support wildcard permissions. Some wildcard permissions are defined in the plugin.yml manually, so if you have permission priorisation problems wth grouped or wildcard permissions, check this file at first to validate the prio based of child permission and the default value.

Basic Permissions

Full tutorial: here

Node Description Default
protection info lwc.info false
modify lwc.modify false
unlock lwc.unlock false
remove lwc.remove false

Create a protection

Full tutorial: here

lwc.create: The main permission to create a manually or auto protection. It also gives you access to create every protection type, so you have to use the follow specific permissions to disable it. (Default: true)

Node Description Default
Private protection lwc.create.private false
Password protection lwc.create.password false
Public protection lwc.create.public false
Donation protection lwc.create.donation false
Display protection lwc.create.display false

Autoprotect / Autoregister

Full tutorial: here

lwc.autoprotect: Gives you access to creating automatic protections. (Default: false)

Protection Flags

Full tutorial: here

Node Description Default
Magnet flag lwc.flag.magnet false
Redstone flag lwc.flag.redstone false
Auto Close flag lwc.flag.autoclose false
Allow Explosions flag lwc.flag.allowexplosions false
Hopper flag lwc.flag.hopper false
Hopperin flag lwc.flag.hopperin false
Hopperout flag lwc.flag.hopperout false
Exemption flag lwc.flag.exemption false

lwc.allflags: Gives you access to every usable flag. Alternative, the normal wildcard permission lwc.flag.* will also work. (Default: false)

Basic Permission Pack

lwc.protect: The main permission node that is given to players by default. (Default: true)

It allows players to:

  • lwc.info
  • lwc.modify
  • lwc.unlock
  • lwc.remove
  • lwc.create.∗
  • lwc.autoprotect
  • lwc.flag.∗

Access Deny

lwc.deny: Denys you access to any block LWC can protect based your block configuration. (Default: false)

For example, with this permission set, you cannot open even unprotected chests (if protectable).

Player modes

Full tutorial: here

Node Description Default
Persist mode lwc.mode.persist false
Nolock mode lwc.mode.nolock false
Nospam mode lwc.mode.nospam false
Droptransfer mode lwc.mode.droptransfer false

lwc.allmodes: Gives you access to every usable mode, provided they are already disabled in the core.yml. Alternative, the normal wildcard permission lwc.mode.* will also work. (Default: false)

Misc / Staff Permissions

Node Description Default
remove all protections you own lwc.removeall true
open anyone's protection but not remove them lwc.mod false
shows protection notices ¹ lwc.shownotices op

¹ For example, when they click on a protection they can access, they will see Notice: This XXXX is protected by YYY. This is mainly useful for administrative roles so that you know that a chest you opened is protected by LWC and who it is protected by.

Admin Commands

Full tutorial: here

Node Description Default
view lwc.admin.view false
find lwc.admin.find false
forceowner lwc.admin.forceowner false
forceownerall lwc.admin.forceownerall false
remove lwc.admin.remove false
purge lwc.admin.purge false
cleanup lwc.admin.cleanup false
version lwc.admin.version false
update lwc.admin.update false
report lwc.admin.report false
convert lwc.admin.convert false
clear lwc.admin.clear false

lwc.admin: It gives them destructive powers along with the ability to view and remove any protection at will. The player can essentially delete every protection if they are not careful with one command. They also have access to any Admin Commands. It down't include the lwc.protect permission. (Default: false)