Easier to create new jobs than base classes?

[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.

[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.

[Shurrikhan]

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. Classes aren't really an issue but adding more classes is.

But, at level 30 you had essentially only 9 skills, only three of which were at all new to anyone who's played a tank: enmity combo, dark-RB Combo, mana-Lob*, dark-Flash, dark-Brutal Swing*, dark-Fracture, dark-Rampart, tank stance, and (stackable) damage stance*. They take barely a minute to read and set up on your bars. If you have used played any tank, used Blizzard II or Flash, DoTed, or stunned an enemy before, there's only 1 truly new button to figure out. (I keep this Darkside thing on, but, how would it run out in anything but the most massive AoE spams anyways?)

Levels 1-30 don't take that long to play through anyway and it lets you get acquainted with the jobs mechanics and gives low levels more players to play with.

It makes little sense for a hero who must be at least level 50 to necessarily drop to level 1 to take on a new form of an old role. Of course, I'd say that's an issue I have with the class and job system in general, as well.

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.

That's pretty much how I feel on the subject as well. To replace cross-class skills with native job/class forms that function almost identically anyways seems a wasted opportunity.

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.

This can also be done while still being cross-classed. You borrow a concept from another job, such as TP restoration. The borrowing job in turn pulls that off in their own style. At that point the only real question is whether you want to have more than 60 levels of character progression. In the present system you're done at, say, 60/26/12. In the other, you're done at 60/15 tops, or if having removed even the off-class requirement for jobs, at 60/0/0/0/0/0/0. On to the next role.

Now, I'd be cool with that. But let's keep things in perspective. The mere fact you have that a set of abilities, from which you have an amount learnable exceeding the amount equippable, learned through and shared by various classes, does not mean that every class would be unable to use an individual form of each of those abilities (even if each by a different name). That is a separate issue.