Permissions
Version: 1.0.0
Heirlooms checks two permission nodes. Command syntax is on the Commands page.
Permission nodes
Section titled “Permission nodes”| Permission | Default | Gates |
|---|---|---|
ks.heirlooms.user.open | allowed | /ksheirloom (the story window) |
ks.heirlooms.admin | not granted | /ksheirloom admin, test, check, clear, wear, reload and the admin window |
How the defaults work:
ks.heirlooms.user.openis checked as “allowed unless set”. A player whose node is set tofalsegets “You are not allowed to do that.” when typing/ksheirloom.ks.heirlooms.adminis the only admin node. The admin window checks it while it is open and closes itself when the node is taken away./kslanghas no permission.
What the nodes do not cover
Section titled “What the nodes do not cover”- Counting. Every player’s items count kills, ores, trees and hits and earn fame and titles, also without
ks.heirlooms.user.open. What counts is decided by the rules, not by permissions. - The tooltip. Everyone who hovers over an heirloom sees its story.
- The buttons in the story window. Wearing a title, choosing a boon and Show in chat have no node of their own. Show in chat is switched on or off for everyone with
messages.share. - Boons and banes. They are switched on or off for the whole server with
boons.enabled, not per player.
LuckPerms examples
Section titled “LuckPerms examples”Staff gets the admin commands
Section titled “Staff gets the admin commands”/lp group admin permission set ks.heirlooms.admin trueTake the story window away from a group
Section titled “Take the story window away from a group”/lp group guest permission set ks.heirlooms.user.open falseGuests then cannot open the window. Their items still count, and they can still read the tooltip.