Wanderer’s Minuet, Gauss Barrel and Positive Gameplay Additions

[RiceisNice]

Pretty much, yes. MCH is, honestly, in a similar boat. It has a similar load of oGCD use (especially now with Quick Reload on a 15-second cooldown) to that of BRD, and the difference between playing MCH at 50 and with GB at 60 is comparable to that between BRD at 50 and BRD at 60 with WM. MCH tends to "flow" a little better, as their proc system for the main combos seems to update client side better than Straighter Shot does for BRD, and they don't have something like Bloodletter that constantly resets, but a lot of the oGCD awkwardness is still there.

Honestly there is no oGCD awkwardness for MCH imo because you don't have an oGCD that resets it's cooldown, or otherwise an oGCD that has a cast time. Any time you double up or otherwise clip into your weaponskill, it boils down to your fault for hitting two oGCDs in one weaponskill. BRD can't help it when they have an oGCD that resets it's cooldown and a oGCD cast time that's also 1.5 seconds (which will clip no matter what when you have a weapon skill that has a 1.5 second cast time in a 2.5 GCD)

[Alahra]

Honestly there is no oGCD awkwardness for MCH imo

Even outside of oGCD resets for BRD, oGCDs are akward in terms of timing with WM/GB up. Without them up (and for other classes), you have a larger window of time in which to hit them than you do because of the length of the cast time, which is longer than the "animation" lock for most GCD abilities. If you don't queue your oGCDs exactly perfectly with WM/GB up, they clip into the next GCD, whereas you have a little bit more room for them under normal (non-cast-time) functionality.

That's the awkwardness I was referring to. The "rhythm" is off from every other class in the game and off from the rhythm MCH/BRD have without WM/GB.

[RiceisNice]

Even outside of oGCD resets for BRD, oGCDs are akward in terms of timing with WM/GB up. Without them up (and for other classes), you have a larger window of time in which to hit them than you do because of the length of the cast time, which is longer than the "animation" lock for most GCD abilities. If you don't queue your oGCDs exactly perfectly with WM/GB up, they clip into the next GCD, whereas you have a little bit more room for them under normal (non-cast-time) functionality.

That's the awkwardness I was referring to. The "rhythm" is off from every other class in the game and off from the rhythm MCH/BRD have without WM/GB.

You can queue up a oGCD as your cast time finishes up, it's not that overly difficult. You can still do one oGCD inbetween each weaponskill with a 1.5 second casttime. The problem comes when you try to do two oGCDs inbetween weaponskills with cast times (or otherwise, a 1 second opportunity, which is given with the [GCD 2.5] - [cast time 1.5]. A machinist with rapid fire can still weave oGCDs just fine inbetween each weapon skill (which at that point has no cast time and the GCD is 1 second) without ever clipping into another weaponskill unless you doubled dipped.

The only exception to above (which is practically a bug) is if you use a straight shot right after a HS that gave you the proc; the proc doesn't get used up and you still have cast times on SS, but for some reason it still delays your oGCD use when it otherwise doesn't.

[Alahra]

You can queue up a oGCD as your cast time finishes up, it's not that overly difficult.

I didn't say it was difficult. I said it was awkward with the respect to the timing for the other classes in the game. There is enough time for one oGCD but there is less time than the other classes get because the 1.5 cast time is a bit longer than the point at which, during the normal GCD, oGCDs become available for use. That change in flow makes WM and GB "feel" awkward even before you consider Bloodletter, Flaming Arrow, etc. BRD is more awkward than MCH because of those things (though MCH still has the same awkwardness present with Flaming Arrow from its turrets, which do need to be moved mid-fight sometimes), but the fundamental awkwardness with oGCDs from GB/WM is present in both.

Edit: This is mainly of note because of latency, as even slight latency can make ability queuing less reliable.

[RiceisNice]

I didn't say it was difficult. I said it was awkward with the respect to the timing for the other classes in the game. There is enough time for one oGCD but there is less time than the other classes get because the 1.5 cast time is a bit longer than the point at which, during the normal GCD, oGCDs become available for use. That change in flow makes WM and GB "feel" awkward even before you consider Bloodletter, Flaming Arrow, etc. BRD is more awkward than MCH because of those things (though MCH still has the same awkwardness present with Flaming Arrow from its turrets, which do need to be moved mid-fight sometimes), but the fundamental awkwardness with oGCDs from GB/WM is present in both.

