Machinist feels pretty good now.

[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.