Getting an error on every login..
Zephryl87 opened this issue · 9 comments
Date: 2020-05-28 18:43:14
ID: 1
Error occured in: Global
Count: 1
Message: ...AddOns\stat_weights_classic\stat_weights_classic.lua line 12841:
Usage: GetActionInfo(slot)
Debug:
[C]: ?
[C]: GetActionInfo()
...AddOns\stat_weights_classic\stat_weights_classic.lua:12841:
...AddOns\stat_weights_classic\stat_weights_classic.lua:12745
...AddOns\stat_weights_classic\stat_weights_classic.lua:13089:
...AddOns\stat_weights_classic\stat_weights_classic.lua:12955
Locals:
AddOns:
Swatter, v8.2.6377 (SwimmingSeadragon)
Aptechka, v1.13.47
Atlas, vv1.47.00.11303.00
AtlasClassicWoW, vv1.47.00.11303.00
AtlasLootClassic, vv1.5.1
AtlasLootClassicData, vv1.5.1
AtlasLootClassicDungeonsAndRaids, vv1.5.1
AtlasQuest, v4.11.64
ATTClassic, v0.2.0
AucAdvanced, v8.2.6430 (SwimmingSeadragon)
AucFilterBasic, v8.2.6364 (SwimmingSeadragon)
AucStatHistogram, v8.2.6366 (SwimmingSeadragon)
AucStatiLevel, v8.2.6370 (SwimmingSeadragon)
AucStatPurchased, v8.2.6367 (SwimmingSeadragon)
AucStatSimple, v8.2.6399 (SwimmingSeadragon)
AucStatStdDev, v8.2.6369 (SwimmingSeadragon)
AucUtilFixAH, v8.2.6371 (SwimmingSeadragon)
AutoLoggerClassic, vv1.1-release
BasicMinimap, vv3-classic
BeanCounter, v8.2.6434 (SwimmingSeadragon)
BestInSlotClassic, v2.5.2
BetterVendorPrice, vv1.13.04
BijouRR, v1.1.2
Capping, vv4-classic
CharacterStatsClassic, v3.5.3
CharacterTooltip, v1.0.4
ClassicSpellActivations, v
Comix, v1.13.2.5
DBMCore, v1.13.47-7-g4bd5c26
DBMDefaultSkin, v
DBMStatusBarTimers, v
Details, v
DetailsStreamer, v
DetailsTinyThreat, v
Dominos, v8.3.10
DominosCast, v
DominosProgress, v
DominosRoll, v
EavesDrop, v1.0.0
EnchantrixBarker, v8.2.6469 (SwimmingSeadragon)
FADEWorldTimers, v1.0
FastGuildInvite, v66
FreeRefills, v116
GroupCalendar, v
GuildRosterManager, v1.88
Hemlock, v1.1.2
honorspy, v1.7.3
Informant, v8.2.6374 (SwimmingSeadragon)
ItemRack, v
LeatrixMaps, v1.13.65
Masque, v8.2.8-Classic
MasqueCaith, v8.2.6-Classic
MBB, v1.1.1
MissingTradeSkillsList, v1.13.44
MonolithDKP, v2.1.2
OmniCC, v8.3.5
PerfectDominanceLootPriority, v1.0
PowerRaid, v3.2.2
Prat30, v3.7.81
Prat30Libraries, v
Quartz, v3.5-classic-5
Questie, v5.10.3
RollTrackerClassic, v2.21
SafeQueue, vv3.5
SahneTeamClientVanilla, v
ScepCalendar, v0.1a
ShadowedUnitFrames, vv4.2.3-Classic
SlideBar, v8.2.6375 (SwimmingSeadragon)
Spy, v1.0.28
statweightsclassic, v
Stubby, v8.2.6376 (SwimmingSeadragon)
Talented, vv191112
TalentedData, v
TitanClassic, v1.2.3.11304
TitanClassicAmmo, v1.2.3.11304
TitanClassicBag, v1.2.3.11304
TitanClassicClock, v1.2.3.11304
TitanClassicGold, v1.2.3.11304
TitanClassicLocation, v1.2.3.11304
TitanClassicLootType, v1.2.3.11304
TitanClassicPerformance, v1.2.3.11304
TitanClassicRegen, v1.2.3.11304
TitanClassicRepair, v1.2.3.11304
TitanClassicVolume, v1.2.3.11304
TitanClassicXP, v1.2.3.11304
TitanSocial, v1.13.3
TomTom, vv11304-1.1.2
TradeSkillMaster, vv4.9.35
WeakAuras, v2.17.5
WeaponSwingTimer, v4.1.0
WideQuestLog, v
BlizRuntimeLib_enUS v1.13.4.11304
(ck=a5c)
I have no idea what causes it..
Haven't heard of any others experiencing this so this might be a special case, perhaps interactions with other addons. Try reinstalling it but make sure to clear the addon's cache in the middle of it. I think twitch has a way of doing this but if not go into this folder: World of Warcraft_classic_\WTF\Account\ACCOUNT_NAME\SERVER_NAME\CHARACTER_NAME\SavedVariables and delete both stat_weights_classic.lua and .bak files while the game is closed.
After an update. Should i delete and redownload it? I always update my addons with the Twitch app
EDIT:
Just deletet and redownloaded it and the same error appears..
It was working fine before
Tried it, same error.. =/
I have a feeling, that it is related to my macros somehow..
I'm gonna test later, if i get the error, without macros on my actionbars
EDIT:
Alright, so it has nothing to do with my macros.. removed them all from the actionbars and the error still appeared. However after disabling Dominos, the error disappeared. Enabling it again and the error comes back. I have played around with Dominos in the options (disabling macro text, etc.), but nothing seems to help.. =/
Just wanted to also clarify, that I used Dominos before installing this addon and it worked flawlessly before.
Latest update didn't change anything.. =/
Have you been able to replicate the error with the addon Dominos?
Nope, Dominos with default settings works fine on my end. What Dominos version are you using? I'm thinking that you have configured Dominos in a way that becomes problematic for this addon in some way.
Maybe you can try to back up / save your current Dominos settings and try using the default settings to see if the error goes away. Or maybe you are able to send me your Dominos settings and I can try it out myself.
I can´t see from your error report the nature of the issue but a function call to GetActionInfo(slot) seems to be the issue. Are you able to find out the value of the input variable (slot) is at the time of failure and what it is returning? My lua error logs usually shows a bit more information which might be from another addon but unsure. Or if you have a code editor handy, you can try putting print statements before and after the function call to GetActionInfo(slot) at the line where it fails to visualize input/output variables.
After trying different things, I now found out, that it has in fact something to do with my profile.. I'm guessing it is the scaling of my bars, because when I resinstalled Dominos it didn't give me any errors with the default settings. Now it gets weird though:
When I copied my backup settings back in, the error came back and switching to the default settings didn't help. However, when I reloaded with the default settings, the error didn't show up and stat_weights_classic was working fine. Switching back to my profile, it kept working as intended.
So my assumption is, it has something to do with my profile being first loaded..
I'm attaching my profile into this. Maybe you can take a look into it. Thank you btw for your patience lol
Dominos.zip
EDIT:
Oh, btw, the profile I'm using is labelled "Standard"
I was able to reproduce it using your settings. Strange issue, not sure why it's happening. However, I have pushed a commit as a workaround for this problem. You can try out the most recent master branch and see if it works.