So had something happen in MC last night that I can’t really explain, curious if anyone knows what actually happened? I can’t say I’ve ever looked into Golemagg logs deeply to see if this is has happened before.
Edit: This wasn’t parry haste, parry haste won’t make a double swing happen, like that.
Relevant events: 00:00:05.619 Jaxson casts Shield Block 00:00:05.619 Golemagg the Incinerator swings at Mayatau 00:00:05.619 Golemagg the Incinerator swings at Mayatau 00:00:05.664 Jaxson is afflicted by Weakened Soul from Elvenessense 00:00:05.668 Golemagg the Incinerator Melee Mayatau *3617* 00:00:05.669 Golemagg the Incinerator Melee Mayatau 398 (O: 1587)
Link to logs: https://classic.warcraftlogs.com/reports/r1fqhmRMTdt9vKNC/#fight=50&type=summary&view=events&source=2
Not concerned with the death or anything, just the double swing.
00:00:05.008 Mayatau Heroic Strike Golemagg the Incinerator Parry
Batching sucks, with latency that probably started right as he was swinging and then two swings got batched. Parry haste is up to 40% faster swing, you literally probably just got the worst luck in the world and the boss perfectly parry hasted you.
It’s just a normal thing in classic. You gotta deal with it. If it makes you feel any better, in TBC the same mechanic exists, only they hit 3 times instead of 2.
The only thing to help deal with it is to tell your other melee to stop standing in front of the boss. They likely aren’t, but, yeah.
That’s what I blamed it on in the moment too, but looking back it was something else.
Yeah, I know what thrash is, but that wasn’t thrash. And in classis thrash is +2 additional attacks, so things hit 3 times with it too or when thrash bug happens and it stacks, an odd number of times (3, 5, 7) .
Again, not parry haste. And parry haste has nothing to do w/ thrash.
Afaik, even HoJ and Windfury push the extra attack behind 1 batch. Though I have heard conflicting reports on that and have not combed logs to confirm or deny.
This is most likely a simple spell batch plus parry haste combo, nothing more. If you look at the steady swings hitting Lucina from 40 seconds onward, you can find 0.8 sec differences between swings with no Parry on Golemagg occurring. The only reason I can think of why this sudden burst of haste can occur is that either (a) bosses like Golemagg have some obnoxious variable swing timer or (b) some other mechanic on Golemagg resets his swing timer or hastens him in some way. The longest swing Golemagg has is 2 seconds, but he frequently gets in 1.6, 1.2, and 0.8 swings and these don’t always have Parries near them at all.
I don’t know exactly how batching groups or when the threshold is but given the double queued melee, the parry haste came late enough to trigger an reset of the swing timer (as it is supposed to do if you’re in the last 40% of the swing), but queued the event with the next batch and the natural swing finished and proc’d the hasted hit as well.
This isn’t something I’ve messed with too much because I just haven’t crawled logs looking for oddball behavior like this, but I’ll look into it more.
I guess thats possible? I checked the video and the logs definitely show an accurate recreation of what happened with the double swing atleast, I auto-splatted.
Yeah I’ll look at it. Your log is a good one because the boss doesn’t move much and no one debuffed the boss with anything like Thunderfury or Thunderclap, so I’ll see if I can make sense of the numbers.
