I've seen all this stuff about Adding new jobs to existing classes

[lokilullaby]

I'm just wondering, how do y'all think that would work with leveling? I mean...let's say my BRD/ARC/is level 60. They add in Ranger. Doesn't that put Ranger automatically on level 60? How would they balance that, and wouldn't that be detrimental to LEARNING your job?

[ErryK]

Except we've got a lot of people that played MCH, DRK and AST from Lv30 and didn't complain about the learning aspect?

[lokilullaby]

I mean the fact that if you have a max level class, and they add a new job to it, it'll start max level. Yea, you'd still need job quests, but for the most part you could just run through them. MCH DRK and AST starting at level 30 isn't the same, because you still had to go through 30 levels, which gave time to learn the job.

[Derio]

They would probably give the Job itself actual level, with the abilities from the original class built in. Example: Original class is lvl 60. start off as lvl 50 Ranger.

[lokilullaby]

I suppose they could do that, make it where in order to unlock the quest that unlocks the job, you have to have the prereq classes, then it works like DRK, AST, or MCH. So, require Archer and whichever class to be such and such level, then just give it the soul crystal, so you're the new job. Make weapons interchangeable till a certain point, then split them off after, similar to how SCH and SMN work, and then the levels would still be there for learning purposes. give cross class skills with ARC/BRD for the levels, or have them come wiht levels, and RNG specific actions pop from quests.

[Niwashi]

I'm just wondering, how do y'all think that would work with leveling? I mean...let's say my BRD/ARC/is level 60. They add in Ranger. Doesn't that put Ranger automatically on level 60? How would they balance that, and wouldn't that be detrimental to LEARNING your job?

Sounds like playing Scholar to 60, then unlocking Summoner and having it automatically start at 60, or vice versa. (And yes, that is rather detrimental to learning it, but it's how the game is working now.)

[Normalizer]

Sounds like playing Scholar to 60, then unlocking Summoner and having it automatically start at 60, or vice versa. (And yes, that is rather detrimental to learning it, but it's how the game is working now.)

SCH/SMN were a mistake they never want to make it again. Also they have already said many times they won't branch new job from current classes anymore, too many troubles with balancing. SE wanted to kill off the classes but couldn't. All new jobs will probably like HW jobs and will start at lvl 30, no base class.

[jazo]

easiest way would be a level cap increase on par with those new alternate jobs, but the problem of knowing the job like SCH/SMN would be more spread out

so what if the levels beyond 60 would be job exclusive. but that would make the point on dual classes moot.

So what if we get branching jobs after 60 (2 of each class) and you choose only 1 of the branch to level (and doing something like a quest to reset the level to try the other and only when you have the 2 at max level and complete their quest switchable (and even gain a skill that benefits both branches).

[lokilullaby]

So what if we get branching jobs after 60 (2 of each class) and you choose only 1 of the branch to level (and doing something like a quest to reset the level to try the other and only when you have the 2 at max level and complete their quest switchable (and even gain a skill that benefits both branches).

The problem I see here is that that would only work if both classes focused the same stat. I mean, My SMN is weaker because I spec'd for SCH, and the same issue would persist there.

[Rufalus]

The short answer is they are not doing this, with Heavensward setting the precedent for jobs which have no base class at all.

At this point, I think it's probably for the best. Jobs sharing classes is going to make them excessively similar and limit creativity.