Reference

Permissions

Player permissions are on by default. Admin permissions are for operators by default. mcvaults.admin.* and mcvaults.user.* include all the nodes of their group.

Per-crate open permission

When a crate has no permission: of its own, opening it checks mcvaults.user.open.<crate-id> (for example mcvaults.user.open.example_crate). This node is not declared in plugin.yml, so give your players mcvaults.user.open.* in your permissions plugin (for example LuckPerms) or they may be told they have no permission. To lock a crate to a rank, set permission: in the crate file to your own node.

PermissionWhat it allowsDefault
mcvaults.user.*All player permissions below.true
mcvaults.user.openOpen crates with keys or through the crate screen, and quick-open with a key.true
mcvaults.user.open.<crate-id>Open one specific crate (checked unless the crate sets its own permission: node). Grant mcvaults.user.open.* for all crates.not declared
mcvaults.user.bulkOpen several crates at once (sneak quick-open, x5, x10).true
mcvaults.user.previewView a crate's rewards and use /mv list and /mv preview.true
mcvaults.user.menuUse /crates.true
mcvaults.user.withdrawUse /mv withdraw and /mv deposit.true
mcvaults.admin.*All admin permissions below.op
mcvaults.admin.reloadUse /mv reload.op
mcvaults.admin.panelOpen the admin panel.op
mcvaults.admin.givekeysUse givekeys, takekeys and setkeys.op
mcvaults.admin.setkeysListed in the admin group in plugin.yml. The key commands check mcvaults.admin.givekeys.op
mcvaults.admin.forceopenUse /mv forceopen.op
mcvaults.admin.bindUse /mv bind and /mv unbind. Breaking a bound block also unbinds it.op
mcvaults.admin.resetUse /mv resetdata.op
mcvaults.admin.simulateUse /mv simulate.op
mcvaults.admin.historyUse /mv history.op
mcvaults.admin.createUse /mv create.op
mcvaults.admin.deleteUse /mv delete.op
mcvaults.admin.updatesReceive update notices on join.op