Why only 1 job per class?

[Betelgeuzah]

I recall him saying they were thinking of not making it as simple as just leveling one class to 30 and then unlocking the Job. One class to 30, another class to 15 => ability to unlock a Job.

If classes are to receive more than one Job in the future, there will be some interesting problems the dev team has to solve. If you toss one class a bone, you need to do the same for all other classes.... current and future. 2 Jobs per class? Every future class needs to have 2 Jobs as well, by default.

If they implement one Job per class, they will have an easier time in the future as well. They still need to bring both class and a Job to the game at once (well, nothing says they have to, but a class by itself won't be of much use), but at least it'll be easier than to implement a class and 2 Jobs at once.

They could also implement shared Jobs to keep the classes on an equal ground without having to do so much work in the future. But other interesting issues arise from that; if Jobs follow a class (and vice versa) in level progression, which class should these Jobs share their levels with?

[Sephrick]

Right now I could seperate most classes in 2 jobs:

That's great. Now give them abilities designed for a specific role but also so that they feel unique from other jobs in the same role; balance them so no one job is too much more powerful than another; design weapons, armor and animations; and flesh out at least five quests each. So simple.

And Yoshi did say in an interview over the summer that it was 1:1 just for now.

[Raistlin]

coz if your class auto-level your job to 50, has no sense to autolevel 2 jobs to 50.

In my opinion, autolevel fails.

[Shneibel]

coz if your class auto-level your job to 50, has no sense to autolevel 2 jobs to 50.

In my opinion, autolevel fails.

the right thread Job Auto-leveling Yes or No

[Raistlin]

this is too the right thread... is my opinion about why we canot have 2 jobs per class. Because u will have a free job leveled.

[mesterjester]

it may actually go the other way, needing multiple classes to unlock a single job.

from this interview at rpgsite: http://www.rpgamer.com/news/Q4-2011/101811b.html

the relevant bit is this:

Another major change in the pipeline is the addition of a job system to compliment the current class system. Yoshida states that jobs will not be replacing the classes, but will be built upon them when they are introduced in version 1.21, coming in early 2012. The example given was for unlocking the Paladin job quest. Players would first need to level the Gladiator and Marauder classes to level thirty and then complete a job quest. Once completed, Paladin would become available on top of the class system, almost like a subjob. Leveling up the Paladin would also increase the strength of the original job, Gladiator, and open a new job-specific quest every five levels or so. These jobs will grant unique skills and bonuses that can mix and match with the original armory class system, so a Paladin would gain abilities to help in playing a tank role.

so we might have to level multiple classes that all contribute to the skills of that job.

i can easily imagine needing gla,con and thm to unlock red mage, since red mage has features of all those classes.

[Betelgeuzah]

Okay... what determines which Class the Job shares its levels with if, say, both MRD and GLA need to be leveled to 30?

Will every Job have 2 class requirements? Will each have its own combination of classes, or can you, say, unlock BLM and WHM at once by leveling CNJ and THM?

[Wynn]

it may actually go the other way, needing multiple classes to unlock a single job.

from this interview at rpgsite: http://www.rpgamer.com/news/Q4-2011/101811b.html

the relevant bit is this:



so we might have to level multiple classes that all contribute to the skills of that job.

i can easily imagine needing gla,con and thm to unlock red mage, since red mage has features of all those classes.

I think the tactics approach is exactly the way the game should have been and should be going forward. It makes so much sense for the armory system that it completely blows me away that isn't what they did.

But this reported system is still not a true tactics-like system since the job is tied to one specific basic job and auto levels. Ah well... whatevs.

[Carpe]

They could also implement shared Jobs to keep the classes on an equal ground without having to do so much work in the future. But other interesting issues arise from that; if Jobs follow a class (and vice versa) in level progression, which class should these Jobs share their levels with?

This is basically what I hope for in the future. I think you solve the problem you mentioned when you stop thinking in terms of "level progression" but in terms of a stance or mode that your class can take. So for example I unlock the Paladin job by quest after meeting the level requirements from certain classes. Now my Gladiator can go into Paladin mode by equipping a "job stone". This would probably alter his stats so they are more like a "Paladin" (lower his str and int a little and increase his vit and mnd). Going into this mode blocks him from using some actions from other classes and gives him some new abilities to use. Each time I meet the next threshold of class level requirements (ex. 35, 40, 45, 50) I unlock a new quest that gives me some new abilities. Let's say each time I finish a paladin job quest I rank up my paladin like "novice", "apprentice"..."master", etc.

Now let's say I want to use the Paladin job with my Marauder. Let's say my paladin job is maxed out, but my Marauder is only level 40. Then all you need to do is have the abilities that you learn at each tier of paladin (30, 35, 40, 45, ...) have a class level requirement. So the Marauder can equip Paladin but only use up to level 40 paladin abilities. When he hits 45 he cause use level 45 paladin abilities without having to go back and do a paladin quest again.

It really depends on how much the Job abilities will be dependent on the core classes. If Paladin abilities do a lot of things with shields then it wouldn't make sense to have a Paladin mode for Marauder.

But I like the idea of having classes being able to share a common job. This gives you a little more choice in playstyle since the Job supports your ability to perform a role, while the class determines the underlying mechanics for how you will perform that role.

[Carpe]

Okay... what determines which Class the Job shares its levels with if, say, both MRD and GLA need to be leveled to 30?

Will every Job have 2 class requirements? Will each have its own combination of classes, or can you, say, unlock BLM and WHM at once by leveling CNJ and THM?

I think the multiple class requirements are just to give a final fantasy tactics feel to unlocking jobs and to make sure that someone who has unlocked the job has a sufficient pool of abilities to choose from to perform that job. Like we see in the game now, your ability to tank increases greatly if you've aquired skills not just from Gladiator but also from Marauder and Pugilist. Having this additional requirement forces ppl to learn some of these skills so they'll be less gimp at doing what the job is intended to do.