Thanks for the reply - I wasn't far off it turns out.
In case you're interested, the macro I ended up with was the following:
#showtooltip Last Stand
/use Offering of Sacrifice
/cast Last Stand
/run s,d,e = GetSpellCooldown("Last Stand") if s == 0 then b = BigWigs:GetModule("Custom Bars") b:TriggerEvent("BigWigs_SendSync", "BWCustomBar 20 Last Stand!") end
hi guys, seems i have an odd issue since wotlk release. no more raid warning spam. and this happens to littlewigs too.
i did try some configs, bossblock, raidwarning broadcast is cheched and uncheckable (grey). played around with ora2 too, but no way, no spam, even if i'm leader :(
BW Common Auras is updated however the current rev has not been taged as release or beta, so it still stuck on the previous tag & that is for the 3.0 patch as wrath was released.
If some one could tag it that'd be great..
I would be willing to keep it maintained / updated as needed, I'd need to be added as a project author.. People round here get twitchie if non-authors tag stuff
Umm, I don't think you really want to send that as a sync?
Pretend ( ;-) ) I'm a complete noob to this stuff and elaborate why not? I wrote it this way so as to emulate as closely as possible the /bwcb slashcommand. But I'm not a lua developer - just a programmer trying to hack something in place with a minimal knowledge of the basics. The macro seemed to perform correctly on tonight's raid. Is there a technical reason that it is wrong?
That will only show it to people with BW_CA installed (as I understand it). My intention was to push the bar out to anyone with vanilla BW installed through the existing custom bar functionality.
That will only show it to people with BW_CA installed (as I understand it). My intention was to push the bar out to anyone with vanilla BW installed through the existing custom bar functionality.
Your original post made it sound like you just wanted a bar for yourself, not for the entire raid, which is what sending it as a sync message will do.
That said, though, you should be aware that not everyone in your raid wants or even needs to see a bar for your Last Stand. Rogues and warlocks, for instance, don't need to see that, since there's nothing they should or even can do about it. Healers may already have their own way to see when you have Last Stand up. And pretty much everyone already has enough information on their screen as it is, without you adding to it with bars for things they probably don't care about.
I'd suggest you just ask your raiders who need or want to see your Last Stand to install BigWigs_CommonAuras, which allows them to configure which things they actually want to see, instead of forcibly spamming them with extra screen clutter.
Personally, if I ever had a tank in my raid start spamming me with Last Stand bars like you're doing, I would immediately write an addon to block his spam and send annoying messages to raid chat and whispers to him every time he did it. :mad:
hehe, phanx when ever you say things like that i get the idea to write an addon called "Subscribed Spam". Setup class modules for it for the minor CD's in the game.. Realistically only useful to interupt classes for only a select few encounters.
Your original post made it sound like you just wanted a bar for yourself, not for the entire raid, which is what sending it as a sync message will do.
Ah - I thought I had made it clear when I originally posted quoting the /bwcb command that this is what I was intending to emulate. I know others have used this macro command for this purpose, but for myself I was attempting to do it in such a way that I didn't fire spurious bars should I accidentally hit the macro while LS was on cooldown.
As for whether or not it is desirable, I tend to raid within a fixed set of people, most of whom have been in favour of the bar; many of them are reluctant (I'd hate to use the word "fearful"...) about installing addons beyond the "mandated" few our guild prescribe. I tend to be RL and MT, so I like to let everyone know when I hit the panic buttons.
As an additional note, since quoting the macro above (and before reading your reply), I did add an "if 1==1" clause to the bar code to enable me to quickly and easily disable the synch should anyone object. I'll run with it for a while and see how people go.
And to be perfectly honest, I would probably have just given up (partly for the reasons you gave), but once I had the idea, I hated to abandon it simply due to failure; I'm a typical geek in that I needed to solve the problem more than I needed the solution ;-)
Problem with bw_common-aura is a lot of the timers aren't correct, bug out or don't exist.
BWCA doesn't sync, it isn't needed. This means only 1 person in the raid can have it to see everyone's cooldowns.
Also the code is so simple I'm having a hard time imagining how it could "bug out or be incorrect". Could you please point me to the problem in question?
BW Common Auras is updated however the current rev has not been taged as release or beta, so it still stuck on the previous tag & that is for the 3.0 patch as wrath was released.
If some one could tag it that'd be great..
I would be willing to keep it maintained / updated as needed, I'd need to be added as a project author.. People round here get twitchie if non-authors tag stuff
PM what the problem is (or diffs if you prefer) on IRC. I'll test and tag the latest.
Now available at Curse
BigWigs_CommonAuras v3.1.0:
-Fixed portals so it works and added new mage portals
-Added new repair bot
-Added Guardian Spirit duration, bar removes if a fatal blow is received
-Added Hand of Sacrifice duration
-Tried to add the repair Mammoth but currently blizzard has no events for this, commented out.
hi guys, seems i have an odd issue since wotlk release. no more raid warning spam. and this happens to littlewigs too.
i did try some configs, bossblock, raidwarning broadcast is cheched and uncheckable (grey). played around with ora2 too, but no way, no spam, even if i'm leader :(
I suggest you remove BigWigs completely & the BigWigs saved variables so that all the settings are default (do this out of wow). Install BigWigs, log in, enable and only tick "Broadcast". It should work.
Just got 2 of these upon entering Eye of Eternity (latest version of bigwigs):
[19:45:59] This seems to be an older version of Big Wigs. It is recommended that you upgrade before entering into combat with a boss.
Could this be because the ingame version gets reported as 4964, while the one on projects is 4983?
It's simply because someone in the raid has a 10+ revisions higher BigWigs than you do. You should only get that message once per session though, I'll look into that.
Thanks for the reply - I wasn't far off it turns out.
In case you're interested, the macro I ended up with was the following:
Thanks again, and all the best,
Bob.
http://www.wowace.com/projects/big-wigs_common-auras/
i did try some configs, bossblock, raidwarning broadcast is cheched and uncheckable (grey). played around with ora2 too, but no way, no spam, even if i'm leader :(
any suggestion?
RaidCoolDowns and rcd_display work fine (although they appear to be no longer updated either).
If some one could tag it that'd be great..
I would be willing to keep it maintained / updated as needed, I'd need to be added as a project author.. People round here get twitchie if non-authors tag stuff
Pretend ( ;-) ) I'm a complete noob to this stuff and elaborate why not? I wrote it this way so as to emulate as closely as possible the /bwcb slashcommand. But I'm not a lua developer - just a programmer trying to hack something in place with a minimal knowledge of the basics. The macro seemed to perform correctly on tonight's raid. Is there a technical reason that it is wrong?
That will only show it to people with BW_CA installed (as I understand it). My intention was to push the bar out to anyone with vanilla BW installed through the existing custom bar functionality.
Thanks again,
Bob.
Your original post made it sound like you just wanted a bar for yourself, not for the entire raid, which is what sending it as a sync message will do.
That said, though, you should be aware that not everyone in your raid wants or even needs to see a bar for your Last Stand. Rogues and warlocks, for instance, don't need to see that, since there's nothing they should or even can do about it. Healers may already have their own way to see when you have Last Stand up. And pretty much everyone already has enough information on their screen as it is, without you adding to it with bars for things they probably don't care about.
I'd suggest you just ask your raiders who need or want to see your Last Stand to install BigWigs_CommonAuras, which allows them to configure which things they actually want to see, instead of forcibly spamming them with extra screen clutter.
Personally, if I ever had a tank in my raid start spamming me with Last Stand bars like you're doing, I would immediately write an addon to block his spam and send annoying messages to raid chat and whispers to him every time he did it. :mad:
Ah - I thought I had made it clear when I originally posted quoting the /bwcb command that this is what I was intending to emulate. I know others have used this macro command for this purpose, but for myself I was attempting to do it in such a way that I didn't fire spurious bars should I accidentally hit the macro while LS was on cooldown.
As for whether or not it is desirable, I tend to raid within a fixed set of people, most of whom have been in favour of the bar; many of them are reluctant (I'd hate to use the word "fearful"...) about installing addons beyond the "mandated" few our guild prescribe. I tend to be RL and MT, so I like to let everyone know when I hit the panic buttons.
As an additional note, since quoting the macro above (and before reading your reply), I did add an "if 1==1" clause to the bar code to enable me to quickly and easily disable the synch should anyone object. I'll run with it for a while and see how people go.
And to be perfectly honest, I would probably have just given up (partly for the reasons you gave), but once I had the idea, I hated to abandon it simply due to failure; I'm a typical geek in that I needed to solve the problem more than I needed the solution ;-)
Thanks again,
Bob.
BWCA doesn't sync, it isn't needed. This means only 1 person in the raid can have it to see everyone's cooldowns.
Also the code is so simple I'm having a hard time imagining how it could "bug out or be incorrect". Could you please point me to the problem in question?
PM what the problem is (or diffs if you prefer) on IRC. I'll test and tag the latest.
BigWigs_CommonAuras v3.1.0:
-Fixed portals so it works and added new mage portals
-Added new repair bot
-Added Guardian Spirit duration, bar removes if a fatal blow is received
-Added Hand of Sacrifice duration
-Tried to add the repair Mammoth but currently blizzard has no events for this, commented out.
lol seems i'm the only one with that issue
I suggest you remove BigWigs completely & the BigWigs saved variables so that all the settings are default (do this out of wow). Install BigWigs, log in, enable and only tick "Broadcast". It should work.
[19:45:59] This seems to be an older version of Big Wigs. It is recommended that you upgrade before entering into combat with a boss.
Could this be because the ingame version gets reported as 4964, while the one on projects is 4983?
It's simply because someone in the raid has a 10+ revisions higher BigWigs than you do. You should only get that message once per session though, I'll look into that.