Machinist feels pretty good now.

[Eorzean_username]

Machinist changes were a band-aid on a severed limb.

Yes, you can get 5 shots of Heat Blast off now, even if you live in Antarctica.

However, if you need the 5-stack system to fit 5 Heat Blasts in, then you will almost-certainly still clip your GCD if you try to weave during those 1.5s GCDs.

Therefore, this design still places high-ping MCH in a situation where the clipping caused to avoid overcapping Gauss/Rico charges will drift and derange your rotation over time, as well as necessarily push potency outside of the buff windows by which Jobs live-or-die now.

Are the 6.30 changes an improvement? Yes, in the same way that being fed a diet of 100% raisins is technically an improvement over being fed a diet of 100% chunks of concrete.

Is MCH now in an actually healthy state? No, I do not think MCH is there yet. But I am sympathetic that right now, MCH players must feel euphoric to have received any sort of positive attention at all from their neglectful and unstable parent. And, admittedly, for players who already had adequate latency to play MCH, the 6.30 changes are just a straight-up and fairly chunky performance buff — which is certainly nothing to scoff at.

However, I feel pretty strongly that the overall "band-aid" here has fundamentally failed to both understand, and to actually address, the most fundamental issues affecting MCH design, and so I think "Daily reminder that Flamethrower is bad" and "Surprise, I miss Turrets" — while both perfectly-cromulent personal opinions — seems lower on the priority list than, "Maybe this game should not force people to weave during 1.5s GCDs, all factors considered"... and so on.

[Seraphor]

Machinist changes were a band-aid on a severed limb.

Yes, you can get 5 shots of Heat Blast off now, even if you live in Antarctica.

However, if you need the 5-stack system to fit 5 Heat Blasts in, then you will almost-certainly still clip your GCD if you try to weave during those 1.5s GCDs.

Therefore, this design still places high-ping MCH in a situation where the clipping caused to avoid overcapping Gauss/Rico charges will drift and derange your rotation over time, as well as necessarily push potency outside of the buff windows by which Jobs live-or-die now.

Are the 6.30 changes an improvement? Yes, in the same way that being fed a diet of 100% raisins is technically an improvement over being fed a diet of 100% chunks of concrete.

Is MCH now in an actually healthy state? No, I do not think MCH is there yet. But I am sympathetic that right now, MCH players must feel euphoric to have received any sort of positive attention at all from their neglectful and unstable parent. And, admittedly, for players who already had adequate latency to play MCH, the 6.30 changes are just a straight-up and fairly chunky performance buff — which is certainly nothing to scoff at.

However, I feel pretty strongly that the overall "band-aid" here has fundamentally failed to both understand, and to actually address, the most fundamental issues affecting MCH design, and so I think "Daily reminder that Flamethrower is bad" and "Surprise, I miss Turrets" — while both perfectly-cromulent personal opinions — seems lower on the priority list than, "Maybe this game should not force people to weave during 1.5s GCDs, all factors considered"... and so on.

So it's fine as long as you don't live in Antarctica?
Weaving in 1.5s windows has never been a problem for me, and my ping isn't amazing.

[Shurrikhan]

So it's fine as long as you don't live in Antarctica?
Weaving in 1.5s windows has never been a problem for me, and my ping isn't amazing.

We're trying to fit two .5s animation periods, each with an additional uptime cost of roundtrip ping, right? So, we'd just need to be under 250 ms roundtrip ping, or what the game would call 125 ms, I'd imagine.

Perhaps that should be a bit lower than 125ms, for safety, if there's any need to account for time between the query's actual start and that of the server query check.

But... honestly, seems like there are a fair few of us who'd still fall above that.

The game quite simply shouldn't charge us twice our ping's worth of potential uptime after each animation. Once I could understand, but there's no reason for the game to then reset the animation timer on server confirmation of the action.


EDIT (for clarity):

Heat Blast itself, as with any other action, has a minimum period in which no other actions can be cast for a fixed length of 0.5s seconds plus whatever your roundtrip ping is (because you start the 0.5s animation lock timer and then it is reset when the server sends back confirmation of that action). From there, Gauss/Ricochet takes up another fixed mutually exclusive period of 0.5s, plus whatever your roundtrip ping is. That is still a "single weave."

A 1.5s GCD does not give you 1.5s of "GCD gap". It gives you, at 0 ping, exactly 1.0 second of "GCD gap". To double-weave in 1.5s, one would have to have literally 0 ping. To single-weave in 1.5s, one would have to have <250 ms roundtrip ping (what most games would show as <125 ms).

But many XIV players have pings exceeding 125 ms and will therefore lose uptime. That is a problem that would be easily solved if the game just didn't reset that minimum animation period upon server confirmation, in which case every animation time would be just 0.5s instead of 0.5s+roundtrip_ping.

[Seraphor]

