Okay, so in situations like Ossirian and Chromaggus, is there a reason BigWigs waits for people to do specific types of spell damage to determine the weaknesses instead of picking it up from the emotes? Ossirian definitely has an emote, Chromaggus I can't remember but I assume is the same way.
afaik both bosses do like Chrommy - just emote about his skin shrimmers (spelling?) and resistance changed. There is no information about weakness. As for Ossi - maybe BW just scans for debuffs on him, dunno
afaik both bosses do like Chrommy - just emote about his skin shrimmers (spelling?) and resistance changed. There is no information about weakness. As for Ossi - maybe BW just scans for debuffs on him, dunno
Well I know Ossi actually emotes the new weakness, you can see it with WitchHunt or SpellAlert (or just looking at the Combat Log) but the actual weakness doesn't get announced until it's he's hit by a spell of the school he's weak to.
Hmmm - I really like BigWigs but in the recent builds there where introduced some real nasty bugs (tested in a raid with 20 people who installed BW):
1. Naxxramas - Razuvious: Shout isn't shown always - sometimes there are phases where the shout-timer isn't shown. Is this a sync-problem? There was a time where the razuvious-mod was doing it's task flawlessly.
2. C'Thun: In earlier builds there where shown raid-icons on the person who got the green beam. There where also icons on a group who got the dark glare. Both isn't the case in the current bw-builds (have to test it with 107xx because ther seemed to be some changes in the C'Thun-Module). Also the dark glare isn't shown everytime (only the first 2-3 times then never again). Same to the group warnings. Early Versions of BW2 didn't have those problems.
3. Chromaggus: Breath timers aren't shown everytime (it's random). Since the creators of bw say they hadn't such problems I think this could be a sync-problem between english and german clients (some people use english, some use german clients including the MT). Sometimes I get German (!!!) local bw-messages like: Chromaggus is casting "Ätzende Säure" etc.
My question is why simply do not leave the modules which do there task flawlessly alone (C'Thun or Razuvious for example). How do you change an existing module? Do you rewrite the complete code or do you take the newest module and modify/add some code there? Due to the introduced bugs (look at the "Module "Großwitwe Faerlina" not found" Problem with german/english clients which was introduced again and again before this localisation-sync was fixed) I would say you rewrite the complete code.
I hope you fix those problems (some of my guild mates want to switch to LaVandetta BossMods if those bugs remain :( ).
afaik both bosses do like Chrommy - just emote about his skin shrimmers (spelling?) and resistance changed. There is no information about weakness. As for Ossi - maybe BW just scans for debuffs on him, dunno
Well I know Ossi actually emotes the new weakness, you can see it with WitchHunt or SpellAlert (or just looking at the Combat Log) but the actual weakness doesn't get announced until it's he's hit by a spell of the school he's weak to.
Unless I'm just totally nuts.
Ossirian does not emote the next vulnerability. What you are seeing is an activated crystal getting a specific debuff-ability. Yes, this is essentially the same, but does not mean that debuff is going to hit Ossirian, thus not a reliable source. And yes, Ossirians debuffs are being scanned.
3. Chromaggus: Breath timers aren't shown everytime (it's random). Since the creators of bw say they hadn't such problems I think this could be a sync-problem between english and german clients (some people use english, some use german clients including the MT). Sometimes I get German (!!!) local bw-messages like: Chromaggus is casting "Ätzende Säure" etc.
Hi guys! Hunters in my guild are asking is there any way to play different sound when boss does FENZY? They say that they like BW, but CTRA's different sound for this ability helps alot!
I got ownership of BigWigs on wowinterface last night, I will update today.
Thanks! I personally update daily from svn.wowace.com and usually don't encounter problems, and when I do I come here and bitch. :P Unfortunately, my guildies don't have that kind of patience and like to stick with the stable releases on WoWi, and they've been complaining that often the releases on WoWi cause all kinds of nasty errors with other Ace2 mods released there.
I just noticed this when looking at my ace addons list. It seams with the modular system BigWigs uses ACE thinks each boss or feature is a seperate addon? Well I guess technically it is, but is there someone to condense the list?
I just noticed this when looking at my ace addons list. It seams with the modular system BigWigs uses ACE thinks each boss or feature is a seperate addon? Well I guess technically it is, but is there someone to condense the list?
I reported that some time ago too, got told that it needs changes in ace2 if I remember correctly. Right now the /ace2 list ace2 listing is useless for me, chatbuffer is to small allready for the full listing :(
edit: maybe some kind of filtering would be good... "/ace2 list ace2 a e" would list all ace2 addosn from A to E ... or "/ace2 list ace2 raid" would list all raid ace2 addons - but thats not a bigwigs thingy ;-)
I got ownership of BigWigs on wowinterface last night, I will update today.
Thanks! I personally update daily from svn.wowace.com and usually don't encounter problems, and when I do I come here and bitch. :P Unfortunately, my guildies don't have that kind of patience and like to stick with the stable releases on WoWi, and they've been complaining that often the releases on WoWi cause all kinds of nasty errors with other Ace2 mods released there.
I'd like to see BigWigs come with BossBlock not enabled by default. I've slowly been getting everyone to convert to BigWigs, but I have had to explain to literally each person that converts how to disable the BossBlock plugin. This has also lead to a number of these new users assuming that because they are not seeing RaidWarnings they need to turn on the RaidAnnounce portion of the addon. In turn, this has lead to a lot of spam on Bosses for the non-BigWig users.
Again, these are all user errors. Although, I do think that if BossBlock was not enabled by default, most problems of this type would not be encountered.
BossBlock is meant to be on by default, why do they want to see raidwarn messages? That's duplicate spam there...
Because they're nubs, honestly. Had to just start removing raid promotions in Naxx last night to reduce the raid chat spam during bosses. I don't get how half of the people can't find their BigWigs button (it must be under another minimap button for some users or something, stop using Titan Panel you fools!). Anyways, this stuff isn't the developer's fault, I've just found that a number of end users are pretty dumb.
I leave BossBlock off except for blocking the RaidWarning frame so that I can make sure RaidAnnounce is being done by someone. If I see that it isn't, I quickly turn my announce on. How about that instead? BossBlock on except for the RaidWarning frame in middle of the screen blocking.
If not, no big deal. I made a whisper macro explaining things for the smacktards who can't figure out how to use BigWigs.
The C'thun dark glare timers seems to disappear after the first timing(s) and doesn't come back. In the Ace-version it works I believe.
Had this happened today too.
RL was reporting every dark glare (he's using the wowinterface version) but he had some issue so i had to annouce instead and realise i only reported dark glare on the first time then no more.
I leave BossBlock off except for blocking the RaidWarning frame so that I can make sure RaidAnnounce is being done by someone. If I see that it isn't, I quickly turn my announce on. How about that instead? BossBlock on except for the RaidWarning frame in middle of the screen blocking.
Actually, I've been thinking about it lately... everyone keeps wanting some sort of means to verify that raidwarns are being sent for the "peons" to see... so maybe we need some sort of solution here?
How bout we add a detector to the raidwarn module... it'd add info into the fubar tooltip that shows what members are sending raidwarns if it detects any, and have an optional user-side alert to let you know if noone is sending any warnings during a boss fight. Something simple, like say we schedule a "no announcers" warning in 5 seconds every time a local message is shown. Whenever someone sends a raidwarn they also send a comm sync indicating that they're announcing. If you get one of these syncs the timer is cancelled... at least for the current boss fight.
1. Naxxramas - Razuvious: Shout isn't shown always - sometimes there are phases where the shout-timer isn't shown. Is this a sync-problem? There was a time where the razuvious-mod was doing it's task flawlessly.
I and a couple other people in our raid noticed this one last night as well. It just... stopped running or something. No more warnings, no more candybars. After 2-3 rounds of shouts wondering what happened, I clicked on the minimap button to reset running modules and all was well again for the rest of the fight.
I don't get how half of the people can't find their BigWigs button (it must be under another minimap button for some users or something, stop using Titan Panel you fools!).
Hehe I just converted a bunch of our officers to BigWigs recently and had 2 of them ask me how to find their minimap button. I guess it must have been behind another button or something like you said, I told them to try doing /bigwigs minimapAttach because I thought they literally meant the button disappeared but they said that every time they typed that it just kept saying "Off"... I use FuBar so I have no clue what they are actually seeing. :) I'll have to let them know to look behind their other buttons... I didn't think of that last night. :)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
afaik both bosses do like Chrommy - just emote about his skin shrimmers (spelling?) and resistance changed. There is no information about weakness. As for Ossi - maybe BW just scans for debuffs on him, dunno
Well I know Ossi actually emotes the new weakness, you can see it with WitchHunt or SpellAlert (or just looking at the Combat Log) but the actual weakness doesn't get announced until it's he's hit by a spell of the school he's weak to.
Unless I'm just totally nuts.
1. Naxxramas - Razuvious: Shout isn't shown always - sometimes there are phases where the shout-timer isn't shown. Is this a sync-problem? There was a time where the razuvious-mod was doing it's task flawlessly.
2. C'Thun: In earlier builds there where shown raid-icons on the person who got the green beam. There where also icons on a group who got the dark glare. Both isn't the case in the current bw-builds (have to test it with 107xx because ther seemed to be some changes in the C'Thun-Module). Also the dark glare isn't shown everytime (only the first 2-3 times then never again). Same to the group warnings. Early Versions of BW2 didn't have those problems.
3. Chromaggus: Breath timers aren't shown everytime (it's random). Since the creators of bw say they hadn't such problems I think this could be a sync-problem between english and german clients (some people use english, some use german clients including the MT). Sometimes I get German (!!!) local bw-messages like: Chromaggus is casting "Ätzende Säure" etc.
My question is why simply do not leave the modules which do there task flawlessly alone (C'Thun or Razuvious for example). How do you change an existing module? Do you rewrite the complete code or do you take the newest module and modify/add some code there? Due to the introduced bugs (look at the "Module "Großwitwe Faerlina" not found" Problem with german/english clients which was introduced again and again before this localisation-sync was fixed) I would say you rewrite the complete code.
I hope you fix those problems (some of my guild mates want to switch to LaVandetta BossMods if those bugs remain :( ).
Greetings
Timo
Ossirian does not emote the next vulnerability. What you are seeing is an activated crystal getting a specific debuff-ability. Yes, this is essentially the same, but does not mean that debuff is going to hit Ossirian, thus not a reliable source. And yes, Ossirians debuffs are being scanned.
I reported this 8 pages earlier
:: http://www.wowace.com/forums/index.php/topic,1762.msg38366.html#msg38366
Got no reply to it, and wasn't at chromaguss for a while now, thought it got fixed maybe. Seems like it's still bugged.
-Ammo
Thanks! I personally update daily from svn.wowace.com and usually don't encounter problems, and when I do I come here and bitch. :P Unfortunately, my guildies don't have that kind of patience and like to stick with the stable releases on WoWi, and they've been complaining that often the releases on WoWi cause all kinds of nasty errors with other Ace2 mods released there.
I just noticed this when looking at my ace addons list. It seams with the modular system BigWigs uses ACE thinks each boss or feature is a seperate addon? Well I guess technically it is, but is there someone to condense the list?
Attached screenshot of /ace list ace2
I reported that some time ago too, got told that it needs changes in ace2 if I remember correctly. Right now the /ace2 list ace2 listing is useless for me, chatbuffer is to small allready for the full listing :(
edit: maybe some kind of filtering would be good... "/ace2 list ace2 a e" would list all ace2 addosn from A to E ... or "/ace2 list ace2 raid" would list all raid ace2 addons - but thats not a bigwigs thingy ;-)
It's updated.
-Ammo
I'd like to see BigWigs come with BossBlock not enabled by default. I've slowly been getting everyone to convert to BigWigs, but I have had to explain to literally each person that converts how to disable the BossBlock plugin. This has also lead to a number of these new users assuming that because they are not seeing RaidWarnings they need to turn on the RaidAnnounce portion of the addon. In turn, this has lead to a lot of spam on Bosses for the non-BigWig users.
Again, these are all user errors. Although, I do think that if BossBlock was not enabled by default, most problems of this type would not be encountered.
Thank you for the great tool, guys.
Because they're nubs, honestly. Had to just start removing raid promotions in Naxx last night to reduce the raid chat spam during bosses. I don't get how half of the people can't find their BigWigs button (it must be under another minimap button for some users or something, stop using Titan Panel you fools!). Anyways, this stuff isn't the developer's fault, I've just found that a number of end users are pretty dumb.
I leave BossBlock off except for blocking the RaidWarning frame so that I can make sure RaidAnnounce is being done by someone. If I see that it isn't, I quickly turn my announce on. How about that instead? BossBlock on except for the RaidWarning frame in middle of the screen blocking.
If not, no big deal. I made a whisper macro explaining things for the smacktards who can't figure out how to use BigWigs.
Had this happened today too.
RL was reporting every dark glare (he's using the wowinterface version) but he had some issue so i had to annouce instead and realise i only reported dark glare on the first time then no more.
Actually, I've been thinking about it lately... everyone keeps wanting some sort of means to verify that raidwarns are being sent for the "peons" to see... so maybe we need some sort of solution here?
How bout we add a detector to the raidwarn module... it'd add info into the fubar tooltip that shows what members are sending raidwarns if it detects any, and have an optional user-side alert to let you know if noone is sending any warnings during a boss fight. Something simple, like say we schedule a "no announcers" warning in 5 seconds every time a local message is shown. Whenever someone sends a raidwarn they also send a comm sync indicating that they're announcing. If you get one of these syncs the timer is cancelled... at least for the current boss fight.
I and a couple other people in our raid noticed this one last night as well. It just... stopped running or something. No more warnings, no more candybars. After 2-3 rounds of shouts wondering what happened, I clicked on the minimap button to reset running modules and all was well again for the rest of the fight.
Hehe I just converted a bunch of our officers to BigWigs recently and had 2 of them ask me how to find their minimap button. I guess it must have been behind another button or something like you said, I told them to try doing /bigwigs minimapAttach because I thought they literally meant the button disappeared but they said that every time they typed that it just kept saying "Off"... I use FuBar so I have no clue what they are actually seeing. :) I'll have to let them know to look behind their other buttons... I didn't think of that last night. :)