Quote Originally Posted by Sorel View Post
One of the problems with direct one-to-one, two-to-one, or X-to-Y restrictions is that the raw numbers make it a mess.

(using the ":=" nomenclature for assignment)

You can't have Job := Role because there are only 4 basic Roles in a party (Healer, Damager, Tank, Support), and there are at least 6 basic Jobs in Final Fantasy (White Mage, Black Mage, Red Mage, Warrior, Thief, Monk).

You could add Paladin, Dark Knight, Dragoon, and remove the generic Warrior Job. That would give us 8 Jobs total. Then you can *attempt* to assign 2 Jobs to each Role.

Damager := Black Mage, Dark Knight
Tank := Paladin, Monk
Healer := White Mage, ??Red Mage??
Support := Thief, ??Dragoon??

See the problem. It's hard to use Jobs to help define Roles when half the Jobs themselves don't neatly fit into Roles, or a Job can fit into 2 or 3 Roles easily (like Red Mage).

Now there is nothing to say that Jobs and Roles should be balanced on assignment. I'm pretty sure I'm currently arguing against that.

But on the other hand, not balancing the Roles evenly between the Jobs would lead to ultra-versatile Jobs that can handle multiple Roles (like Red Mage). Those Jobs would be in higher demand, more valuable, and thus more powerful than the Jobs "specialized" in a single Role (like Paladin).

Something to think about, I guess.
Crazyness! Dark Knights are tanks too

and they should keep the generic warrior job.