Okay, sounds like something's hanging up in OnUpdate, specifically one of the first bars that gets updated. It should be erroring out, though if it's consuming that much CPU I suppose it's also likely that it's getting caught in an infinite loop. A couple questions:

Do you have an error-catching addon like BugSack (I highly recommend this for anyone trying to troubleshoot addons, by the way, it's a very good addon)? If not, do you have the default UI set to show Lua Errors? It should be in one of the last couple option panels in the Interface options.

Right now I'm thinking that trinket procs are causing the hangup (because they're the first bars generated). Do you have trinket bars turned on? If so, how are they configured? Merged? Cooldowns? Does the hangup seem to occur when you get a trinket proc? Which trinkets are you using? It's possible that I haven't covered the case where SAA doesn't know about the trinket you have equipped, and it's searching for something that doesn't exist in its database.

Living Flame is a Use: trinket, which I haven't been able to test for lack of having one of my own. EotS should be fine, since it's a proc, and one I have to boot, so I know the code for it works. Is Flame macro'd, or do you trigger it manually each time?

I updatet my SAA from 1.2.1 to 1.3.3 because I didn't like the new look and 1.2.1 still worked with patch 3.2. But I finally switched and want to ask several things.

- There is a lot of space between the bars if the borders are disabled. Could you please insert an option to toggle the padding?
- Between MF and IS, the FF is positioned. This is really strange, because you have to cast FF less often and the info about the timer seems to be of less importance, so I would put it below MF and connect MF with IS. Maybe you could insert on option to reposition the bars in any way the user would like it to have ;-)

By the by, if I enable MF ticks, my frame rate drops from 90 to 9. Don't know why.

- That sounds doable.
- Something I've been planning, though I've been saying that for a while.
- This concerns me. I'll try turning them on tonight and see what happens. I run with debuffs merged, so I've never noticed it.

SquawkHard does this, and was the reason many people thought I'd quit updating SAA (because I mentioned it and that it implemented exactly that, and that I would hence not implement it). I used it for quite a while, but have since given it up. It was really only serving as a double-check for me, and I decided it wasn't worth the screen real-estate.

As for the tick bars, a lot of people use them to determine when to refresh DoTs (i.e. not right before a tick). I've never been fond of such micromanaging, so I don't use them.

Living Flame is macro'd in. I never experienced the frame-drop issue last night, though.

In case anyone hasn't noticed, the Eclipse/cooldown icon serves as a sort of mini-SquawkHard. Assuming you're in the normal rotation, if it's the Lunar icon you should be casting SF, and if it's the Solar you should be casting W. It's a good sanity check.

I've never tried SquawkHard (to be honest I just assumed it would be useless for me since it's probably a less refined rotation than the one I use normally). Does anyone have a basic pseudocode of how it determines priorities? Writing a really spiffy one might be a fun task once the TTT article is done.

(also, for what's it worth, I still use SAA 1.2 since it works fine and I never needed anything more. No issues currently).

A thought: you can only root/cyclone one thing at a time, yet when you switch targets (like you commonly would when CCing) you lose the duration bar.

Would it be possible to have both those be "sticky"? I realize that root can be broken early -when it happens I usually know about it- and I'd rather have an incorrect root bar in that situation then none at all ever.

CC bars check Focus as well as target. It's a good habit to focus your CC target even without SAA, and use focus CC macros so that you don't have to waste time retargeting.

May it be possible to add a textual note to the eclipse-cooldown-bar which eclipse is currently on cooldown respectively if wrath or sf should be cast to procc the next eclipse? (Sth. like "(Solar|Wrath) Eclipse Cooldown: x.y sec" or "Eclipse Cooldown: x.y sec (cast Wrath|SF)")
During some encounters (brezzing, innervating someone else, running across the room) i sometimes simply forget which eclipse was recently used, so that might help.

May it also be possible to highlight the eclipse-bar when it proccs, e.g. colour it red for 3 seconds, pulse it, flash it, shake the screen or sth. similar?

I also had errors, related to the Trinket bars. I'm investigating it, but I'd suggest turning them off and seeing if that fixes things. For some reason it's not getting the item name correctly. Since trinkets are the first bars to be updated, if they error out none of the other bars will work until the trinket proc is over.

I may use NG as my test case for adding bars without needing to reversion SAA, though I don't know if keeping it in the same timescale would be useful. How much time it has left is less important than its presence.