What would you think of the original CLASSES being expanded into full JOBS?

[Controller]

Not going to happen. The devs even said making SCH/CMN share was a mistake. The only thing you'll get from them as fas as those base jobs will be them taking them out the game completely.

[Bright-Flower]

There are a few that could potentially branch into different jobs, only a few at most, and when they could just make brand new jobs not beholden to base classes it just feels unnecessary to me.

I doubt they'll ever remove the classes that are there though. Not only do they have their own guilds and stories that would be awkward to remove, but many of the JOB questlines bring back npcs from the class quests. The paladin SB and SHB quests, the monk SB quests, some of the Ninja quests etc.

[Dyvid]

The real question is who keeps digging up these old post? O.o

[BasicBlake]

Honestly Yoshi P has stated that he doesn’t even like the starter classes and felt trapped by them in the beginning. It’s why nothing new requires them. I wouldn’t be surprised if they got purged in this continuous ARR purging.

[Bright-Flower]

Honestly Yoshi P has stated that he doesn’t even like the starter classes and felt trapped by them in the beginning. It’s why nothing new requires them. I wouldn’t be surprised if they got purged in this continuous ARR purging.

I doubt it, the class stories have their own lore and plots, and often times these creep back into the job stories too. Again, the last couple paladin stories have been more gladiator than paladin, and several other job stories have npcs from the class quests pop in too. I doubt they're going to want to remove them and have to rework the job stories to that degree to cover levels 1-30 and also having to adjust higher level job stories that reference the old class ones. Just seems like too much work for too little benefit.

[Shurrikhan]

I don't want to see the shared roots go away, but I would like to see there be a more thematic split thereafter. A bow makes sense as a weapon for a Bard, but after their split, any further bow tech should be optional and all actual Bard growth should be, well, more support- or musically-oriented. Or alternatively, as a Bard or Ranger, each stemming from Archer, I could choose how much of my playflow I want to owe directly to Archery, rather than to trapping, tracking, or target-marking, or songs, harmonies, and other thematically cohesive but miscellaneous forms of support.

Ideally, I'd eventually like to see a traits selection system, whereby as a Machinist, for instance, I could choose how deeply I want to go into Gunner techniques, Machinist technicraft, Arcanist aetheromancy, Archer focus techniques, Monk gun-fu, etc., in order to perform well in my preferred playflow and aesthetic style. Of course, that'd require that fights not be limited almost wholly to matters of long-term DPS and burst-multiplicity, with most utility a barely noticeable footnote, else our choices would all be made for us rather than providing a means of enjoyably diversifying PuG fights or complementing each others' builds in statics.

[Roda]

I doubt it, the class stories have their own lore and plots, and often times these creep back into the job stories too. Again, the last couple paladin stories have been more gladiator than paladin, and several other job stories have npcs from the class quests pop in too. I doubt they're going to want to remove them and have to rework the job stories to that degree to cover levels 1-30 and also having to adjust higher level job stories that reference the old class ones. Just seems like too much work for too little benefit.

We'd probably see them eliminate classes on the backend, while the player story will still have you progress through the class storylines and graduate to a job automatically. So like class lables and icons would really only be a cosmetic switch in the system instead of assigning a whole new class id to your character. At least it's probably the cheapest/easiest way to "get rid of classes" in a way that won't call for massive retcons.

[RitsukoSonoda]

While it's never going to happen, especially given how the devs have repeatedly brought up the back end issues caused by Summoner and Scholar using the same base, it's definitely something I would like to see. For me, I'd much rather have a pure Archer class rather than a pseudo support Bard.

TBH I think it had less to do with actual back end technical issues and more to do with people complaining on the forum when an SCH joined their duty in DF that had severely outdated gear and was being played by someone that didn't know what their skills did and decided to queue healer because they didnt want to wait for the DPS queue on their SMN main.

[RitsukoSonoda]

There are a few that could potentially branch into different jobs, only a few at most, and when they could just make brand new jobs not beholden to base classes it just feels unnecessary to me.

I doubt they'll ever remove the classes that are there though. Not only do they have their own guilds and stories that would be awkward to remove, but many of the JOB questlines bring back npcs from the class quests. The paladin SB and SHB quests, the monk SB quests, some of the Ninja quests etc.

Random thoughts...

Lancer -> Templar (tank)
Thaumaturge -> Sage (Healer)
Conjurer -> Geomancer (DPS) They could have done this before introducing Geomancer as what they did on the AST quests later.
Gladiator -> Fighter (DPS) They could have even added swordchucks if they wanted.
Marauder -> Berserker (DPS)
Archer -> Made BRD a healer role adding more support skills and healing abilities. Make Ranger a DPS branch.
Pugilist -> Made the DPS role path Blackbelt. Designed MNK as a healer type
Rogue -> Duelist (Tank)

So I mean it was easily doable back when they did ARR. Most of those could be done now if they really wanted to. The problem areas are the 2 jobs using titles that would have been better suited to the other role proposed and the 1 that had it's title used for story fluff later for a different job. Doing it now would generate mixed reactions however. You'll have people that like having more options. Then you'll have others that complain about it for various reasons such as more people potentially being able to queue a role at higher levels they hardly ever play.

[HeulGDarian]

Random thoughts...

Lancer -> Templar (tank)
Thaumaturge -> Sage (Healer)
Conjurer -> Geomancer (DPS) They could have done this before introducing Geomancer as what they did on the AST quests later.
Gladiator -> Fighter (DPS) They could have even added swordchucks if they wanted.
Marauder -> Berserker (DPS)
Archer -> Made BRD a healer role adding more support skills and healing abilities. Make Ranger a DPS branch.
Pugilist -> Made the DPS role path Blackbelt. Designed MNK as a healer type
Rogue -> Duelist (Tank)

So I mean it was easily doable back when they did ARR. Most of those could be done now if they really wanted to. The problem areas are the 2 jobs using titles that would have been better suited to the other role proposed and the 1 that had it's title used for story fluff later for a different job. Doing it now would generate mixed reactions however. You'll have people that like having more options. Then you'll have others that complain about it for various reasons such as more people potentially being able to queue a role at higher levels they hardly ever play.

How dare you sir.
Rogue would have obviously have thief as a side class