Results 1 to 10 of 184

Hybrid View

  1. #1
    Player
    Ultimatecalibur's Avatar
    Join Date
    Jan 2014
    Posts
    2,737
    Character
    Kakita Ucalibur
    World
    Siren
    Main Class
    Paladin Lv 86
    Quote Originally Posted by whiskeybravo View Post
    I don't see how that would work and be equivalent.

    Current target is 6 fell cleaves + 1 Upheaval + 2 Onslaughts in 8 GCDs, this only leaves 2 GCDs for building gauge.
    The current target is kinda the problem. It is trying to cram as much BG expenditure into 8 or 9 gcds as it can and this ends up making the burst very tight and ridged. Any lost gcds will lead to lost FCs. My suggestion is mostly focused on making it more flexible.
    Proposal to increase gauge generation instead of halving costs messes up that flow. Down to 10 gauge after FC+Inf+FC+Up+On, then you use preloaded Maim/Path for 60 gauge which leaves 20 after a FC, that's 5 GCDs out of 8. You need one of those next GCDs for Heavy Swing which generates no gauge, which means you can not use a 4th FC in the 8 GCD window (20+20 = 40, because the last GCD is for FC). The only way I can see to resolve that is have Heavy Swing generate 10 gauge so you can get the last FC and end at 0 gauge. I think it would be problematic to fit in the extra onslaught.
    Squeezing in the Onslaughts (primarily intended as a utility action) is where your problem is coming from.

    I believe the rotation in my suggestion would end up something like this:

    Heavy Swing (Berserk + Inner Release) -> Fell Cleave (Infuriate) -> Fell Cleave -> Maim (Upheaval) -> Fell Cleave -> Storm's Path -> Heavy Swing -> Maim -> Fell Cleave -> Storm's Path end at 30 BG at 8 gcds and 50 BG at 9 gcds.

    You only really need 4 gcds to get in the majority of the burst's potency which would make being interrupted during it less punishing.

    Unless I'm missing something (probably) I don't really see that as a viable solution. Additionally, would you not have to significantly increase the damage from a single FC to make up for the fact you are replacing 2 or 3 500 potency attacks with 2 or 3 150-270 potency attacks? (ties back into the "Imagine losing an 800 potency Fell Cleave as compared to missing a 500 potency Fell Cleave.")
    The Fell Cleaves would only need to be about 800 potency and it would be much harder to lose them. In a 8 gcd burst you would be more likely to lose a 270 potency Storm's Path than an 800 potency Fell Cleave.
    (0)

  2. #2
    Player
    whiskeybravo's Avatar
    Join Date
    Nov 2013
    Posts
    2,840
    Character
    Whiskey Bravo
    World
    Leviathan
    Main Class
    Warrior Lv 100
    Quote Originally Posted by Ultimatecalibur View Post
    The current target is kinda the problem. It is trying to cram as much BG expenditure into 8 or 9 gcds as it can and this ends up making the burst very tight and ridged. Any lost gcds will lead to lost FCs. My suggestion is mostly focused on making it more flexible.
    I just meant from a potency standpoint, that's the target. Trying to find an optimal rotation under this consideration is tough lol, but I tried.

    The suggested rotation would end at either 10 gauge or 50 gauge, in either case it would prevent you from using a final FC under the current buff times. The 8th GCD is that last FC in your chain, so by the 9th GCD you're only sitting at 10 gauge (so you can't execute path to get one more buffed FC). You'd actually only need 4x 650 pot FCs to match the current potency (according to my shoddy math skills), but there are a lot of GCDs consumed restoring gauge in this scenario and it seems kind of weird to have leftover gauge (unless that's a goal so we could still do "something" after a burst window)

    Overall, I don't really see much distinction as you are still trying to fit x amount of GCDs in y amount of time. And increasing the potency that much does make missing one more impactful than in the current situation. But obviously if you missed a heavy swing instead of a FC due to mechanic timings or whatever, then it does favor the proposed change.

    As it stands, at least the burst window right now is wrapped up in a nice little package if executed correctly (no leftover buff time/gauge). This example doesn't really accomplish that aspect of it, though some of the buff timings could be adjusted to accommodate it I think.
    (1)