TESO UI Error (PC NA)

Shadowshire

The following UI Error dialog was shown on the HUD when I left-clicked the mouse with its cursor on a Banker's Bank > Deposit icon. As far as I can determine, the UI Error does not appear to have been explicitly caused by an add-on, although one is listed among the "Locals" in the first function call in the stack traceback.

bad argument #1 to 'pairs' (table/struct expected, got nil)
stack traceback:
[C]: in function 'pairs'
EsoUI/Ingame/Inventory/Inventory.lua:1540: in function 'ZO_InventoryManager:PlayItemAddedAlert'
|caaaaaa<Locals> self = [table:1]{itemsLockedDueToDeath = F, selectedTabType = 1}, slot = [table:2]{traitInformation = 0, functionalQuality = 2, stackLaunderPrice = 0, stackCount = 1, quality = 2, requiredChampionPoints = 0, isJunk = F, equipType = 0, sellInformation = 0, specializedItemType = 177, locked = F, launderPrice = 0, statValue = 0, sellPrice = 9, isPlayerLocked = F, name = "Blueprint: Solitude Serving Di...", statusSortOrder = 16, itemType = 29, iconFile = "/esoui/art/icons/crafting_plan...", age = 41725.51171875, actorCategory = 0, slotIndex = 16, brandNew = T, sellInformationSortOrder = 1, itemInstanceId = 3683303109, rawName = "Blueprint: Solitude Serving Di...", displayQuality = 2, isGemmable = F, isBoPTradeable = F, isFromCrownStore = F, traitInformationSortOrder = 1, bagId = 1, meetsUsageRequirement = T, requiredLevel = 1, stackSellPrice = 9, isPlaceableFurniture = F, condition = 100, stolen = F, uniqueId = 347607296.06886}, inventory = [table:3]{currentSortKey = "statusSortOrder", currentSortOrder = F, freeSlotsFullStringId = 4319, currentContext = "playerBankTextSearch", subFilter = 0, freeSlotType = 1, freeSlotsStringId = 4318, rowTemplate = "ZO_PlayerInventorySlot", listDataType = 1, slotType = 2}, isSlotAdded = F, currentFilter = 
user:/AddOns/NTakLootSteal/NTakLootSteal.lua:407 </Locals>|r

EsoUI/Ingame/Inventory/Inventory.lua:679: in function 'callback'
|caaaaaa<Locals> oldState = "hidden", newState = "showing", _ = 1, data = [table:2] </Locals>|r

EsoUI/Libraries/Utility/ZO_CallbackObject.lua:107: in function 'ZO_CallbackObjectMixin:FireCallbacks'
|caaaaaa<Locals> self = [table:4]{fireCallbackDepth = 1, duration = 200, allowShowHideTimeUpdates = F, animationTemplate = "FadeSceneAnimation", state = "showing"}, eventName = "StateChange", registry = [table:5]{}, callbackInfoIndex = 1, callbackInfo = [table:6]{3 = F}, callback = EsoUI/Ingame/Inventory/Inventory.lua:668, deleted = F </Locals>|r

EsoUI/Libraries/ZO_Scene/ZO_SceneFragment.lua:143: in function 'ZO_SceneFragment:SetState'
|caaaaaa<Locals> self = [table:4], newState = "showing", oldState = "hidden" </Locals>|r

EsoUI/Libraries/ZO_Scene/ZO_SceneFragment.lua:161: in function 'ZO_SceneFragment:ShouldBeShown'
|caaaaaa<Locals> self = [table:4] </Locals>|r

EsoUI/Libraries/ZO_Scene/ZO_SceneFragment.lua:232: in function 'ZO_SceneFragment:Refresh'
|caaaaaa<Locals> self = [table:4], oldState = "hidden" </Locals>|r

EsoUI/Libraries/ZO_Scene/ZO_Scene.lua:108: in function 'ZO_Scene:AddFragment'
|caaaaaa<Locals> self = [table:7]{fireCallbackDepth = 0, restoresHUDSceneToggleUIMode = F, disallowEvaluateTransitionCompleteCount = 0, wasShownInGamepadPreferredMode = F, state = "shown", wasRequestedToShowInGamepadPreferredMode = F, restoresHUDSceneToggleGameMenu = F, name = "bank"}, fragment = [table:4] </Locals>|r

EsoUI/Libraries/ZO_Scene/ZO_Scene.lua:137: in function 'ZO_Scene:AddTemporaryFragment'
|caaaaaa<Locals> self = [table:7], fragment = [table:4] </Locals>|r

EsoUI/Libraries/ZO_Scene/ZO_SceneManager_Base.lua:119: in function 'ZO_SceneManager_Base:AddFragment'
|caaaaaa<Locals> self = [table:8]{numTopLevelShown = 0, initialized = F, remoteSceneSequenceNumber = 245, hudUISceneName = "hudui", fireCallbackDepth = 0, exitUIModeOnChatFocusLost = F, hudUISceneHidesAutomatically = T, numRemoteTopLevelShown = 0, hudSceneName = "hud"}, fragment = [table:4], state = "shown" </Locals>|r

