Anyone have any info on the purpose of the 'spirit_bar' timer, for Halazzi?
- Registered User
Member for 14 years and 13 days
Last active Tue, Sep, 30 2008 22:06:02
- 0 Followers
- 7 Total Posts
- 0 Thanks
May 15, 2008BigBrother's console output on CC breaks is typing over itself, from adding the raid icons. This is causing some character shifting/blurring as the font only partially overwrites the old version. My guess: the string is being output twice (before and after adding in the raid icons).Posted in: General AddOns
Should be fixable by preventing the output of the string until the final version is built?
May 15, 2008I have a question on the Halazzi module:Posted in: Raid AddOns
What is the purpose of the 'spirit_bar' timer?
spirit_bar = "~Possible Normal Phase",
I have never experienced any ability/event during the Halazzi encounter, that would relate to this timer. As far as I'm aware, the only trigger for moving from Split Phase --> Normal Phase is the low-health threshold on either Halazzi or Spirit of the Lynx. Is there another trigger that can occur, that I've never seen?
May 15, 2008On Al'ar Phase 1, discussing whether or not platform transitions are set to 30s timers:Posted in: Raid AddOns
Quote from Rabbit »
They're not. The transitions are on a cooldown, it's not a static timer. It's been a long time since I was there, but I remember him staying on one platform for at least a minute, possibly more.
I'm sure you'll experience the same thing after a few more attempts.
Al'ar can become 'stuck' at a platform, but the timed event still occurs. Notice that a new Ember of Al'ar spawns, even though Al'ar itself doesn't advance to the next platform correctly.
I too would like to see a 30s timer added for Al'ar Phase 1, to countdown until next possible transition/Ember spawn. I don't know if it's a hard-time trigger (exactly 30s until next event) or the more general cooldown (minimum of 30s before event). In the context of adding a timer bar, it doesn't matter, and can just treat it as a cooldown-style event.
My question is: Does the Al'ar encounter fire off a trackable event when spawning an Ember? This could be used to control the timer resets, if it occurs.
Nov 16, 2007Posted in: Raid AddOnsQuote from phaze »
Akil'Zon timer for the initial Storm is off by about 5 seconds, for the cooldown (5s remaining on Storm timer, when Storm occurred).
r55005.1 still showing as 55s for the engage-timer Storm, which was giving the above issue of the first Storm occurring with ~5s left on the timer.
FWIW, another raid member was running DBM and having accurate timing on the initial Storm. DBM's values are 49s for the engage-timer Storm, and 56s for the following Storms.
I'm still betting the true value is just 50s cooldown, that doesn't begin until the 5s channel is complete.
Nov 15, 2007Posted in: Raid AddOnsQuote from ManniAT »
I still have to select every raid member to if they ate correct buff-food
or simply "Nagrand Cherry" just to show up they ate something.
The purpose of BigBrother is to remind your raiders to buff, not to police them and punish. If you truly have a major problem with your raiders sabotaging buff checks:
Step 1) Tell all raiders to bring appropriate food.
Step 2) Check buffs manually once; anyone with 'lazy' food gets warning
Step 3) Check manually on next attempt; kick out anyone who does it again. They aren't interested in helping the raid, and shouldn't come.
Should be enough to avoid having to manually check the food buff for a while. ;)
Is it possible to show more detailed information on that tooltip or are there technical limitations that prevent this.
I'm unsure if the stats on the Well Fed buff are visible to an addon like BigBrother; it may only be designed for detecting the 'Well Fed' name of the buff. If that's the case, adding specific food detection might require a redesign, and would then be more trouble than it's worth.
Nov 15, 2007Akil'Zon timer for the initial Storm is off by about 5 seconds, for the cooldown (5s remaining on Storm timer, when Storm occurred).Posted in: Raid AddOns
I suspect it's related to the Storm being a 5-second channel, which is not accounted for by the timer. Looks like the storms following the first one are timed correctly for the cooldown, since the 5-second channel is rolled into the 55s cooldown that way.
On my client, I modified the initial timer from 55s (43s warning) to 50s (38s warning) and it seemed fairly accurate for the next attempt. So if you don't want to add an additional timer for the channeling period, then just fudging the initial cast timer is probably good enough.
Akil'Zon has a hard enrage as well, but I wasn't timing the fight to measure it (he died less than 5s after the hard enrage started, killing the non-topped tank with a ~12k regular hit and a DPS warrior with a 33k regular hit). I'd venture a guess at 10 minutes.
Timers for Nalorakk seemed spot on, as did the timers for Jan'Alai.
- To post a comment, please login or register a new account.