A Wish List for Ninja changes in later patches

[Ninji]

-Rename "Armor Crush" -> "Aeolian Edge"(since Armor Crush increases Huton, a Wind ability...aka an Aeolian ability); Rename "Aoelian Edge" -> "Dancing Edge"(since you jump up with a spin, kind of like a dance); Rename "Dancing Edge" -> "Armor Crush"(since "Dancing Edge" reduces slashing resistance, almost like reducing armor potency)


-Make current "Armor Crush" combo off of "Shadow Fang" instead of "Gust Slash"(This will help keep "Shadow Fang" from falling off and lower the number of finishers combo'ing off of "Gust Slash") or maybe have the current "Armor Crush" combo off of "Spinning Edge" and have "Shadow Fang" combo off "Armor Crush" to avoid clipping the DoT.


-Make "Shukuchi" a 35 yalm range, up from 25 yalm range.(-Almost- not worth doing)

[Ninji]

-Make new poison that does something with "Dream Within A Dream", like how Wasp = Jugulate modifier and Viper = Mug modifier. We have a new oGCD ability, but without a modifier, just seems out of place.

My wish for it? Using "Dream Within A Dream" with "Insert new poison here" causes your next "Death Blossom" to poison all targets hit for X seconds for Y potency.(maybe 18 seconds dealing 30 potency?) it could be something else, SUGGESTIONS PEOPLE!

-Make "Huton" duration last 90 seconds(instead of 70)...just messes with my OCD >.>'.


-Change "Hide" to not decrease movement speed...it is completely useless as it is.


-Cause "Shade Shift" to actually negate its 20% dmg...seems like EVERYTHING goes through that move, why even use it? Is there a use for it aside from -if you steal threat-? I use it before a big physical OR magical straight line or round AoE, get hit for full dmg.

[Ninji]

-Not particularly a -Ninja- revision, but more of an overall game revision that would affect Ninja: Change TP(and MP) regen to be smooth rather chunk by chunk, it'd help with using abilities faster when you are low on TP(and MP).


In-Combat TP regen is 30/3 seconds I think? It could be like 1TP/.1second, which would be the same ratio and help us do our moves ASAP. Need 120TP for that death blossom but you have 110TP? Gotta wait 3 seconds for TP to tick...or...just wait 1 second for the TP to regen smoothly, saving 2 seconds of time, which can be crucial. (you can apply the same scenario to MP for healers, esspecially with something like Shroud, less waiting = faster healing).

What do you guys think? How do you feel about it?

[Draegon]

My wish...
Get rid of Mudra system and make each ability a 1 button press with cast time equal to what it would be if the mudra lag was not horrible. I.E. press huton button and it auto casts all 3 mudras for you(even with a GCD equal to your current Skill speed would be awesome). I know it sounds like idiot proofing but for those with any lag or latency issues its a dam fine solution. Can keep the actual cast button so you can make sure to be in correct position for abilities like Trick Attack or to preload for an adds popping in(within 5 secs). Really do not understand why it was not implemented this way to begin with. I fricking LOVE playing ninja but the latency/lag issue has me tearing my hair out sometimes.

[Ninji]

Get rid of Mudra system and make each ability a 1 button press with cast time equal to what it would be if the mudra lag was not horrible. I.E. press huton button and it auto casts all 3 mudras for you(even with a GCD equal to your current Skill speed would be awesome). I know it sounds like idiot proofing but for those with any lag or latency issues its a dam fine solution.

Yea, I can see your point, the mudra lag can be an issue, pressing 1 button to cast the mudra with the same GCD is a good idea, heck, it is what I do with my G-keys on my keyboard, press 1 button and it does each mudra every .6 seconds(to account for lag)and casting the ninjutsu .2 seconds after the last mudra). Macro'ing the mudras hurt with the GCD by 2-2.5 seconds, so that is innefficent(G-keys mimics my delay in pressing the buttons in real time, so I don't have to worry).

[ErzaScarlet77]

My wish...
Get rid of Mudra system and make each ability a 1 button press with cast time equal to what it would be if the mudra lag was not horrible. I.E. press huton button and it auto casts all 3 mudras for you(even with a GCD equal to your current Skill speed would be awesome). I know it sounds like idiot proofing but for those with any lag or latency issues its a dam fine solution. Can keep the actual cast button so you can make sure to be in correct position for abilities like Trick Attack or to preload for an adds popping in(within 5 secs). Really do not understand why it was not implemented this way to begin with. I fricking LOVE playing ninja but the latency/lag issue has me tearing my hair out sometimes.

i mean isnt that just macro?

[Ninji]

i mean isnt that just macro?

