Commands and permissions

The root command is /sigil; /sg is an equivalent alias. Run /sigil help for the syntax your installed build exposes. Item arguments accept namespaced ids such as aether:mythril.

/sigil menu

Browse every registered item. Click one to see its recipe laid out.sigil.command.menu

/sigil give <item> [player] [amount]

Hand out an item by its namespaced id.sigil.command.give

/sigil list

List every registered item, including disabled definitions.sigil.command.list

/sigil info <item>

Abilities, triggers, cooldowns, interaction rules and recipes for one item.sigil.command.info

/sigil recipe <item>

Open the recipe viewer for an item. This command is player-only.sigil.command.menu

/sigil refresh [player|all]

Re-render existing Sigil stacks against the current definitions. With no argument, refreshes your inventory.sigil.command.refresh

/sigil reload

Re-read config, items, recipes and loot. Items already in inventories update themselves afterwards.sigil.command.reload

/sigil platform

The detected server, the compatibility tier chosen and the scheduler in use.sigil.command.platform

Command permission reference

Node	Default	Controls
`sigil.command.give`	operator	`/sigil give`
`sigil.command.reload`	operator	`/sigil reload`
`sigil.command.refresh`	operator	`/sigil refresh`
`sigil.command.platform`	operator	`/sigil platform`
`sigil.command.list`	everyone	`/sigil list`
`sigil.command.info`	everyone	`/sigil info`
`sigil.command.menu`	everyone	`/sigil menu` and `/sigil recipe`

Command permissions grant access normally. The deny-only model below applies to using registered items and abilities, not to administrative commands.

Permissions are deny-only

Everything works out of the box. You take things away rather than granting them.

Node	Denies
`sigil.item.<ns>.<id>`	that item entirely
`sigil.ability.<ns>.<id>.<ability>`	one ability, leaving the rest of the item usable

In LuckPerms:

/lp group default permission set sigil.item.aether.mythril false

The ability node is per ability id, which is why the id matters: renaming it in the item file resets both the cooldown key and this node.

An item can override its own node with permission: in its file, if you would rather group several items under one.

Explicit false is what denies an item or ability. An unset node does not deny it, so permission plugins should not bulk-grant these dynamic nodes merely to make items work.