#Is there a easy way to learn to diagnose lua errors in bugsack?

9 messages · Page 1 of 1 (latest)

fallen wren
#

I have had a WA for quite awhile https://wago.io/o0SchIQUa and one of the auras keeps returning a bunch of lua errors. I am not familiar with programming, only having done APL work for a few specs in the past is the extent of my knowledge of that sort of thing, but I didnt know if there was a good way to figure out how to read bugsack lua errors to easily fix issues with new patches etc. for WAs that have been working historically and suddenly break

fallen wren
#

for reference, trigger 1 of "non AMS absorbs" is what is generating lua errors

real valve
#

!deprecated

low onyxBOT
#

With The War Within many functions of the API were deprecated, follow these links for more information 11.0.2 11.0.0

real valve
#

That trigger calls a function you declare in the on-init of that aura

#

That function tries to call UnitAura, which doesn't exist anymore

#

The error should look like

attempt to call global UnitAura (a nil value)

#

It can't find (nil value) that global. So it's gone.