Authors CurseForge

Woohooo. Thanks for the info.
I play on a single-core Athlon 3000, I am happy for every tiny bit of CPU time saved. ^_^

Quote from Shadoweric

So, the new Big Wigs looks good. A lot of work went into it and it shows.


I do have one request (unless I missed the option): I would like to enable raid warnings from other people's boss mods. They appear to be blocked and there's no option I can see to change that. Other boss mods sometimes have other info to give.

What other info do you need that BigWigs does not provide?

-Ammo

Addon seems great so far. Only issue I've ran into so far is Shadowstrike timers. One, they don't seem to reset when the related mobs die, but I'm not sure if this is fixable. Secondly, when they appear seems to be sporadic. For example, the timers don't show up on the first 2 set of adds, but after we go through a phase 2 on Anub H, they reappear. It's really odd. The only thing I've come up with to explain this is that the timer on shadowstrike doesn't seem to reset upon a wipe, so depending on the timing of the wipe, the timer is still there when you zone back in and throws the mod off.

Quote from toin7

Addon seems great so far. Only issue I've ran into so far is Shadowstrike timers. One, they don't seem to reset when the related mobs die, but I'm not sure if this is fixable. Secondly, when they appear seems to be sporadic. For example, the timers don't show up on the first 2 set of adds, but after we go through a phase 2 on Anub H, they reappear. It's really odd. The only thing I've come up with to explain this is that the timer on shadowstrike doesn't seem to reset upon a wipe, so depending on the timing of the wipe, the timer is still there when you zone back in and throws the mod off.

These timers were added in (or most certainly adjusted) a day or 2 before release. They also contained an error which might be your problem. Next release (or the current alphas) should fix these issues.

I have noticed since I started using BigWigs 3, starting with the alpha's that I no longer see MT death warnings from Ora2, is BigWigs somehow blocking these?

Quote from Mikari

I have noticed since I started using BigWigs 3, starting with the alpha's that I no longer see MT death warnings from Ora2, is BigWigs somehow blocking these?

Should be unrelated.

-Ammo

Quote from Ammo

Should be unrelated.

-Ammo

No idea what's causing it then, I have notify death's enabled, just never see the text telling me a tank has died, hear the sound though.

it sends the message to bw2.0 indeed. though cookies.

now only the scaling for the messages and I'm happy. :) i hope^^

cu cardo_

The Onyxia Deep Breath Blizzard-replacement warnings are currently unreliable. They only show up a portion of the time.

BigWigs (BW) r6536 (updated from r5890-5-release version with clean saved variables), BigWigs_Azeroth r206 (the Onyxia module being used is now integrated in BW), LibSink-2.0 r67, MikScrollingBattleText (MSBT) v5.4.66, USEnglish client/server, WoW 3.2.2.10505 live. Have BW set up with "Blizzard Warnings" unchecked (turned off). Which means that BW is supposed to provide its own replacement warnings through the LibSink output (in my case, I set it to MSBT/Notification/Sticky).

Join an Onyxia 25-man raid. Make it to Phase 2. First Deep Breath, no problem. The BW version of the screen alert came without issue. So it did on the second Deep Breath. But after the first two, further Deep Breath screen warnings during that fight never appeared, either the BW ones or the Blizzard ones. They only showed up in the chat frame.

Join a second Onyxia 25-man raid later that day on a different character with the same settings as above. Now on the first Flame Breath, the BW screen warnings never appeared at all, as they continued not to do throughout the fight. They still appeared in the chat frame properly, but never the screen. After the raid wiped in phase 2, came back and made sure that the BW option was set properly. Yes, "Blizzard Warnings" was still unchecked.

This time, I checkmarked it (turned them on). The second try of the fight in Phase 2, the Blizzard screen warning for Deep Breath showed up when it was supposed to all the time (as well as in the chat frame). So BW replacement screen warnings are apparently unreliable currently, at least for that boss.

And...no raid warning alerts in 5-man parties.

BigWigs r6542, LittleWigs r642, BigWigs_CommonAuras r146. Have the option for Broadcast checkmarked; not Raid Channel, though. In heroic Drak'Tharon_Keep with the boss modules for it looking like they are properly activated throughout in the LDB display. Also for CommonAuras, have every alert checkmarked (as default). Was not the leader in the party.

