Unsubscribed from the game until Ninja Mudras are fixed.

[Stella_Khutga]

Hello all,

I am posting this here for lack of any other avenue of communication that I have not yet taken.

As of 6.3, ninja's mudras have been bugged and no longer function correctly. This bug also affects all GCDs with a base recast time below 2.50s before haste is applied (2.20 RDM, 1.50 RPR MCH DNC SGE RDM, 1.00 DNC SGE), however as Ninja's mudras have a base recast of 0.50s, they are the most easily affected. The bug is far more noticeable in instanced content than the overworld or housing districts.

On the second day of patch 6.3, the following threads were made on the English official forums.

Bug report: https://forum.square-enix.com/ffxiv/...eems-to-be-off

DPS roles: https://forum.square-enix.com/ffxiv/...h-ninja-mudras

The former was moved to 'Duplicate Bugs' 2-3 days later and immediately closed with no other communication until the 6.31 patch notes listed it in the 'known issues' section over a week later. The latter has seen some updates since its creation including other players saying that they have experienced the same issue.

Outside of the forums, the Ninja channels in The Balance discord server have created a thread where players may post their own evidence of the bug.

Thread link (requires access to The Balance discord server and the obtaining of the Ninja role):
https://discord.com/channels/2778971...31253153558610

Some of these examples can be seen below, as well as evidence from other sources.

https://gyazo.com/b2a013eddadffec87caed8b48ec5f11e

https://twitter.com/YrisMiretnjer14/...MKXMxAodQ&s=19

https://www.reddit.com/r/ffxiv/comme...a_mudra_delay/

https://clips.twitch.tv/NiceDepresse...sL-rXHCAV5RAyW

https://clips.twitch.tv/StrongSlippe...TjhubXl0W56LS2

Part 2 below.

[Stella_Khutga]

Part 2

It has now been over 3 weeks since this bug was introduced, and it has not been fixed. It is significantly more consistent and more egregious on console compared to PC, and is also more consistent and egregious when playing on higher latency. Both of these affect the bug to the point where the initial mudra recast can last for longer than 0.5s before it fixes itself, making the job mechanically unplayable. This is especially important due to the World Race of The Omega Protocol (Ultimate), where it has assuredly affected the performance of players in the instance over the past week and a half.

As a PS4 player, I have been unable to play my main job since the patch, and as the bug was not fixed in 6.31, I chose to unsubscribe from the game, leaving myself with a little over 3 weeks of play time remaining as of that day. The bug was not fixed by the recent maintenance, and as such I am making this post in order to encourage others affected by this bug to do the same thing in order to show Square Enix that this lack of care is unacceptable.

With the recent revival of the discussion on 3rd party tools, I also feel compelled to mention that the developer of a tool that allows players to mitigate the effect of latency on weaving discovered the source of the bug and implemented a fix for it into their program within days of the patch going live. Many ninja players on PC who took part/are taking part in the world race for The Omega Protocol (Ultimate) would have needed to use this tool in order to play the job, and this should not have been the case.

Of course, console players have no ability to use these tools whatsoever, and as such many were forced to play other jobs during the World Race. A discussion on the slowness of gearing multiple in this game is not relevant to this conversation, but does play a part here as more than one Ninja player was either unable to take part in the race at all, or was forced to play Ninja in its crippled state as they lacked the gear for other jobs.

Thank you for reading. I hope that this bug is fixed soon.

[Avoidy]

With the recent revival of the discussion on 3rd party tools, I also feel compelled to mention that the developer of a tool that allows players to mitigate the effect of latency on weaving discovered the source of the bug and implemented a fix for it into their program within days of the patch going live. Many ninja players on PC who took part/are taking part in the world race for The Omega Protocol (Ultimate) would have needed to use this tool in order to play the job, and this should not have been the case.

Of course, lmao.
How utterly embarrassing for SE. Fix your game, or your players will fix it for you in ways you won't approve of.

[Rein_eon_Osborne]

NIN isn't my main job (still my fave melee) but I felt the pain when I was trying to win a scouting top from Euphrosyne.

First Mudra input was highly messy I thought it was my own connection. Glad I wasn't the only one, it was incredibly frustrating to need to wait a moment to let the first Mudra registers properly or else it's rabbit of shame or Fuma Shuriken comes out instead.

