The new MCH likely carries old unfixed issues

[Hussain]

It is designed to be weaved with gauss round and rico because heat blast reduces both of their CD 15 with each heat blast so you wanna spam that while you're in OH

[PangTong]

New MCH looks fine to me. To be perfectly optimal you might have to single-weave Gauss Round and Ricochet during Overheat periods, but if you don't then it's not a huge loss. Because of the 15s refresh effect on Gauss Round and Ricochet caused by Heat Blast, just 6 Heat Blasts is enough to refresh all your stacks from 0, so it is likely that it will be optimal to single weave at least one or two Gauss Round/Ricochets during Overheat. So there may be a need to single-weave between Heat Blasts, but as long as you make sure you have depleted all your Gauss Round and Ricochet stacks before entering Overheat, you are probably not losing out on TOO much damage if you simply don't use oGCDs at all during Overheat.

From looking at the changes it -does- look like single-weaving between 1.5s Heat Blasts is encouraged (not just Gauss Round and Ricochet but Hypercharge too), which is a bit of a problem for me since 1.5s is too short for me to single weave with my ping. But I think if you live in the same region as the servers it should be fine.

If it were me, I would change Gauss Round and Ricochet so either Heat Blast only refreshes maybe 6-10s of each of them, and I would maybe alter Hypercharge so that instead of just being a flat exchange of 50 heat to 8s of Overheat, you could also get 12s for 75 Heat and 16s for 100 Heat off 1 button press (instead of having to extend it manually). That should totally eliminate the need for weaving between Heat Blasts.

[Kabooa]

It is designed to be weaved with gauss round and rico because heat blast reduces both of their CD 15 with each heat blast so you wanna spam that while you're in OH

I got the impression you want to dump them prior.

[Hussain]

Sure but with 6 Heat blasts in that window you'll get 3 charges of each back so you'll end up having to weave anyway cause remember heat blasts reduces the recast of both GR and Rico by 15 sec

[Sigiria]

Sure but with 6 Heat blasts in that window you'll get 3 charges of each back so you'll end up having to weave anyway cause remember heat blasts reduces the recast of both GR and Rico by 15 sec

you can only put 5 heat blasts on the 8 seconds of the overheat (6x1.5=9s) So if you've emptied your charges you'll still have 15 seconds to use one charge of each oGCD

Edit: Scrap that, since you actually do shot>1.5>shot>3.0>shot>4.5>shot>6.0>shot>7.5>shot. You should indeed have the time to use 6 heat blast, still I feel like it would be better to not risk losing one GCD on the wildfire for the few seconds you'll loose on overcharging the oGCD.

[PangTong]

you can only put 5 heat blasts on the 8 seconds of the overheat (6x1.5=9s) So if you've emptied your charges you'll still have 15 seconds to use one charge of each oGCD

You can get 6 as long as you use the first one within 0.5 seconds of the overheat buff starting. For example:
1st Heat Blast - 0.4 seconds
2nd - 1.9 seconds
3rd - 3.4 seconds
4th - 4.9 seconds
5th - 6.4 seconds
6th - 7.9 seconds
Whether this is actually possible in game with how server ticks work, I'm not sure.

[Sigiria]

Yeah, I was rewatching Mrhappy's video with the machinist and he actually manage to only get 5 heat blast on wildfire. And in that case SE should indeed adress the issue, either they balanced the skill thinking it should fit 5 heatblast and gave a very generous window that'll probably be exploited by players with a good ping and some skill speed to put an extra one. If that's it I feel like they should either reduce the timer to 7s to make sure everyone get 5 on it. Or they planned to have 6gcd and thought 0.5s to fire the first shot was enough and really overstimate how responsive the game is. In which case they should add 1s to the timer of overheat.

If it's made on purpose to have different result for "skilled" player, it's dumb since the only skill involved would come from your connection to the server.

Hopefully they already noticed this and tweaked it.