I've added an 'Ignored Items' option to the add-on. It allows you to ignore items by quality, item type, level, name, etc. The implementation allows you to use LUA patterns (which also means simple string matching is supported.) This may not be perfect for your particular case, but it may work.

I've modified the 'Raw Materials' category to include raw materials from all tradeskills. Let me know if this is the behavior you were looking for. In the next release I'm providing finer control over item types and restructuring how groups are presented/managed. Thus, if you need more control than the current version provides, stay tuned, it's on the way.

Yeah, not only for this addon, but typically for authors of other addons looking for ideas now and in the future as well. Suggestions are always welcome!

WILL-FIX:
I cleaned out my savedvars and this helped uncover a bug they were previously hiding.

Thanks for this report, I've resolved the issue and will have new packages uploaded later tonight (or tomorrow, at the latest, I need to do a lot of testing before I publish with some of the changes I'm making.)

Thanks!

yeah found this a bit ago, fix is about to get uploaded.

i rushed the deployment this morning, i shouldn't have. i know better.

PLANNED-
I'll look into it. I scanned a few addons this morning and nothing obvious jumped out, and the ItemSaver docs don't explicitly note any libStub-based mechanism for hooking into ItemSaver. What little I saw just now looked hack-ish. Worst case I reach out to ItemSaver author(s) and legitimize integration (if it hasn't already been done.) Best case is there are already integration hooks exposed and I just need to find them.

Yeah, I hear ya. It's hard to trust an update when you don't know what was changed (or, rather, what may have broken.)

I used to publish the changelog on ESOUI, but it actually takes me a fair amount of time to upload packages let alone edit the text. It drives me a little bonkers. Sometimes I wish ESOUI would optionally use the included README.md instead of requiring me to hand edit BBCODE, in the same vein, I wish ESOUI would let me upload a ZIP and read the Addon name out of the one root-most XXX.txt file and make assumptions about which addon i'm attempting to update (verifying, of course, that it's the right one.) Unfortunately, ESOUI's primary user flow isn't uploads. It's downloads. I doubt the current flow will change.

That said.. I *do* maintain a user-friendly changelog for each Addon, I'm just not publishing it on ESOUI anymore (this saves me about 10-15 minutes overall when republishing, and spares me a bit of sanity.)

You can check the changelogs inside the download(s) or on Github where the source code is hosted. The changelogs are at the end of each README.md (except for All-In-One, for this I include no Changelog, only installation notes.)

For example:

• README for X4D Bank
• README for X4D Loot
• README for X4D XP
• README for X4D Chat

I plan on rendering these inside the Addons (inside or next to the Settings UI for example) but it has been at the bottom of my list since the beginning.

Hope this helps!

I forgot to mention, there is also the commit log. I'm a diligent dev, and usually make very clean commits with concise descriptions, and 99% of the time I prefix with a tag so I know "where" in the code the change was made:

X4DESO Master Commit Log

While it's not as attractive as the README, this is more accurate and will let you know *everything* I changed (and occasionally I explain why.)