What would happen if Mudra gcd recast time reduced to 0.2 sec?

[cactuarzzzz]

I'm curious

[IBLazORI]

People with excellent ping would benefit more than those without.
The slower recast helps even it out a little bit more.

[Seraphor]

If only there was some way it could collate the mudras client side and then relay the full jutsu over to the server side when you use it.

[wereotter]

Probably I would mess up more Mudra.... I have at least a few times accidentally hit the same input twice in a row and got bunnied. If the cool down were shorter, at least at first, people would likely mess up the input more often.

[Furious]

I'm curious

People who don't live next door to a data center would spend a lot of time with funny hats on?

Ninja is a terribly designed job for an online game where people have widely different pings, let's not try to make it worse.

[Shurrikhan]

Probably I would mess up more Mudra.... I have at least a few times accidentally hit the same input twice in a row and got bunnied. If the cool down were shorter, at least at first, people would likely mess up the input more often.

To be fair, is there really any reason to keep that possibility [of bunny-ing]? Our main reason for double-hitting has typically been expected possible packet loss or animation lock conflicts losing the queue if we don't send multiple requests. Were we finally using client side collation, that'd be a non-issue. At that point, why even allow for bunnying? Instead, we could eventually get more complex or separable Ninjutsu down the line without requiring a larger button count spent on additional Mudra.