Hurry up and fix V5s WAR ghost exploit

[Sacred_Nym]

Is Aether PF really trying to enforce this strategy? That just seems dumb given that it has generally little room for error. Every PF group for the fight on Primal that I've been in just did it the intended way.

[Metalwrath]

The party shouldnt be using Warrior for this.Its an extremly bad waste of dps when other jobs can nuke it without losing big cooldowns compared to Warrior losing his only big dps cooldown.

[Theodric]

Using long standing game mechanics the way they're designed is not an exploit. SE made tank LB3 do what it does, and SE made LB not go up as quickly with duplicate jobs, deliberately to encourage people to not bring duplicate jobs.

Players reacting to that by not bringing duplicate jobs is working exactly as intended.

Each to their own, then. I'll continue to frown at it since - whilst convenient - it's making the PF rather toxic and stifling getting fresh blood into the raiding scene. Much like how 'SKIP SOAR' served to do the same thing with Zurvan EX. Hopefully when we get 4.3, the associated Primal fight will be free of such things.

Granted, I do understand why people do it.

[Nerfworthy]

In my FC's PF we will usually ask if the pug people want to/are comfortable with the skip strat and if not then we don't do it. I don't see how it's such a big deal?

[Jijifli]

How DARE players use the tools devs gave us to learn new strats. How dare it use what a class has normally available, instead of o6s's squad LB bug that was clearly not intended to be possible.

How dare RDM players for doing the same thing.

[Mithron]

Yes, he did, said that both were unexpected but legitimate.

Misinformation. It is true he stated Byakko ex tank LB3 was unexpected but fine, he never said specifically that this strat for V5s was fine. He misunderstood the question about "needing an SSD" and never actually touched on the real subject of using one person to kill the ghost so no one else needs to.

If this was an intentoinal mechanic, there would only be one ghost and you'd put the best person for the job in it. It's not though, because there's specific ghosts for tanks, healers and DPS, meaning it's meant to be done with everyone participating.

How many fights can you phase push so hard that you skip add phases? I'm sure there's some, but not many.

[Kewitt]

This isn't an Exploit as RDM can do it to.
And more jobs will with over gearing.

Just because DEV can't try or think of every posiable thing doesn't make it an exploit.
An exploit to me is something that isn't normally posiable in the game. Not something that is just not thought about by the dev team.
ie using the /ac command to do action you normally can't because Dev team didn't code them correctly.

[KDSilver]

The party shouldnt be using Warrior for this.Its an extremly bad waste of dps when other jobs can nuke it without losing big cooldowns compared to Warrior losing his only big dps cooldown.

It's a dps loss for war, but a dps increase for the whole party.
Who is expected to deal the most damage in the party? DPS. Who will keep their CD then to be able to burn it on the boss and make his life drop even faster ?
DPS.

So, in the end, this slight personnal DPS loss from warrior is a huge increase to the party, and that's how it should be taken. TO THE PARTY.

[Squintina]

It's not an exploit if the game gives absolutely no indication that this might not be a valid way of doing things.

And it doesn't. There's absolutely nothing in the game to indicate that everyone has to do all ghosts.

For something to be considered an exploit, it needs some degree of obviousness. We do not have the ability to read dev minds.

For example, Ungarmax exploit had that obviousness because its skill section is in squadron and clearly states it.
Warp exploit had that obviousness because it is only given to players in pvp.

Something that has absolutely 0 obviousness because the devs force the players to completely figure out the whole thing on their own cannot be considered an exploit. It is a strat and if the devs do not like it, they can do something to stop it, but it doesn't change that it is not an exploit.

This is precisely why even though the devs admitted to not thinking of the tank lb3 strategy for byakko, they said they would allow it, because we cannot read dev minds and using a tank lb3 to do what tank lb3 is supposed to do (reduce damage) isn't an exploit. The same goes with ghost strat.

Devs also admitted that they watch world first clears to see how players did things (and that one of the reasons they do so is to see the various strategies players come up with), so believe me they've seen this strategy of having 1 person stop the whole phase on their own. If they didn't approve of it, they'd have done something about it by now.

Also it doesn't take that long to decide on whether or not to use it at the beginning of a run. If someone feels they can definitely do it in time - do it. If they don't think they'll be able to because they're not confident in their damage and lag (yes I know SE said the loading times are the same, but server lag with actions after loading is still individual and can still lead to variances), then don't do it. If no one is confident they can do it, you have no choice than the do all the ghosts.

[basketofseals]

It's a dps loss for war, but a dps increase for the whole party.
Who is expected to deal the most damage in the party? DPS. Who will keep their CD then to be able to burn it on the boss and make his life drop even faster ?
DPS.

So, in the end, this slight personnal DPS loss from warrior is a huge increase to the party, and that's how it should be taken. TO THE PARTY.

Technically it's a dps loss for the party since they're just standing around for 20 seconds doing nothing, but that only really matters if you're worrying too much about meters.