Giving each job a second spec: would it work?

[justinjarjar]

Sorry but it seems to me the argument behind this changes any time it's brought up.

First it's "Arcanist was a failed experiment" except that the Jobs stemming from Arcanist are both very successful and exemplary in their roles.
Then the argument becomes "Well Devs don't like it" because it's extra work for them to balance stuff? Isn't that what they have to do any time the release anything new? Are all the jobs really on equal footing because last I checked there is still an optimum party setup...

So basically your argument is "We can't have this thing that your asking for because it takes Devs time and effort to make that." To which I would respond - well duh. Anything we ask for takes time and effort to make - be it a minion, or cash shop mount, or anything else.

no the devs are on record saying they did not like that direction. Completely different.

[Dhex]

no the devs are on record saying they did not like that direction. Completely different.

So if Devs decide they don't like something - even if players request more of it because it's successful from a functional and practical use standpoint (SCH/SMN) - they shouldn't consider it?

[justinjarjar]

So if Devs decide they don't like something - even if players request more of it because it's successful from a functional and practical use standpoint (SCH/SMN) - they shouldn't consider it?

Never said to not bring it up, but the OP asked would it work? The answer is the devs don't want to go that direction. You can clearly see that with the new jobs DRK, MCH, and AST going completely away from the class system, which is most likely how we will see new jobs (no one has explained to me why the new jobs are badly implemented). And this forum is split, so in that case the devs view point (which is final anyways) is going to be more important. If it was all yes best idea then maybe the devs are missing something, but it is not.

[Delily]

So if Devs decide they don't like something - even if players request more of it because it's successful from a functional and practical use standpoint (SCH/SMN) - they shouldn't consider it?

Short answer, yes, because players and designers have 2 different definitions of what's successful, and the designers are able to accurately measure how well a change is doing.