Dragoon Punished at lvl 58 - What needs to be done with Wheeling Thrust

[GrizzlyTank]

Only if you can't hit positionals. Which mechanics sometimes dictate, but that's mostly on the player.

Only a nerf if it changes after the fact we got a buff in the positional already not sure what else you people want? It is some good ass design in ramping up difficulty with level. I also like the skill set at level 60 makes DRG unique and one of my favorite jobs.

Boss is about to drop aoe on dragoon position.
The dragoon position behind boss so F&C can be landed without taking damadge.
It's not F&C so now 90 potency is lost due to RNG.

The dragoon could have moved away from the boss but then more than 90 potency is lost in the same time.

So yeah, it's RNG and got nothing to do with skill.

[Leonus]

Boss is about to drop aoe on dragoon position.
The dragoon position behind boss so F&C can be landed without taking damadge.
It's not F&C so now 90 potency is lost due to RNG.

The dragoon could have moved away from the boss but then more than 90 potency is lost in the same time.

So yeah, it's RNG and got nothing to do with skill.

It sometimes does, how long until the attack goes off?

Why are you camping DIRECTLY behind the boss? Why are you not trying to minimize the chance that an aoe eats all your rear space by standing at the edge of flank meets rear? For both you and your fellow melee dps?

What if the OPPOSITE happened, WT proc'd. There's a few good scenarios to fire right back at the one you used.

[Grimm08]

Sooooo Our ability got buffed, even with being the highest potential DPS in the game, and people are STILL complaining? Wow.

Continuing complaints about "Complexity" with the job, sure, you have to PAY ATTENTION and hit your positional from the correct side and missing that is a slight DPS loss, so what? It sounds to me like you're just complaining about having to actually try, wanting highest DPS handed to you. Well, if you don't like the complexity and the intricacies of the job, play something else. You don't want to hit a 4th tier combo from 2 possible positions? Go play Ninja. Play Monk for awhile, then come back to Dragoon and complain about missed positionals. This community sounds like (mostly, not all of you) a bunch of spoiled brats who want what they want when they want it no questions asked.

[Fynlar]

Do you know what nerf means?
The design of class is at 60 not 56 or 58.

Frankly it's still a nerf even at 60. The only reason WT has to be unlocked is just because the quest for it happens to be before the one for Geirskogul. If we could obtain Geirskogul somehow without obtaining WT, that would be advantageous.

Can you think of any other quested ability that any other job gets that you wish you could just skip because simply *learning* it is detrimental to the job? I cannot, and to me that's indicative of a problem.

Only a nerf if it changes after the fact we got a buff in the positional already not sure what else you people want? It is some good ass design in ramping up difficulty with level.

Difficulty ramping up is fine if players are rewarded for it properly in a similarly scaling manner.

Difficulty just for the sake of more difficulty (which is what WT is whether you admit to it or not) is just lazy design.

It sounds to me like you're just complaining about having to actually try, wanting highest DPS handed to you.

It would sound like that to somebody that doesn't actually care about the topic and just wants to get his "highest DPS has no right to complain about anything" licks off.

Here's a hint: the amount of damage DRG does compared to other jobs has absolutely bupkis to do with the topic at hand

[Adventica6]

loldrg -ff11/ff14

[justinjarjar]

At this point you are just a bunch of whiners no way to argue with people who will never be happy. And your aoe comment makes no sense not getting hit by AOE or mechanics>than any amount of dps. With the buff even missing positionals you will still top dps charts (thats why I liked prebuff you could tell who was shit and who was not). It is working as intended move along please you whiny people.

[Altanas]

Alternative suggestion:

1. Either remove wheeling thrust or award it with fang and claw.

2. Lower Geirshokul to 58

3. The Level 60 ability should be the HP-Drain ability. That would make a lot more sense given its what the actual NPC in the 60 quest spams on you ! And it would be very useful imo!

[Houston009]

F&C and WT were obviously designed to separate the Good from the Bad(based on forums). DRGs complaining about finally having some type of complexity to their job, its hilarious. And no, that 27(don't remember number) button rotation w/e thing DRGs claim they had to make their job sound complicated was never a thing.

All the DRGs I play with actually enjoy some type of RNG factor so that they can't watch Netflix mid-raid anymore.
Some of you may call it Design flaw, but you are the minority.

[Shurrikhan]

F&C and WT were obviously designed to separate the Good from the Bad(based on forums). DRGs complaining about finally having some type of complexity to their job, its hilarious. And no, that 27(don't remember number) button rotation w/e thing DRGs claim they had to make their job sound complicated was never a thing.

All the DRGs I play with actually enjoy some type of RNG factor so that they can't watch Netflix mid-raid anymore.
Some of you may call it Design flaw, but you are the minority.

Even then, that one move of checking which buff you got every 9.6 to 14.4 seconds hardly qualifies as complexity. If not for the inability to queue macros, you could still have a completely automated DRG losing only a maximum of some 450 potency per minute. I wish the job was more complex. Still doesn't have anything to do with the OP though. Again, no one has been calling the RNG too complex. It has been called (1) poor ability introduction, (2) a waste of a 4th real ability (instead of an advantage-less second half of a pair), or, in far rarer cases, (3) two abilities that could have created much greater complexity being wastefully pigeon-holed into a single check-once-and-execute-accordingly proc. The (1), the actual "design flaw", is obvious -- it is not even debatable. The only possible excuse it could have is to provide learning curve. The "design flaw" you seem to think most people talking about WT have instead applied to the whole job has never been part of the topic. Many of those pointing out the WT issue invite the complexity that you seem to think they're at odds with.

[Houston009]

You see it as a design flaw, others see it as an opportunity.