Mudra's seem sluggish?

[ShaolinMike]

an example of trouble you can face, you actionnate Chi> Jin but only fuma shuriken appear, because of the latency, you dunno which mudra you did register... do it have get Chi or Jin? i did end in quite weird situation because of the latency on the mudra, adding a windows will take them close of no time, and will make the mudra more clear. we will all gain from this, it will be a QoL change for the ninja and it ninjutsu.

Not trying to sound like a d**k, but is the big kanji flashing on the screen not visual cue enough to see that a mudra has registered? I'd think that adding a window would be redundant.

[silentwindfr]

be european, you will see, time to time i even have some weird animation bug, like i sending a Raiton, but because of the latency, he do two animation... sending a fuma shuriken and a raiton :x or my GCD not geting updated and i need to use the mudra for get the gcd appear and paf he do the animation of the mudra when i'm still in cooldown.

the ninjutsu is an amazing system, but if you do have a latency of 100+ it can become horrible.

[Riepah]

Not trying to sound like a d**k, but is the big kanji flashing on the screen not visual cue enough to see that a mudra has registered? I'd think that adding a window would be redundant.

Sadly, it isn't. I've come across an issue where the animation for my second mudra happened, but the mudra didn't really register. I used two mudras, but ended up throwing a Fuma Shuriken instead of Raiton. Doesn't happen very frequently of course, but it can happen.

[ShaolinMike]

be european, you will see, time to time i even have some weird animation bug, like i sending a Raiton, but because of the latency, he do two animation... sending a fuma shuriken and a raiton :x or my GCD not geting updated and i need to use the mudra for get the gcd appear and paf he do the animation of the mudra when i'm still in cooldown.

the ninjutsu is an amazing system, but if you do have a latency of 100+ it can become horrible.

Wow that sucks big time. How would a window help that though? Wouldn't the window display suffer from the same issue with latency?

[silentwindfr]

because it will show us what the game did register, not the interface visual bug.

Maybe macro your mudras to echo. Just a thought.

macro will not work since the <wait> command is 1 sec of base, you can't do 0.5... meaning on mudra of 3 you loose 1.5 sec that quite a lot.

[ShaolinMike]

Maybe macro your mudras to echo. Just a thought.

[roninoftagrm]

It's not sluggish, it's just we're not used to skills being on a .5 second cooldown. It's JUST slow enough that you can screw it up if you try to spam press the combos. Also, it's makes macroing the combos inefficient, thereby keeping the intent of the whole Ninjutsu combo system.

this is why ill just go with /wait 1 macros, no screw ups when finally get up to ninja fever levels

[Zish]

This could be solved by simply having no cooldown on the Mudras...

There's really no reason for it, as you can avoid the GCD most of the time anyway.
The current system doesn't allow you to input your combination as fast as you'd like. You have to sit there and wait to make sure it registered first before moving on. (It's a super slight delay, but it's incredibly annoying)

Having no cooldown on them would allow for quick input with zero worry about missing one.


The skill of a ninja should come from being able to memorize the combinations and using all seven to your advantage.
You shouldn't be punished for having latency screw up your combination that you did input correctly.

[Pyros]

Having no cooldown wouldn't help since they're still being checked server side and lag would still force you to wait until you input next or randomly fail, see any 2 off GCD abilities put together, as well as off GCD+instant skills sometimes failing and such. The solution would have been to make mudras client side only, so they wouldn't be affected by lag. Then ninjutsu is checked server side as usual to prevent cheats, it's not like casting mudras does anything until you ninjutsu anyway.

Not a big deal but it's pretty annoying at times, as lag spikes will generally mean a failed ninjutsu. This isn't really new either, there's always been issues in this game with off GCD abilities, for example you cast Swiftcast then Rez(or whatever else), and sometimes you will actually start casting the Res even though you gained the swiftcast buff, sometimes you'll start casting then it'll cancel the cast because Swiftcast fired "at the same time", and sometimes it works as you'd expect.

[Zish]

Having no cooldown wouldn't help.

It absolutely would.

You could input your combo without delay or having to make sure your next mudra isn't on a cooldown, thus your chain would not be interrupted.

For the user this would remove the issue of sometimes clipping mudras due to lag.
Ex: You input your entire combo line (near instantly if you're fast enough), and as long as you got it in the right order, the server cannot argue with you after you've pressed the buttons.