Quote Originally Posted by Alkar View Post
Right now we have 1 class going into 1 job. When they decide to include more job options for said class they could always include new abilities for classes and lock some when switching to jobs.
Let's take Gladiator as an example: right now the class is a pure tank with a lot of tanking abilities so it's natural that Paladin gets access to everything GLA has to offer. If they want to add DRK to GLA all they would need to do is add a new set of abilities to the base class (thus making classes even more varied than they are now) that aren't tank oriented and then ,when switching to DRK, you'd lose all those tanking abilities while keeping the damaging buffs and add more with job exclusive abilities. The opposite for Paladin.
If you're going to create 2 or more unique sets of skills for GLA just to accommodate jobs, then GLA itself is unnecessary. (which its already is!) and jobs should exist on their own.

Also if GLA has access sets of abilities (currently 20 so multiply that) for 3 jobs (thats 60 abilities) that would be super convoluted.

Quote Originally Posted by Ryans View Post
Thats not a bad idea, have classes stop learning abilities after 50, or at least at a lot slower frequency, and make jobs get the rest of the new skills from that point on. I could see that working with a level cap increase if each job learned enough new abilities to really differentiate itself from its base class.
Then why have classes at all if PLD75 would have so many more (I'm thinking 10 more atleast if we get 1 every 5 levels) skills than GLA75 (which will still have the same number it had at 50 and the same cross class abilities since all other classes stopped gaining skills at 50)

Down goes classes!