Quote Originally Posted by Gandora View Post
It is, I'm a main WAR, if DRK is a DD that come from MRD main, i'll have to get 50k GC credit everytime I want to change job, because i'll be loled at as WAR with 30 STR, or loled at as DRK with full VIT..

SCH & SMN are facing this problem currently if you did not know.

I really wonder if the majority of the posters think before posting on this forum.



also this ^
It may not be *that* bad for DRK, depending on how it's implemented. Darkness/Souleater often increases the damage done/augmented when you have higher hp, so it's possible high hp could be a benefit for a DRK by increasing their max Darkness/Souleater damage.

Aside from that possibility, they probably need to change it so that the jobs have their own stat allocation separate from the base class.

If they don't there's other ways to look at it. The game sort of encourages you currently to focus on a main job. With lockouts on coil and the weekly myth cap, you can't really gear 2 classes with the best of the best stuff at the same time. You focus on one, getting your +1, myth and allagan gear for that, and gear up your alts in gear from the next tier down. Your alts won't be *as* strong, but they'll be pretty good. It goes a little further if your alt uses the same base class, you don't get optimal stat allocation for your alt job either. But it will still probably do a pretty good job in most scenarios outside of the top tier raids as long as you gear it up with the best available outside of the gear that's limited by caps and lockouts.

Also, even then, you can sort of get around it. Don't main/alt two jobs in the same class. If you want a tank and dps, and you *must* have a DRK (assuming DRK is based of MRD), then make your tank a PLD. May not be your first choice, but then you get to allocate the stats the way you want to.

Anyhow, you may not *like* that classes can branch into 2 jobs that focus on 2 different things, but it's a system that they've pretty much assured us they're going to expand. It's much less work for them to add new Jobs based on existing classes so they figure they get more bang for their buck (more jobs, less work). So you can argue against it all you like, I don't think it's going anywhere any time soon. Best to make suggestions that work within that framework. You'll probably get further and be less frustrated with it.