MCH ping related issues

Hello,

with the newest post from the devs about the use of 3rd party tools, I would like to remind them that machinist has serious issues when played at high ping. This issue has been a thing that has plagued the job since it's inception in Heavenwards (Rapid Fire) and has not been changed since it's rework in ShB. Hypercharge by it's design doesn't mesh well with high ping. I actually asked this question to Yoship during last year's fanfest on if they are planning on addressing this issue, but was met with a non answer. Mr Happy also asked in an interview if they plan on addressing said issue but was told not enough complaints were made about it. This resulted in more and more users either dropping the job or having to resort in using 3rd party tools as well as (sometimes pricy) VPNs to be able to play the job. Multiple post on these forums have been made by members of the community about this same issue for years. This issue has been explored and discussed in this post made a few months ago.

https://forum.square-enix.com/ffxiv/...tions-normally

The job needs to be looked at. A simple addition of stacks to heatblast would not fix the issue as weaving would still be the same. The netcode has to be looked at, or copy a similar structure to the tools used. Animation lock on Gauss Round and Ricochet could also be looked at. If none of these options work out the job's design needs to be changed.

We were told that not enough complaints have been made on the subject yet these forums are full of them. Are we supposed to just wait another two years for this issue to be finally recognized and changed via another machinist rework? The job has so many issues yet it feels ignored. I highly recommend the devs to take a look at the above post as it explains the situation in greater details. Punishing players for living further away from the server or wanting to play a certain job isn't the way to go.

New crackdown on third-party tools, RIP everyone who needed XIVAlexander or NoClippy to play the job.

They need to make PVE Wildfire similar to the PVP version:

- Wildfire pops at 6 GCDs automatically and has a long timer
- Hypercharge has 5 stacks and a long timer so that it can be expended fully without concerns due to clipping

This way the method/rotation stays the same, but now high ping players can get 6 GCD WFs without good ping

Quote:

---

Originally Posted by iiTzSeb

They need to make PVE Wildfire similar to the PVP version:

- Wildfire pops at 6 GCDs automatically and has a long timer
- Hypercharge has 5 stacks and a long timer so that it can be expended fully without concerns due to clipping

This way the method/rotation stays the same, but now high ping players can get 6 GCD WFs without good ping

---

Hire this man square, he fix MCH.

Quote:

---

Originally Posted by Zarkovitch

Hire this man square, he fix MCH.

---

isn't it kinda sad that the most insightful ideas come directly from the players while the devs are always trying to come up with ideas to resolve the issue?
makes you wonder if what Yoshi said is true, that they do read the official forums, because many ideas on the forums could easily be added and fix most of the problems players have.

Quote:

---

Originally Posted by iiTzSeb

They need to make PVE Wildfire similar to the PVP version:

- Wildfire pops at 6 GCDs automatically and has a long timer
- Hypercharge has 5 stacks and a long timer so that it can be expended fully without concerns due to clipping

This way the method/rotation stays the same, but now high ping players can get 6 GCD WFs without good ping

---

I like this idea but is better for everyone if SE just fix the bad netcode of the game, clipping is not only a MCH issue, every job with double weave or a single weave between short GCD (RPR enshroud) and even healers suffer from this problem.

If SE fix this problem, they can focus on other things to change on MCH instead of changing just for ping issues.

Quote:

---

Originally Posted by Kitfox

New crackdown on third-party tools, RIP everyone who needed XIVAlexander or NoClippy to play the job.

---

What really baffles me is why SE can’t just do this themselves. XIValexander just replaces a file in the game directory and makes it simulate 0 ping. Why can’t SE just include that feature as standard?? It would solve so many issues.

Quote:

---

Originally Posted by Cabalabob

What really baffles me is why SE can’t just do this themselves. XIValexander just replaces a file in the game directory and makes it simulate 0 ping. Why can’t SE just include that feature as standard?? It would solve so many issues.

---

The bug has recently been accepted, described and forwarded to the GM's by this guy https://forum.square-enix.com/ffxiv/...rmally./page12

MCH isn't the only class to struggle with ping.

Ninja can struggle to, due to the 0.5 sec mudra (even if it was worse before being a GCD), leading to a bunny.

RPR also got a 1.5 GCD rotation with five hit and oGCD in between. Latency can be an issue here again

Red Mage got a fast combo (especially the 3 first hit) that goes slower the further you go in it, but it can still delay the use of oGCD because of Latency in order to no clip it. Minor Issue for this one, but still there.

Also, any class that need to double weave will suffer from Ping Issue (Depending on how high the ping is, of course), making rotation clip.