Probably just need to iterate over quests, steps and conditions and look for items. Not sure precisely what it would take, but if they're just normal quests then that makes the problem easier to solve (since the structure of quests are already known.)

ESO's Quest Structure isn't the prettiest, for examples of how hairy quest iteration can get check the Loot addon (which does change detection on the quest system to pretty-print when quest items are picked up.)

SOLVED-

I suppose in-game the canonical identifier is "ITEMTYPE_ALCHEMY_BASE" but these are in fact referred to as "Solvents" in-game.

That said, if you change the settings for "Alchemy->Bases" that should do what you want, if not I may need to know more, such as examples of items so I can look up their internal details.

In the meantime I'm going to update the dropdown titles to use localized names. Hopefully this will resolves confusion in any case where I've used an unexpected/non-standard name for a thing.

Thanks!

Hmm, you might try using all-lowercase in the ignore list, since you're matching item names.

so, instead of "Leerenstoff" you would use "leerenstoff".

i would auto-lower the patterns, but there are also upper-case tokens (special tokens are upper-case, item names are lower case, when matching.) For example, if you only wanted to ignore stolen Leerenstoffs, you would use a pattern like "STOLEN.*leerenstoff"

Other upper-case tokens include item quality (e.g. MAGIC, LEGENDARY), item type (examples include POTION, FOOD, DRINK, WEAPON, etc.)

These also support Lua patterns, so you can use wildcards like ".*", ".+" and ".-", or more advanced patterns if you're keen on Lua patterns at all. I believe there is a pattern tutorial on the web.

The reason this may have stopped working is item names are being normalized to lowercase for lookups now, and the ESO API is being used to denormalize them when displaying them to the user. It was always the intent that users would specify lower-case for matching, but I switched from using scrubbed text to the normalized item link data (to allow pattern-matching on ESO link options, which is a bit more advanced than matching just the name, you can pattern out levels, enchantments, etc)

I can explore auto-lower-casing patterns, but probably only safe when no special pattern characters are in use. As a workaround for now I would suggest just editing the caps to be lowercase. It should work then.

Sorry for any confusion on this one it wasn't actually meant to work the way it had been working before.

I've made changes in the current release which should work around this issue until I'm able to figure out the root cause and fix it proper. I'll try fishing tonight, see if I turn anything up.

EDIT: to be clear, the workaround for this is in X4D_Core v1.10, not the Bank addon itself, though both will need to be updated (since Bank relies on code in Core which I changed earlier this week.) If you try updating only the Bank Add-on this problem will persist.

PLANNED-

Yes. I agree it is becoming (was already) a wall of text. It's been on my list of things to do since last year. I need a tiny bit more than what LAM offers, and I've been putting off extending LAM since the beginning of these Addons (and good thing, too, since someone decided to rewrite LAM at some point, but it's still as limited as v1... actually, I'm now able to do *less* than what I was doing with LAM1.. but that's neither here nor there.)

There's the off scenario that I drop LAM and replace it, but that would likely cost me ~2-3 weeks of development time that would normally go elsewhere.

.... so,I keep putting the issue off and focusing on features and bugs. =\ It's not a question of "if" but "when" I'll get to it.

Interesting. I'll do some testing on fish tonight and get it resolved. Hopefully just missing an itemtype in the internal lookup used to populate the canonical field.

Thanks!