With the recent revival of the discussion on 3rd party tools, I also feel compelled to mention that the developer of a tool that allows players to mitigate the effect of latency on weaving discovered the source of the bug and implemented a fix for it into their program within days of the patch going live. Many ninja players on PC who took part/are taking part in the world race for The Omega Protocol (Ultimate) would have needed to use this tool in order to play the job, and this should not have been the case.

Lmao.

I had a feeling they'll just do the "We're not aware this is an issue!!".

[Llynethil]

Wait it's still not fixed?

Man, even bethesda hotfixed the major bug in fo76 from last friday on this tuesday, this should have really been hotfixed 2 weeks ago.

[JuicyHeals]

Being on console and recently taking a liking to ninja it's disheartening not being able to play it.

[Keichi]

Why making such a scene?
Yes, it sucks for ninja. That is understandable.

But, they have at last mentioned this Bug in the last Patch note.
That it isnt fixed yet can have multiple reasons.
Maybe, they didnt has the Personal for the moment to do it.
Or, they dont found yet the reason for the Bug or wasnt able to remove it for the time.

Or, they simply wait for the 6.35 patch. It would suck. But i can not remember a case yet, where they maked a hot fix patch for only one bug.
Isnt it a little to overreacting to make such a scene? Dont you have a other class, that you can take for the moment, until it is fixed?

[Stella_Khutga]

Why making such a scene?

I do not believe I'm making a scene. I have filed bug reports since the day the patch went live, and taken part in documenting evidence of this bug since that date too, and nothing has been done. By contrast, bugs that had less effect on gameplay, such as the Warrior Shake it Off bug (which only came into effect when the warrior was the only target for the heal, and when under the effect of both Thrill and Bloodwhetting but not Vengeance) was discovered during the second week of 6.3 and fixed when 6.31 released.
However, I have no other avenue to take. I have been, with perhaps a single two-week break due to an extended holiday abroad, been subscribed to the game since late December 2019 with no interruptions. At £7.69 a month for more than 4 years, that totals £369.12 that I have given Square Enix, not including buying expansions and other optional items. Until such a time as they can continue to provide the service they promise, I will not continue to pay them.

But, they have at last mentioned this Bug in the last Patch note.
That it isnt fixed yet can have multiple reasons.
Maybe, they didnt has the Personal for the moment to do it.
Or, they dont found yet the reason for the Bug or wasnt able to remove it for the time.

See above regarding the Warrior bug for 'not having the personnel'. It is unlikely bordering on impossible that they don't have enough employees to fix a simple bug such as this one (the source of which was found by the community within a few days and is, quite literally, a single line of code). I do not believe that they have yet to find the reason when they have much easier access to the code of the game, and I do not know why it has not been removed at this time.

Or, they simply wait for the 6.35 patch. It would suck. But i can not remember a case yet, where they maked a hot fix patch for only one bug.

If they wait until 6.35, I will resub in 6.35. That's fine by me. As for when they hotfixed a single bug, they literally did it a couple of days ago, where the boss of Phase 3 of The Omega Protocol (Ultimate) was auto-attacking as soon as it was targetable and frequently killing non-tank players. They hotfixed this bug by taking down the instance servers for 4 hours. They also had emergency maintenance on the first week of 6.3, in order to revert the changes they made to their packet system in the 6.3 update. It has happened many times before and will happen again.

[Stella_Khutga]

The bug was fixed 10 days ago. This sounds like a latency or skill issue.

[Hpynso]

Why making such a scene?
Yes, it sucks for ninja. That is understandable.

But, they have at last mentioned this Bug in the last Patch note.
That it isnt fixed yet can have multiple reasons.
Maybe, they didnt has the Personal for the moment to do it.
Or, they dont found yet the reason for the Bug or wasnt able to remove it for the time.

Or, they simply wait for the 6.35 patch. It would suck. But i can not remember a case yet, where they maked a hot fix patch for only one bug.
Isnt it a little to overreacting to make such a scene? Dont you have a other class, that you can take for the moment, until it is fixed?

Playing another class for the moment is only an acceptable argument if you ignore the fact that gearing to bis takes a long time, and you need bis for TOP.
Might not be a problem for a good chunk of people, since they might have bis on multiple jobs, or who aren't even bothering with TOP.

But what about those who didn't get bis for more jobs while farming savage? What if they are on console which exarcebates the mudra bug? What if they are east coast, or god forbid further from the server.
Your message just comes across as somebody insensitive to something because it does not affect you.