Wut? Maybe with skilled enough people, the brd doesn't need to play ballad. But the brd needs to play tp song, for example, in turn 8, especially if there is a skilled mnk in the party.
Uhh I dont know what kind of group youre in but a BRDs songs are needed. TP Song in T8 for Melee, Foe Req and Mages Ballad for Casters Nuking.
A DRG is generally gonna run out of TP before the MNK. Especially if the DRG does what its supposed to do and die mid-fight.
I like classes, simply because it makes the Job feel more special from a lore perspective. Lots of people are thaumaturges, anyone can train to be one! But you're a black mage because you're awesome. So it gets "discarded" in usage. I don't really think that's a bad thing.
The second reason is that I like one class being able to split into different roles like Summoner and Scholar. They should keep doing that, they just need to make bonus points a per-job thing when the split causes you to use a new primary stat.
The idea you're limiting jobs to X weapons or Y skills is artificial and fixable.
My real disagreement with the system they have in place now is that the class and job share levels. I'd love to see you unlock a new job but it starts at level 1 (or hey, it starts at 30, why not...) but has its own advancement in levels from there. Your example brings up the big problem with it. Summoner and Scholar. I focused on Scholar before anything in 2.0, was my first 50. And you know what? I magically had a level 50 Summoner too that I just had to do a handful of quests to unlock.The second reason is that I like one class being able to split into different roles like Summoner and Scholar. They should keep doing that, they just need to make bonus points a per-job thing when the split causes you to use a new primary stat.
The idea you're limiting jobs to X weapons or Y skills is artificial and fixable.
It'll be the same if they add new jobs to existing classes if the system stays as is. Something has to change. If, for example, in 3.0 they add Dark Knight as a job for... i dunno. Lets say Gladiator because swords (Really, Just using it as an example, not saying it will or should be this class or anything of the sort). That means a level 50 Paladin just has to do about five quests or so, then they have a level 50 Dark Knight.
Last edited by Mysteran; 10-23-2014 at 05:13 AM. Reason: Character Limit..., typo
I would say give the Class system time to expand. It does no harm to the game being there. You are going on a progressive route to 50 ability and level wise. Not to mention, what Yoshi-P said during the expansion announcements was "New Jobs", meaning possibly just new jobs attached to a previous class. Only thing SE really needs to change is letting you allocate stats within a job and not the class itself.
That PLD still needs to get gear for DRK, assuming DRK is the melee DPS counterpart. Which arguably is the hard part of getting a character ready, not necessarily the route from 1-50.My real disagreement with the system they have in place now is that the class and job share levels. I'd love to see you unlock a new job but it starts at level 1 (or hey, it starts at 30, why not...) but has its own advancement in levels from there. Your example brings up the big problem with it. Summoner and Scholar. I focused on Scholar before anything in 2.0, was my first 50. And you know what? I magically had a level 50 Summoner too that I just had to do a handful of quests to unlock.
It'll be the same if they add new jobs to existing classes if the system stays as is. Something has to change. If, for example, in 3.0 they add Dark Knight as a job for... i dunno. Lets say Gladiator because swords (Really, Just using it as an example, not saying it will or should be this class or anything of the sort). That means a level 50 Paladin just has to do about five quests or so, then they have a level 50 Dark Knight.
Foe Req and Mage's Ballad aren't strictly needed. It's not like healers run out of MP in every fight, and in my experience if they ARE there's a wipe coming soon whether or not ballad is up. Foe req is a convenience more than anything and completely pointless if you have no caster DPS in your party.
TP song maybe, but i've only seen one fight where that's cited. Recovery from death doesn't count, as my assumption is against encounters where no one is actually messing up.
Just as there ARE situations where the songs could come in handy or are necessary, there are also situations where they collect dust on the hotbar. Most of the songs are catered towards situations where people are dying. If no one in the party is dying, there's no need to sing.
Again things like t8 and Moggle Mog EX are the exception.
no, you have a lv 50 ACN; and that ACN learned SMN and SCH skills, through job stones. you just did the same thing with SMN, as you did with SCH.
you don't level up SCH, you lv up ACN.
you don't lv up PLD, you lv up GLD; as such, if DRK comes from GLD, then you already know how to use a sword, so you just unlock your DRK skills from quests, like with every other job.
classes=wep skill level, which is why classes are tied to weps.
THIS. tbh, this is the only major problem with the class system. Everything else is relatively minor and could be fixed via tweaks. Job levels should not be equal to class levels. They should have their own level that is independent of your class. Classes should be more generalized and designed to branch into multiple jobs. For example, the basic Gladiator should be a tanky DPS hybrid. It should have multiple style stubs, such as sword&board (tank style), one-handed w/o shield or two-handed sword w/ heavy armor (DPS style), etc. They would have skills that apply across the class (but perhaps have special procs that occur when using specific weapons). Then, the Jobs are specialized versions of specific styles. Paladin uses tank-style Gladiator skills. Dark Knight uses DPS-style skills.My real disagreement with the system they have in place now is that the class and job share levels. I'd love to see you unlock a new job but it starts at level 1 (or hey, it starts at 30, why not...) but has its own advancement in levels from there. Your example brings up the big problem with it. Summoner and Scholar. I focused on Scholar before anything in 2.0, was my first 50. And you know what? I magically had a level 50 Summoner too that I just had to do a handful of quests to unlock.
It'll be the same if they add new jobs to existing classes if the system stays as is. Something has to change. If, for example, in 3.0 they add Dark Knight as a job for... i dunno. Lets say Gladiator because swords (Really, Just using it as an example, not saying it will or should be this class or anything of the sort). That means a level 50 Paladin just has to do about five quests or so, then they have a level 50 Dark Knight.
Also, classes should have extremely open cross-class ability access, while jobs should be extremely narrow (perhaps only allow skills from the primary class and the secondary class). Add in generalized high-level class gear that can be crafted, and you've got a workable system.
Last edited by TheRogueX; 10-23-2014 at 05:43 AM. Reason: I'm tired of the 1000char limit
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.