-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bad argument #6
Comments
Are you trying to use this as a warrior, rogue or hunter? If so, as stated in the readme:
I may add a check so the addon doesn't load when on those classes, because I probably won't get to finish the rewrite on the core system to finish melee support for some time. If you're also using it on a supported class then you should disable it on the not supported characters to not get the error there. Sorry about that. |
no, this is a paladin. i get that error when i first login, it works fine
otherwise.
…On Thu, Apr 16, 2020, 9:04 PM coolmodi ***@***.***> wrote:
Are you by any chance trying to use this as a warrior, rogue or hunter? If
so, as stated in the readme:
Warrior, Hunter and Rogue have no support at all.
I may add a check so the addon doesn't load when on those classes, because
I probably won't get to finish the rewrite on the core system to finish
melee support for some time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APGZEKY6EC2NX7SAOI6LBFDRM6TK5ANCNFSM4MJ2MYHA>
.
|
Can't reproduce it with a lvl 22 paladin. Also can't see how it's even possible to happen tbh. Does it only happen with that char? |
yeah it;s on a level 1 pala
…On Sun, Apr 19, 2020 at 10:03 PM coolmodi ***@***.***> wrote:
Can't reproduce it with a lvl 22 paladin. Also can't see how it's even
possible to happen tbh. Does it only happen with that char?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APGZEK522XX5ZEEKTBZB3ODRNOUPLANCNFSM4MJ2MYHA>
.
|
I found another error with level 1 paladins and fixed it, but I still can't reproduce the error you got. Maybe try the newest version and see if you still get it. Maybe the error message you got was just misleading. |
latest version looks good :) |
Message: Interface\AddOns\SpellCalc\system/buffs.lua:418: bad argument #1 to 'ipairs' (table expected, got nil)
Time: Thu Apr 16 11:48:45 2020
Count: 1
Stack: Interface\AddOns\SpellCalc\system/buffs.lua:418: bad argument #1 to 'ipairs' (table expected, got nil)
[C]: ?
[C]: in function
ipairs' Interface\AddOns\SpellCalc\system/buffs.lua:418: in function
UpdateTalents'Interface\AddOns\SpellCalc\system/stats.lua:284: in function
FullUpdate' Interface\AddOns\SpellCalc\events.lua:20: in function
?'Interface\AddOns\SpellCalc\events.lua:109: in function <Interface\AddOns\SpellCalc\events.lua:108>
Locals:
The text was updated successfully, but these errors were encountered: