Why would they make the change "to avoid confusion," if that wasn't the case? To assume something as simple as Firaga vs Fire III would be cause for confusion is to assume your customers' brains are leaking out of their ears.
I mean, I've seen what players are like in DF, so it's not far off, but to assume that it's only a problem for the English localization? It's dumb.
And when SE is generalizing the player base for FFXIV, it's a much, much broader audience than is going to be attracted to Theatrhythm. The LCD that will be catered to is different between the two.
I don't play BLM so it's whatever, as I said I just think the situation is funny.
Idk, it could of been to avoid confusion or not, I wish I had the answer. I just don't really see why they'd add it into older and newer games then say well you're suddenly really dim.
Plus is it just in FFXIV english version that this occurred in, that's a question that I have. I don't have a client of JP or EU nor can I translate from JP to see if they say Fira or Firaga but it could be the same as ours.


I do agree the simplification of spells has gone overboard. It's just laughable that they just blanketed the whole west to be "slow", yet they introduce a crap load of one shot mechanics that are not "slow" friendly. But maybe players and SE can meet halfway? Like the varying voice acting/languages and UI modifications, maybe they can also add something related to naming etiquette regarding spells.
Normal (default) : it would function as it is now.
Classic (optional) : displays classic spell terms like cura/fira etc.
Advanced (optional) : for players that wanna modify everything, maybe can rename spells (not just making a macro that doesn't have the text popup)

^this would be fair to everyone pleases us classic fans and makes it simple for the idoit newbis who would get confusedI do agree the simplification of spells has gone overboard. It's just laughable that they just blanketed the whole west to be "slow", yet they introduce a crap load of one shot mechanics that are not "slow" friendly. But maybe players and SE can meet halfway? Like the varying voice acting/languages and UI modifications, maybe they can also add something related to naming etiquette regarding spells.
Normal (default) : it would function as it is now.
Classic (optional) : displays classic spell terms like cura/fira etc.
Advanced (optional) : for players that wanna modify everything, maybe can rename spells (not just making a macro that doesn't have the text popup)
advanced would be cool for alot of ppl i myself wouldnt use it but i know alot of people would
I would approve of this kind of option, but wouldn't it cause some confusion to some extent? Since everyone has different preferences, how would people differenciate between Fire II and Fira, given that Fire III was named Fira because it is a single-target attack?
And I'm sure a lot of people would complain if the naming conventions were Fira (Fire II), Firaga (Fire III), and so forth. Since Fira would be an AoE and Firaga a single target, you'd get people who would be like, "yo se wai firaga no aoe laik fira? Fix plx"
Of course, you could reverse it, but then you'd get people who would argue, "like yo se why firaga dose tiny damage than fira fix pls"
The current naming convention is determined by the order you receive the spell. So I guess that doesn't overcomplicate things. They may need to completely rework the DoM classes if they were to change the current naming conventions. Other languages may have the -, -ra, -ga prefix, but according to their response, it is because it fits and makes sense in their respective language.
Last edited by AdamFyi; 10-15-2014 at 12:42 PM.
Besides all this simplification to make spell names less complicated, there is one thing that still wonders me. Esuna is called "Medica" in german while Medica 2 is called "Vitaga" in german. So if you tell a newbie-german to use medica 2, he might think it is some kind of aoe-esuna.



I'd like to add that this was not a decision made by Square Enix but by the english localization team. While SE has done some bad things in the past, let's not just blame the entire company for a small teams decision. Ferne was very specific about that in his post back then, saying they wouldn't be allowed to change Phoenix down or something like that to Phoenix Feather. I still very much disagree with the English localization teams decision for this (and many other things in the game they've done which just add confusion when they think its supposed to be simple).
And while I don't mean to diss Ferne or his team. They've done lots of wrong with EN FF14. Picking a (at the time) unused monster name from FFIII just because they couldn't use Titan, Messing up the fruit descriptions, absolutely destroying the worth of Hunt hints, requiring us to get the JP ones translated to actually have correct spawn conditions, then there's the naming convention meant for simplicity that can't even do that(This is why so many BLM just spam Fire III).
Translation and Localization isn't an easy task to accomplish and mistakes happen. But owning up to those mistakes and changing them? They only did it for the monster they messed up. Our hunt hints are still abominable , those dying fruits are still absolutely incorrect, and even though I II III conventions were proven many times to be more confusing, we still have that. Now the other teams aren't perfect either with localizing, but my very first time booting up 2.0 in beta and seeing the intro text, I knew putting faith in localization would be a bad idea for FF14.
ITT: People will complain about anything.
also
ITT: People that don't read spell descriptions won't know the difference between I II III & -ra -aga -ja either.
PS:
Firaga
/micon "Fire II"
/ac "Fire II" <t>
Last edited by Dhex; 10-15-2014 at 07:36 AM.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.

Reply With Quote



