Sample display

AdiBags displays the content of your bags in one view, distributed into several sections using smart filters.

It is heavily inspired by Nargiddley’s Baggins.

Configuration is available through Blizzard addon panel, /adibags chat command or right-clicking on the LDB plugin.

Important note about localized filters: some filters rely on translations from LibBabble-Inventory-3.0 so if some of them behave strangely in your locale, please take a look at the library translation status.

About patch 6.0.2

Blizzard has introduced a lot of new inventory features with the patch 6.0.2. I (Adirelle, AdiBags’ author) have absolutely no control over the way these built-in features work. It is all or nothing: either AdiBags uses a feature as is, either I have to code it myself. I had some of these features built into AdiBags in the past, but this was clumsy, using the API in a way that it was not meant to, and ultimately buggy for some users. So I decided to remove my code in favor of the built-in ones, even if it meant a minor degration of the original feature. If Blizzard improves some of these features in the future, AdiBags will automatically benefit from these improvements.

So, in short:

  • AdiBags now uses the built-in “new itemAPI, though it only detects looted/crafted/reward items. I added another module to highlight you what moves in bags to compensate for the loss of full item detection.
  • AdiBags now uses the built-in “sort bags“ feature. It may cause a spike of lag but works very quickly and does the job right.
  • AdiBags fully supports the reagent bank, including the built-in “deposit all reagents” feature. I know it moves enchanters’ velum to the reagent tab, but hopefully Blizzard will fix this.


Important notice: since v1.6.12-beta-1, AdiBags embeds BugGrabber, an error catching addon. Please check the error is really about AdiBags before reporting them here. I suggest installing BugSack to catch the errors.

Please report any bug or error using the wowace bug tracker (your Curse account works there). The comments section below is not meant to report and track bugs. I won’t reply to bug reports in the comment section anymore.

Some words about submitting bug reports:

  • I do not care about “it doesn’t work, fix it!” messages. I need to know how it failed and a way to reproduce the bug so I can test it and make sure I fix it.
  • Bug reports are not in the “fire and forget” kind of things. I may have to ask you some details.
  • Please check all existing tickets and the “known issues” section below before submitting new ones. Duplicate reports will be rejected on sight.

Bug tracker
WoWace forum thread


Most of these features may be configured. Check out the configuration panel ! (using the /adibags chat command or clicking on the bag icon, you have any LDB display)

  • Smart filters are used to distribute items into several sections, including:
    • Item sets of the Blizzard’s gear manager (one section per set),
    • Junk items (whitelist and blacklist available),
    • Quest items,
    • Equipment (items your character can wear),
    • Sections based on item category: trade goods, consumables, recipes, ...
    • Manual filtering (drag and drop items on section header, or add new section from the configuration panel),
    • Free space.
  • Smart item sorting inside each section.
  • Smart section layout; change the setting “Automatic layout update” to control the frequency of updates.
  • Track new items; use the [N] button resets the “new” flag.
  • Display slot type.
  • Bag sorting: left-click on the [S] button; right-click toggles auto-sorting, which sorts the bag on close.
  • Hide some sections, using the [V] button.
  • Name-based search.
  • Equipped bags (click on the bag icon in the top left corner),
  • Display character money in the backpack.
  • Display character tokens in the backpack.
  • LDB data source, displaying free space.
  • Two bag placement modes (choose one in the configuration panel):
    • Anchored: the bags expand from an anchor towards the center of the screen. The anchor can be unlocked and moved.
    • Manual: move the bags by dragging their title.

Separate modules

I have written two separate modules for AdiBags:

Tips & tricks

  • you can create your own sections using the “manual filter” in filter configuration. You can then drag and drop items on section titles to reassign them ; this works for any section.
  • if you want to highlight new items without putting them into a specific section, edit the “new items” filter priority to put it at the end of the filter list.

Known issues

  • New items detection does not work like it did before 1.8: Ihis is normal. I switched to the NewItems API that Blizzard has added in patch 6.0. This API does not work for bank nor items coming from the bank or the mailbox, but it does not having the timing issue my code had.
  • Opening the bank or closing my bag cause lag spike: this is an know issue with Blizzard bag sorting. For now, it is called every time you close your bag with auto-sorting enabled. I am working on a solution to sort bags only if their content actually changed.
  • Protected action/addon blocked error: they sometimes happen with AdiBags. Even though my effort, I can not reproduce these. Blizzard taint reports are very buggy, often blaming the wrong addon. As such they are pretty much useless.
  • Please note that prospecting, disenchanting or milling can create new items (e.g. that were not in your inventory yet). This can cause the whole bag to be updated. In this case, the items that were under your mouse cursor may move around. There is no easy solution for this so be cautious.

Things that likely will not be implemented

Anything else than the existing “all-in-one” views

AdiBags has been built around, and optimized for, the idea of the “all-in-one” view. Doing anything would require to redesign big parts of the addons, especially the layout code that is quite complex at the first place.

Anything that requires to scan item tooltips

Tooltip scanning is quite CPU-consuming and above all requires asynchronous programming, since item tooltips would not always be available at the time AdiBags should use them. This would raise the complexity of bag filtering be an order of magnitude and turn AdiBags into a CPU hog.

Some examples what requires to scan the item tooltips:

  • detecting the kind and state of binding: unbound, soulbound, bind-on-pickup, bind-on-equip…
  • detecting already known spells/pets/recipes or faction/race/level/skill/class restrictions ; basically any “red text” in the tooltip.

