Armoury System is Broken

[Jre418]

I have noticed that when you unlock a job nobody ever goes back to their class. The whole system should be redone with the removal of all classes and just keep the jobs. They should then bring back the sub job system which makes more sense then what they have now.

[AlexiaKidd]

I agree, the armoury system in it's current form is the remnants of a broken system. They should have just got rid of Classes while they had the chance or kill the Class at 30 when you unlock your Job, which they could have easily done but have now gone and buggered that up by letting Arcanist unlock both Scholar and Summoner.

They could have let the class end at 30 and then you level your Job after that which would have meant you could level Summoner and Scholar independently. As it is now if any other "Classes" get secondary Jobs attached to them most people will be an instant level 50 in that Job and breeze through the few sidequest you have to do to unlock the skills.

I think it was pretty stupid of SE to let this happen and I'm sure it will cause them headaches down the line.

[Dhalmel]

It's situational, in some cases you need the flexibility of the armory classes instead of job to clear something.

1.0's Riven Road Hard (Nael Van Darnus Hard) would be the best example of this situation.

[AlexiaKidd]

It's situational, in some cases you need the flexibility of the armory classes instead of job to clear something.

1.0's Riven Road Hard (Nael Van Darnus Hard) would be the best example of this situation.

But is there any situation in ARR where an example could be given?

[Dhalmel]

But is there any situation in ARR where an example could be given?

Well ARR hardly has the challenging content where flexibility has the advantage.(yet)

Maybe PvP.

[AlexiaKidd]

Well ARR hardly has the challenging content where flexibility has the advantage.(yet)

Maybe PvP.

So the answer is no? 1.0 was built from the ground up for the armoury system with a Job system tacked on top of a shaky foundation. ARR is not, so why implement it?

All it will do long term is give SE headaches because instead of having to balance content for just the Jobs they will also have to consider possible Class combo's to. It does seem as though SE's way of dealing with that though is to just make Job superior that way they don't have to worry about people using Classes. Which if thats the case why do we still have them?

This situation with SCH/SMN being levelled off the same Class really irks me though as I personally can't wait and hope DRK gets implemented at some point and I would hate for it to come off LNC or something and I only have to do a few quests to be a Level 50 DRK.

[Flionheart]

Fine with Class > Job advancement, not fine with subjobs.

Subjobs were one of the worst parts of XI. They made every DD feel generic and samey.

[Jre418]

Every DD in this game feels more Generic and samey then ff11 ever did.

[Arkista]

Fine with Class > Job advancement, not fine with subjobs.

Subjobs were one of the worst parts of XI. They made every DD feel generic and samey.

Subjobs made playing a DD job different /war /nin /sam lots of different set ups so you could be different. FFXIV at some point everyone is going to be the same nothing to set us apart from one another.

[AlexiaKidd]

Fine with Class > Job advancement, not fine with subjobs.

Subjobs were one of the worst parts of XI. They made every DD feel generic and samey.

I do kind of agree with this, while I did overall like the subjob system from FFXI as you could have some great and varied combo's, I do not want a repeat of /NIN please. I think the idea of subjob is fine just don't a give a class/job a skill that make everyone demand you use it. Like I said earlier I used to love playing DRK and using a variety of subjobs like /SAM for the WS bonanza or /WAR for procs on double attack and buffs to put out silly high number WS's, if I went out soling I could use /DNC for some extra cures. I did however hate it whenever I would get a party and then get told please go /NIN :-(