Machinist feels pretty good now.

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

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

[Soge01]

Flamethrower could be changed to Electrical Charge and use as an AoE battery Dump for trash pulls. Because right now there's no use for battery gauge outside of Queen / Single Target.

That would be neat!

[Semirhage]

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.

Close, but not quite.

Let's say you have 200ms of ping. When you use an ability, you enter a mandatory 0.5s animation lock. This is true for all abilities, GCD or off. Your client says "I'm using this ability now!". That hits the server 100ms later. The server then says "okay sure, that ability isn't on cooldown and your job can use it. This looks okay. Use it." Let's say it takes 0ms for the server to say that, even though there's still a tiny amount of time there. 100ms later, your client gets the thumbs up. You're now 200 total milliseconds into your 0.5 second lock, so you've got 300ms to finish out before you can queue up another ability. Makes sense, right?

Except that's not how FF14 works. FF14 takes that request 100ms in, then replies with a packet that takes 100ms to get back. You're now 200ms into your animation lock. FF14 resets your animation lock back to 0.5 seconds at this point. So your *actual* animation lock is 0.7 seconds. It's 0.5 seconds + your ping, due to this reset. Stupid, right?

Those third party programs don't remove the 0.5s lock (I think you could set them up to, but they don't by default). They instead ignore the instruction to reset your animation lock, making your client behave like every other professionally-designed MMO does with an internal animation lock that doesn't artificially double tax you for the sin of not living in the server closet in San Francisco.