Closed filliph closed 1 year ago
Adding
if not v.triggerData then
DevTools_Dump(v)
end
Directly beneath
JDT.buildAura = function(ExportTable,DungeonValue,BossNameValue,TypeKey,v,ExpansionValue,ExpansionKey)
Prints enabled = false
.
The problem is these two blocks in Main.lua:
for k,v in pairs(TypeValue) do
local AuraToCheck = JDT.buildAura(ExportTable,DungeonValue,BossNameValue,TypeKey,v,ExpansionValue,ExpansionKey)
local InstalledAura = WeakAuras.GetData(AuraToCheck.id)
if v.enabled == true then
for k,v in pairs(TypeValue) do
local AuraToCheck = JDT.buildAura(ExportTable,{groupName= ExpansionValue.groupName},{additionalName = ""},TypeKey,v,ExpansionValue,ExpansionKey)
local InstalledAura = WeakAuras.GetData(AuraToCheck.id)
if v.enabled == true then
I think the problem is pretty obvious 😉
Fixing this bug re-opens #59 - mousing over the updates in /wa
menu still shows the same Lua error as in that issue.
man i tested this extensivly but missed this bug
I can't seem to reproduce this issue though i don't even get how trigger data could ever be nil. Time for bed though I can't get anything done anyways
v1.0.8 does not fix the issue.
i finally managed to reproduce this but it feels like debugging this requires advanced knowledge of quantum physics. Adding if not v.triggerData then DevTools_Dump(v) end results in nothing xD but a nil error on trigger data
i finally managed to reproduce this but it feels like debugging this requires advanced knowledge of quantum physics. Adding if not v.triggerData then DevTools_Dump(v) end results in nothing xD but a nil error on trigger data
If you follow the instructions in this post: https://github.com/Jodsderechte/DungeonAuraTools/issues/64#issuecomment-1335674716 you'll see the same output I referenced in that post.
i did but i didn't see the same output however i found the error and hopefully fixed it
@Jodsderechte this has not been fixed, the line number has however shifted:
1x DungeonAuraTools/Export.lua:175: attempt to index field 'triggerData' (a nil value)
[string "@DungeonAuraTools/Export.lua"]:175: in function `buildAura'
[string "@DungeonAuraTools/Main.lua"]:223: in function `CheckIfAuraUpdates'
[string "@DungeonAuraTools/Main.lua"]:302: in function `?'
[string "@AllTheThings/lib/CallbackHandler-1.0-7/CallbackHandler-1.0.lua"]:119: in function <...ings/lib/CallbackHandler-1.0/CallbackHandler-1.0.lua:119>
[string "=[C]"]: ?
[string "@AllTheThings/lib/CallbackHandler-1.0-7/CallbackHandler-1.0.lua"]:29: in function <...ings/lib/CallbackHandler-1.0/CallbackHandler-1.0.lua:25>
[string "@AllTheThings/lib/CallbackHandler-1.0-7/CallbackHandler-1.0.lua"]:64: in function `Fire'
[string "@DataStore/libs/AceEvent-3.0-4/AceEvent-3.0.lua"]:120: in function <DataStore/libs/AceEvent-3.0/AceEvent-3.0.lua:119>
mad life it fixed the bug that i encountered with trigger data being nil guess i'll have to do more checking
Description
After #59 was fixed, a new error has been introduced.
WeakAuras Version
5.2.2
World of Warcraft Flavor
Retail (Default)
DungeonAuraTools Version
1.0.7
Tested with only WeakAuras and DungeonAuraTools
Lua Error
Reproduction Steps
Saved Variables
DungeonAuraTools (2).zip
Last Good Version
1.0.6
Screenshots
No response