Do we have any ETA about some bug fixes?

[Overtime]

Here's a combat log of ironfoe from level 60 official WoW, you can see the comment is from 2006.
3rd comment on the highest rated commenter

Runawaynow on 2006/10/03 (Patch 1.12.1)
http://img519.imageshack.us/img519/351/ ... g12909.png

source http://www.wowhead.com

That Combat log isn't from Vanilla wow. First off, the numbers are way too high and secondly, in the bottom SS he gets a proc from water shield which is from TBC.

Probably from 2.0, pre-launch patch for few months. Because proc rate was nerfed for level 70s.

[Dessel]

Here's a combat log of ironfoe from level 60 official WoW, you can see the comment is from 2006.
3rd comment on the highest rated commenter

Runawaynow on 2006/10/03 (Patch 1.12.1)
http://img519.imageshack.us/img519/351/ ... g12909.png

source http://www.wowhead.com

That Combat log isn't from Vanilla wow. First off, the numbers are way too high and secondly, in the bottom SS he gets a proc from water shield which is from TBC.

The SS is from tbc, where Ironfoe worked similarly to vanilla.

The question is what the core problem is.
- Heroic strike and slam?
- Ironfoe and hoj?

Seeing as this is a warrior exclusive problem at the moment, it should be heroic and slam being the sinners, preventing item procs.

Worth to note here is that heroic strike runs the animations of both hoj and Ironfoe procs, but nothing happends as a result of it, no hits or damage.

[Ektelion]

Here's a combat log of ironfoe from level 60 official WoW, you can see the comment is from 2006.
3rd comment on the highest rated commenter

Runawaynow on 2006/10/03 (Patch 1.12.1)
http://img519.imageshack.us/img519/351/ ... g12909.png

source http://www.wowhead.com

That Combat log isn't from Vanilla wow. First off, the numbers are way too high and secondly, in the bottom SS he gets a proc from water shield which is from TBC.

The SS is from tbc, where Ironfoe worked exactly the same as vanilla.

The question is what the core problem is.
- Heroic strike ,Cleave and slam?
- Ironfoe and hoj and sword spec and windfury?

Seeing as this is a warrior exclusive problem at the moment, it should be claeve/heroic and slam being the sinners, preventing item procs.

Worth to note here is that heroic strike runs the animations of both hoj and Ironfoe procs, but nothing happends as a result of it, no hits or damage.

I wanted to add Cleave on your reply since its a next melee attack aswell thus affecting hand of justice sword specialization and every other instant melee ability/proc

There's no doubt people been using Ironfoe during many TBC encounters on execute phases that's to be mentioned, thus the weapon looks like its working properly at the current state, next melee attacks don't let it release its full potential

[Moodeus]

This problem increasingly impacts warrior dps, as gear gets better warriors should have the rage to heroic strike more often thus this bug is more and more noticeable. I believe specials are also causing HoJ and Ironfoe not to proc.

http://report.nostalrius.org/plugins/tracker/?aid=994

This bug's status is confirmed. Do you need anymore information from the community to help resolve this issue or is i just a matter of a Dev getting some time to work on it? I have a HoJ/Ironfoe and would be happy to help test if its required.

[Dessel]

I would also volounteer to spend time helping a dev with these issues. Core class mechanics not working properly are so noticeable, compared to other bugs.

[Slicy]

Sweeping strikes and blade furry do the same damage as the attack that triggers them but I think sweeping strikes only does execute damage to the second target if it is also below 20% (It's in the patch notes somewhere).

I'm pretty sure any "Extra attack" mechanic simply resets your swing timer immediately after the attack that triggers it and in the case of ironfoe, it resets it twice.

"Extra attack" is not the same as "Attacks hit an additional nearby target".

Just correcting false informations and bumping another bug. The statement in bold is completely wrong. It's not working like a pale copy of the damage dealt by attacks on the initial target. The "cleave damage" is supposed to be mitigated by additional target's armor (post 1.10, which is the fixed version).
Blade Flurry is completely bugged and this seems to apply to Sweeping Strikes as well.

In the current patch, the damage dealt to the additional target should completely ignore mitigation, both from the initial target and the cleaved target.
Later on, Blizzard fixed this : Patch 1.10.0 (28-Mar-2006): The additional attacks generated by this ability will now properly take into account the armor of the second target.
At the moment and since this server launched, Blade Flurry damage dealt to the additional target is mitigated by both the initial and the additional targets' armor, instead of just being mitigated by the armor of the additional target.

This bug has been reported since a few months on the tracker @ http://report.nostalrius.org/plugins/tracker/?aid=723

[Dessel]

There are several instances of essentially the same type of bugs reported on bugtracker for months now. Not even one of them have even been assigned. This seem familiar from other projects, where many core class fixes just floated in a vacuum and remain unfixed for months and years. Judging by the bugtracker, there are essentially no bugs being fixed outside of unreleased content, so I think it's safe to assume we're just going to have to live with the current class bugs for any foreseeable future.

[Ektelion]

Mistake reply, didn't mean to leave it here

[Everen21822]

Warlock Affliction tree has a lot of broken talents atm.

[Pottu]

There are several instances of essentially the same type of bugs reported on bugtracker for months now. Not even one of them have even been assigned. This seem familiar from other projects, where many core class fixes just floated in a vacuum and remain unfixed for months and years. Judging by the bugtracker, there are essentially no bugs being fixed outside of unreleased content, so I think it's safe to assume we're just going to have to live with the current class bugs for any foreseeable future.

The WF totem and HS proc bug has been fixed. I am locking this thread for now.