Permissions
Every permission node, what it grants, and a sensible split between players and staff.
All nodes live under deluxepouches.. Grant them with whichever permissions plugin you
run.
The nodes
| Node | Grants |
|---|---|
deluxepouches.use | Open pouches, and take a pouch from the menu. Every player needs this |
deluxepouches.help | /dp help and /dp version |
deluxepouches.gui.open | /dp gui |
deluxepouches.list | /dp list |
deluxepouches.give | /dp give |
deluxepouches.reload | /dp reload |
deluxepouches.admin.debug | /dp debug, /dp testmodel, and right-click details in the menu |
deluxepouches.* | Everything above |
Without deluxepouches.use a player cannot open a pouch at all, even holding one.
This is the node people forget.
Per pouch permissions
A pouch can demand a node of its own on top of deluxepouches.use:
legendary:
permission: pouches.legendaryThe node is yours to name, it does not have to sit under deluxepouches.. Leave the
key out, or set it to an empty string, and anyone with deluxepouches.use can open the
pouch.
Handy for donator tiers: give the pouch away freely, but only paying ranks can open it.
A sensible split
- deluxepouches.use
- deluxepouches.helpEnough to open pouches and read the help. Add deluxepouches.gui.open if you are happy
for players to browse the menu, but see the warning below.
The menu shows each pouch's reward list and chances. If you would rather players not
read the odds, keep deluxepouches.gui.open for staff.
Notes
- Nodes are not granted by default. Operators pass every permission check, so test with a normal account, not from an op account.
deluxepouches.createanddeluxepouches.editappear inplugin.ymlbut no command uses them at the moment. Granting them changes nothing.- Right-clicking a pouch in the menu checks
deluxepouches.admin.debug, so staff see the configuration dump instead of receiving the pouch.