Just did Sartharion again, the latest version (4899 currently) still does not have working timers for Tsunami beyond the first one.
Rolled back to Sartharion.lua of version 4866, worked fine.
OK, thanks for the test. Someone unknown did a semi-"rollback" in the subsequent r4900, but it wasn't really a full rollback. The only thing changed was
tsunami_trigger = "The lava surrounding Sartharion churns!",
back to
tsunami_trigger = "The lava surrounding %s churns!",
and similar for French & German.
But the above change won't affect it working or not; the revisions that broke it already contained the r4900 string.
So I've now fully rolled back the trunk revision to the working r4866 code in r4901. Hopefully there will be no more issues like this in the future.
Okay, is there anyway we can get a raid icon added to Kel's frost blast? I could really careless as a healer who gets mana detonate, but i need to know quick who is in the iceblocks to heal them through it.
There is a problem with the Anub'rekhan swarm timer. After the first swarm the timer starts to gradually be off by 10,15,etc,etc seconds. It has been like this for a bit (running latest commit as of yesterday the 13th)
In Anub'Rekhan's case it is indeed just a cooldown timer. I don't think it's possible to predict when exactly it's going to happen.
I remember it being like this at level 60, too.
My guild has serious issues with people missing the Malygos focusing. It appears bigwigs doesnt' warn for this at all.
Am I missing it? This event is significant enough to warrant a flask and shake IMHO.
While Bigwigs should probably DO flash and shake the screen, I really fail to understand how anyone can miss the huge "Malygos is focusing on you" text across the middle of the screen that is displayed by the default Blizzard UI.
as far as Anub is concerned... DBM seems to have it nailed. I have to have it on just for that fight because the timer on it is actually on the spot, which makes it annoying because then I have to disable it after that fight :/, I like my BW
While Bigwigs should probably DO flash and shake the screen, I really fail to understand how anyone can miss the huge "Malygos is focusing on you" text across the middle of the screen that is displayed by the default Blizzard UI.
this isn't displayed across the default UI for me or several other people in our raid, after asking about it last night after reading your post. The only indicator I get is a tiny yellow line in my chat log where emotes go.
So you are saying the default UI does this? What could possibly be blocking it then?
10-man Grand Widow Faerlina does not have a 60 sec timer for if her frenzy is interrupted via the death of one of her friends. It only has the silence. My guess is that this is because they do not actually cast the suicide thing like 25 man. They instead have to be killed.
What is the Silence timer for anyway? I've never gotten silenced, or had anyone else in my raid mention getting silenced, in either 10-man or 25-man raids. ???
What is the Silence timer for anyway? I've never gotten silenced, or had anyone else in my raid mention getting silenced, in either 10-man or 25-man raids. ???
Sacrificing a worshipper silences Faerlina for 30 seconds.
What is the Silence timer for anyway? I've never gotten silenced, or had anyone else in my raid mention getting silenced, in either 10-man or 25-man raids. ???
Killing (10) or Sacrificing (25) an add near her silences her, therefore preventing enrage.
Killing (10) or Sacrificing (25) an add near her while she is enrage dispells this enrage.
10-man Grand Widow Faerlina does not have a 60 sec timer for if her frenzy is interrupted via the death of one of her friends. It only has the silence. My guess is that this is because they do not actually cast the suicide thing like 25 man. They instead have to be killed.
That is fixed r4886 and later. You have to download the latest Alpha, there hasn't been a Beta or Release for a long time.
Btw:
@Devs
Wouldn't it be good to tag a Beta/Release again? People using the version from Curse are using a quite old version now. Especially for deDE the current Curse version is quite buggy.
That is fixed r4886 and later. You have to download the latest Alpha, there hasn't been a Beta or Release for a long time.
Btw:
@Devs
Wouldn't it be good to tag a Beta/Release again? People using the version from Curse are using a quite old version now. Especially for deDE the current Curse version is quite buggy.
That explains it. I have the latest beta version. I'll get an alpha one, unless a new beta is coming soon.
Btw:
@Devs
Wouldn't it be good to tag a Beta/Release again? People using the version from Curse are using a quite old version now. Especially for deDE the current Curse version is quite buggy.
I almost though bigwigs is dead till I went over and checked that there are still alpha builds being released ;)
As far as I am concerned, Bigwigs is an abandoned project with no commits from the authors since October/November, nor any posts from them. Most of my guild has switched to DBM now. Inaccurate timers, wrong triggers, off-sync warnings, triggers that only trigger once, etc.
While many of these have been fixed, the fixes were from... localizers. Those alphas you see... aren't official fixes, but band aids. Heck, some of the fixes don't even work.
Likewise, Transcriptor, the logging utility that Bigwigs relies on for logging data isn't updated either, and affects the usefulness of all submitted boss logs.
There is also no proper support for different difficulty modes (some bosses are different in 10/25 modes) with different spellIDs being used in each difficulty, and updates conflict each other with boss triggers not working in one mode and only in the other.
Think of it like FuBar or Cartographer, Bigwigs is on life support.
OK, thanks for the test. Someone unknown did a semi-"rollback" in the subsequent r4900, but it wasn't really a full rollback. The only thing changed was
back to
and similar for French & German.
But the above change won't affect it working or not; the revisions that broke it already contained the r4900 string.
So I've now fully rolled back the trunk revision to the working r4866 code in r4901. Hopefully there will be no more issues like this in the future.
Any help is appreciated.
Maybe its just a cooldown and you cant announce it exactly
I remember it being like this at level 60, too.
Am I missing it? This event is significant enough to warrant a flask and shake IMHO.
While Bigwigs should probably DO flash and shake the screen, I really fail to understand how anyone can miss the huge "Malygos is focusing on you" text across the middle of the screen that is displayed by the default Blizzard UI.
this isn't displayed across the default UI for me or several other people in our raid, after asking about it last night after reading your post. The only indicator I get is a tiny yellow line in my chat log where emotes go.
So you are saying the default UI does this? What could possibly be blocking it then?
just a guess, maybe it's something else
Sacrificing a worshipper silences Faerlina for 30 seconds.
Killing (10) or Sacrificing (25) an add near her silences her, therefore preventing enrage.
Killing (10) or Sacrificing (25) an add near her while she is enrage dispells this enrage.
That's what I understand, could be wrong.
That is fixed r4886 and later. You have to download the latest Alpha, there hasn't been a Beta or Release for a long time.
Btw:
@Devs
Wouldn't it be good to tag a Beta/Release again? People using the version from Curse are using a quite old version now. Especially for deDE the current Curse version is quite buggy.
That explains it. I have the latest beta version. I'll get an alpha one, unless a new beta is coming soon.
As far as I am concerned, Bigwigs is an abandoned project with no commits from the authors since October/November, nor any posts from them. Most of my guild has switched to DBM now. Inaccurate timers, wrong triggers, off-sync warnings, triggers that only trigger once, etc.
While many of these have been fixed, the fixes were from... localizers. Those alphas you see... aren't official fixes, but band aids. Heck, some of the fixes don't even work.
Likewise, Transcriptor, the logging utility that Bigwigs relies on for logging data isn't updated either, and affects the usefulness of all submitted boss logs.
There is also no proper support for different difficulty modes (some bosses are different in 10/25 modes) with different spellIDs being used in each difficulty, and updates conflict each other with boss triggers not working in one mode and only in the other.
Think of it like FuBar or Cartographer, Bigwigs is on life support.
I don't wanna switch to DBM... :(