Permissions
KyuubiSoft Lootbags uses two permission nodes. Command syntax is on the Commands page.
Permission Nodes
Section titled “Permission Nodes”| Permission | Default | Gates |
|---|---|---|
ks.lootbag.user.use | allowed | Opening a bag with a right-click, /kslootbags (aliases lb, lootbag) with every subcommand (catalog, crate, stats, settings), and pressing F on a placed bag |
ks.lootbag.admin | not granted | /kslootbagsadmin (alias lbadmin) with every subcommand, the admin panel (also when opened from the KyuubiSoft Core admin menu) |
How the defaults work:
ks.lootbag.user.useis checked as “allowed unless set”. Every player can open bags and use/kslootbagsout of the box. To block it, set the node tofalse; the player then gets “You do not have permission for this.” from the command and from a right-click (the bag is not used up); F on a placed bag does nothing.ks.lootbag.adminis the required permission of/kslootbagsadminand of each of its subcommands. The admin panel checks it again on every click, so taking the node away while the panel is open stops it at the next click (“No permission (ks.lootbag.admin)”)./kslanghas no permission: every player may pick their language.
What the Nodes Do Not Cover
Section titled “What the Nodes Do Not Cover”- The Open another button. The opening window only appears after an opening that passed the
ks.lootbag.user.usecheck; its Open another button does not check the node again. - Placing bags. Crouch + right-click places a bag like any block.
- Drops. Every player can receive bags from creatures and mining. Use the drop rules or
dropEnabledto change that. - The catalog through an NPC. A KyuubiSoft Core citizen with the ID
showcase_lootbagopens the catalog for every player who talks to it, without a permission check. - Tooltips (DynamicTooltipsLib) show for every player.
LuckPerms Examples
Section titled “LuckPerms Examples”Staff gets the admin tools
Section titled “Staff gets the admin tools”/lp group admin permission set ks.lootbag.admin true/lp user Steve permission set ks.lootbag.admin trueNo lootbags for a group
Section titled “No lootbags for a group”/lp group guest permission set ks.lootbag.user.use falsePlayers of that group can neither open bags nor use /kslootbags or F on a placed bag. They can still receive bags from drops and still see the catalog through a showcase_lootbag NPC.
Everything default (no setup)
Section titled “Everything default (no setup)”Nothing to do: ks.lootbag.user.use is allowed when it is not set, and ks.lootbag.admin is only granted where you add it.
Notes for Upgrades
Section titled “Notes for Upgrades”- The admin command is
/kslootbagsadmin(with “s”), its node isks.lootbag.admin(singular “lootbag”). The old auto-generated command permission is not used anymore. - Before 2.0.0 the admin panel opened from the Core admin menu did not check
ks.lootbag.admin. It does now; Core’s ownks.adminnode only opens the Core menu itself. - Before 2.0.0 right-click opening had no permission check. It now checks
ks.lootbag.user.use; groups where you set the node tofalsecan no longer open bags.