Heavy Thrust on DRG job gauge

[Llugen]

Yeah I'm also thoroughly impressed by that, Remedi. It's incredible how many people don't even bother reading the thread. What is the point of threads/forums if you're not going to at least read it???

Apparently I need to say this again, since it didn't sink in the first time:

So, during AoE rotation it's very easy to get lost in spam and forget heavy thrust.

Furthermore, the other maintenance buffs like Straight Shot and Hot Shot are on the gauges. The mere fact that Heavy Thrust is not on the gauge is not only inconsistent, but short-sighted. This should be addressed.

AoE situations are not "irrelevant", it is by their very nature to upkeep heavy thrust. What does that even mean? It is never not a big deal to lose 10% damage because not paying attention.

[Karshan]

Yeah I'm also thoroughly impressed by that, Remedi. It's incredible how many people don't even bother reading the thread. What is the point of threads/forums if you're not going to at least read it???

I do read, you just don't like the answers cause they don't go your way.

So, during AoE rotation it's very easy to get lost in spam and forget heavy thrust.

As Hyomin expressed way better than I did : shouldn't happen. with our item level adds should be burning. Anyway, every 5 AoE combos, you HT

Furthermore, the other maintenance buffs like Straight Shot and Hot Shot are on the gauges. The mere fact that Heavy Thrust is not on the gauge is not only inconsistent, but short-sighted. This should be addressed.

Yes, there is inconsistency, and I did grant that in my previous comment.
What I disagree with, is that it is NOT a maintenance buff like those of ranged, because DRG is a set rotation type, not a priority type, like Kabooa said. So HT is ON the rotation, while there is no rotation on Ranged, in the sense of : you can't know when HS or SS are to fall off, could be after a clean shot ? after a refulgent ? For DRG, HT always ends after FT combo and that's it. No room for anything else after 70.

So consistency is not an absolute necessity here. Why are we arguing for longer that it could take the dev to put the option you'll say ? Because with unimportant changes like this one we lose sight of real issues (not with DRG, but in general). Devs have limited attention span, and don't seem to have a strong quality testing and implementation process with checklists and all, I'd rather they focus on absolute needed changes like BLM and DRK, then when it's done, to re open the subject.