*Cringe*
Oh god, really? It's worse than I thought, then. You can buy new servers, but a tangled web of inefficient netcode? That's kind of a nail in the coffin then. Very unfortunate. =(



Mhm. They probably never thought to test NIN outside of the internal servers and so never considered how problematic the 0.5 recast on Mudra might be. I'm not sure what kind of solution they can really implement outside of the Mudra clint-side, Ninjutsu server-side fix that others have proposed (but they're probably wary of doing so because of the possibility for abuse).
There is no Mudra lag.
I wondered why sometimes my mudra screwed up.It's a player thing.Nothing to do with servers.Basically whats happening is we are hitting the commands too early with mudra so the input isn't being recognised properly.Each part of Mudra has a cast time.We're trying to cast too early which is screwing it up.I've done it myself a few times.
My main concern with Ninja despite being a great dps class is it in the long run especially on single targets worth it to actually have an extra rotation to keep Huton up.
Obviously we need to keep Huton up but given the coolodown times between our mudra that lets us do sneak attack skills is it really any benefit to Ninjas to waste our give up a lot of our main dps combo for an extra raition.I don't think so.
Overall it probably gimps our dps more than if we were sticking with preheavensward rotations.I say this as Dream within a dream is of cooldown skill anyway.



This is actually demonstrably false. While player skill can and does impact mudra execution, so does latency. It's not reproducible on command but the most visible instance of this involves instances wherein you hit a mudra, its cooldown finishes, and the Ninjutsu button doesn't change to the proper Ninjutsu because latency has prevented the server from seeing that the mudra was executed properly. If you then hit the next Mudra, it will at times over-ride the first (or sometimes not be registered at all, depending on when the server "catches up" to your client-side inputs).
Like i said it's a player issue not a server issue.SE has not created Mudra lag.you haveing a bad connection has made Mudra lag.Get a decent ISP and stop blaming SE servers.There is nothing wrong with them and the majority of the community will agree with me on this statement.For a while the servers did have some issues due to too many players.This is actually demonstrably false. While player skill can and does impact mudra execution, so does latency. It's not reproducible on command but the most visible instance of this involves instances wherein you hit a mudra, its cooldown finishes, and the Ninjutsu button doesn't change to the proper Ninjutsu because latency has prevented the server from seeing that the mudra was executed properly. If you then hit the next Mudra, it will at times over-ride the first (or sometimes not be registered at all, depending on when the server "catches up" to your client-side inputs).
N-... No. That's just not true. People with great connections still miss all kinds of interstitial moves. I play Dragoon, which now requires three moves per GCD in places, and I have a stellar connection; it still drops moves. To say nothing of what a nightmare working with pets is in the game. This is not an imagined issue nor purely the fault of one's ISP. I'm sorry but you're just mistaken on this one.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.


Reply With Quote


