Thread: Remove the Class System in 3.0

Originally Posted by Rbstr

There's no reason at all that jobs/classes can't use different weapons. They're "Gladiator's Arms" not Gladiator's swords. Conjurers and Thaums both use 1 and 2-handed weapons. So you have Gladiator's Arm which is a scythe. It's also clearly possible to prevent a Paladin from holding a scythe in this case given Summoners can't use Scholar books. And as you see on Relic Weapons and Armor, it's possible to keep a straight gladiator from using a scythe too.

The actual problem with DRK coming from GLA is two-fold; You do not swing, or even hold, a scythe/zweihander like you would a broadsword. That means adding new animations for every single non-magic skill (notice how using Stone Skin on PLD is the same animation as WHM doing it); GLA is very, very heavily rooted in tanking.

As said in the Gamerescape interview, the fact that there is no mention of new classes but only new multiple jobs during Las Vegas Fanfest was a good catch.

I hope we'll see more about the system changes regarding jobs this week end during the London FanFest, on top of some of the new jobs revealed.

Can't wait!

The class system is a relic from 1.0 they should remove it because it is so useless for the most part. Nobody plays classes except for leveling and once you hit level cap and if you play a class you are gimping yourself and missing key abilities. They would probably have to do a kind of big redesign if they took it out. The best time for that is at an expansion release.

They very well might do it because at fanfest they said new jobs and mentioned nothing about classes.

Originally Posted by kiraan

As said in the Gamerescape interview, the fact that there is no mention of new classes but only new multiple jobs during Las Vegas Fanfest was a good catch.

I hope we'll see more about the system changes regarding jobs this week end during the London FanFest, on top of some of the new jobs revealed.

Can't wait!

Could also mean that new jobs are just added to already made classes and you will get instant level 50 for new job. :P

Originally Posted by Valmar

Uhh I dont know what kind of group youre in but a BRDs songs are helpful. TP Song in T8 for Melee, Foe Req and Mages Ballad for Casters Nuking.

Fixed it for you.

Originally Posted by Zumi

The class system is a relic from 1.0 they should remove it because it is so useless for the most part. Nobody plays classes except for leveling and once you hit level cap and if you play a class you are gimping yourself and missing key abilities. They would probably have to do a kind of big redesign if they took it out. The best time for that is at an expansion release.

They very well might do it because at fanfest they said new jobs and mentioned nothing about classes.

Odd one out being MRD/WAR. LNC too can be an effective OT in Garuda Ex.

What if they totally redisigned new abilities for the classes,, split them from jobs and made them their own jobs?

Originally Posted by Tempting

Could also mean that new jobs are just added to already made classes and you will get instant level 50 for new job. :P

True, but i hope at least they'll find a solution for the instant level 50 job if you happen to have the base class at 50 already

Originally Posted by Rbstr

Considering all jobs need a full set of skills how is is going to be any different? Calling a Thaumaturge a Black Mage from the beginning instead of level 30 does nothing to change anything. Everything has to still be there with or without the aspect of class. Keeping classes, at worst, they need to think of synergy to make it branch to two jobs.

Which, as I stated, is causing them to have to work around the system. True every job will require a set of actions, but having to come up with that way to change things like enmity modifiers on abilities just to support a system that is no longer really valid is just a work around. Removing it and giving separate actions really does mainline development especially now with only one class to have to split (arcanist). If they were to decide to do it after adding more additional jobs its more work. Speaking as a developer, it is almost always more effort to continue to support a legacy idea with patches than it is to devote the upfront cost of changing it. The issue is, most people only look at the initial investment instead of the cost paid in continual upkeep.

My initial reaction.


And then I saw that Akiza was the OP.