If you're having the MF/Eclipse/Eclipse CD bar overlap problems described above after updating to SAA v. 1.2, here is a quick fix that is working for me and might help you:
Delete SAA v. 1.2 from your addon folder.
Go to the wowinterface SAA page. See the tab that says "Archived"? Click there.
Download v. 1.1.1 (this is the most recent one before 1.2), install it as usual.
No more overlap! But now you probably have the FF issue. So just use the old fix on that, which is:
Go into the SquawkAndAwe folder in your addon folder.
Open the SquawkAndAwe LUA file (I used notepad to open it in windows)
Scroll down just a bit; you'll see this line:
SquawkAndAwe.combat.faerie = #####
There's some 5 digit number there. Replace that number with 770, the new spell number for FF since 3.1.
Hope this is helpful! Sorry if this is obvious to some people.
ok i found a quick fix i think, in the SquawkAndAwe.lua in the bar creation section,
change the "local barCount = 0" to "local barCount = 1"
and that should cause the overlap to go away. i havent tested this will all the bars on, but it works for having both eclipse bars and both is and mf bars turned on. and this is for the 1.2 verson as well
Good, that's useful info. I'll see if it happens when I raid tonight, though it wasn't an issue for me while I was testing it. As for disconnecting the bars, that would be a lot of work, with little benefit, so not something I'm likely to do. Also, when I get the fix updated, I'll be removing the borders on all "internal" bars, i.e. Eclipse (not cooldown) and both the tick bars.
Figured I'd add that I did not try this (although I saw the fix). It was happening with 1.1.1 (no FF Fix) and the newest release. I've also tried different variations of bars being displayed to no avail.
Odd part is that I'm not getting the issue here, though Cygmus' fix is in the right spot for what would cause it. I'm not sure what's going on, I checked my local copy against the one I uploaded, and they're identical, and none of the changes from 1.1.1 came anywhere close to this. I'll see what I can do, though, maybe there's a workaround.
I had the same issue with 1.1.1 after I did the FF fix. After upgrading to 1.2 I still had the issue until I deleted the addon folder and the saved variables (which had my old 1.1.1 settings in it). After doing this and reinstalling 1.2 the overlapping disappeared.
Now that I'm re-sub'ing to WoW, I've been looking around the addon's sections to see how things have progressed. It's really nice of you to have included original authors, and it got me to thinking about how incredibly far these have come. The addon list actually stretches back at least 2 generations prior in terms of where the work came from.
First was stunwatch by Vector in early 2005.
that bred DiscoDice (rogue timers and cooldowns) in early 2006 which also used an xml file for the gui
that led to DisqoDice which Ace'd it up and built frames in the lua itself
that led to Shock and Awe which I'm excited to start using as soon as my character transfer goes through
Which gets us to here.
You've done an awesome job with this. I don't really have a point to this post, other than I like documenting the history of it. There's probably even more that happened before the original stunwatch, but I don't know that part of history.
If I ever get my druid above 19 (not a twink, just where I happened to stop leveling him and start bank-alt'ing him), I'll definitely install this addon.
I did a 3 moonkin raid last night and it flipped out, was ending up with moonfire showing 15 additional duration adds while there was no moonfire belonging to me on the target. Each time I applied a fresh moonfire it reset the duration on the Moonfire bar but not the # on it and I -think- whenever other people applied their own fresh MF it reset the bar again. Seems to behave normally in a 1 moonkin world so luckily that was a pug. This was 1.1.1 with the faerie fire fix.
I did a 3 moonkin raid last night and it flipped out, was ending up with moonfire showing 15 additional duration adds while there was no moonfire belonging to me on the target. Each time I applied a fresh moonfire it reset the duration on the Moonfire bar but not the # on it and I -think- whenever other people applied their own fresh MF it reset the bar again. Seems to behave normally in a 1 moonkin world so luckily that was a pug. This was 1.1.1 with the faerie fire fix.
Yeah, there are issues with DoT's and multiple Moonkin. When IS expires, is tracks the IS from the other Moonkin as well.
With the new 3.1.1 mini-patch my SAA hasn't been able to track my eclipses. I strictly use SAA for eclipse, so I tried downloading SquawkHard (I think that's the name) and it didn't track my eclipses either. I've tried updating everything to the latest version with no success, I was merely wondering if this was an issue with this patch or possibly my setup :]
With the new 3.1.1 mini-patch my SAA hasn't been able to track my eclipses. I strictly use SAA for eclipse, so I tried downloading SquawkHard (I think that's the name) and it didn't track my eclipses either. I've tried updating everything to the latest version with no success, I was merely wondering if this was an issue with this patch or possibly my setup :]
There's a bug floating around where the Moonfire bar will cover the Eclipse bars. Do your Eclipses show up if you're not casting Moonfire? If not, could you let me know if you're getting any lua errors, and what they say if you are?
There's a bug floating around where the Moonfire bar will cover the Eclipse bars. Do your Eclipses show up if you're not casting Moonfire? If not, could you let me know if you're getting any lua errors, and what they say if you are?
The eclipse and timer bars are the only ones I utilize from SAA, my moonfire, FF and IS are tracked by Classtimers (because I have 5 80's, having one mod in the same spot works nicely). I don't think anything is covering it up, I'll check out if I'm getting any lua errors though.
EDIT: No, I couldn't find any lua errors occuring when eclipse was procced. And no, the eclipse and CD timer don't show up even when I'm not casting MF.
EDIT2: I messed around with some settings, and it seems that the eclipse + CD bar is shown only when I have the MF bar activated, and it does overlap like you said. This is also making my eclipse + CD bar very obscured and it stretches across my screen. Disabling the MF bar also disables the eclipse + CD bar.
"local barCount = 1" worked for me as well. I could not get the overlap to go away with re-install like others mentioned. I also had the bars stretched really far across my screen. I somehow fixed this by selecting "move frame" and then enabling every type of bar. I then disabled all the bars that I don't want to see, and the bars stayed the normal non-stretched size.
There's a bug floating around where the Moonfire bar will cover the Eclipse bars. Do your Eclipses show up if you're not casting Moonfire? If not, could you let me know if you're getting any lua errors, and what they say if you are?
I have that bug and it shows eclipse, its just MF covers it
e: removing mf bar just means the iS bar moves up to cover eclipse...
e2: Hotaka from mmo-champ forums brought this gem in:
I found my solution, I had a talent bug, I had all my talents, but my tree did not reflect that. so the mod was confused and not giving me it. had to hearth and respec. glad they fixed this stuff in 3.1.1 ><
Adoriele -- I've noticed that occasionally after I cast IFF on a target, switch to a new target, and then switch back to the original target, S&A's IFF bar is gone. Now.. I can't say that I've done any exhaustive troubleshooting, but I'm guessing that it's because another boomkin is casting IFF on top of mine. Would it be possible to have S&A treat IFF differently and always show a timer bar for it regardless of who casts?
By the way, thanks for all your efforts for S&A.. it's easily one of my most important addons!
Adoriele -- I've noticed that occasionally after I cast IFF on a target, switch to a new target, and then switch back to the original target, S&A's IFF bar is gone. Now.. I can't say that I've done any exhaustive troubleshooting, but I'm guessing that it's because another boomkin is casting IFF on top of mine. Would it be possible to have S&A treat IFF differently and always show a timer bar for it regardless of who casts?
By the way, thanks for all your efforts for S&A.. it's easily one of my most important addons!
Actually, that's a pretty good idea. I'll add it in.
It's been brought to my attention that there may be an easy reason for the Eclipse/Moonfire bar overlap; Some people are failing the check for whether Eclipse is talented. SAA does a look into your talents when it loads, and whenever they change, and skips over the Eclipse bar when creating the frame that holds all of the timer bars if it thinks you don't have it. The bar still shows up when Eclipse procs, because it's still enabled, it just doesn't have space allocated for it (more precisely, the Moonfire bar is allocated to the same space because it doesn't believe the eclipse bar will ever show up).
It should come as no surprise, then, that with the large number of bugs related to the talent trees introduced in 3.1, one of them appears to be that some people are returning that they do not have Eclipse talented when they do. The fix is simple for this. In the same area as Cygmus' fix [CreateBaseFrame()], there should be a line
if (self.db.char.eclipsecdshow or self.db.char.eclipseshow) and self.db.char.eclipseTalents > 0 then
change it to
if self.db.char.eclipsecdshow or self.db.char.eclipseshow then
This removes the check for whether you have Eclipse, and will allocate the space for the Eclipse bar based solely on whether you have the bar enabled, even if you don't have Eclipse talented. For most people, not an issue, but if you enjoy casting DoTs while resto for some reason and have the Eclipse bar enabled out of habit, the DoT bars won't move up to save space.
This will be committed into the release version once I double-check that the FF change above won't make any horrible issues, though I don't expect it will. I'll change it back once the API for accessing talents gets fixed. In fact, I'll likely remove all talent checks just to be safe. Letting you guys know now how to fix it on your own in case you need it for raiding tonight, as I won't be able to commit at least until I get home, likely not until we're done raiding.
Could it be posible to add a bar for the Tier8 4pice proc?
i dont use the OoC bar, so couldnt it be posible for me, to just change the procwatcher to the 4pice proc instead of omen?
Yeah, there are a couple bars I'd like to add in. Just haven't quite taken the time to code them yet.
Also, 1.2.1 adds the ability to track any FF (not Feral), but I forgot to add the trigger from someone else' cast. So the bar will spawn only if you cast it or retarget a mob that already has it. I'll add that in the next release.
Figured I'd add that I did not try this (although I saw the fix). It was happening with 1.1.1 (no FF Fix) and the newest release. I've also tried different variations of bars being displayed to no avail.
Fixed this, realized I never documented the fix. When I was having the trouble before, I had tried a) deleting/installing the addon and b)deleting recreating the saved vars...never both at the same time (stupid, I know). Did that and it works like a champ.
On a side note, loving the 1.2.1 additions. Thanks!
Just started using the addon and I love it.
I had to add support for Wrath of Elune from the pvp set, but the code is very well organized so it didnt take but a few minutes. Thanks for putting in the time to help the boomkin out with this addon.
I'm currently in the middle of adding a large number of bars to SAA, post here before I get it uploaded and your suggestion may get added (no guarantees). Currently on the list:
4T8 (yay finally!)
4PvP (might as well)
Two trinket bars*
CC bars**
Starfall Duration and Cooldown
FoN (I will not [at this point] remove the bar when they die, will show both duration and cooldown)
Typhoon cooldown
Innervate Duration and cooldown (duration only if used on yourself)
Barkskin Duration and Cooldown
* Trinket bars will exist in two modes: Merged and Unmerged. Unmerged, you get two separate bars, and each will track the duration and cooldown of a separate trinket. Which trinket the bar tracks will be dynamic, first trinket effect will go to the first bar, second to the second. This gets reset any time there are no trinket effects up or cooling. For example: Embrace of the Spider procs, it goes to trinket bar 1. If Dying Curse procs while EotS is still up (or cooling down), it goes to trinket bar two. If EotS has cooled, and DC procs first, it gets bar 1, EotS gets bar 2 when it procs. Similar things happen with clickies, and persistent buffs like IDS/Eye of the Broodmother.
In Merged mode, you get a single bar for both trinket effects, and no tracking of cooldowns. This is more useful if you don't have any clickies/persistent effects, since the CD doesn't matter so much. It saves you a bar's worth of screen space, which is nice, and the bars will be stacked much like the Eclipse bars. You'll see the shorter-duration bar on top, and the longer-duration bar behind it. Again, if you're trying to keep something like IDS up, probably want to keep the bars unmerged.
** CC bars will include Roots, Hibernate, and Cyclone. These will also have the option to merge in the same way as trinkets, allowing them to overlap to save screen space. I probably won't have diminishing returns in this iteration, I'm unfamiliar with the math and when exactly to begin the DR countdown. If I do end up implementing them in the future, merging the bars will remove the display of DR.
*** I may also add the option to merge ability cooldown bars, which would mean removing their duration bars. Unlike most other things, knowing the cooldown on Innervate, for example, is more important than knowing when the buff will drop.
**** I may also add a similar option for debuff bars, i.e. IS/MF/FF, removing the ability to watch Ticks. A lot of this is to conserve space since there will now be potentially a large number of bars active at a given time.
04/16/09, 9:13 PM
