Roar/Silence warning for Nalorakk would be lovely if it hasn't been added or is possible, it seemed to be static. I can probably give timers on my next run, I'll just have to enable everything.
Akil'Zon timer for the initial Storm is off by about 5 seconds, for the cooldown (5s remaining on Storm timer, when Storm occurred).
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.
I had a timer running and we hit it twice, spot on 10' from engage.
2% and 1% attempts hehe.
He wipes the raid at that point... normal hits of 13k on me and 20k on the offtank, basically runs around one-shotting everyone :)
Will be very hard to hit the 10min mark for most, so probably won't be noticed
but it's there.
Enrage added
Quote 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).
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.
Enrage added
Quote from lumparoo »
the storm timers for the eagle boss are a little off (3 secs by my count)
I just ran him today and the timers seemed fine, if you are constantly getting them earlier than the timer run transcriptor and post a log.
Quote from Aprilhelmina »
Roar/Silence warning for Nalorakk would be lovely if it hasn't been added or is possible, it seemed to be static. I can probably give timers on my next run, I'll just have to enable everything.
I did him tonight and as far as I saw he only ever roared once, not sure what you want timed.
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.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorKeep Transcriptor logs to pms please.
Interface\AddOns\BigWigs\ZulAman\Malacrass.lua:87: 'then' expected near ')'
It no werky atm.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorFixed! :)
---
I have this Bug on German Client!
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorShould be fixed
http://ace.pastey.net/75403
I wrote a PM yesterday to funkydude, but apparently he's not in or busy. Maybe someone else can add it, if he has time.
Thanks for your great work on BigWigs.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorAdded, thanks
I'm not sure I understand you, do you mean he has 2 yells(triggers)?
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorI just checked 2 logs, and I can assure you there is only 1 trigger for spirit bolts.
Oh, I see. thx.
It's a cooldown ability. It's not meant to be exact.
-Ammo
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.
I had a timer running and we hit it twice, spot on 10' from engage.
2% and 1% attempts hehe.
He wipes the raid at that point... normal hits of 13k on me and 20k on the offtank, basically runs around one-shotting everyone :)
Will be very hard to hit the 10min mark for most, so probably won't be noticed
but it's there.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorEnrage added
Enrage added
I just ran him today and the timers seemed fine, if you are constantly getting them earlier than the timer run transcriptor and post a log.
I did him tonight and as far as I saw he only ever roared once, not sure what you want timed.
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.
can integrat a box for boss Akil'zon which shows players who are to nearly at you self.
like gruul modul
and the start timer of storm i think ist to long. the message "storm next" comes earleyer as the timerbar ends