Quote Originally Posted by Quor View Post
Yes, I'm aware. By "error" I mean they got an A = B situation instead of A = A. Armor Crush would make total sense as the slashing debuff that NIN once had, while Aeolian Edge would make total sense, being a wind-inspired name, as the Huton extender. Somehow, at some point in time during localization and translating, the wires got crossed and we got what we have now, and SE left it be.

I can't tell if I'm missing something, or...


Shurrikhan mentions that Trick Attack's japanese name translates as Sneak Attack or Trick Attack, and that Armor Crush's japanese name also translates to a similar meaning as the english name. How is this an A = B situation? It seems quite A = A to me. Your gripe is with the naming of the ability in general, not the localisation.



That said, I largely agree with the sentiment that Armour Crush feels like an odd ability choice with which to refresh Huton. Aeolian Edge does seem like a much better choice. That said, I do love Armor Crush's animation, and would hate to see it go like other GCDs (rip Shadowfang...).

I did find the suggestion of Huton being refreshed by Aeolian Edge to be quite interesting. SE seems dead-set on paring down buttons to make way for new ones, and one of the bigger suggestions for this is to make 1-2-3 combos a single button ala PVP. This doesn't work for jobs with branching combinations like Ninja -- but if we removed Armour Crush, this becomes an option.

I wonder what a Ninja with an Aeolian Edge that refreshed Huton by 10s, and no Armour Crush would look like? It takes ~6 1/2 seconds to cycle your 1-2-3 combo if Huton is active, meaning you'd gain 3 1/2 seconds of Huton each 1-2-3 cycle. Assuming (generously) that you're cycling your GCDs for 45s, and then bursting (i.e. not refreshing Huton) for 15s, you would gain ~24.5 seconds of Huton a minute, and lose ~15s of Huton a minute by bursting. In two-minute windows this would be much more severe, as your burst lasts longer which means you're spending less time refreshing Huton.

I don't know if this would be interesting, but it might actually put pressure on managing Huton and minimising downtime. If you disconnect for more than ~9s a minute, you run the risk of Huton dropping entirely.

I don't think I recommend as an option, but it's interesting to think about. I like the idea of Huton being a little more pressured to manage -- or at least a little more flexible. Bring back the 70s Huton cap, please...