War Machine last hit - 7.3.5

Bug Report
Update: After more extensive testing, War Machine appears to be triggering properly in outdoor content, as long as the target is hit within <2s of death with direct damage.

I can confirm that it is also working on Antorus trash, Portal Keeper, Eonar, and Kin'garoth, but is not triggering properly on Antoran High Command or Mythic Varimathras (0% uptime).

The issue appears on M+ bosses which spawn adds (ex: Ymiron) as well.

Logs working

  • Heroic Portal Keeper:
    https://tinyurl.com/y9ktcwq7
    https://i.gyazo.com/85259618a48323917277a8c9f372087c.png


Logs not working

  • Heroic High Command:
    https://tinyurl.com/y88buwew
  • Mythic Varimathras:
    https://www.warcraftlogs.com/reports/9cVTQtAwk3WZrvdf#fight=last&type=auras&start=6942506&end=6954940&source=29
  • LFR High Command:
    https://www.warcraftlogs.com/reports/GTx2dVpBkzWKgtm7/#fight=last&type=auras&source=2
  • Tested in raid and in broken isles outdoors, can confirm only proccing on KB.

    :(
    OMEGALUL
    If this is intended I have no words.
    Apparently it refuses to proc on AHC and mythic Vari, so heres hoping its just a bug. But if the intention is to make the talent proc only on a killing blow, the talent is essentially dead.

    The first row of fury talents isn't very great to begin with. Fresh meat has absolutely no viability in a raid setting. Endless rage is just a default single target option. War machine is by far the most powerful talent in that row, if used in a situation where it can proc. Making it proc only on killing blows makes the talent almost unusable in a raid or group setting, where it can be extremely unlikely to land the killing blow on an add. The "grace period" on the talent proccing was fairly short to begin with, so you couldnt get away with just pressing whirlwind and then ignoring the add.

    If this change is intentional, we are essentially pigeonholed into endless rage, making the only dps talent that will be moved around being avatar/wrecking ball. This does not diversify gameplay, which was something the devs spoke about pre-legion. This change would do the exact opposite.

    I implore blizzard to either A. Fix this bug (if it is a bug) as war machine is a powerful and very important talent for fury in aoe, or B. Not make war machine proc on the killing blow, as it essentially kills the talent in any group content.
    I hope Blizzard will revert this idiotic change; will there even be a choice in first row of talents if WM will remain with KB condition?
    Lord, tell me this is a bug...
    hope its a bug, because that talent is dead if that was an intentional change. also why change that talent so late into the expansion
    silent nerfs xd
    kek
    ok
    Prob just a bug, I´d imagine a nerf like this would go on patch notes if it was intentional.

    OMEGALUL if it is intentional.
    Victory rush is also not proc'ing off KBs outside of world content. so i am assuming this is a bug
    Just wanted to re-iterate the issue, it looks like the only fight that this talent doesn't work properly on Heroic mode is AHC. Log from my kill today about an hour and a half ago, the only time it procced was on the boss death itself: https://www.warcraftlogs.com/reports/qkbH2zDRpJyQYcjX#fight=9&type=auras&source=6

    Logs from the fights it did work on:
    Eonar: https://www.warcraftlogs.com/reports/qkbH2zDRpJyQYcjX#fight=11&type=auras&source=6
    Portal Keeper: https://www.warcraftlogs.com/reports/qkbH2zDRpJyQYcjX#fight=12&type=auras&source=6

    Maybe it has to do with the type of mobs that are being killed, or the level of them (not sure if they actually differ on the fights)?
    01/17/2018 04:05 AMPosted by Warheró
    Victory rush is also not proc'ing off KBs outside of world content. so i am assuming this is a bug


    I had a Victory Rush proc off a cannon on Garothi Worldbreaker LFR today.
    Confirmed
    Why no acknowledgement of this bug from blizzard after 24 hours? seems like it would be an easy fix, is it possible this was an intended change?
    01/17/2018 08:00 PMPosted by Zerum
    Why no acknowledgement of this bug from blizzard after 24 hours? seems like it would be an easy fix, is it possible this was an intended change?


    Calm your persecution complex bro
    01/17/2018 08:19 PMPosted by Shimmerr
    01/17/2018 08:00 PMPosted by Zerum
    Why no acknowledgement of this bug from blizzard after 24 hours? seems like it would be an easy fix, is it possible this was an intended change?


    Calm your persecution complex bro


    Is that not a valid question to ask? There are tons of posts and talk about this, blizzard has to be aware and they have acknowledged every other problem with this patch except this one.
    It's only happening on a select few fights and wasn't a listed change. What would lead you to believe it's intentional

    Join the Conversation

    Return to Forum