We have different perspectives of whats awkward then. If you're not actively trying to fit two oGCDs into one weapon skill cycle, theres no break of flow or clipping of oGCDs. You're able to use an oGCD as soon as the cast time finishes, animation or not (except again in that scenario with SS I mentioned earlier). A way to put it into perspective is to see it as this; "You cannot queue a skill within .5 seconds of using another skill, cast time or not". Which holds true for all jobs, including melee and casters like blm (they can start channeling fire I right after it finishes casting, as well as use a fire III right after a hardcasted fire I, but they cannot start a cast or even use a instant cast right after using an oGCD such as manawall, or use an oGCD right after an instant cast).

As for the flame arrow/turret thing ,you can't bring up the targetting recetitle while casting, but it's still the same principle; you can place it down immediately after the cast time ends with no pause inbetween. And honestly, I've gotten used to it at least as far as turrets is concerned (not so much flame arrow because you have to actually aim it, but even then you can usually eyeball it.

Edit: This is mainly of note because of latency, as even slight latency can make ability queuing less reliable.

Alot of my perspectives comes from without latency (which honestly makes this a legit issue). With latency though, every job gets affected to some degree (esp DRG when it comes to getting theit WT or FnC buff), it's not exclusive to BRD.

you forgot drg battle litany buff , whm now have more dmg and instant healing spells , SCH have better aoe healing and more support skills , even a CD for more raw healing + 3 aetherflow , and some support spells...

in the end all the jobs got improvements in the areas that were more needed. Brd on the other hand....ugh...

Giving a party buff isn't exciting or changing to their gameplay, and certainly would not be the first thing I'd mention to someone I wanted to tell a former 2.0 DRG player what they gained.. When you're looking at a expansion of all things, you want the existing jobs to evolve on top of what they are already doing before, whether it's filling in their downfalls (MNK's damage plummeting on down time for example, they gave them more tools to minimize the detriments of that) or building upon their role and existing playstyle (which is easily all the jobs, debatable with the likes of NIN and especially BRD

[Alahra]

We have different perspectives of whats awkward then.

We probably do, though I'm not the first person to bring up the issue of the timing with GB/WM compared to the timing without them.

[RiceisNice]

We probably do, though I'm not the first person to bring up the issue of the timing with GB/WM compared to the timing without them.

It's not so much the timing directly, but it's the interaction of skills that makes the timing the problem (specifically BRD). To me, not being able to use 2 oGCDs in one weaponskill was not the end of the world provided my job was not designed to do so (such as encouraging you to keep oGCDs off cooldown so it can refresh from a proc)

[Lemuria]

theres no break of flow or clipping of oGCDs. You're able to use an oGCD as soon as the cast time finishes, animation or not (except again in that scenario with SS I mentioned earlier).

I'm not sure if you're playing the same job as I am, but I've noticed a TON of clipping due to the animations for things like barrage, Blood for Blood and Raging Strikes being used after a weaponskill in Minuet. This only becomes even more pronounced when you're using bloodletter regularly.

So, just for the sake of clarity, please don't pretend that an issue doesn't exist just because you're one the exceptions.

[RiceisNice]

I'm not sure if you're playing the same job as I am, but I've noticed a TON of clipping due to the animations for things like barrage, Blood for Blood and Raging Strikes being used after a weaponskill in Minuet. This only becomes even more pronounced when you're using bloodletter regularly.

So, just for the sake of clarity, please don't pretend that an issue doesn't exist just because you're one the exceptions.

It shouldn't clip each other after a weaponskill is what I'm getting at. I have a video uploaded of me using oGCD right after a weaponskill to demonstrate what's wrong with straighter shot, but I can't link it atm on phone.

The one time that your skills clip each other even with a cast time is when you're doing SS right after a HS that gave you a proc, which is a bug because it shouldn't happen


Edit: the wonders of YouTube app.
https://youtu.be/EbqbjJq6-lg

I'm using oGCDs immediately after a weaponskill just fine.