Configuration

Configuration

All global settings live in plugins/QuickDeposit/config.yml. After editing it by hand, run /qd reload (or restart the server) to apply your changes.

Three things deliberately do not live in this file:

• Individual player search radii - set via /qd radius player <player> <radius>, stored in playerdata.yml by UUID. See Commands.
• Individual player container overrides - handled entirely through permissions. See Permissions.
• Whether a command is enabled at all - that's in its own commands.yml, covered at the bottom of this page.

Below is the full file, section by section.

deposit.radius

deposit:
  radius:
    default: 8
    minimum: 1
    maximum: 32

This controls how far (in blocks, in every direction including up/down) /deposit looks for containers.

• default is the radius used for any player who doesn't have their own individual radius set. Raise it if your storage rooms tend to be large; lower it if you want players to have to stand closer to their chests.
• minimum and maximum are hard limits. They are not suggestions - neither /qd radius global <n> nor /qd radius player <player> <n> will accept a value outside this range; the command is simply rejected with an error instead. This is what stops an admin (or a careless /qd radius global 9999) from accidentally making the search radius huge and slowing down /deposit for the whole server.

deposit.cooldown-seconds

deposit:
  cooldown-seconds: 2

How many seconds a player must wait between two uses of /deposit. This exists purely to stop players from spamming the command; it has no effect on how much a single /deposit moves. Players with quickdeposit.bypass.cooldown ignore this entirely. Set to 0 to disable the cooldown for everyone.

inventory

inventory:
  protect-hotbar: true
  protect-offhand: true

These only affect plain /deposit - /deposit all always ignores both settings and includes the hotbar and off-hand regardless. Worn armor is never touched by either command; there is no setting for that because it should never happen.

• protect-hotbar: when true, the 9 hotbar slots are skipped, so a pickaxe, food, or other actively-used item in the hotbar won't be swept into storage.
• protect-offhand: when true, the off-hand slot (shield, torch, etc.) is skipped the same way.

Turn either off if you'd rather have /deposit always be as thorough as /deposit all for those slots specifically.

containers

containers:
  chest: true
  trapped-chest: true
  barrel: true
  shulker-box: false
  hopper: false
  dispenser: false
  dropper: false

Which container types QuickDeposit is allowed to use, server-wide, by default. Ender Chests are never supported at all and don't have an entry here (they hold per-player contents, not a fixed inventory tied to a location, so "already contains a matching item" doesn't make sense for them).

• Chest / Trapped Chest / Barrel default to true - these are the normal, safe storage blocks most servers want covered from day one.
• Shulker Box defaults to false. Shulker boxes are portable and can be picked back up as an item, which some server owners don't want /deposit touching automatically; turn it on if that's not a concern for you.
• Hopper / Dispenser / Dropper default to false because they're commonly wired into redstone contraptions (item sorters, dispensers rigged to a lever, etc.). Having QuickDeposit silently add items to one of these could interfere with what a player built. Turn them on only if you're comfortable with that trade-off.

Every value here can be flipped without a restart via /qd container global <type> <on|off>, and overridden for individual players via permissions - see Permissions for the full priority system.

matching

matching:
  mode: EXACT

Controls how strictly QuickDeposit decides that an item in a player's inventory is "the same" as an item already sitting in a candidate container.

• EXACT (default): the material and all relevant item data must match - custom name, lore, enchantments, durability/damage, potion effects, CustomModelData, and similar. Two diamond swords with different enchantments are treated as different items and will never be mixed into the same stack. This is the safer default: it avoids ever merging items a player would consider meaningfully different.
• TYPE: only the material has to match; everything else is ignored. Any diamond sword matches any other diamond sword, enchanted or not. Use this if you'd rather have looser, more aggressive sorting and don't care about mixing enchanted/unenchanted or named/unnamed items together in bulk storage.

worlds

worlds:
  mode: BLACKLIST
  list: []

Restricts which worlds /deposit (and /deposit all) can be used in at all. This is a full on/off switch for the command in a given world - it doesn't filter individual containers, it blocks the command entirely there, with a message explaining why.

• mode: BLACKLIST (the default): /deposit works in every world except the ones in list. With an empty list (the default), every world is allowed - this section does nothing until you actually add a world.
• mode: WHITELIST: /deposit works only in the worlds in list, and nowhere else.
• list: a plain list of world names, e.g. [world_nether, world_the_end]. Matching is case-insensitive.

Switching mode does not clear list - the same world names simply get reinterpreted the other way around, which makes it easy to try one mode and flip to the other without retyping every world name.

Manage this live, without touching the file, via /qd worlds:

• /qd worlds - show the current mode and list.
• /qd worlds mode <blacklist|whitelist> - switch modes.
• /qd worlds add <world> / /qd worlds remove <world> - edit the list.

A common use case is blacklisting world_the_end and/or world_nether if you don't want players setting up deposit-ready storage in those dimensions, while leaving the overworld unrestricted.

feedback

feedback:
  actionbar: true
  chat: false
  sound: true

Controls how a player is told what happened after running /deposit.

• actionbar: shows a short-lived message above the hotbar, e.g. confirming how many items moved into how many containers, or that nothing matched.
• chat: sends the same result as a normal chat message as well (or instead, if you turn actionbar off).
• sound: plays a short sound alongside the result - a pleasant pickup-style chime when items moved, a quiet neutral click when nothing did.

You can enable any combination of these, including all three at once, or turn all of them off if you'd rather /deposit be completely silent.

integrations

integrations:
  worldguard:
    enabled: true
  griefprevention:
    enabled: true

Controls whether QuickDeposit checks WorldGuard region protection and/or GriefPrevention claim trust before using a container. See Integrations for exactly what each check does. Both default to true, but only actually do anything if the corresponding plugin is installed - if it isn't, QuickDeposit logs that on startup and simply skips the check, with no error.

There's no equivalent setting for LuckPerms or PlaceholderAPI - both of those are used automatically whenever they're installed, with no way (or reason) to turn them off. See Integrations for details.

commands.yml

A separate file, plugins/QuickDeposit/commands.yml, controls whether each top-level command exists at all:

commands:
  deposit: true
  quickdeposit: true

Setting either to false disables that command completely and immediately upon reload - it's hidden from tab-completion for every player and refuses to run for anyone (players and operators alike) with a short "this command is currently disabled" message. Unlike everything else in this wiki, there is no permission that bypasses this - it's a full off switch, not an access control.

Reload this file the same way as config.yml, with /qd reload.

One thing to plan around: if you set quickdeposit: false, /qd reload stops working too, since it's part of the same command. To turn quickdeposit back on, edit commands.yml directly and reload or restart the server - you can't do it from in-game at that point.