Permissions
LumenSmith uses a simple permission system compatible with any permissions plugin (LuckPerms, PermissionsEx, etc.).
Plugin Permissions
| Permission | Default | Description |
|---|---|---|
lumensmith.admin |
OP only | Access to /ls help, /ls list, /ls reload, /ls rescan, /ls fixbook, /ls delete |
lumensmith.gui |
Everyone | Access to /ls recipes (recipe browser GUI) |
lumensmith.create |
OP only | Access to /ls create (in-game recipe creator) |
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
permissionset, 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_messageis 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 recipes) is available to all players by default. To restrict it, negate the lumensmith.gui permission.
LumenSmith