[dev1033] Class name changes

[Kilta_Firelotus]

just reading the OP on this one. I like 90% of it minus the sub job class part. I hate that in ffxi due to the cookie cutting enforcement. Which made the game not as enjoyable as it could have been.

[AreeyaJaidee]

This forum needs better iPhone support:

A sidenote on Advance jobs: I think advanced job abilities are going to have to be class specific only. Can't have everyone running around summoning Ifrit or Ninjas charming raptors like. Beastmaster. If basic classes need utilities from advanced jobs (ie: Widescan) they can learn those via guild marks. This helps promote play of the advanced classes as well.

Also, a few people saying that they wish SE would keep the lore of the current classes. To this I have to add: What lore? Each class has 3 quests which last a total of a few minutes minus the travel time and have a
Few NPCs at their guild who speak about the most vague and useless stuff ever. There is little to no lore for just about everything in FFXIV ATM. Please don't use lore as a validation point in regards to sustaining class names when the truth is people are afraid of change. Call it what it really is.

[Anathiel]

I agree with the mobile support lmao. I can't support card's idea though. It seems like the current system but just more complicated. I think it needs to be rehauled but with the ff:tactics system of job advancement. Really, that way is the best way appease everyone. Casuals, hardcore, fanboys...its a final fantasy system that's. Done in MMO style, which imo is what a mmo final fantasy should be

[Cairdeas]

They already said they are not going to completely overhaul the system they are going to augment it.

[Jennestia]

They already said they are not going to completely overhaul the system they are going to augment it.

They said they're looking into two options currently - Both of which they mention will be finalized and no going back so they have to look at it carefully. I play in both languages so that's why I know for certain they definitely want to change or redo the system in a way it makes it diverse.

This forum needs better iPhone support:

A sidenote on Advance jobs: I think advanced job abilities are going to have to be class specific only. Can't have everyone running around summoning Ifrit or Ninjas charming raptors like. Beastmaster. If basic classes need utilities from advanced jobs (ie: Widescan) they can learn those via guild marks. This helps promote play of the advanced classes as well.

Also, a few people saying that they wish SE would keep the lore of the current classes. To this I have to add: What lore? Each class has 3 quests which last a total of a few minutes minus the travel time and have a
Few NPCs at their guild who speak about the most vague and useless stuff ever. There is little to no lore for just about everything in FFXIV ATM. Please don't use lore as a validation point in regards to sustaining class names when the truth is people are afraid of change. Call it what it really is.

This is true, because in FFXI for example, each job actually had a lore or a key role in society, e.g Summoning becoming forbidden magic or Necromancy being outright banned and the last few Necromancers minus the one in Windurst were driven out of the mainlands or underground.

[Athaya]

I have no problem with the current class names. But let the skills learned fit the classes accordingly. SE has done a good job for the most part, but class uniqueness really needs to be a top priorty now!

[Anathiel]

By rehaul, I didn't mean change any of the core classes, but maybe switching some of the abilities around so they make more sense when the advance jobs are released. I wish we could know what the two options they are considering are so we can provide some feedback. Seems sorta useless to argue any point on class changing if they're going to go in a completely different manner.

[AreeyaJaidee]

I agree the FF tactics model of a class tree would be ideal. Idk how plausible that is for SE to implement though.

The important thing to remember is:
- we can have openness and distinction at the same time: basic jobs get renamed/redefined and provide a solid foundation of skills to mix with both basic and advanced. Then have advanced jobs at their own tier, meaning their abilities are not interchangeable with either basic or advanced. This will allow us to have openness through utilizing our basic jobs as support abilities as needed and at the same time we will have defined roles. everyones happy

[Sorel]

I wish we could know what the two options they are considering are so we can provide some feedback.

Naoki Yoshida has stated that the development team is deciding between two options.

1. Jobs become "specializations" within existing classes (i.e. a Gladiator can specialize to become either a Paladin or a Dark Knight).
2. Jobs become "advanced jobs" in addition to existing classes (i.e. a Gladiator or Marauder can become a Dark Knight).

What we've been discussing thus far in several threads is which should be implemented, how either could be implemented, or whether any should be implemented at all.

[Cairdeas]

Naoki Yoshida has stated that the development team is deciding between two options.

1. Jobs become "specializations" within existing classes (i.e. a Gladiator can specialize to become either a Paladin or a Dark Knight).
2. Jobs become "advanced jobs" in addition to existing classes (i.e. a Gladiator or Marauder can become a Dark Knight).

What we've been discussing thus far in several threads is which should be implemented, how either could be implemented, or whether any should be implemented at all.

I vote Option 2