v1.5.0: 1.5.0 | Bag item slot memory, proper returns, and a full dupe pass
16 September 2026
The bag item now opens and fills with a click, keeps its own slot, and puts you back wherever you opened it from.
đą Opening and Filling the Bag With a Click
- Right-click the bag item on any inventory screen and the screen closes and the bag opens. Your own inventory, a chest, a furnace, anywhere your inventory is showing. Left-click still picks it up in movable mode
- Drop a stack onto the bag item to send it in. Left-click sends the whole stack, right-click sends one, exactly like placing into a normal slot. A full bag leaves the stack on your cursor with the usual full-bag line, and an open bag GUI updates its quantity on the spot
âŠī¸ Closing Puts You Back Where You Were
Right-click the bag item inside a chest, close the bag, and you are back in that chest. The same goes for double chests, barrels, shulker boxes, hoppers, furnaces, ender chests, chest minecarts and chest boats, and it survives a trip through the Settings menu. Opening the bag from your own inventory now simply closes on Esc, with no four-row copy of your inventory in the way.
Only real storage comes back. Other plugins' menus, crafting tables, anvils and the like close with the bag, because reopening a menu that has already closed is a well-known way to duplicate items.
đ The Bag Remembers Its Slot
Move the bag anywhere in your hotbar or inventory and that slot is saved. Joining, dying,
/clear, or trying to drop it all bring it back to the same place, and dropping is now blocked at the click itself rather than bouncing the bag to the configured slot.If something else is sitting in that slot when the bag returns, nothing is pushed out or dropped. Your item stays where it is, the bag takes a free slot for the moment, and it moves itself back as soon as its own slot is empty, checked each time you close your inventory. A completely full inventory waits the same way.
đ Dupe Pass
- The bag cannot go inside itself. Shift-clicking it into an open bag answers with a message, and any bag already stored inside another one is removed when its owner joins, with a single console line
- Reopened containers are looked up live, never restored from an old copy, so a chest broken while your bag was open does not come back
- Two more holes closed: a number key could swap the bag item into a chest, and
/clearwhile carrying the bag on the cursor handed out a second one
đ¨ Making the Item Your Own
The bag item no longer has to be a head. Use
bag-item.material for any vanilla item, bag-item.custom-model-data for your own pack, or bag-item.itemsadder for an ItemsAdder id in namespace:id form. ItemsAdder is optional, and if it is missing or the id is unknown the item falls back to the material and logs one line. Name and lore sit on top of whichever you pick, and leaving the name empty keeps the ItemsAdder name.đ Players Can Opt Out
/bag item off removes the item and remembers the choice, so joins, respawns and /clear stop handing it back. /bag item on returns it, but only into free space: the configured slot in locked mode, any free slot in movable mode, and a clear message if there is no room. /bag item on its own flips it.Each behaviour has its own switch under
bag-item, open-on-click, deposit-on-click, return-to-inventory and player-toggle, all on by default.đĻ Install
Replace the old jar in
plugins/ with InfiniteBags-1.5.0.jar and restart. The new bag-item.remember-slot key is written into your config.yml on boot and the database adds its own new column, so there is nothing to paste in by hand.The bag item ships off. Everything in this update sits under
bag-item.enabled: true.đ Version Breakdown
| Version | Focus |
1.5.0 | The bag returns you to the container you opened it from, keeps its own slot across joins and deaths, cannot be placed inside itself, and closes several duplication routes. |
1.4.0 | Click to open and click to deposit on the bag item, a player opt-out through /bag item, and a custom material, model data or ItemsAdder id for the item. |
Read the documentation | Join the Discord
Enjoying the plugin? A â review goes a long way!
v1.3.0: 1.3.0 | Developer API can now count and remove items
17 August 2026
Two new API methods, so another plugin can read what a bag holds and take items back out of it.
đ Reading and Removing
Until now the developer API could only put items into a bag. These two methods let another plugin on your server take them back out, which is what makes a bag usable as a live source of blocks or materials rather than just storage.
long count(UUID player, ItemStack item)
int remove(UUID player, ItemStack item)
countreturns how many of that item type the bag holds. The amount on the item you pass in is ignored. It returns along, because a well-stocked bag can hold more of one type than anintcan expressremovetakes items of that type back out, with the amount on the item you pass in being the quantity to take. It returns how many were actually removed
âī¸ Removal Is Partial, On Purpose
Unlike
add, which is all or nothing, remove takes what is there. Ask for 5 against a bag holding 3 and you get 3 taken and 3 returned, so the caller can cover the shortfall itself. The return value is always between 0 and the amount you asked for, never more.A slot drained to zero is deleted rather than left sitting empty, so it frees up for a different item type straight away.
đ Worth Knowing
- Same grouping as the rest of the API (material plus full NBT hash), so
count(...) > 0is exactly equivalent tocontains(...). A renamed or enchanted block is a different type and is never consumed to satisfy a request for the plain one - Both work offline and are locked per player, like the rest of the API. They are async-safe, touching only the database and in-memory data
- Neither runs a permission check internally. Call
isEnabled(uuid)yourself if you want that gate - Both see items on pages or slots the player's current permissions no longer reach, the ones
/bag recoverexposes, so everythingcountreports is somethingremovecan actually hand over - Null or air items, and null UUIDs, return
0. No exceptions - Calling the API by reflection is supported and now documented
đĻ Install
Stop the server, replace the old jar in
plugins/ with InfiniteBags-1.3.0.jar, and start it again. No existing method changed behaviour and the storage is untouched, so your bags carry over exactly as they are and anything already built against the API keeps working unchanged.Join the Discord
Enjoying the plugin? A â review goes a long way!
v1.2.3: 1.2.3 | Bag snapshot API + localized item names
03 July 2026
Localized bag item names for every player, plus new snapshot methods for the developer API.
đ Client-Localized Item Names
Item names in the bag and recovery menus now show in each player's own game language. An un-renamed item renders its vanilla name localized to the viewer, instead of a fixed English string. Items you've given a custom name keep that name. (The GUI search filter still matches the English material name, by design.)
đ§Š Developer API: Bag Snapshots
Two new read-only methods let companion plugins (like AT-MailBox) snapshot a bag once and test items against it later, without re-reading the live bag each time.
String typeKey(ItemStack item)the bag's grouping key for an item (material plus full NBT, amount ignored), ornullfor a null/air item. Same "same type" rule thatcontainsuses.Set<String> contentKeys(UUID player)a plain-value snapshot of the grouping keys of every type currently in the player's bag. Safe to keep, persist, and compare later.
Checking whether
typeKey(item) is in a saved contentKeys set answers "was this type in the bag at snapshot time?"- Both work offline (UUID-keyed database read) and are per-UUID locked, like the rest of the API. Async-safe, no world or entity calls.
- No write path or existing method behavior changed, so existing integrations keep working unchanged.
Full details on the Developer API page, including the methods table and a "Snapshotting a bag" section.
đĻ Install
Replace the jar in
plugins/ and restart. No config changes needed.đ Version Breakdown
| Version | Focus |
1.2.3 | New read-only API methods (typeKey, contentKeys) so companion plugins can snapshot a bag and compare later. |
1.2.2 | Bag and recovery menu item names now render in each viewer's own game language. |
Read the Developer API guide | Join the Discord
Enjoying the plugin? A â review goes a long way!
v1.2.1: 1.2.1 | Bag-drop dupe fix
25 June 2026
Patch release, fixes a storage dupe when an auto-collector plugin is installed alongside InfiniteBags.
đ§ Fixed
Dropping an item out of the bag at a full inventory spawns a world item with no thrower, which looked identical to a real overflow drop. An external auto-collector plugin (like a mailbox) could vacuum that item back into its own storage, duping it out of the bag.
InfiniteBags now stamps every bag-withdrawal drop with a persistent marker (
infinitebags:bag_drop) the instant it spawns, so cooperating plugins can tell it apart and leave it alone. The marker is set before the item enters the world, so spawn-time listeners see it.đ§Š Compatibility
Spigot, Paper, and Purpur on Minecraft 1.21.x. A drop-in upgrade with no config changes, and the v1.2.0 developer API is unchanged.
đĻ Install
Just replace your old jar with the new one and restart. No config changes needed.
Read the documentation | Join the Discord
Enjoying the plugin? A â review goes a long way!
v1.2.0: 1.2.0 | Developer API
25 June 2026
An optional developer API so other plugins can read and write a player's bag.
⨠What's New
This release adds an optional developer API so other plugins can read and write a player's bag at runtime. No hard dependency and no extra jar to install, it's soft-depend friendly and ships inside the normal plugin jar.
đĨ For Server Owners
- Nothing to configure. A drop-in upgrade from 1.1.x, with no config or language changes.
- Better integrations. Other plugins you install (mail systems, reward systems, custom shops) can now deposit items straight into a player's bag, even while they're offline.
đ§Š For Developers
A new
InfiniteBagAPI (in cc.arrowtan.infiniteBags.api) with four methods:isEnabled(UUID)can the player use their bagaccepts(ItemStack)would the bag store this item typecontains(UUID, ItemStack)does the bag already hold this exact typeadd(UUID, ItemStack)store an item, returns the amount that did not fit
Also:
- Static accessor
InfiniteBag.getApi()(null-checked, soft-depend safe) - Works offline (UUID-keyed database access) and is async-safe (per-UUID locked, touches only database and bag data)
- Strict item grouping: matches full material plus NBT (name, enchants, damage, custom model data), not just material
đĻ Install
Replace the jar in
plugins/ and restart. No config or language changes needed.Read the Developer API guide | Join the Discord
Enjoying the plugin? A â review goes a long way!
InfiniteBags | Backpack with Shop
zArrowTan
Unlimited per-item storage with a built-in shop hook to sell straight from your bag.
$5.39
Digital product, delivered instantly, no refunds · Terms
No versions available
Share and earn
How referrals work
- Your link is remembered for 30 days.
- 10% of each sale, paid to you as points.
- Yours to spend 30 days later.
- Ask your buyer to turn a VPN off, or the sale will not count.
Earn on every sale you send here
10%
162 pts / sale