Permissions | LumenSmith Wiki

Plugin Permissions

Permission	Default	Description
`lumensmith.admin`	OP only	Access to `/ls list`, `/ls reload`, `/ls rescan`, `/ls fixbook`, `/ls delete`, the browser's Delete Mode, and add/remove of blocked outputs from the browser.
`lumensmith.gui`	Everyone	Access to `/ls`, `/ls recipes`, and `/ls help`. Lets players open the recipe browser and view recipe details.
`lumensmith.create`	OP only	Access to `/ls create`, the browser's Create New Recipe button, and the Edit button inside the recipe detail view.

Per-Recipe Permissions

You can require a specific permission to craft any individual recipe. This is set in the recipe's configuration with the permission field.

custom_recipes:
  - key: "excalibur"
    type: "shaped"
    shape: [" D ", " D ", " S "]
    ingredients:
      D: "DIAMOND"
      S: "STICK"
    result:
      item: "DIAMOND_SWORD"
      amount: 1
      name: "&6Excalibur"
    permission: "lumensmith.craft.excalibur"
    permission_deny_message: "&cYou need VIP rank to forge Excalibur!"

How it works

When a player tries to craft a recipe that has a permission set, LumenSmith checks if they have that permission.
If the player lacks the permission, the crafting output is hidden (empty result slot) and the craft is blocked.
If permission_deny_message is set, that message is shown to the player when they attempt to craft.
The permission node can be anything you want; you are not limited to lumensmith.* names.

Per-recipe permissions are optional. If you don't set a permission field, anyone can craft the recipe.

Example Permission Setup (LuckPerms)

Grant all admin commands to a group:

/lp group admin permission set lumensmith.admin true

Allow a VIP group to craft a specific recipe:

/lp group vip permission set lumensmith.craft.excalibur true

Allow a builder group to use the recipe creator:

/lp group builder permission set lumensmith.create true

The recipe browser (/ls / /ls recipes) is available to all players by default. To restrict it, negate the lumensmith.gui permission.

Security Notes v0.1.5

Several permission gaps from earlier releases have been closed:

Tab-completion now respects permission. /ls delete <TAB> no longer leaks recipe keys to non-admins.
GUI delete requires lumensmith.admin (matching /ls delete; previously inconsistent with lumensmith.create).
GUI buttons are hidden when a player lacks the required permission, then re-checked server-side on click. Both the visual gating and the actual gating are in place.
Default-true lumensmith.gui means new users can immediately type /ls help and discover what's available without an op having to grant anything first.