Authors CurseForge

Was using latest Bigwigs from wowinterface.com and firemaw timers were way off, saying a wing buffet was coming when it was actually 15seconds away, and it reset the wing buffet timer at the 15sec mark when a wing buffet happened. This problem happening to anyone else?

Quote from Aaron »

Was using latest Bigwigs from wowinterface.com and firemaw timers were way off, saying a wing buffet was coming when it was actually 15seconds away, and it reset the wing buffet timer at the 15sec mark when a wing buffet happened. This problem happening to anyone else?

We have noticed that our timers are way off this past week as well, in AQ40 and in BWL. I remember the Firemaw and Chromaggus ones being pretty far off, as well as the Twin Emperors. Sometimes there was a good 5-10 seconds after the Emperors' port warning before they actually ported, sometimes it was right on. I just attributed it to bad syncing or something.

Same problem, although only the 3 drakes seem affected. It is as if MULTIPLE timers are running, at the same time, affecting each other over the sync. :(

Quote from Aileen »

as well as the Twin Emperors. Sometimes there was a good 5-10 seconds after the Emperors' port warning before they actually ported, sometimes it was right on.

That's becuase there is a small random factor on the teleport timer.. Nothing we can do about that.

//Shyva

Feature request:
- Enable bossmod when maintank is targeting boss.

Why?
- Well I'm a priest, never ever targeting/mousing over an enemy. Well, only by exident. Thus I nearly ALLWAYS forget to turn on bigwigs... :<

Quote from Sirow »

Feature request:
- Enable bossmod when maintank is targeting boss.

Why?
- Well I'm a priest, never ever targeting/mousing over an enemy. Well, only by exident. Thus I nearly ALLWAYS forget to turn on bigwigs... :<

BigWigs already works this way, iff. your tanks also use the addon to sync with you. Convince more people in your raid group to start using BW and module activation will be a distinct non-issue.

Quote from Shyva »

That's becuase there is a small random factor on the teleport timer.. Nothing we can do about that.

Woops! Thanks, I didn't realize that one had some randomness. :)

Quote from Aileen »

Quote from Shyva »

That's becuase there is a small random factor on the teleport timer.. Nothing we can do about that.

Woops!  Thanks, I didn't realize that one had some randomness. :)

Maybe BigWigs could adopt some kind of naming convention for exact vs approximate timers? eg. prefix or postfix all guildline timers with "~" and no prefix for exact timers?

This naming convention could be applied to warning (text) messages also.. so Huhuran's Viper sting could be "Viper Sting in ~3 seconds" with the timer bar showing "~Viper Sting", as opposed to "Wing buffet in 3 seconds" with the timer bar showing simply "Wing Buffet"

Also, this weekend, I found Maexxna's timers to be very inaccurate after the first webspray, but it fixed itself after the second... it was about 10 seconds out on the cocoon/spider spawn messages.

I wholeheartedly support the use of '~' on all variable warnings.

OK - now I can confirm that the razuvious module seems to be seriously bugged (tested it 2 Weeks).

Some shouts simply aren't shown (no timers, no message). This is random and sometimes the shout-timers return.

Greetings

Timo

Please show me where it is stated that this is a "known bug". Someone said that there "isn't a bug" with the razuvious module (was that you?).

But nice to know that there is a bug with this module. so why didn't you confirm this earlier in this forum or on curse (if I oversaw the posting in which you told that this is a known bug I appologize for the "whining")? It would have saved you from many "whining" posts like mine...

I heard of a bug-tracking-system named "Flyspray". Can someone give me a link to it? Do only devs have access-rights to this stuff or can everyone post there. If this is free for everyone I'll post bugs there (and only there)in the future to avoid such postings like yours Ammo.

Sorry for stealing your time

Regards

Timo

Hmm never had any problems with the Razuvious Module here, never ever.
The only "negative" thing about it might be that a warlock has to have his VW outside to make the timers work, since it seems that the Shout isnt detectable if not atleast 1 mana users gets it (not sure though Oo but all addons need a mana user getting it atleast...) but iam no Warlock so.... who cares :P

Quote from HellknightFA »

I heard of a bug-tracking-system named "Flyspray". Can someone give me a link to it?

Sticky in the Ace2 Addons forum...
:: http://www.wowace.com/forums/index.php/topic,1793.0.html

Quick question, I'm sort of new to BigWigs and I've been using it in our most recent Razorgore attempts. The egg destroy warning are nice, but since there's only about three of us in the room with BigWigs installed it misses pretty much all of them unless we're on top of the eggs. We all increased the range to 200, but it doesn't seem to make any difference. I'm guessing it's more of a Blizzard problem that can't be fixed unless we get more people with BigWigs installed?

2 of my guildies are claiming that bigwigs is disconnecting them during the Maexxna encounter. They are running old versions (around revision 9400). Disabling bigwigs solves this problem for them.

this has only effected 2 people out of around 20 that use bigwigs (many of whom run around the same revision). So im guessing this is something to do with conflicing mods, but thought i'd mention it

Oo, no one was a druid and one was a warrior (who happened to be our MT at the time)