Results -9 to 0 of 687

Threaded View

  1. #11
    Player
    Quor's Avatar
    Join Date
    Aug 2013
    Location
    Limsa Lominsa
    Posts
    663
    Character
    Alexya Ultor
    World
    Leviathan
    Main Class
    Dark Knight Lv 90
    Yeah the new Tenka fart is very bland and uninteresting, not to mention it now hits like a wet noodle.

    Doing a bit of math on this, our current aoe GCD combo at 90 has a ppGCD (potency per GCD) of 144 per target. So a full combo of Fuko > Oka > Fuko > Mangetsu > Tenka hits for 144 potency for every target hit. It also builds a total of 40 Kenki to be used on Kyuten at 110 potency per target. Kyuten currently has a ppK (potency per Kenki) of 4.4. Spread out over the course of the GCD combo that builds it, this 40 Kenki brings the total ppGCD up from 144 per target to 179.2.

    If we remove Tenka from the equation (via using Hagakure to generate 20 Kenki from the 2 Sen we have) we now have 70 Kenki to work with because our 5-GCD aoe combo now looks like Fuko > Oka > Fuko > Mangetsu > Fuko. The base ppGCD of this combo is 108 across 5 GCD's. Clearly Tenka at 280 potency has a marked effect, raising the total ppGCD of the combo across 5 GCD's by almost 40%. But with an additional 70 Kenki to work with due to Hagakure and not using Tenka, the additional oGCD from the Kenki translates into 308 extra potency on top of the standard GCD potency. Divided across those 5 GCD's we get a ppGCD of 169.6 per target, up from 104. Which is 9.6 potency less than we get from the Tenka combo. This means on five targets you're getting 48 less potency per 5 GCD sequence by using Hagakure instead of Tenka. This doubles to 96 less potency per 5 GCD sequence at 10 targets. Since aoe packs rarely go past ten mobs (most stop at around 7-8) the best case scenario for using Tenka over Kyuten is for an additional 96 potency, and only assuming all ten targets are hit by all your aoe.

    So let's look at current Tenka with the theoretical addition of Kaiten. At a 50% boost to potency, Kaiten is worth 140 potency in damage when used on Tenka. This, when added to our other 5 GCD's, gives a total potency of 840 across the combo sequence, or 172 ppGCD. Just using 20 out of the 40 Kenki we get on Kaiten already puts the basic aoe combo ahead of the Hagakure/Kyuten version (172 vs. 165.6). Adding in the ppK from the last 20 Kenki generated by our aoe combo the total potency over 5 GCD's comes to 928 for a ppGCD of 185.6.

    Given that Tenka has a cast time and Kyuten does not there's also the negligible matter of potential lost auto attacks. I won't calculate this because it's, well, negligible, but it's still worth mentioning in the context of how Tenka - as a circular aoe - now forces the SAM to sit in the middle of a pack of mobs for maximum effect. Kyuten is also circular but it is instant and easy to seamlessly weave while dodging enemy attacks. Tenka has no such benefit, and if you're forced to cancel the cast due to an aoe for some reason then this very-narrow 8.6 potency gap between Tenka and Hagakure/Kyuten start to close very quickly.

    So what are the take-aways from this:

    1 - Tenka as a circular aoe puts the SAM right in the middle of danger, locking us down while we cast it. We either move if an aoe is coming or risk eating avoidable damage, something that no one wants to eat when running a 4-man.

    2 - the damage difference between current non-Kaiten Tenka and Hagakure/Kyuten spam is very low. So low that if you *are* forced to move to dodge something then you're almost certainly better off just eating your Sen with Hagakure and spamming Kyuten to maintain mobility.

    3 - the damage difference between Kaiten+Tenka and Tenka+Kyuten spam is about 3.4% before considering crits. This is a direct nerf for no good reason.

    4 - the damage difference between Tenka+Kyuten and Kyuten/Hagakure spam is about 5.5% before considering crits. Given that new Tenka can much more easily be interrupted by forced movement to avoid aoes, this is more of a wash than it would appear from the numbers. Even one delayed/cancelled Tenka cast is enough for the Kyuten/Hagakure spam option to catch up in ppGCD.

    5 - if lots of movement is necessary to avoid spammed enemy aoe (common in a big pull) then using Tenka+Kyuten over pure Kyuten spam is the way to go as the damage is almost identical and the freedom of movement means you don't get tagged unnecessarily.

    The one seemingly-big disadvantage of Kyuten spam over Tenka+Kyuten is the lack of access to Kaeshi. The total potency of this combo across 6 GCD's is 1000 even, for a ppGCD of 166.6. Adding the additional 40 Kenki on top of it we get a total ppGCD of 196 across 6 GCD's and a total potency for the cmobo of 1176.

    Using the Kyuten/Hagakure spam version across those same 6 GCD's gives a total ppGCD of 660 with 90 additional Kenki (60 from GCD's, 30 from Sen) for Kyuten. This gives us a total potency across the combo of 1056 for a ppGCD of 176. Compared to one another this is about a 10% damage difference (10.2% or so) in favor of Tenka+Kaeshi over Kyuten/Hagakure. But again, if you're forced to move and delay your Tenka cast due to incoming aoe the difference starts to narrow. Optimal play would seem to be trying to keep Kaeshi cooldown rolling while in aoe situations but not to stress about it otherwise. If you can't safely get Tenka off then it's better to eat the Sen instead and just spam Kyuten. If you can't guarantee you'll hit every target with Tenka but are confident you can maneuver to hit everything with Kyuten then you're better off eating the Sen and using Kyuten, as even missing one target with Tenka puts it below hitting all the targets with the Kyuten-focused combo.

    Which is to say that all of this is a very long-winded means of advocating for bringing back Tenka as a conal attack. The entire consideration presented here could be removed from the equation if Tenka was still a cone, allowing SAM's to safely cast Iaijutsu without worrying about dodging enemy aoe's.

    Oh and bring back Kaiten.
    (10)
    Last edited by Quor; 04-19-2022 at 01:41 PM.