Help with annoying LUA error?

Since the last update I get this error constantly, what is causing this and how can I fix it?

Message: …ard_SharedMapDataProviders/SharedMapPoiTemplates.lua:633: attempt to index field ‘poiInfo’ (a nil value)
Time: Thu May 15 08:32:00 2025
Count: 13
Stack:
[Interface/AddOns/Blizzard_SharedMapDataProviders/SharedMapPoiTemplates.lua]:633: in function ‘GetSuperTrackData’
[Interface/AddOns/Blizzard_SharedMapDataProviders/SharedMapPoiTemplates.lua]:617: in function ‘DoesSuperTrackDataMatch’
[Interface/AddOns/Blizzard_SharedMapDataProviders/SharedMapPoiTemplates.lua]:564: in function ‘UpdateSuperTrackedState’
[Interface/AddOns/Blizzard_SharedMapDataProviders/SharedMapPoiTemplates.lua]:560: in function <…ard_SharedMapDataProviders/SharedMapPoiTemplates.lua:559>
[C]: ?
[Interface/AddOns/Blizzard_SharedXMLBase/CallbackRegistry.lua]:144: in function <…e/AddOns/Blizzard_SharedXMLBase/CallbackRegistry.lua:143>
[C]: ?
[Interface/AddOns/Blizzard_SharedXMLBase/CallbackRegistry.lua]:147: in function ‘TriggerEvent’
[Interface/AddOns/Blizzard_FrameXMLUtil/Mainline/Blizzard_QuestSuperTracking.lua]:59: in function ‘CacheCurrentSuperTrackInfo’
[Interface/AddOns/Blizzard_FrameXMLUtil/Mainline/Blizzard_QuestSuperTracking.lua]:17: in function <…rameXMLUtil/Mainline/Blizzard_QuestSuperTracking.lua:15>

Locals:
self = ContinentDelvePinTemplate {
SuperTrackGlow = Texture {
}
HighlightTexture = Texture {
}
Texture = Texture {
}
SuperTrackMarker = Texture {
}
pinFrameLevel = “PIN_FRAME_LEVEL_DELVE_ENTRANCE”
}
(*temporary) = 0
(*temporary) = nil
(*temporary) = “attempt to index field ‘poiInfo’ (a nil value)”

Try sticking down a map pin, ctrl-click, then removing it.

It was worth a shot, but no, that didn’t work. If I open a map and click a quest the error pops right up again.

Does it happen with addons disabled? If so, you may need to reset your cvars.

This is non-reversible (you’ll just need to reconfigure your stuff)

/console cvar_default

As far as I can tell, ContinentDelvePinTemplate is not from the Blizzard UI so whatever addon is creating/using it is out of date with the latest changes.

1 Like

Looks like it was Handy Notes: Mapnotes even though CurseForge says it current.

1 Like

Curseforge says it’s current because the author has indicated it is updated for the latest build. But bugs happen and sometimes not every change to the API gets identified (by Blizz. or the author) so stuff occasionally happens.

2 Likes

If you have it, disable HandyNotes: MapNotes, and MapNotesInstances only. I did that an my errors went away.

1 Like