The reason why BRDs damage was too low due to it being the most mobile of all classes on top of mp/tp.
But that thinking fallsapart since BRDs (and MCH more or less) now have to cast.
The reason why BRDs damage was too low due to it being the most mobile of all classes on top of mp/tp.
But that thinking fallsapart since BRDs (and MCH more or less) now have to cast.
While the thinking may fall apart, its what SE is still hiding behind for their explanation. I'm just letting you know what they said when they responded over the whole fiasco over WM in the first place. They reduced the penalty to turn it on and off and said, see, you're still mobile. I really dont think they will let ranged dps get much higher dps levels to be honest. When 2.0 first came out, BRD was the king due to high mobility and the original RoD. Groups would stack 4 BRD's and clear things quite easily. They nerfed RoD and made it so the LB doesnt go up as fast when you stack classes due to this very reason.
IIRC, they actually have given no official reasoning for WM's inclusion, just what the purpose of it was. Which...honestly doesn't make sense because at that point, it's not buffing their dps anymore as the other jobs buffing their dps with their post-50 skills. The end result is that you have WM getting rid of the mobility aspect...and them still being lower in output.
Theoretical question, if all jobs as of right now did the same amount of damage (regardless of caster, ranged or melee), would it still be favorable to stack double, triple, or all four?
____________________
Not who you asked, but the honest answer is if all DPS was equal, you would stack 4 ninja. They have the best overall party support with both the slashing debuff helping tanks, and trick attack helping everyone. Rotate the CD properly among the 4 NIN to get a constant +10% damage. They can also provide regen for sustained fights, Goad still being a thing to provide the TP boost to the tank and the other NIN.IIRC, they actually have given no official reasoning for WM's inclusion, just what the purpose of it was. Which...honestly doesn't make sense because at that point, it's not buffing their dps anymore as the other jobs buffing their dps with their post-50 skills. The end result is that you have WM getting rid of the mobility aspect...and them still being lower in output.
Theoretical question, if all jobs as of right now did the same amount of damage (regardless of caster, ranged or melee), would it still be favorable to stack double, triple, or all four?
So the answer is, in a world where all damage is equal, and you don't get a LB penalty for stacking classes, go 4 NIN in DPS. Best overall support, and better overall party DPS.
Except, you have a warrior for slashing debuff, you have no regen for healers, no foe requiem or RoD to boost healer damage, no STR bonus for tanks, and of course the obligatory reduced LB charge. Would the increased uptime on the 10% debuff be enough to win out on foe reqiuem, the loss of STR on tanks, and the reduced LB charge?Not who you asked, but the honest answer is if all DPS was equal, you would stack 4 ninja. They have the best overall party support with both the slashing debuff helping tanks, and trick attack helping everyone. Rotate the CD properly among the 4 NIN to get a constant +10% damage. They can also provide regen for sustained fights, Goad still being a thing to provide the TP boost to the tank and the other NIN.
So the answer is, in a world where all damage is equal, and you don't get a LB penalty for stacking classes, go 4 NIN in DPS. Best overall support, and better overall party DPS.
That's also not getting into issues with positioning for mechanics like lightning storm or sluice.
Last edited by RiceisNice; 01-14-2016 at 01:57 PM.
____________________
I assumed in your theoretical (as I stated) that we went back to no reduced lb charge, as that's the only way the theoretical even makes sense. Healer damage is less than tank damage, and really only takes off when you have actual magic DPS in the party. So really it comes down to is the extra up time on trick attack worth the loss of the strength buff, and the the extra 5% more damage from your scholar? Reduced limit break charge makes it all moot, however.Except, you have a warrior for slashing debuff, you have no regen for healers, no foe requiem or RoD to boost healer damage, no STR bonus for tanks, and of course the obligatory reduced LB charge. Would the increased uptime on the 10% debuff be enough to win out on foe reqiuem, the loss of STR on tanks, and the reduced LB charge?
That's also not getting into issues with positioning for mechanics like lightning storm or sluice.
I meant it in the scope of the game if all classes are equal. You're also only looking at it from a complete damage perspective and not in regards to an actual encounter. Running with all melee (not just NIN) will cramp you boss to deal with mechanics that hit players in an AoE, reducing uptime on dps.I assumed in your theoretical (as I stated) that we went back to no reduced lb charge, as that's the only way the theoretical even makes sense. Healer damage is less than tank damage, and really only takes off when you have actual magic DPS in the party. So really it comes down to is the extra up time on trick attack worth the loss of the strength buff, and the the extra 5% more damage from your scholar? Reduced limit break charge makes it all moot, however.
You don't want to stack the current ranged jobs either, BRD and MCH lacks a piercing debuff from DRG's disembowel, casters won't have a BRD for foe or regen for the healers.
That's sort of the thing, they're little nuances that wouldn't amount to much to a capable player. Melee dps is very well capable of maintaining full uptime and hitting their positionals through the fight mechanics. Heck, even during 2.5, a BRD undeniably has full uptime on dps, and they are still behind that of a melee/caster dps by good amount. And well, right now you already gave them WM/GB and the damage discrepancy is still there despite not having full uptime.
Last edited by RiceisNice; 01-14-2016 at 11:47 PM.
____________________
|
![]() |
![]() |
![]() |
|
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.