View Bug Report
Specialized Item Type "furnishing_attunable_crafting_station" is not recognized
Bug #: 3306
File: Auto Category - Revised
Date: 12/11/20 06:30 PM
By: acapela
Status: Game Bug (Cant fix)
Bought some attunable crafting stations, and discovered that the default installation of "Auto Category - Revised" did not appear to recognize them. They did not appear in my inventory with the addon enabled, and did appear with the addon disabled.

Tried to add a "Crafting Station" category, with the rule
Code:
type("furnishing_attunable_crafting_station","furnishing_crafting_station")
The "check" function in the category creation dialog recognized "furnishing_crafting_station" as a valid type, but flagged "furnishing_attunable_crafting_station" as "unrecognized". I tested these two types separately, in isolation. While "furnishing_crafting_station" was acceptable as a type (the "check" passed as "good"), the category did not appear to recognize my unused attunable crafting stations in my character's inventory.

Is "SPECIALIZED_ITEMTYPE_FURNISHING_ATTUNABLE_CRAFTING_STATION" an ESO global of some kind? I have a lot of LUA experience in World of Warcraft, but I would have no idea how to find out about something like this in ESO (I don't know how to dump the default Zenimax LUA, nor where to go for documentation of globals, etc). Perhaps that particular global has been deprecated/no longer exists, or now has some sort of typo in it, and you need to reference something different?

I am a complete neophyte, so perhaps there is a different/better approach to achieving this that WILL work, but it appears the whole concept of the attunable crafting station is currently not accessible in "Auto Category - Revised".

FYI. Thanks.

RSS 2.0 Feed for Bug CommentsNotes Sort Options
By: Shadowfen - 12/26/20 04:54 PM
Yes, it is an ESO global, but that does not mean that ESO used it correctly. After all, SPECIALIZED_ITEMTYPE_LOCKPICK does not match against lockpicks either - it matches against SPECIALIZED_ITEMTYPE_TOOL instead and they have not fixed that for a couple of years now.

As a work-around, you might be able to work with itemname("attunable") assuming that the name includes that word.