Baggins
Inventory Management with virtual view divided into sections.
Now with baggins you can not only separate your bags into virtual view of your inventory but organize the items in your virtual view by item type! Bag options with endless possibilities. Add/remove/create categories, change skin of the view baggins does it all! Customize your bags to show items exactly how you like! No more looking for items and not being able to find them, look and know exactly where they should be!
For example one bag with profession items, one bag with gear, and so much more! You can even make your own categories!
You can use the minimap icon or /baggins to open the options window.
In reply to Runkel:
I know you said the other is more important but just wanted to give you an update, container type is now re-enabled for classic.( v3.4.0)
In reply to Doadin:
At first thank you for all the work you put into maintaining this Addon and please don't think i take all your effort for granted but i think excluding "LibPeriodicTable" in current and future releases is a bad decision imho, it's a big part of what makes using filters in Baggins so comfortable and easy to use.
For example if i wanted to make a "Herb" Category with "LibPeriodicTable" all i had to do was:
Type ->PeriodicTable->Tradeskill.Gather.Herbalism-> DONE
Without LibPeriodicTable
Type->Item ID->ID of every Single Herb
In reply to Runkel:
Noted, and will work on adding it back in and hopefully have release sometime within the next day or two, should be a simple reverse commit.
Todays update Broke Baggins for me.
The latest Update (Classic) broke Editing Categories for me.
Before the Update:
After the Update
In reply to Runkel:
still happening in 3.1.7?
In reply to Doadin:
Unfortunately yes
In reply to Runkel:
I know what the issue is the problem is one thing fixes something on retail other fixes something else on classic.
In reply to Runkel:
should be ok in 3.1.8 . for classic.
In reply to Doadin:
It's fixed! Thanks a lot! :)
Working great so far!
Just one question. Is there a way to show the "item ID, type/group, PeriodicTable and so on" of an item? I'm pretty sure there was a way to show those information in the items tooltip but i can't remember how to do this.
In reply to Runkel:
New here but i think what your looking for was in a Baggins plugin called "Baggins_SyLevel" which requires !SyLevel . At least that has some of what your looking for, i think. Unfortunately it seems those have not been update in a long time.
Experimental classic version is https://github.com/wolfcon/Baggins/releases/download/release-2.2.1/Baggins-release-2.2.1.zip
It is just an experimental test for authors to merge in.
In reply to wolfcon:
Thank you for your work, it's really exciting to see someone is working on a fix for Baggins! :)
In reply to wolfcon:
I have gotten permission to take over. I will have more updates soon.
In reply to Doadin:
https://github.com/wolfcon/Baggins
This is my github codes exported from svn.
In reply to wolfcon:
I have already began merging those changes the only thing I didn't bring in is the commits moving stuff to new files. So if theres any classic changes in those clusters of code then I missed them. I wanted to go a different route in making changes for classic as I dont want to remove code for retail just make checks for classic or not so that it will work for both versions. Seeing that the commit is pretty big for moving those files I cannot easily compare at least not in the 10min i've had since starting this. :P Im working on it though and hopfully curse mods will approve my version soon.
In reply to wolfcon:
I have my repo up here https://github.com/doadin/Baggins2 if you wouldnt mind looking that would be much appreciated.
In reply to Doadin:
That would be nice.
I've tried to make changes work for both version. But one more lib should be updated, which is also belong to mikeclueby4. So.......
Other changes are OK if don't remove them.
Moving code is just a refactor for maintaining code structure. Thats fine if don't do.
In reply to wolfcon:
Which lib is that?