Guild bank

AdiBags presents you a nice view of your bags but actually they are in a complete mess. With AdiBags, there is no need and no way to tidy up the items in the actual bags. Guilds usually try to keep their bank tidy. What would happen if some people in a guild used AdiBags for the guild bank ? Well, they would mess up the guild bank content and people NOT using AdiBags would have to deal with that mess. I can hear the screams from there. So that is why I will not implement guild bank.

Alt bags and bank

AdiBags is not an alt bags/bank viewer. If you want to keep track of what your alt owns, I suggest using an addon like BagSync.

Full bag skinning

Basic skinning is available using LibSharedMedia-1.0: you can choose the bag font, background and border, as well as the color.

Comprehensive in-game filter/section editor

According to my experience with Baggins, comprehensive editor is awful to write as an author and awful to use as an user. Hence I focus on creating filters that have a smart built-in behavior and only a few options. I try to avoid the 20% of features that would require 80% of development effort.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of PoMR PoMR May 16, 2010 at 13:16 UTC - 0 likes

    Two things I'd like to mention(other than how much I love this addon):

    1) I have an addon (Zzmisc Helper) that among other things autorepairs and autosells grey items that stopped working since I've installed AdiBags. They work fine when AdiBags is not enabled, or if I reinstall Bagnon. 2) Is there some way to view one's bank when not at a banker?

    Neither of these are horrible things, but they are nice features and I wonder if there's a possibility of a fix in the first case, and an enhancement in the second assuming that functionality isn't there already.

    Thanks much for a wonderful bag addon!

  • Avatar of Allara Allara May 15, 2010 at 20:31 UTC - 0 likes

    Light: Just install the Bagnon modules too. They work with AdiBags (tested just now).

  • Avatar of light light May 14, 2010 at 15:10 UTC - 0 likes

    Nice addon with some features i missed in bagnon - but somehow some features i like from bagnon i'm missing here. Sad that you already stated that you wont add such things like "bagnon forever" or "bagnon tolltips" ...

  • Avatar of kergoth kergoth May 12, 2010 at 18:17 UTC - 0 likes

    Nicely done on this, by the way. Extremely nice, yet lightweight. Don't miss the configurability, personally, it acts great out of the box.

  • Avatar of kergoth kergoth May 12, 2010 at 18:15 UTC - 0 likes

    Get an error about no GetInventorySlot method upon going to the bank. Appears that you call the UpdateLocked from the bank frames on yours, but you don't provide all the methods they expect. Haven't looked into it closely.

  • Avatar of Adirelle Adirelle May 12, 2010 at 08:33 UTC - 0 likes

    @leks0d: this is related to your ticket #2. Does it happen with only AdiBags enabled ? I don't think of any way this would happen unless some other addon messes with Blizzard's API. I'll add some checks in next version.

    @Cal: no. There are dedicated addons for this task.

    Edit: BTW, I created a thread on the forum :

    Last edited May 12, 2010 by Adirelle
  • Avatar of leks0d leks0d May 12, 2010 at 02:50 UTC - 0 likes

    Error after auto restock reagents(same with auro sell grey items and auto stuck in auction house): Interface\AddOns\AdiBags\modules\NewItemTracking.lua:126: attempt to index local 'link' (a function value) Count: 1

    Call Stack: (tail call): ? Interface\AddOns\AdiBags\modules\NewItemTracking.lua:126: in function <Interface\AddOns\AdiBags\modules\NewItemTracking.lua:125> Interface\AddOns\AdiBags\modules\NewItemTracking.lua:153: in function `?' ...ags\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...ags\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146> [string "safecall Dispatcher[5]"]:4: in function <[string "safecall Dispatcher[5]"]:4> [C]: ? [string "safecall Dispatcher[5]"]:13: in function `?' ...ags\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `SendMessage' Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:339: in function `UpdateButtons' Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:138: in function <Interface\AddOns\AdiBags\widgets\ContainerFrame.lua:132> (tail call): ? [C]: ? [string "safecall Dispatcher[2]"]:9: in function <[string "safecall Dispatcher[2]"]:5> (tail call): ? ...\AddOns\AdiBags\libs\AceBucket-3.0\AceBucket-3.0.lua:116: in function <...\AddOns\AdiBags\libs\AceBucket-3.0\AceBucket-3.0.lua:109> (tail call): ? [C]: ? [string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5> (tail call): ? ...ce\AddOns\AdiBags\libs\AceTimer-3.0\AceTimer-3.0.lua:166: in function <...ce\AddOns\AdiBags\libs\AceTimer-3.0\AceTimer-3.0.lua:138>

    Last edited May 12, 2010 by leks0d
  • Avatar of Cal Cal May 12, 2010 at 01:06 UTC - 0 likes

    Do you intend to track items across characters and display that information on the tooltips?

  • Avatar of Talyrius Talyrius May 11, 2010 at 23:04 UTC - 0 likes

    Nope, no error message. When I click the Configure button, the Interface options close and it shows me the ESC menu again.

  • Avatar of Adirelle Adirelle May 11, 2010 at 22:51 UTC - 0 likes

    Hrm, that's annoying because I have it working fine there. Any error message ?


Date created
May 07, 2010
Last update
Nov 18, 2014
Development stage
  • enUS
  • frFR
All Rights Reserved
Curse link
Recent files