We're trying to fit two .5s animation periods, each with an additional uptime cost of roundtrip ping, right? So, we'd just need to be under 300 ms roundtrip ping, or what the game would call 150 ms, I'd imagine.

Perhaps that should be a bit lower than 150ms, for safety, if there's any need to account for time between the query's actual start and that of the server query check.

But... honestly, seems like there are a fair few of us who'd still fall above that.

The game quite simply shouldn't charge us twice our ping's worth of potential uptime after each animation. Once I could understand, but there's no reason for the game to then reset the animation timer on server confirmation of the action.

Two? No, you don't need to double-weave Ricochet and Gauss in each 1.5s window. If you've depleted at least 2 charges of each already, you can just alternate them.
Double-weave during your regular 2.5s skills sure, to get those charges out of the way before you go into Hypercharge.

[Shurrikhan]

Two? No, you don't need to double-weave Ricochet and Gauss in each 1.5s window. If you've depleted at least 2 charges of each already, you can just alternate them.
Double-weave during your regular 2.5s skills sure, to get those charges out of the way before you go into Hypercharge.

The GCD itself has an animation lock. If it were a double-weave, there'd be 3, which means you'd need literally 0 ping to do so within the 1.5s seconds.

Heat Blast GCD - Heat Blast ICD - GB/Rico ICD =
1.5 - (0.5s + RT_Ping) - (0.5s + RT_Ping) =
0.5s - 2xRT_Ping

You can support at most a roundtrip ping of 250 ms.

[Zomkei]

We're trying to fit two .5s animation periods, each with an additional uptime cost of roundtrip ping, right? So, we'd just need to be under 300 ms roundtrip ping, or what the game would call 150 ms, I'd imagine.

Perhaps that should be a bit lower than 150ms, for safety, if there's any need to account for time between the query's actual start and that of the server query check.

But... honestly, seems like there are a fair few of us who'd still fall above that.

The game quite simply shouldn't charge us twice our ping's worth of potential uptime after each animation. Once I could understand, but there's no reason for the game to then reset the animation timer on server confirmation of the action.

The GCD itself has an animation lock. If it were a double-weave, there'd be 3, which means you'd need literally 0 ping to do so within the 1.5s seconds.

i'm very confused by these statements. you're saying you're double weaving ricochet and gauss between your heat blasts? because if so, that's why you're having issues. you're supposed to single weave / alternate as Seraphor said. and im not sure what you mean by there being an animation lock? heat blast, or wild fire, or anything like that doesnt have an animation lock. flame thrower (sort of) does, but i dont recall anything else having one

[DixieBellOCE]

i'm very confused by these statements. you're saying you're double weaving ricochet and gauss between your heat blasts? because if so, that's why you're having issues. you're supposed to single weave / alternate as Seraphor said. and im not sure what you mean by there being an animation lock? heat blast, or wild fire, or anything like that doesnt have an animation lock. flame thrower (sort of) does, but i dont recall anything else having one

This.

Your not supposed to double weave during heat blast. Single weave for the 5 shots.

[Caddo]

The GCD itself has an animation lock. If it were a double-weave, there'd be 3, which means you'd need literally 0 ping to do so within the 1.5s seconds.

I'm kinda confused with this. Before Heast Blast can completely finish it's animation (be it swinging close to the ground), you can clip the animation about 75% through and instantly round/richo and you'll also cancel richo full animation of jumping and landing (meaning mid air right after the jump, you'll magically appear on the ground and do another Heat Blast).

Not sure what animation you are speaking of when all 3 can be cancelled.

[Shurrikhan]

I'm kinda confused with this. Before Heast Blast can completely finish it's animation (be it swinging close to the ground), you can clip the animation about 75% through.

That's because the "animation lock" (0.5 seconds + roundtrip ping from the start of the animation) =/= the total animation time. Else old oGCD Tornado Kick would actually have taken a full GCD of uptime with its 2-second animation.

With very few exceptions (traditionally, pretty much just gap-closers, though even those have shortened greatly by now), all use that exact same .5s_+_2x_ping internal cooldown.

That internal cooldown simply has happened to be typically called the "animation lock" since "ICD" is typically used instead for shared very short recast times or for the safety periods over which consolidated buttons transition between states.

Not sure what animation you are speaking of when all 3 can be cancelled.

Not the animation. The "animation lock" / "animation period," which is the same one every time: 0.5s (+ roundtrip ping).

[DixieBellOCE]

I'm kinda confused with this. Before Heast Blast can completely finish it's animation (be it swinging close to the ground), you can clip the animation about 75% through and instantly round/richo and you'll also cancel richo full animation of jumping and landing (meaning mid air right after the jump, you'll magically appear on the ground and do another Heat Blast).

Not sure what animation you are speaking of when all 3 can be cancelled.

I think he is referring to the inbuilt 0.5s GCD lock. Not the animation.
Every OGCD ability had a 0.5s lockout after pressing it, people double weaving during hypercharge windows are using 3rd party programs to remove that lock.