Permissions
For breaking LuckyBlocks or getting it from mineable addon, or performing some commands
you need a permissions manager plugin like PermissionsEx
or LuckPerms (Recommended)
tip
You can disable break permission requirement using config
You can read about granting permissions nodes on plugin's wikis. (/op <name>
grants all permissions)
tip
LuckPerms permission granting examples:
- Break pink LuckyBlock:
/lp group default permission set luckyblock.break.pink
- Craft yellow LuckyBlock:
/lp group default permission set luckyblock.craft.pink
- Execute reload command:
/lp user Danirod_Gaming permission set luckyblock.command.reload
- You can find more examples at official LuckPerms wiki
LuckyBlock Permissions
luckyblock.break.<color>
- Break LuckyBlocks permission (example:luckyblock.break.red
) orluckyblock.break.*
for allluckyblock.craft.<color>
- Craft LuckyBlocks permission (example:luckyblock.craft.red
) orluckyblock.craft.*
for allluckyblock.dye.<color>
- Dye LuckyBlocks permission (example:luckyblock.craft.red
) orluckyblock.dye.*
for allluckyblock.command.<command>
- Access to some command (The command should be primary)- ⚠️
luckyblock.command.gui
andluckyblock.command.gui.get
both required for/lb gui get
. There you will needluckyblock.get.<color>
orluckyblock.get.*
to purchase a LuckyBlock luckyblock.mineable.<material>
- Permission for getting LuckyBlocks by digging blocks (example:luckyblock.mineable.stone
) orluckyblock.mineable.*
for allinfo
You should set up Mineable addon first. Mineable addon is a premium version feature
luckyblock.place.disabled
- Permission to place LuckyBlock to disabled worldsinfo
You can still disable this ability using
worlds.yml
option (place-admins: false
)
Commands Permissions
Now you can check permissions in commands list,
but most often it is luckyblock.command.<command>
(example: luckyblock.command.reload
for /ntdluckyblock reload
)