Permissions

Permissions

Defaults out of the box

Without touching any permission plugin at all, right after installing QuickDeposit:

• Every regular player already has quickdeposit.use and quickdeposit.all - so /deposit and /deposit all work for everyone immediately. This is intentional: QuickDeposit is meant to be a QoL feature available to the whole server, not something you have to manually grant.
• Every regular player has none of the admin permissions and none of the fourteen per-container override permissions - those all default to false/op, so a normal player cannot change any global setting and has no individual container overrides.
• Server operators (op) additionally get every permission marked op below for free - all four quickdeposit.admin.* commands and quickdeposit.bypass.cooldown - without needing a permission plugin at all, since that's how Bukkit's op system works for any permission whose default is op.

If you don't run a permission plugin, this is all you get: regular players can deposit, operators can additionally administrate. To grant anything more granular than that (letting a non-op moderator use /qd reload, giving a VIP rank an individual radius override behavior, etc.) you need a permission plugin such as LuckPerms - see the sections below.

Basic use

Permission	Default	Description
quickdeposit.use	true	Allows using /deposit.
quickdeposit.all	true	Allows using /deposit all.
quickdeposit.bypass.cooldown	op	Skips the /deposit cooldown entirely.

Both quickdeposit.use and quickdeposit.all default to true, so every player can use the plugin the moment it's installed - you only need to touch permissions if you want to restrict it for some players/groups, or grant quickdeposit.bypass.cooldown to certain ranks.

Admin commands

Permission	Default	Description
quickdeposit.admin.info	op	Allows /qd info.
quickdeposit.admin.reload	op	Allows /qd reload.
quickdeposit.admin.radius	op	Allows all /qd radius ... subcommands.
quickdeposit.admin.container	op	Allows all /qd container ... subcommands.

Per-player container overrides

Container types are enabled or disabled globally in config.yml (or via /qd container global), and QuickDeposit deliberately does not have its own commands to override that per player. Instead, individual overrides are done entirely through permissions, so they plug directly into whatever permission plugin you already use (LuckPerms, PermissionsEx, etc.) and can be assigned to groups, tracks, or individual players exactly like any other permission.

For each of the seven supported container types there are two permissions:

Container	Enable permission	Disable permission
Chest	quickdeposit.container.chest.enable	quickdeposit.container.chest.disable
Trapped Chest	quickdeposit.container.trapped-chest.enable	quickdeposit.container.trapped-chest.disable
Barrel	quickdeposit.container.barrel.enable	quickdeposit.container.barrel.disable
Shulker Box	quickdeposit.container.shulker-box.enable	quickdeposit.container.shulker-box.disable
Hopper	quickdeposit.container.hopper.enable	quickdeposit.container.hopper.disable
Dispenser	quickdeposit.container.dispenser.enable	quickdeposit.container.dispenser.disable
Dropper	quickdeposit.container.dropper.enable	quickdeposit.container.dropper.disable

All fourteen default to false (not granted to anyone) - nobody has an override until you explicitly give them one.

Priority rules

For a given player and container type, QuickDeposit decides what to use in this order:

1. Disable permission - if the player has the .disable node, that container is off for them, full stop.
2. Enable permission - otherwise, if they have the .enable node, it's on for them.
3. Global config value - otherwise, whatever config.yml (or /qd container global) currently says.

The disable permission always wins if a player somehow has both. This means you can, for example:

• Turn Shulker Boxes off server-wide, but grant quickdeposit.container.shulker-box.enable to your VIP group so only they can use them as deposit targets.
• Leave Barrels on server-wide, but grant quickdeposit.container.barrel.disable to a specific player if you have a reason to exclude just them.

Use /qd container list <player> at any time to see exactly what's in effect for a specific player, and whether each value came from [GLOBAL] config or a [PERMISSION] override - very useful when debugging a complex LuckPerms group setup. See Commands for details, and Integrations for how this looks for players who are currently offline.