I have 2 characters that have been suffering from disconnects soon after loading in for months now. I know it’s due to 1 or more of my addons but my other characters load the exact same addons without issue. So clearly there’s an issue specific to these 2 affected characters. I suspect it is because of the fact that the 2 characters in question have had their names changed in the passed and this is probably causing some massive LUA error that the game just force disconnects me for. Currently I work around the issue by simply disabling all addons for these 2 character on first time load in and then enable all the addons and do a /reload. By doing this, I do not get a forced disconnect. But this is extremely annoying to do every time.
So what I think I need to do is clear the affected characters caches? But I do NOT want to lose all my addon customization. For some addons its OK since I can import from a exported user profile. But most addons do not have that function.
Can anyone please tell me how to clear the caches of the affected 2 characters whilst still preserving my addon customization?
Thanks.
Note: It can be a bit RNG. There are times when I load the affected 2 characters with all addons enabled and I do not get force disconnected.
I don’t think there is a simple way. You can hunt the miscreant addon and delete any mention of it in the cache folder. But I’m sure the addon settings are kept in the WTF folders
2 Likes
I use an error collection addon called BugSack to help identify misbehaving Addons. It will also display the line that is throwing the error which can be reported to the addon developer.
You can always keep a copy of the folders just in case. So don’t delete it, just rename it, that way you can put it back if needed.
You should be able to just delete the cache folder without losing any settings. I think. It’s possible this would fix things.
But most settings are saved in the wtf folder. If these settings are corrupted, there wouldn’t be that easy of a way to find it. You might be able to get some better help in the ui and macro forum, or possibly technical support.
1 Like
Thanks for the tip. I tried that addon but it only picks up the last couple addon bug reports. I have about 70 addons. So its not gonna help me that much unfortunately.
Bugsack and Buggrabber are the “standard” addons for this.
They’ll report the chain of failures back to the root failure, but as different errors.
If you need help deciphering this, I’m Kaldara#11970 and I can assist you any time I’m on.
If you want to find an addon that’s causing an error, the simplest method (not necessarily the most efficient) is to turn off all addons and then reload and then turn them on one at a time until the error appears.
A more efficient way is to turn half of them off. If the error goes away, turn that half on, then turn the other half off. If the error comes back, whichever half had the error, turn half of THOSE off and narrow it down by halves.
Either way, you can isolate a bad addon pretty quickly.
If you end up with BOTH halves not giving the error, but getting the error when you have both halves turned on then it’s likely an incompatibility between addons (usually the result of complex hooking or variable name collisions).
That’s when it gets sticky, but again, I can help if you need me to.
Just caught the bit about name changes:
Some addons, mostly those that use the ACE3 architecture, do not play well with Blizzard’s character-level data. That could be part of the problem.
3 Likes
If the issue is disconnects shortly after login you may want to try an addon like Warmup to profile what’s happening on a login and seeing if the affected characters are much different than unaffected ones.
Disconnects can happen for a variety of reasons, and an addon doing too much should (in theory) never be a cause; but I have had painful experience with disconnects happening for mac users in an addon that dynamically created a lot of complex UI elements when it was first shown.
1 Like
Figured it out. Turns out there was addon that I thought had been deleted but in reality only the main component folder had been deleted. There were 2 additional addon folders that were dependencies that hadn’t been deleted for some reason. Once I deleted the offending folders, my issue disappeared.
2 Likes