No boss raid warning alerts were broadcast at any time throughout the instance. As well, put up Guardian Spirit (verified for sure) and no broadcast for it either. No personal chat output/alerts either for boss deaths or abilities.

If you are Broadcasting your own messages are bossblocked. So you won't see your broadcasts. They do work however. Ask a teammate without bigwigs if they saw em :p

-Ammo

Quote from Ammo

If you are Broadcasting your own messages are bossblocked. So you won't see your broadcasts. They do work however. Ask a teammate without bigwigs if they saw em :p

-Ammo

Ugh, sorry to hear. It kills LittleWigs functionality for own-use and makes raid broadcasting substantially less useful than it use to be. There are raid leads who actually like seeing the raid warnings. Why not make bossblocking optional (at least for your own broadcasts)?

That wasn't the only problem, however. Boss deaths and other boss alerts provided by LittleWigs were not output anywhere (besides broadcasting) during the runs.

Quote from Zidomo

Ugh, sorry to hear. It kills LittleWigs functionality for own-use and makes raid broadcasting substantially less useful than it use to be. There are raid leads who actually like seeing the raid warnings. Why not make bossblocking optional (at least for your own broadcasts)?

That wasn't the only problem, however. Boss deaths and other boss alerts provided by LittleWigs were not output anywhere (besides broadcasting) during the runs.

I used to think like you aswell, but i've really gotten used to the self-output option of bigwigs in chatframe1. Besides, bigwigs warnings can be redirected to raid warning anyway, so having both BW warnings and the broadcast there will just make it a bit spammy.

Quote from cremor

Isn't it possible to disable the shaking (without showing nameplates all the time) but leave the flashing enabled any more?

I too would like to see this as an option.

Quote from Skylinee

I used to think like you aswell, but i've really gotten used to the self-output option of bigwigs in chatframe1. Besides, bigwigs warnings can be redirected to raid warning anyway, so having both BW warnings and the broadcast there will just make it a bit spammy.

Then don't redirect self-alerts to raid warning if you prefer less spam. If you prefer self-alerts in some other output (scrolling text, etc.), being forced to redirect them to raid warning to simulate the option that used to be there isn't good at all.

Sure, people can get "get used" to anything. But why? Why not just make the bossblock on broadcasts optional? Or remove the broadcast bossblock completely and instead have the broadcast on-off toggle the only option?

Zidomo, you're talking poo. Excuse the term.

1. You want stuff in your raidwarning frame? -> set the output to raidwarning
2. You want to broadcast -> turn on broadcasting
3. You want to see stuff in chatframe -> turn on configre -> message -> chatframe

And you're done.

-Ammo

P.S. Just because you're vocal on the forums and the bigwigs thread doesn't make you get a say in what gets in bigwigs or not. We do listen to suggestions, but either you give good argumentation with a proper explanation or your voice is simply ignored.

Quote from Ammo

Zidomo, you're talking poo. Excuse the term.

1. You want stuff in your raidwarning frame? -> set the output to raidwarning
2. You want to broadcast -> turn on broadcasting
3. You want to see stuff in chatframe -> turn on configre -> message -> chatframe

And you're done.

-Ammo

P.S. Just because you're vocal on the forums and the bigwigs thread doesn't make you get a say in what gets in bigwigs or not. We do listen to suggestions, but either you give good argumentation with a proper explanation or your voice is simply ignored.

Of course I don't have a say. Its just a shame that I and guild mates (and others, I'm sure) will most likely have to move to some other boss mod(s) after years of satisfaction with BigWigs.

None of the three points quoted above have any bearing on what I'm suggesting. I'm suggesting to be able to to see both broadcasted raidwarnings as well as output directed to a sink that is different from raidwarning (and/or the optional chatframe output per Configure/Messages) at the same time. As has been the case with BigWigs for years until the transition to Ace3.

As it is now, that is not possible; there is only a choice of a single sink output (as well as the chatframe). There is not currently a choice for seeing broadcasted raidwarnings as they are automatically bossblocked for some reason, as per your first reply. For those that don't want to see the broadcasts they put out, either disable them or optionally (not mandatory) bossblock them. What in this suggestion can I make less poo-like?