of course, there are no errors , only the DoItAll does not work , I turned off your beautiful addon latest version and DoItAll earned correctly , when using previous versions autocategory problems did not arise, worked together fine .

You're exceptional, you know that? Seriously, THANK YOU! The latest update is AMAZING, and will make categorising things so much more easier! Can't wait for the quality() API! Hopefully all goes smoothly as intended. Keep well!

So I ran into an issue that really sucked, and I wish I backed up my saved variables...

Using the new Import From Bag option somehow permanently links the current "bag" to the chosen bag. For example, if I selected the Guild Bank bag, and imported from Backpack, and then I delete any categories from the Guild Bank it ALSO deletes the categories from the Backpack.

Is this intended? I'd much prefer if it didn't link them, and simply copied them once, allowing you to delete categories as you please, without fear of it also removing the categories you deleted from the imported bag...

I would still like to see a "use same settings for ALL bags" option, for those of us who will use the same categories, everywhere. And then obviously those who want separate categories can still manually set them up per bag.

EDIT: Also, at least from my side, when having about ~30 or so different categories, I am noticing quite some lag when using Bank Manager Revived to auto-push items to a guild bank, and having Roomba automatically stack items thereafter. Can you confirm if this is true on your side, and if there is anything can be done, performance wise? Like, perhaps wait to display categories AFTER BMR/Roomba have completed? As I have a feeling with the items being added/removed while Roomba is working, the categories are constantly refreshing?

EDIT 2: I just have to mention how in-love I am with this add-on! It completely caters to the OCD of me!!! I honestly cannot wait for the quality() API to hit so I can easily categorise items to be kept or sold, etc. For example, not deconstruct items under blue quality, as it just isn't worth it, to me.

Here's what my Deconstruct category currently looks like:


And no doubt it'll grow as you add more handy API calls!

EDIT 3: Definitely need a way to solve the insane lag added by Roomba re-stacking items to banks... Perhaps a quick fix is to add a keybind to toggle all categories on/off?

EDIT 4: Shouldn't isbound() match Bind On Pick-Up items considering you can't trade them with anyone anyway? As right now I have to add an extra; to catch those.

You're seriously one of the best and active developers around! So happy about the quality API, wow! That'll come in super handy! I assume trash and white are just synonyms for each other, correct? The same as "magic" and "green"? Use either or?

I'll be sure to try the keybind option, forgot you just added it in the last update, hopefully that works! Perhaps another option would be to add a delay to when the categorising starts for a certain bag (Guild/Bank)? Or to not have auto-update happen as items are added to the bank (that is what BMR + Roomba do) and leave it so categories only update when either 1) user pushes a keybind or 2) user switches tabs? That would be super helpful.

Also, I just wanted to ask if this is normal behavior.

As, the way it is, read recipes still get categorised as "Unknown" as per my rule, but if I put the islearnable() in the front of that rule, then it works normally? I'd have thought it works either way?

Also, regarding the new function, you'd still have to manually "export settings" each time you add a rule. Is there no way to just have an option in the settings menu where we just use one setting for all bags?

This add-on is seriously on its way to becoming an amazing all-in-one tool for every scenario... The amount of time it shaves off of handling inventory items is INSANE! And with the API I can have smart rules to help filter what items I can sell to the guild store, such as rare recipes or set items of a certain quality and level... The possibilities are endless. Perhaps one thing we'd need is occasional backups, but that I can handle on my end for myself.

Do you think you can get an API up that can handle items currently needed for a Writ? That way we can just select "ALL" items in a bank, and the category will show only Writ items, as suggested before; if I need to make a Calcinium item, it'll show Calcinium Ingots, etc.

EDIT: I've noticed that sometimes the research category I have doesn't work as it should. Going by this image, do you see anything that should stop it from marking it correctly? My Researchable category is rather simple, compared to the rest... keepresearch() and cp() < 160. It is researchable, it isn't in my bank but in my inventory, it is under CP 160... What gives?

EDIT 2: I notice we can specify the exact quality type and match from there, but is there no way to say something like quality() < "blue" so it matches EVERYTHING under Blue, instead of having to match each quality up until Blue? Imagine if it were for Gold...

Also, minor request, but what are the chances there could be a message that says when we have toggled on/off the category rules by keybind? Helpful to know prior to entering the bank.

not in your plans, I'll have to turn off your addon when deconstruct all /

Thanks for your response, rockingdice, I truly appreciate it! The amount of progress that has been made is exceptional, and right now it is in a perfectly satisfactory state, covering many aspects such as item quality and cost! Can't wait to see what else you end up adding.

I am also having issues with deconstructing gear using Doitall in conjunction with Autocategory. I also use FCO. Using 'deconstruct all' the game will wig out with a in game message 'You can't deconstruct an item you are wearing.' followed by a spam message 'No usuable item found' which will continue until I esc out of the deconstruct interface. I have cleared out the saved variables of both and reinstalled with no luck. The issues started with AutoCategory v.110 and has persisted through v.113. V.109 works fine. If there is any other information I'll do my best to provide. Thanks for addressing this issue.