NIN Needs a Mudra builder UI

[Almagnus1]

So thinking about the server lag issue with NIN, and one thing came ot mind that would really help it is a mudra builder UI that shows you where you are in the current mudra going by what the sever thinks you're mudra is. We'd see the ninjutsu skill in the top part of this UI element with the current ninjutsu, and the mudra used to make it below (for example, I'd see Houton as the ninjutsu with Jin Chi and Ten below in that order). This would work by putting a grey box with a question mark in the builder, and leaving the Ninjutsu as the default icon. Once the server confirms that you have used a mudra, the box would change to what the server thinks was used, and the ninjutsu would change according to what's being built.

This would be a useful UI for the less experienced because it's showing you what you're building as you're are building it. For the vets, it would let you know what mudra the server thinks you're building, and essentially give the vets an easy way to slow down and work around the lag issue, as you're going to want to wait to put in the next mudra once server confirms your last mudra (that is, the grey question mark becomes the last mudra used).

All in all, NIN has been a lot of fun, but the randomness introduced by the lag has not been - and hopefully this idea helps minimize that RNG.

[KaiBa]

Just press it in the last quarter of the skill.

[Almagnus1]

Just press it in the last quarter of the skill.

One of the things I've heard from FC mates (and even happens to me on occasion) is having lag decide that you're going to misorder your skills... even though you've done everything correctly.

That's a very large reason why I wrote the OP, as it gives us a way to make sure that the mudra we are building is the exact same one the server thinks we're building. It should also help us figure out when the server thinks we've used a skill twice (when we haven't) and other such shenanigans.

Yeah, I get the entire git gud argument, but if latency decides to take a dump on you, then you're gonna bunny.

[KaiBa]

Honestly, it isn't lag. It's precision timing. Once you reach a certain input speed the game is completely behind on your inputs but even casting mudra doesn't change. You may not see the cast timers when your going ham but if you have the millisecond jolt delay required to cast mudra combinations embedded into yourself at that speed then, there shouldn't be any problems, unless you arent using a ethernet cable in which case there's your problem.

Interesting thought you've contributed but there isn't really a problem unless you're paying for the lowest package your ISP provides and I'm not saying "git gud" at all. Just there isn't really a problem to be fixed but I suppose there's always room for improvement regarding design and performance. Location can be a thing aswell, I guess.

[Zfz]

I play with a ping of about 75-100ms, depending on the time of the day (lol). NIN is a job I've tried and tried and just can't play reliably because it just feels so cluncky. You get this fluid and speedy rotation and then you get to the mudra and it's like hitting a speed bump on a highway.

Which is why I'm really looking forward to their overhaul of the NIN mudra system they mentioned in the live letter. Yes, the devs have openly acknowledged that it is a problem and that they are already fixing it, just that it didn't make it into the 5.0 release.

So no it's not a git gud problem and it's not an ISP problem. It's a backend design problem of the game.

[Almagnus1]

I play with a ping of about 75-100ms, depending on the time of the day (lol). NIN is a job I've tried and tried and just can't play reliably because it just feels so cluncky. You get this fluid and speedy rotation and then you get to the mudra and it's like hitting a speed bump on a highway.

Which is why I'm really looking forward to their overhaul of the NIN mudra system they mentioned in the live letter. Yes, the devs have openly acknowledged that it is a problem and that they are already fixing it, just that it didn't make it into the 5.0 release.

So no it's not a git gud problem and it's not an ISP problem. It's a backend design problem of the game.

That's exactly why I want to see a UI that can both help with learning the mudras (as you see the mudra and what built it), and also see what the server thinks I built.

[KaiBa]

Averaging 75-100 ping, ninja won't be fun to play. I can see how that's unfair for people who want to specifically play ninja, I can agree. I am quite lucky I barely ever suffer from lag but if did then I'd probably be saying the same things as you two. Much to my own ignorance.

[MaraD_]

Honestly dont see it helpping much.
The final ability is the only one that matters,
so if you pressed ABC, and it only saw BC, then your suggestion helps a bit, as you adjust with BAC, but u could hear and see the animation only go off twice/once anyways.
so if you pressed AB, and it thinks you did AA, you cant finish the mudra w/o failing anyways. AAC and AABC all fail.

[Almagnus1]

Honestly dont see it helpping much.
The final ability is the only one that matters,
so if you pressed ABC, and it only saw BC, then your suggestion helps a bit, as you adjust with BAC, but u could hear and see the animation only go off twice/once anyways.
so if you pressed AB, and it thinks you did AA, you cant finish the mudra w/o failing anyways. AAC and AABC all fail.

That still gives higher visibility to the server issues, which is going to help with isolating the issue that SE is having where the sever screws up the order. Having more info is better than none, especially when half the problem is not knowing what the server thinks you're doing.