My weakauras are having a problem and I dont know what it is.
121368 errors in one key, and I’ve reinstalled it, updated it, redone all the weakauras I have, and it still is giving the same error.
It goes “not ready” every time I’m in combat, and also says interface action failed because of an addon. But I dont know what action it’s having an error with, getting very annoying
there’s no possible way anyone can troubleshoot this for you here. your best bet is to check wago to make sure you have the latest version of your WAs. if that doesn’t work, try disabling them all then enabling one by one. (that might not help either, it could be an interaction between two or more.)
1 Like
I have done that. I’ve done quite literally everything pertaining to the entire addon as I said in the OP.
Whatever though
Have you tried the WA discord? They’ll probably be the best bet for support.
1 Like
You should be able to see which addon/WA is erroring out. WeakAuras recommends downloading BugSack and BugGrabber.
Tracing the bugs back to the WA is your best first-step solution. Once you know what is causing those errors, you should find a replacement WeakAura (it’s probably not worth your time to try and fix it).
2 Likes
I have a M+ WA to auto-mark priority targets in keys. It’s not as good as the one I had in S1, but the WA author for the code I used in S1 didn’t update their project for S2, so I picked up a new aura that did most of the same functions/options.
However, I note that when my friend and I run a key together, we get conflicts as we’re both using the same WA but it has no prioritization if multiple players are using it. My friend and I have different marks for the same target and so the aura frequently flips between his mark and my mark and eventually Blizz over-code steps in and says “too may interface actions” and nothing gets marked by either of us for a while. We could coordinate our options to use the same marks or, like the S1 author, the new coder could use a priority check (leader, tank, etc.) to ensure that only one instance of the aura is running in a key to avoid duplicate actions that trigger warnings/errors.
That could be what’s happening for you, but as Pyri said, without more details on what auras you’re using, when the errors happen, etc. it’s difficult to offer any useful insights to your specific situation.
Cyous’ recommendation to get BugSack and BugGrabber WAs to trace the specific errors you’re getting is a good first step.