Results -9 to 0 of 69

Threaded View

  1. #11
    Player
    WhyAmIHere's Avatar
    Join Date
    Apr 2017
    Location
    Gridania/Lominsa
    Posts
    950
    Character
    Mute Shellback
    World
    Behemoth
    Main Class
    Gunbreaker Lv 100
    Quote Originally Posted by ForteNightshade View Post
    It's an optimized GNB. How well did you perform in TEA? Did you clip your GCD, delay Burst Strike/Faded Circle out of raid buffs or lose a GCD moving the boss? All of these are issues GNB already has but can be mitigated to an extent with current Burst Strike. That will no longer be the case in Endwalker since you'll have a oGCD tied to it.



    Nothing about this is added complexity because the solution will always be more work for the party. If the GNB cannot move the boss without losing an oGCD due to the new rigidness of Burst Strike, it'll either be a damage loss for them or force their co-tank to move it for them. Neither scenario requires forethought from a gameplay perspective. Likewise, if you can only time Rampart to line up with an upcoming tank buster but won't have the weave space to add a second CD, you'll just take more damage than any other tank in the same position.

    You say you don't want GNB to be dumbed down. Is it now? Why would allowing it to keep it's current weave slot suddenly make it dumbed down? Because all Hypervelocity does is remove what already exists.
    You can look up yourself, but both my clears in TEA were grey. The one death was not being healed after double rocket punch, but there's drama to tell between me and that healer. the second kill was lag during ordained stillness/motion, tho at that time i was having to tether off of my phone to even raid.
    But, every cooldown barring HoS (except in some cases) was planned out for the entire fight. I've still got a copy of the excel doc if you want that too.
    Again: I value the clear over the parse. I don't engage in speedun shite because it's not my forte.
    If it's "Moving the boss is going to be harder" then just figure out ways to move the boss where either you're not going to be using burst strike, or start to move ahead of time. If WHM can figure out movement during a boss fight, GNB can.
    --
    "If you only hit the tail end of rampart with a tank buster, you take more damage!"
    ...what? Did you read what you wrote? Besides which, your "2nd weave" is still free, even now. If you gotta push a gap closer around to make room for Heart of Stone or Heart of Light, then how will having hypervelocity impact that?
    Again though, you're not making sense in what you're asking.

    "You say you don't want GNB to be dumbed down. Is it now? Why would allowing it to keep it's current weave slot suddenly make it dumbed down? Because all Hypervelocity does is remove what already exists. "

    As GNB is now is what we should be using as the control in comparison. GNB isn't dumbed down now because there's nothing else to compare it to. I'm not complaining about how it is now, I'm saying "complaining about Hypervelocity cannot lead to a gutting of GNB how DRK got gutted in 5.0 due to a perceived "wah it's too hard"." As has been said in the past, "if you don't like it no one's forcing you to play it." If GNB getting Hypervelocity in 6.0 is suddenly going to make GNB too troublesome to play, and people would want to see it removed, I'd say be careful what you wish for. If enough people start on this train I wholly expect 7.0 GNB to be neutered, and having a tank that is not just "press 1 2 3, spam 4 every so often" is a good thing. I joked about "Bloodthrist now allows your next 5 Burst Strikes to not consume cartridges," but given how SE tends to react to "wah gameplay too hard, SE fix," I wouldn't be surprised if that's what they kneejerk implement.
    (0)
    Last edited by WhyAmIHere; 10-27-2021 at 01:26 AM.