Easier to create new jobs than base classes?

[FaileExperiment]

RE: classes vs jobs, for me the biggest design issue is that the classes continue leveling past the point where you can assign a job. Personally, classes should have stopped at 30 period, and to continue leveling you'd have to assign a job. All the class base abilities should be learned by 30 ( which might have required some ability simplification, but seeing how bloated skills are now that would have been a good thing). That way, adding new jobs would be easier to balance, and they'd start at 30 so not cumbersome to level, while still making you learn the class.

[Dorander]

I really don't get why we can't have more divergent classes into other jobs.

Marauder could branch into Berserker, dropping all his extra tanking abilities to allow for more DPS options.

Gladiator could branch into Myrmidon, dropping the shield along with shield abilites to pick up a second sword, to do dual wielding sword to turn into a DPS.

Pugilist could branch into Brawler, gain a stance that increases HP/Threat, and drop positionals on their abilities while dropping their damage.

The base abilities of these classes wouldn't change any, and you'd unlock their job abilities one by one, so wokring out how they play different should be that rough.

If they're not going to bother doing anything more with base classes/jobs, just drop the concept already. Jobs vs Classes are strange to new players, especially if they're ultimately pointless and no one has a good answer to anyone when they ask why it's set up that way.

The reason why they won't be doing this anymore is because of how much of a pain Scholar and Summoner are to balance code wise, and on the players side gear out, since they branch off the same base class. So, the likely hood of branching jobs happening anytime in the future in very very slim.

Also, once you hit 30, you put on your crystal and thats that. If you don't have it on, you start missing out on the stat bonus, the skills (which is only going to get more apparent as we go higher in level and get more skills and possibly traits), and the job specific gear. Like I've said in another thread, they need to just level cap base classes at 30. There really is no reason not to at this point. Toss all existing 30+ skills and traits on to the job (allowing a complete rework of scholar) and shuffle down cross class skills that are level 30+ to bellow 30. Which is easily doable and not game breaking by putting the level 34 cross class skills at 28 (in pugilists case put mantra at 28).

The reason why it's set up this way is because it's a hard coded remnant of 1.0 and because it's a FF1 staple to do a job change/advancement. If it was done like my suggestion, we really wouldn't have to worry about people being a 50+ archer because "They don't want to be a bard!" in any dungeon past Haukke Manor. It would force players to get their job crystal if they wanted to advance further.

[Bourne_Endeavor]

They need to admit they goofed and just remove the class system all together. Give each job unique abilities that fill the current cross class meta and just smash the storyline quests together.

Nothing will be lost asides the relic of a system holding the developers down.

They've essentially done this already. None of the new jobs will ever have a class nor will current jobs be able to learn new abilities as a class. There's no point in officially pulling the system out of the game entirely.

[FeliciaTheSecond]

I think they really need to overhaul the way this system works in this game. The cross class thing was one of the little things that made the FF MMO unique and at this point I don't know why they don't just get rid of it entirely with the treatment its gotten. I was really disappointed that rogue didn't have any cross class abilities for existing classes when it launched.

[KitingGenbu]

The dev team screwed themselves when they 1) made jobs in this game bound by weapons and 2) made classes + jobs. They would have more flexibility if they had just made jobs from the beginning instead of adding this "growing immersion" element that some people feel (like I'm training as a conjurer to become a white mage). In theory it sounds nice, but they realize what they did and are now trying to slowly untangle themselves out of this web. Flexibility with weapon types would allow them to add any job they wish in the future without fear that they will run out of job and weapon pairing, which in itself is kind of silly since white mage and black mage honestly use the same weapon type. Sure a cane is slightly smaller than a staff in reality but in this game, the weapon model sizes of both the white mage and black mage are identical. People honestly think this game is so polished and to a degree it is but honestly, the ideas lacked too much forethought and as time goes on it becomes more and more clear to more and more people.

One thing you can respect about Blizzard is that they are bold enough to revamp their class systems given how long the game has been out and for a little bit it greatly increases their sub base. Maybe the dev team and SE will learn by 5.0 that they have to go back to drawing board with a lot of their "core concepts" that people believe the team honestly believes in.

[JustPlainLucas]

I kinda miss the sub class system of FFXI. I know the cross class system in XIV works similar to that, but FFXI allowed you to really experiment and make something unique. As for new jobs, I really hated that the HW jobs started at 30, because I felt robbed of time getting to know the role. The first time I started leveling DRK, I had no idea what I was doing because I had like 16 skills and abilities to learn at once. Starting off at level one feels like you're spending time getting to know your job. Starting off at level 30 feels like you just took over someone else's character.

[Alaltus]

They shouldn't do a job starts above level 1 again. I really didn't like being landed a ton of actions and have to sit and figure out what each and every single one does. And at the same time try to work out where to put them. Levels 1-30 don't take that long to play through anyway and it lets you get aquainted with the jobs mechanics and gives low levels more players to play with. Classes aren't really an issue but adding more classes is. If they changed it i would be in favor of that so long as they added depth into the system; not so they can take away choices or repackage what we already have.

[MilesSaintboroguh]

I don't think the devs would keep having new jobs start at level 1. If jobs are going to be gated behind expansion packs like Heavensward did, then people are going to get tired of having to go back to very old areas just to level up their new jobs (or new low level areas if they even do that) before they can even begin to use them in the new zones and dungeons. I don't want to have it where 75 is the next cap and I have to start at level 1 and play the same old content for the umpteenth time for a new job.

[Alaltus]

I don't think the devs would keep having new jobs start at level 1. If jobs are going to be gated behind expansion packs like Heavensward did, then people are going to get tired of having to go back to very old areas just to level up their new jobs (or new low level areas if they even do that) before they can even begin to use them in the new zones and dungeons. I don't want to have it where 75 is the next cap and I have to start at level 1 and play the same old content for the umpteenth time for a new job.

Your still going to have to do low level content for the uptenth time anyway just not as low level. They have other ways they can mitigate it like more lv 1-x exp rings etc.

[Jynx]

There's no point in officially pulling the system out of the game entirely.

Actually there is a point a good one.

They can get rid of cross class skills and focus on keeping each job unique and diverse giving them their own solutions to common problems while maintaining the flavor of the job and adding more diversity to the jobs themselves so everyone isn't so samey.