Mega Macro

Mega Macro

39.7k Downloads

src/mega-macro.lua:225 script ran too long

MikeCook9994 opened this issue · 2 comments

commented

Installed the macro after running the backup as specified in the documentation. When I signed into the game, bugsack has this error (also occurs on /reloadui). Macro import appears to silently (? idk what the expected failure behavior is) fail as well. Default macro UI has all my macros and they haven't been imported into the addon.

1x MegaMacro\src/mega-macro.lua:225: script ran too long
[string "@MegaMacro\src/mega-macro.lua"]:225: in function `GetMacrosInScope'
[string "@MegaMacro\src/mega-macro-icon-evaluator.lua"]:53: in function <...eMegaMacro\src/mega-macro-icon-evaluator.lua:31>
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
...
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "@MegaMacro\src/mega-macro-icon-evaluator.lua"]:184: in function <...eMegaMacro\src/mega-macro-icon-evaluator.lua:170>
[string "@MegaMacro\src/mega-macro-icon-evaluator.lua"]:207: in function `Initialize'
[string "@MegaMacro\src/main.lua"]:34: in function <MegaMacro\src/main.lua:16>
[string "@MegaMacro\src/main.lua"]:44: in function <MegaMacro\src/main.lua:42>

Locals:
scope = "cs"
(*temporary) = <table> {
 Character = "ch"
 Global = "gg"
 CharacterSpecialization = "cs"
 Class = "gc"
 Specialization = "gs"
}
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = "script ran too long"
commented

Worth noting that this same error is occurring on beta where I have no macros at all.

commented

Hi Mike,

Thanks for pointing this out! It happens when you have zero macros defined I think. I had logic to handle this but I was missing 2 characters haha.

I'll create a 1.1 release now and that'll fix the issue.

Regards,
Sellorio