- Registered User
Member for 11 years, 4 months, and 24 days
Last active Fri, Oct, 4 2013 14:32:22
- 0 Followers
- 13 Total Posts
- 0 Thanks
Dec 22, 2008Would there be any possibility of fixing the way extra attacks are tracked by this addon? Currently the addon assumes that the attack immediately following the combat log "You gain X extra attacks through Sword Specialization" entry. Below is my post detailing the way the combat log actually reports extra attacks:Posted in: General AddOns
I have retested this functionality periodically since that time (including as recently as last week) and it still works this way. I'm a little bit tired of rogues popping up every other week to tell me that Sword Spec has been changed because Recount told them so; it'd be fantastic if this could be fixed.
May 18, 2008Posted in: General AddOnsQuote from Elsia »
How do you know that's true? Why can't line 1 be the proccing attack, and line 3 be the proc? Even if line one is not the proc attack how do you know that 3 and 4 related to procer and procee in the way you describe it and not the other way around?
I coded this based on windfury procs and my combat logs show heroic strike windfury procs to have the following order:
1) Heroic strike (causes the proc)
2) Gain windfury attack
3) Heroic strike
All white damage attacks have the same pattern, i.e. that you see a white attack, the proc, and a next attack at the same time stamp.
I didn't study sword spec procs in detail (but did take a look if it matched the pattern and it did). I am so far assuming that all proc mechanisms are the same internally as the combat log doesn't distinguish between abilities themselves. If you have a proof that this assumption isn't valid I'd love to see it.
A final word about this is that I'm unaware that blizz has ever stated that combat log order/sequences are stable/guaranteed. I personally treat everything that Recount does that requires watching multiple combat log events as inherently heuristic (though a lot of it turns out to work well in practice), not only because we don't know if sequences are stable, but also because we don't know if you will always see the full sequence.
I know it's true because I have studied sword spec procs pretty extensively for rogue mechanics and the result is always as I described it. It's feasible that the Heroic Strike version is different, but the particular reason I can tell that it functions this way for sword spec is that I have a main hand fist (can't proc sword spec) and an off hand sword (can proc sword spec). I verified it yesterday in testing that the "You gain 1 extra attack" message was preceded by a main hand hit (damage range was too high to be an off hand hit) and followed by an off hand hit, which was then followed by a main hand hit.
This behavior has been pretty consistent across all of my testing, so I'm not sure why yours would be different other than the idea that perhaps Heroic Strike itself is unique.
(edit) Here are some links that support the interpretation I've given:
May 17, 2008There is currently a mistake in the way Recount counts damage of extra attacks. The way the combat log reports an extra attack is like so:Posted in: General AddOns
Line 1) Vulajin's melee swing hits Some Mob for XXX. (unrelated melee swing)
Line 2) Vulajin gains 1 extra attacks through Sword Specialization.
Line 3) Vulajin's melee swing hits Some Mob for XXX. (swing that caused the proc)
Line 4) Vulajin's melee swing hits Somb Mob for XXX. (sword spec swing)
Currently, Recount assumes that the swing on line 3, the one immediately following the proc announcement, is the sword spec extra attack. Instead, the swing that causes the proc always immediately follows the proc announcement, and then the extra attack comes next.
This isn't a particularly high priority thing to fix, as Recount still counts the total damage correctly (as far as I can tell), but it would be helpful for accuracy in analyzing my damage after a fight.
Dec 16, 2006Posted in: General AddOnsQuote from Phanx »
Quote from mahiro »
with teh original ui its possible to remove the weapon buffs with a rightclick on them.
Are you sure? I've never been able to remove a weapon buff with a right-click.
As for the problem you're having with weapon buffs, it sounds like something Blizzard needs to fix with regards to letting you choose which weapon the buff casts on. I couldn't say for sure though... I'm resto, so no dual-wielding here. :P
It's new in 2.0, weapon buffs can be removed by right-clicking them. Buffalo doesn't allow this functionality at the moment, but I would assume (hopefully not incorrectly) that it would be easy enough to implement.
Dec 16, 2006For some reason, this addon simply does not work for me. I can bring up the Spellbinder window and set up keybindings for the macros I've written, but when I press those keybindings, nothing happens. I've also tried running with no addons and simply using /script SetBindingMacro() to set the same things up, and that never works either, so I can't imagine that it's a taint problem holding me back here. I've tried the same thing with spells, using both Spellbinder and SetBindingSpell() manually, and it just doesn't work. Any ideas?Posted in: General AddOns
Dec 14, 2006I fixed up KombatStats for WoW 2.0. I just need to get a hold of the original author and see if it's alright for me to release it on his behalf...Posted in: Addon Ideas
(edit) Rophy informs me that he's already posted a fixed version on WoWInterface.com. Looks like his changes pretty much match mine, which makes me all giddy about being right. ;-)
Dec 12, 2006_ForgeUser1186848 posted a message on ag_UnitFrames - suggestions, requests and temp fixes threadPosted in: Unit FramesQuote from Ariarra »
I just installed ag_UnitFrames today, along with the latest versions of oRA2 and sRaidFrames (although sRaidFrames was disabled since I was on my rogue and didnt really need them). While raiding with my guild I had an annoying problem where whenever I clicked on the MT windows I got an error that ag_UnitFrames had tried to access part of the Blizzard UI and did I want to disable or ignore. It also would not pick up the target. I thought perhaps it is more likely to be a oRA2 problem and just misreported by Blizzard, but figured I should post it here as well.
This is because oRA's main tank frames still use TargetUnit() to target the main tanks when you click on them, which is now prohibited by Blizzard. I'm not sure why the problem reports as being caused by ag_UnitFrames, but I can tell you for a fact that ag is not at fault for that one.
Oct 4, 2006Please, somebody Ace this abomination. It's a good idea, a useful mod, a ridiculously helpful resource for small and large guilds alike, but it's also a monstrosity, it gobbles up megabytes of memory every few minutes, and it just generally makes me want to cry. Please tell me someone is working on this.Posted in: Addon Ideas
- To post a comment, please login or register a new account.