Endwalker GNB Discussion

[WhyAmIHere]

Except it becomes less skill oriented and more bothersome when your co-tank needs to voke because you simply don't have the space or properly move the boss without losing a Continuation combo. This is already a thing in speedkills, and was an issue in some fights this expansion. E5 comes to mind.

A simple soluation Xeno has brought up on his stream is making Continuation have a higher range. While it doesn't help the weaving problem, you'd at least be able to position the boss without risking your combo.

I mean I'd just say... "Git Gud, GNB adjust."

[ForteNightshade]

I mean I'd just say... "Git Gud, GNB adjust."

There's nothing to "Git Gud" about if you physically can't adjust. Instead, everyone else has to adjust for you. It's fairly common when optimizing for your co-tank to take the boss back simply because GNB can't weave CDs in. Or you plan out parts of the fight where healers have extra oGCDs; allowing you to eat something raw. Hypervelocity will only make this worse. Which will result in "good" GNB forcing more work on their team and "bad" GNBs simply losing damage through no fault of their own.

[WhyAmIHere]

There's nothing to "Git Gud" about if you physically can't adjust. Instead, everyone else has to adjust for you. It's fairly common when optimizing for your co-tank to take the boss back simply because GNB can't weave CDs in. Or you plan out parts of the fight where healers have extra oGCDs; allowing you to eat something raw. Hypervelocity will only make this worse. Which will result in "good" GNB forcing more work on their team and "bad" GNBs simply losing damage through no fault of their own.

nah that just sounds like bad GNB.
I did TEA on GNB, and all i had to do was say/think to myself "of, X is happening at Y, and I'll be at Z in my rotation. where to slot mitigation?"
the only annoying bit i can recall from tanking savage was hating OT'ing e5s.

[Ixon]

nah that just sounds like bad GNB.
I did TEA on GNB, and all i had to do was say/think to myself "of, X is happening at Y, and I'll be at Z in my rotation. where to slot mitigation?"
the only annoying bit i can recall from tanking savage was hating OT'ing e5s.

There is a difference between what's possible, and what's optimal. By adding forced oGCDs you unnecessarily restrict flexibility and remove options when coordinating throughout an encounter. Sure, you can drop a combo, or drop an oGCD, or triple weave to make things fit, but most of us would like to do better than minimal and optimize efficiency. Having them add extra speedbumps on that road is neither fun nor rewarding gameplay.

[WhyAmIHere]

There is a difference between what's possible, and what's optimal. By adding forced oGCDs you unnecessarily restrict flexibility and remove options when coordinating throughout an encounter. Sure, you can drop a combo, or drop an oGCD, or triple weave to make things fit, but most of us would like to do better than minimal and optimize efficiency. Having them add extra speedbumps on that road is neither fun nor rewarding gameplay.

And I'd still counter with "git gud."
Having complexity on a tank and making it require preplanning and forethought, as well as an ability to adapt on the fly, for how to weave in your mitigation in the midst of doing your rotation, is optimization. It's just not "I'm tryna get top parse" optimization, but tbf that's not something I personally ever felt like chasing. If you wanna push for top numbers then more power to you. I'd rather not have yet another tank have it's gameplay be dumbed down because a few people wanna complain "wah GNB too hard, SE fix."
What all this comes off to me as is "GNB is gonna become even more technical and difficult to master and perform well with in the midst of an encounter," and frankly I'm salivating over that.

[Ixon]

And I'd still counter with "git gud."
Having complexity on a tank and making it require preplanning and forethought, as well as an ability to adapt on the fly, for how to weave in your mitigation in the midst of doing your rotation, is optimization. It's just not "I'm tryna get top parse" optimization, but tbf that's not something I personally ever felt like chasing. If you wanna push for top numbers then more power to you.

Some of us don't want to settle for mediocrity.

I'd rather not have yet another tank have it's gameplay be dumbed down because a few people wanna complain "wah GNB too hard, SE fix."
What all this comes off to me as is "GNB is gonna become even more technical and difficult to master and perform well with in the midst of an encounter," and frankly I'm salivating over that.

No one is asking to "dumb down" current GNB? We are suggesting that additional bloat may take enjoyment out of the job and add an unnecessary level of clunkyness.

[WhyAmIHere]

Some of us don't want to settle for mediocrity.



No one is asking to "dumb down" current GNB? We are suggesting that additional bloat may take enjoyment out of the job and add an unnecessary level of clunkyness.

Good for you/them. Didn't know clearing content was just "mediocre" nowadays, but semantics. If you wanna push for those top color numbers, either play a job that's more conducive to reaching those peaks, or figure out how to utilize the kit to it's fullest. Sounds like "git gud GNB" to me.
--
"I don't like how often I have to press Dark Arts. It's too spammy and just button bloat since all it is is a "press for 140 potency" unless used on Carve and Split." is all I'm hearing with complaints about Hypervelocity. The whole Continuation thing was even added to tie in to the Trigger thing from FF8, a key selling point for the job and part of it's core identity. Complaining about that to me is akin to complaining that medicine is bitter, or that a diesel engine's too loud.
The only clunkiness from 6.0 that's foreseeable is not being able to fit in Hypervelocity (which.. how tf should that be abbreviated? HV?) if you use burst strike at the end of No Mercy.

[Absurdity]

nah that just sounds like bad GNB.
I did TEA on GNB, and all i had to do was say/think to myself "of, X is happening at Y, and I'll be at Z in my rotation. where to slot mitigation?"
the only annoying bit i can recall from tanking savage was hating OT'ing e5s.

There's a difference between playing GnB right now and playing GnB when your only tool to "adjust on the fly" suffers from the same problems as the thing you're currently trying to adjust.

[ForteNightshade]

nah that just sounds like bad GNB.
I did TEA on GNB, and all i had to do was say/think to myself "of, X is happening at Y, and I'll be at Z in my rotation. where to slot mitigation?"
the only annoying bit i can recall from tanking savage was hating OT'ing e5s.

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.

And I'd still counter with "git gud."
Having complexity on a tank and making it require preplanning and forethought, as well as an ability to adapt on the fly, for how to weave in your mitigation in the midst of doing your rotation, is optimization. It's just not "I'm tryna get top parse" optimization, but tbf that's not something I personally ever felt like chasing. If you wanna push for top numbers then more power to you. I'd rather not have yet another tank have it's gameplay be dumbed down because a few people wanna complain "wah GNB too hard, SE fix."
What all this comes off to me as is "GNB is gonna become even more technical and difficult to master and perform well with in the midst of an encounter," and frankly I'm salivating over that.

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.

[WhyAmIHere]

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.