MCH future changes from the live letter

[Alchemii]

The new turret overload is really great now that the damage dealt combined with the downtime breaks even with continuous attacks over the same 30 second period (give or take a bit).

You can think about it as it letting you take all the turret autos from up to 30s in the future, and cashing them in right now for damage. If the boss goes untargetable in the future, or you have a buff on you, there's the potential for massive damage gains; and like El said it will be a huge benefit in any situation where you need a big damage spike.

Don't forget the effect of Hypercharge causes the turret to place a 10sec debuff on the enemy with every auto-attack the turret makes. So you you should beable to Hypercharge, then right at the end of hypercharge you can use Overload and the damage being done by the Overload will be effected by Hypercharge, for a net gain in dps.

Edit: Fixing Typoes

[Lastelli]

Don't forget the effect of Hypercharge causes the turret to place a 10sec debuff on the enemy with every auto-attack the turret makes. So you you should beable to Hypercharge, then right at the end of hypercharge you can use Overload and the damage being done by the Overload will be effected by Hypercharge, for a net gain in dps.

Edit: Fixing Typoes

That probably won't happen. You'd gain 40 potency but the probability that you'll miss a turret AA because you dispatch it one second later after the penalty is over is very high and as soon as you lose that one AA, it becomes a dps loss.

[Raikai]

I was hoping they'd ditch Gauss Barrel mechanic lol.

It's a worthless maintenance thing just for the sake of it. It doesn't reward you for timing or anything. If you overheat it's just a click you have to do at the end of the cooling timer.
1) Remove it altogether, be the heat gauge always on.
2) Turn it into some sort of interesting cooldown.

[Myon88]

The turret autoattack interval is 3 seconds, not affected by your weapon or stats like skillspeed.

There is currently a bug though where it will randomly pause for a long time between autoattacks, which explains the 4-5 second intervals some people are seeing at times.

[Fannah]

The turret autoattack interval is 3 seconds, not affected by your weapon or stats like skillspeed.

I actually used a chronometer, with the function to get timers between 2 clicks I did for each hit. It was always closer to 3.2 than 3.0.
I'm not saying I was perfect or that the game should be this way, but it was still always around 3.2 and not around 3.0. And I did several tries, and just did it again to be sure.
So the total timer of 2m40s for 50 shots gives the result of 3.2sec and the "delay between 2 clicks" function always was around 3.2sec, so I believe what I see first.

And machinists don't have a 3.2 weapon skill delay, so I believe it doesn't change anything. According to the weapon you use, you have a delay of 2.48s (some rare weapons as Thordan, Licorn pvp weapon, legendary weapons) / 2.56s / 2.64s (the most used delay) / 2.72s (Mog weapon only) / 2.76s (Bismark weapon only) / 2.80s.

So I invite you to try on your side and tell us if you found a 3.0s delay the way I did. If you do, it means there is another bug.

[Myon88]

You mean a stopwatch with a split lap function? Yes I used that too, and got a 3 second value. But don't take my word for it, the next step would be record some footage and measure it to your heart's content off there - anyone is welcome to try.

As for turrets not being affected by weapons nor skillspeed, this has been known since Heavensward, and nothing so far leads me to believe that has changed. I don't know why you're bringing weapons up at all.

If it is the case that turrets fire at a greater than 3 second interval, that can only be a good thing for Turret Overload, as the breakeven point assumes a 3 second interval (30s = 10 attacks @ 3s, 80 potency attacks = 800 potency). A longer default autoattack interval only increases the degree to which Turret Overload is a dps increase.

[Fannah]

You mean a stopwatch with a split lap function? Yes I used that too, and got a 3 second value. But don't take my word for it, the next step would be record some footage and measure it to your heart's content off there - anyone is welcome to try.

I believe we speak about the same function, yes, I just am not English native speaker and I never read or heard about this function in English until now (so, thx :3 )
Maybe a bug, or something due to some settings or power of my computer/screen, I dunno.

As for turrets not being affected by weapons nor skillspeed, this has been known since Heavensward, and nothing so far leads me to believe that has changed. I don't know why you're bringing weapons up at all.

I just said the attack weapon delay of some weapons in the game is 3.2sec (like White mage melee auto attacks), and I found 3.2sec, so it wouldn't be surprising if they used such weird number as 3.2sec for the turret's auto attack delay (I only tried for the monotarget one). I never said weapon attack delay was impacting on the turret attack delay. The other one responding to my comment did.

If it is the case that turrets fire at a greater than 3 second interval, that can only be a good thing for Turret Overload, as the breakeven point assumes a 3 second interval (30s = 10 attacks @ 3s, 80 potency attacks = 800 potency). A longer default autoattack interval only increases the degree to which Turret Overload is a dps increase.

Not really, it just lower the overall dps of the turret people expect from it The fact it indirectly upgrade the efficiency of Overload is not relevant enough, we shouldn't use it randomly anyway.

[Elnidfse]

You mean a stopwatch with a split lap function? Yes I used that too, and got a 3 second value. But don't take my word for it, the next step would be record some footage and measure it to your heart's content off there - anyone is welcome to try.

Editrido. There is 3 seconds which you already knew and there is indeed some weird lag. Wicked.

[Fannah]

Can you give me some figures? I know and I'm sure to have an average of 3.2sec. I'm wondering how you do, and what you do, let's assume I even count the very 1rst hit at 0sec, it would do a total of 51 attacks (the 1rst one at 0sec, and then the 50 ones after this one). And if I count 51 attacks, I would have an average of 159sec for the 51 hits (I don't know how it happened, but I once had 159 sec, so I take the best score I did). 159/51 = 3.12sec (which is mathematically wrong, but still closer to your results).

If it's only happening where I am, I am wondering what magic is making my own turret slower. And I hope you don't use old data of yours.