You would lose 2-2.5 seconds of time every time you would use the macro. The Global CD between mudra is .5 seconds, but the shortest macro /wait time is 1 second, so you lose .5 seconds each time between mudra. Then the GCD between the last mudra and the casting of the ninjutsu is .1 second, so you lose .5+.5+.5+.9 seconds or 2.4 seconds for suiton or .5+.5+.9 = 1.9 seconds for raiton, every 20 seconds + Kassasatsu, which will lose you about 8.1 seconds per minute, and over the course of a 3-5 minute fight, that is a loss of 24.3 - 40.5 seconds, and the dmg you can lose in an avg time of 32.4 seconds is about 16 weapon skills which can be around ~30k dmg lost on avg per boss fight when doing about 1.1k avg dps is normal.

[Atreides]

My wish...
Get rid of Mudra system and make each ability a 1 button press with cast time equal to what it would be if the mudra lag was not horrible.

That would be like "Get rid of Ninja and turn it into Thief", I would welcome that change since I was Pro Thief from the beginning and Ninja hooked that spot now which is a shame.

[Taranok]

-Rename "Armor Crush" -> "Aeolian Edge"(since Armor Crush increases Huton, a Wind ability...aka an Aeolian ability); Rename "Aoelian Edge" -> "Dancing Edge"(since you jump up with a spin, kind of like a dance); Rename "Dancing Edge" -> "Armor Crush"(since "Dancing Edge" reduces slashing resistance, almost like reducing armor potency)

Surprisingly logical. I more or less like this change. The devs would need to shift the animations with the name change as well to keep everything nice and tidy, but I like it.

-Make current "Armor Crush" combo off of "Shadow Fang" instead of "Gust Slash"(This will help keep "Shadow Fang" from falling off and lower the number of finishers combo'ing off of "Gust Slash") or maybe have the current "Armor Crush" combo off of "Spinning Edge" and have "Shadow Fang" combo off "Armor Crush" to avoid clipping the DoT.

I disagree not because I don't want the rotation changed (it needs to be changed. Seriously.) but because I don't agree with how you want to change it. Right now, we have 2 20-second-long buff/debuffs. Or, more accurately, a 20 and 18 second duration ability. Dancing Edge and Shadow Fang. Putting Shadow Fang after Crush Armor makes no sense, as that's just "You permanently have Huton pending boss mechanics." Having AC after SF makes less sense for the same reason. If you apply SF, why wouldn't you just crush armor? Even with changes in potency, it'd still be required. You could lower the amount increased, but AC fits best as a "You use this to rebuild Huton if you need to." And it should stay this way.

The natural combo is Spinning Edge -> Dancing Edge -> Shadow Fang. The only change that would need to be made is that DE might need its duration increased, along with SF. Naturally, the potency of these 2 abilities would need a mild adjustment as well, but the current NIN combo is 2 3-length combos for every Shadow Fang, and since DE needs to be up anyways, may as well put it before SF.

Another alternative is to make DE its own combo starter that chains into Shadow Fang. The devs would just, again, need to adjust potency as necessary. Though I feel this might be less skill-intensive on the rotation than making SF a 3-length combo.

Either way, the nature of how DE interacts with AE and AC needs to be changed, because right now, the NIN rotation is just a mess unless a Warrior is present.

-Make "Shukuchi" a 35 yalm range, up from 25 yalm range.(-Almost- not worth doing)

The problem is less the range, and more how horrible the UI is for ground-targeted abilities in combo with the range.

For instance, if they made it teleport you to the closest point to your mouse cursor when casting the ability outside of max range, it would be substantially more useful. Extra range would only serve to mitigate the horrible UI issues.

Hell, I kind of wish I had the option to simply "Target GTAoEs at closest point to current target" as an option, honestly. That would also fix the problem, and make GTAoE abilities not a horrible mess to cast.

25 yalms isn't bad. 25 yalms with many fights that have distances exceeding 25 yalms in addition to a badly designed UI makes 25 yalms bad.

[Taranok]

Yea, I can see your point, the mudra lag can be an issue, pressing 1 button to cast the mudra with the same GCD is a good idea, heck, it is what I do with my G-keys on my keyboard, press 1 button and it does each mudra every .6 seconds(to account for lag)and casting the ninjutsu .2 seconds after the last mudra). Macro'ing the mudras hurt with the GCD by 2-2.5 seconds, so that is innefficent(G-keys mimics my delay in pressing the buttons in real time, so I don't have to worry).

The better solution is to just make it so Mudras don't require a server response in order to advance to the next one. That's the entire reason Mudra Lag is even a problem. All the devs need to do is create a specific function for specific abilities that allows them to bypass the talkback.

All the devs would then need to do is make sure that the server can check that the mudra casts are valid, as well as making sure that the timing is accurate enough to not care (whatever tolerance they want) and then accept or reject the ninjutsu cast pending on the tolerances on the timestamp. Since most people won't try to cheat the system in some gamey way, the tolerances just need to be something that won't come up in regular play, and the only thing that needs to be changed is the addition of a function for the client that allows it only with specific abilities to bypass the server.

Granted, there could be a security quagmire preventing this from being easy, but that's what needs to be done to fix the problem.