FAQ

FAQ & Troubleshooting

"I ran /deposit and nothing happened."

Check, in order:

1. Is there actually a matching item in a nearby container already? QuickDeposit never uses a completely empty container as a target. Put at least one of the item in the chest first.
2. Is that container type enabled? Hopper, Dispenser and Dropper are disabled by default - see Configuration. Run /qd container list to check the current global settings, or /qd container list <yourself> to see what's actually in effect for you specifically (permissions can override the global value).
3. Are you within the search radius? Run /qd info to see your current effective radius, and move closer if needed, or ask an admin to raise it with /qd radius global / /qd radius player.
4. Is matching.mode set to EXACT? If so, small differences (a custom name, a different enchantment, different durability) will stop two stacks from being considered the same item. Try /deposit with a completely vanilla, unmodified item to rule this out, or ask an admin to consider switching to TYPE mode.
5. Are you on cooldown? If nothing visibly happens and you don't even see a "please wait" message, double check feedback.actionbar/feedback.chat aren't both turned off in config.yml - the deposit might be running (or being blocked by cooldown) with feedback simply not visible.
6. Is this world blacklisted, or - in whitelist mode - not on the whitelist? Run /qd worlds to check. See Configuration.

"Why does /deposit say it's not available in this world?"

An admin has restricted which worlds /deposit works in - see the worlds section in Configuration. Run /qd worlds (requires quickdeposit.admin.worlds) to see the current mode and list, or ask an admin to adjust it with /qd worlds mode/add/remove.

"Why doesn't QuickDeposit support Ender Chests?"

Ender Chests aren't tied to a single, fixed inventory at a location - every player has their own contents in every Ender Chest they open. QuickDeposit's whole approach relies on checking a specific container's current contents to decide whether it's a valid target, which doesn't translate to Ender Chests. This is by design and won't change.

"Can I make QuickDeposit use Hoppers/Dispensers/Droppers?"

Yes - they're just turned off by default because they're commonly used in redstone contraptions (item sorters, dispenser traps, etc.) and QuickDeposit adding items to one automatically could interfere with what a player built. If that's not a concern on your server, enable them with /qd container global hopper on (or dispenser/dropper), or set them to true in config.yml. See Configuration.

"A player says a container should count but it doesn't."

Double chests are counted as a single container (correctly matching vanilla behavior), and only currently loaded chunks are searched - a container in an unloaded chunk at the edge of a large radius won't be found. Also confirm the container type itself is enabled for that specific player with /qd container list <player> - an individual permission override might be disabling it just for them even though it's on globally.

"Does this work with WorldGuard/GriefPrevention/LuckPerms/PlaceholderAPI?"

Yes, all four are supported as fully optional integrations - see Integrations and Placeholders. None of them need to be installed for QuickDeposit's core functionality to work.

"I installed WorldGuard/GriefPrevention/LuckPerms after QuickDeposit was already running - do I need to restart?"

No - run /qd reload. It re-checks which of those plugins are currently installed in addition to reloading config.yml and playerdata.yml.

"Can a player empty their own inventory into random empty chests?"

No. QuickDeposit will never place an item into a container that doesn't already hold at least one matching item. This is a deliberate, non-configurable design choice - it's the whole reason the plugin can be handed out to every player by default without any risk of it becoming an auto-storage/dumping tool.

"Can I lose items through a /deposit?"

No. Items that don't fit anywhere (container full, no matching container found, etc.) simply stay in the player's inventory exactly as they were. Nothing is ever deleted.

"Where is per-player data stored, and what happens if a player changes their name?"

Individual search radii are stored in playerdata.yml, keyed by UUID rather than name, so renaming a Minecraft account has no effect on it.