Booguh 0 Report post Posted March 16, 2017 I've been using Call of Elements addon since I first created my shaman. Today the addon randomly won't work anymore, completely broken. I have uninstalled/reinstalled the addon several times. Deleted the saved variables from my account and character folders. Uninstalled/reinstalled again, cried, tried again, cried. I simply cannot get it to work anymore no matter what I try. I haven't messed with any of my addons prior, I don't understand why its not working now. The only thing I can think of is last night I did the Linken quest chain and had the Silver Totem of Aquementas in my inventory, but it didn't break it then, I don't have it in my inventory now. I'm desperate to get this working again. Has anyone had the same issue? At first login I get the error "Interface\AddOns\CallOfElements\COE_TotemData.lua:593: attempt to index field `?' (a nil value)" upon typing /coe and bringing up the config window I get the error: "Interface\AddOns\CallOfElements\COE_TotemVisual:193: attempt to perform arithmetic on field `?' (a nil value)" The config window open but nothing works, the buttons dont appear. I'm at a loss as to what I can do to fix this. 0 Share this post Link to post Share on other sites
gotmilk0112 10 Report post Posted March 18, 2017 Try deleting the .lua file in the WTF folder. When CoE didn't work for me, I just deleted its data file in the WTF folder, and it worked after that. 0 Share this post Link to post Share on other sites
Booguh 0 Report post Posted March 20, 2017 Did that already. Deleted the WTF files in both Account and character folders. Same errors. =/ 0 Share this post Link to post Share on other sites
gotmilk0112 10 Report post Posted March 20, 2017 Do you have the dependency for it? (Chronos) Do you have the right version? I'm using the one downloaded from here: http://www.vanilla-addons.com/dls/callofelements/ 0 Share this post Link to post Share on other sites
Booguh 0 Report post Posted March 20, 2017 Yup that's the version I've tried removing/reinstalling multiple times. It was working flawlessly from lvl 10-60. Randomly it stops working, didnt add any additional addons or make any changes to my UI, i just log in and its no longer working and nothing I do even changes the error I get. 0 Share this post Link to post Share on other sites
gotmilk0112 10 Report post Posted March 20, 2017 Huh. Weird. For me, it didn't work at first and I had to delete the .lua and .lua.bak files in the WTF folder and it worked fine after that. Haven't had any issues with it since then. 0 Share this post Link to post Share on other sites
Booguh 0 Report post Posted March 20, 2017 Yea thats why its so frustrating, it was working for weeks. And then after an honor update its all broken 0 Share this post Link to post Share on other sites
gotmilk0112 10 Report post Posted March 20, 2017 (edited) Have you tried disabling all other addons except CoE / Chronos, just to make sure that it's not another addon interfering? Also, there are two different .lua and .lua.bak files for CoE, one in the account / savedvariables folder, and another in the character / savedvariables folder. Try deleting them both. Edited March 20, 2017 by gotmilk0112 0 Share this post Link to post Share on other sites
Booguh 0 Report post Posted March 20, 2017 1 hour ago, Booguh said: Did that already. Deleted the WTF files in both Account and character folders. Same errors. =/ Yea aware there were two different locations it creates .lua and .lua.bak files. Whenever I try deleting those files I've deleted them both. Currently I have now completely uninstalled and reinstalled the entire wow client. Disabled every addon except CoE and Chronos. Deleted the .lua and .lua.bak files in both the account and character saved variables. Still getting the exact same error like nothing has changed. One thing its been saying everytime I log in is: [COE] Call of Elements v2.6 [COE] Errors in the SavedVariables have been corrected. I don't remember if it said that in my chat log for the 50 other levels while it was working, but I'm still getting the same error with a completely fresh install of both the client and addon. I'm at a loss of what I could possibly do more 0 Share this post Link to post Share on other sites