I've been using this addon for awhile now and I have to say I love it. Posting the quick link in raid causes everyone to immediately get their consumables on. The fact that it also tracks CC breaking is an added bonus. I must say thanks for working on this and keep up the good work!
The Misdirection alerts seem a bit buggy. If I cast Misdirection on my pet I get a single line for myself and 1 for my pet which is what I expect to see, but when I cast it on someone in a raid I usually get multiple lines for that person and multiple lines for myself.
Hey Cryect and Treibh, great mod. I use it and it does almost everything I need it to.
One feature which would be GREATLY appreciated would be for us to choose where mod output is placed. Currently, it can only go to the chatbox but I'd love it to be in SCT, raid warning, a popup, etc. like some other mods do.
Hey Cryect and Treibh, great mod. I use it and it does almost everything I need it to.
One feature which would be GREATLY appreciated would be for us to choose where mod output is placed. Currently, it can only go to the chatbox but I'd love it to be in SCT, raid warning, a popup, etc. like some other mods do.
Thanks a lot!
I wanted to suggest this as well, only thing I could possibly miss in this addon would be the ability to output polymorph breaks to /ra or other channels.
I added the ability to output misdirect/poly/shackle to raid, party, officer or guild. Hopefully that should be enough options - if someone would really like it somewhere else let me know. Thanks to my guild who put up with a lot of chat spam on Kael trash while I tested these changes
I'm not sure what the problem with misdirection is and why it seems to report the target multiple times sometimes. I'll try and look in to that more.
I added the ability to output misdirect/poly/shackle to raid, party, officer or guild. Hopefully that should be enough options - if someone would really like it somewhere else let me know. Thanks to my guild who put up with a lot of chat spam on Kael trash while I tested these changes
I'm not sure what the problem with misdirection is and why it seems to report the target multiple times sometimes. I'll try and look in to that more.
needs an option to... "output to chat channel" too! See alot spam as is in raid chat, having it set to like "ccbreaker" channel or something so people want to see it can be better.
also... I noticed the report range for any broken sheep was like... 30-36y? is there a way to get big brother to catch sheep/shackle breaks from like 100-200y away?
I like the sheep breaking messages to raid a lot. Misdirection reports would be nice too.
Also, any chance to add /rw as a target instead of just raid?
It mentions MD's alot (mentioned above if enabled it does multiple MD notices sometimes)
and... having it as a raid warning in like Kara or something 10 man be nice but... when I was in BT, and hunters multi shooting, tanks grabbing next mob, or blade flurry or warrior whirlwind... it was spamming 2 liner "so and so broke sheep with ???" and they wanted me to turn it off ;/
(Hell I think people did it jsut to see the message >.> )
If you could make a seperate channel that people that want to see it can see it, would be nice.
Yeah, the MDs don't usually happen often enough to be a spam issue. And for the sheep breaking, I turn off the warning for Kael'thas trash where we're constantly spamming it. In normal situations, anyone breaking sheep gets bitched out, so they don't do it just for fun.
NECB lets you keep track of when CC will break and abilities of your friends and foes so you can see that the warrior has shield wall on CD or more importantly how much longer the ice trap or banish will last. So I call out on TS or vent how much longer to party members so it's not a surprise which helps a lot in confusion and wipes.
I added the ability to output misdirect/poly/shackle to raid, party, officer or guild. Hopefully that should be enough options - if someone would really like it somewhere else let me know. Thanks to my guild who put up with a lot of chat spam on Kael trash while I tested these changes
As I mentioned elsewhere, this has been awesome sauce.
It'd be kinda cool if I could have Misdirect reporting to me and CC breaks reporting to the raid, since the raid reasonably doesn't care about Misdirects whereas I, as a tank and RL, certainly do. But it's not a make or break feature by any means.
I like Big Brother a lot and use it religiously. However I've been modifying it beyond it's original function to notify me of additional buffs besides Misdirection (Bloodlusts, Shield Walls, BoPs, etc.), but it's something of a pain to stay updated with the current version and keep up with my edits.
I was wondering if it might be feasible to add functionality to let the user add buffs they'd like to be notified of within the addon, rather than writing them into the mod itself. The more I use BB the more buffs I've started adding just to keep track of what's happening in the raid and what I need to be aware of, and I've love to see this sort of addition to BB.
I was wondering if it might be feasible to add functionality to let the user add buffs they'd like to be notified of within the addon, rather than writing them into the mod itself. The more I use BB the more buffs I've started adding just to keep track of what's happening in the raid and what I need to be aware of, and I've love to see this sort of addition to BB.
I like this idea.
Right now the configuration is still done via the ACE options menu, but I think the the mod is slowly outgrowing that mode of configuration. If I allow the user to specify the buff they'd like tracked and where they'd like the notification sent then it is going to require a more complex configuration.
I was wondering if there was a way to change the misdirect text into a single line. So instead of "Misdirect on Hunter" and "Misdirect on Target" it should be "Misdirect from Hunter on Target".
I guess it'd involve looking at the class getting the misdirect buff and some kind of table storing misdirection information for the last 2-3 minutes only. Then you should be able to generate above combined line, based on the fact that first MD will always come from a hunter and only once from a hunter every 2 minutes. This should eliminate multiple MD lines from the same hunter as well.
The only scenarios where it might not work is where you got multiple hunters popping MD, but only one of them actually uses it. E.g. if Hunter1 pops MD first, then Hunter2 pops it at well, but only Hunter1 uses it on a tank. And of course if a hunter uses MD on another hunter, but I've yet to see that needed other than on our Vashj strider kiter.
I did look at the code and I realized that I'm not solid enough with Lua to do it myself yet.
I guess it'd involve looking at the class getting the misdirect buff and some kind of table storing misdirection information for the last 2-3 minutes only. Then you should be able to generate above combined line, based on the fact that first MD will always come from a hunter and only once from a hunter every 2 minutes. This should eliminate multiple MD lines from the same hunter as well.
Yes, I'm looking at something like that as well as trying to figure out why ACE is generating duplicate events. It seems to mostly happen in raids ... when I test misdirects alone with a hunter in our guild it seems to be much better behaved.
Yes, I'm looking at something like that as well as trying to figure out why ACE is generating duplicate events. It seems to mostly happen in raids ... when I test misdirects alone with a hunter in our guild it seems to be much better behaved.
It's because both the hunter and the target gets the exact same buff, the solution (if any) is to search for something like "X casts Misdirect on Y", but I'm not sure that event is even in the combat log - most likely all you get is "X gains Misdirect", hence the current output.
It's because both the hunter and the target gets the exact same buff, the solution (if any) is to search for something like "X casts Misdirect on Y", but I'm not sure that event is even in the combat log - most likely all you get is "X gains Misdirect", hence the current output.
You could probably fix that by checking whether one of the mentioned names is a hunter, the only flaw would be if you were to misdirect to a hunter, but I don't think that happens particularly often.
You could probably fix that by checking whether one of the mentioned names is a hunter, the only flaw would be if you were to misdirect to a hunter, but I don't think that happens particularly often.
True, but on the other hand - I like to know which hunter did the misdirect, so while it's spammy at the moment, it tells me what I need to know.
Yes, I'm looking at something like that as well as trying to figure out why ACE is generating duplicate events. It seems to mostly happen in raids ... when I test misdirects alone with a hunter in our guild it seems to be much better behaved.
Yup, we get that very often, I believe it's because of how misdirection works. The hunter gets the misdirection buff on him twice in a row, due to a server side script being triggered. In a non-raid situation this seems to happen so fast that a second event never gets generated, but in a raid where there's a lot of other stuff going on, it sometimes slips past the clients internal "spam" filter for messages.
Anyways it should be easy to fix with a short timed duplicate check, say no misdirection spam if it's already been output once on that player within the last 5 seconds or so.
I'll probably fool around with the single line misdirect patch once my hunter hits level 70 (level 69 at the moment).
True, but on the other hand - I like to know which hunter did the misdirect, so while it's spammy at the moment, it tells me what I need to know.
That's true. It could also be done that it actually keeps track of both names and doesn't report until it's got a "linked" misdirect, but that's going to get too complicated I think especially if you consider having to add in failsafes in case only one misdirect buff message goes through for some reason.
Don't hack code if you don't have to. The current state is not "broken" per say, and might just require a few extra eyes on the combat log to tweak it.
Sidenote: Sheep spam on Kael'thas trash is way more annoying than the occasional Misdirect
Don't hack code if you don't have to. The current state is not "broken" per say, and might just require a few extra eyes on the combat log to tweak it.
I wasn't going to SVN it, I don't even have an account for the wowace SVN.
It'd only be a manually applied patch for myself (and others interested), at least until it's stable enough for release. And of course only if the authors wants it.
I quickly grepped a few hundred megabytes of raid combatlogs and I couldn't find any duplicate events, so it doesn't seem like there's being generated a second event. Digging further though the code it looks like it's the SpecialEvents-Aura-2.0 library that generates the double event for some reason. I don't know enough about that library to say that's the one for sure, but it seems like it recognizes the buff as a new one incorrectly the second time.
I've been experimenting with this for the last few days, and I really like it, but I can't say as much for the people who are getting spammed with MD/CC messages (I have the output directed to officer channel). I'd like to be able to automatically disable the reporting outside of raids (enabling only for boss fights would be fantastic!), because I invariably forget to do it until people get spammed.
For CC-Breaking you can also use the Addon CCBreaker.
The addon provides a list of all CC-breaks since the beginning of the raid or since the last reset.
It´s an ACE addon and available here: http://files.wowace.com/CCBreaker/CC...r-r53397.8.zip