EsoUI/Libraries/ZO_Scene/ZO_SceneManager_Base.lua:148: in function 'ZO_SceneManager_Base:AddFragmentGroup'
|caaaaaa<Locals> self = [table:8], fragmentGroup = [table:9]{}, i = 1, fragment = [table:4] </Locals>|r

(tail call): ?
EsoUI/Libraries/ZO_MenuBar/ZO_SceneFragmentBar.lua:89: in function 'callback' EsoUI/Libraries/ZO_MenuBar/ZO_MenuBar.lua:286: in function 'MenuBarButton:Release'
|caaaaaa<Locals> self = [table:10]{m_highlightHidden = F, m_locked = T, m_state = 1}, upInside = T, skipAnimation = F, playerDriven = T, buttonData = [table:11]{categoryName = 7651, highlight = "EsoUI/Art/Bank/bank_tabIcon_de...", normal = "EsoUI/Art/Bank/bank_tabIcon_de...", pressed = "EsoUI/Art/Bank/bank_tabIcon_de...", descriptor = 7651} </Locals>|r

EsoUI/Libraries/ZO_MenuBar/ZO_MenuBar.lua:656: in function 'ZO_MenuBarButtonTemplate_OnMouseUp'
|caaaaaa<Locals> self = ud, button = 1, upInside = T </Locals>|r

ZO_MainMenuCategoryBarButton1_MouseUp:3: in function '(main chunk)'
|caaaaaa<Locals> self = ud, button = 1, upInside = T, ctrl = F, alt = F, shift = F, command = F </Locals>|

ZOS_Bill

Have you tried the steps below for completely removing ESO add-ons?

How do I get rid of my add-ons?

Shadowshire

ZOS_BillE wrote: »

Have you tried the steps below for completely removing ESO add-ons?

How do I get rid of my add-ons?

No, why would I do that?

Each of the two ESO UI Errors have occurred since the most recent update to the game client. Before that update, I do not recall ever seeing a UI Error reported for the game client per se. I know enough about Lua to recognize what the UI Error text means. Namely, there is at least one bug in the game client, without a doubt.

So why don't the ZOS maintenance programmers track it down and fix it? Oh, wait ...... there aren't any maintenance programmers are there? ZOS hires only developers, right?

As far as I can determine, there is no add-on which somehow causes the UI error that is shown on the HUD. If ZOS can demonstrate that there is one which does, then please do. But may I point-out, that perchance an add-on actually does interfere with the game client or incorrectly alters the game-state, then perhaps there is a bug in an Application Programming Interface feature which the add-on uses?

Please understand this clearly, I will stop using add-ons the day that ZOS creates for each and every feature a comparable UI and corrects any and all bugs and design flaws which are already in TESO UI, such as the native Guild Store, for example. ZOS evidently regards pretty much all of them as "cosmetic". Which means that they don't literally stop most players from playing the game, regardless of whether they make everyone wonder whether their investment of time, effort, and money in playing TESO will end with a major crash some day. I think it is more likely that the accumulation of malfunctions will eventually render the game so undesirable that people will begin to abandon it.

That said, because of their effects upon performance, I am very judicious about choosing whether to use any particular add-on at all. Many that I install are only enabled during certain activities, and others which are ordinarily enabled are disabled before I engage in other activities (especially those during which a lot of combat is expected).

Occasionally, an add-on causes a UI Error dialog to be displayed, so I copy the text of the message and post it on the ESOUI website page that pertains to downloading the offending add-on. Most add-on developers are definitely concerned about such errors, whether their add-on works without causing problems, and whether the add-on might have a design oversight or some implementation flaw. There are a few tender egos and arrogant technocrats in every group, of course. But ordinarily the attitudes and reactions of the add-on developers are cordial, and we focus on the facts.

Some add-ons that I use rectify bugs that occur in the native software, e.g., Elsweyr Mural Mender. Whether ZOS eventually remedies any of these might be mentioned in some Patch Notes, else apparently ZOS just accepts that the add-on makes a correction unnecessary.

Other add-ons that I use remedy oversights in the implementation of the game -- like the one which changed how familiars are summoned, then "activated" by pressing the same key -- which had been used to dismiss the familiar instead. So all players with sorcerers welcomed the add-on Pet Dismiss. It has been updated to include the Warden's bear, too. Granted, there probably is a work-around for the oversights, but who wants to use a work-around when an add-on is so much better in comparison?

There are plenty of other add-ons which add quality-of-life improvements to the game UI -- and to the player's experience -- that ZOS would be unlikely to ever invest the time and effort to add, let alone develop before releasing the software for use. In my experience, many ZOS QoL improvements have been released with bugs and flaws which may (or may not) be corrected .... eventually. More often, someone develops an add-on which provides a remedy instead.

Indeed, given the evident limits to time and effort to develop each Chapter and DLC , apparently the ZOS policy is to invest as little money as possible in the product. Funny, isn't it, how there have been very few design flaws and bugs in the Crown Store, in comparison to the actual game?

IMHO, ZOS should be fervently thanking their lucky stars that they have a game for which so many competent, knowledgeable, and talented programmers have been willing to voluntarily invest their personal time and effort for the benefit of the players. Please, stop treating them like orphaned stepchildren, and give them the support and respect that they deserve as partners in a cooperative endeavor.