Hurry up and fix V5s WAR ghost exploit

[Bourne_Endeavor]

Curious about this, it's it really a DPS loss for the party? I mean the ghosts you fight in the cabins are not linked to the boss's HP so any damage you do to them isn't going to make a big difference. Yes I suppose you could say well it's easier to keep buffs that come through using rotations etc, but you would also be saving MP/TP for not wasting it on the ghosts to begin with, not to mention you don't have to spend seconds interacting with the point, reappearing on the train and then traveling within damage range to attack the boss.

It's a DPS gain. Unlike normal mode, Phantom Savage appears much faster. Therefore, everyone outside will usually get 3-5 extra GCDs. Not to mention, since healers can't DPS their adds at all, they get flat bonus damage they wouldn't have otherwise. Right now though, it's shifted to Red Mage being the ideal candidate. It loses virtually nothing and can zerg the tank ghost down faster than Warrior. Machinist and Summoner may also work if they don't lose much going in.

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.

Exploits would be Ungarmax as it deliberately involves using an ability not designed for content outside Sqaudrons. Tank LB3 is fully intended for high, snap mitigation. People just found a creative way around dealing with Byakko. In regards to dublicate jobs. People tend to do that for everything since why lose a possible LB just to bring two Black Mages or Dragoons?

[EorzeaHero69]

I don't see it as an exploit. If it really was, then I don't think it would have been scripted for ghost phase to automatically end after one ghost death in savage.

[Crescents]

I don't see it as an exploit, its an unconventional strat, sure but there is a fair amount of risk involved and seeing as im sure the devs are well aware of it by now and we havent seen any emergency maintenance it's fine. Its doing mechanics in a way it wasnt designed sure, but its not exploiting or breaking anything as was the case with the squadron limit break. Besides if the war/rdm mess up the entire party dies I'd think if something counted as an exploit it would be a universal gain with zero risk involved rather than (in wars case) having to sac their entire burst phase.

[Squintina]

This is pure nonsense. There's EVERY indication that players are meant to do all ghosts - there's a ghost for everyone, you die if you don't get caught by a ghost (barring the WAR/RDM strat), and those ghosts are even keyed to job roles!

This is an exploit in every sense of the word. If SE decided never to do anything about it, that doesn't change the fact that it's an exploit. It's no different from the Coil 2 enrage strat - unintended, but never patched.

There's no sense getting bitter about it, but it's also hilarious to claim that it's working as intended.

While I understand that the game certainly hints at it very strongly, and it does, the fact remains that there's no actual text to officially say that. Without text, anything else is an educated guess. Those educated guesses might be correct, but without something actually saying it, it remains just that - conjecture. No matter how many things you can find to support your educated guess, without clear text it remains a guess.

For example.
Ghosts existing for each?
Who's to say the strategy wasn't officially "Players will choose a select few members, 3-4, to go in and stop the ghosts while others stay behind. Enough ghosts will be provided to let parties determine how many players go and try and provide enough time to reach a ghost depending on where they are located in the platform".


Heck, considering that depending on the order you come out in you can completely screw over the whole party, I could say that this design where healers pretty much always comes out last because they have to wait for the ghost to kill itself (while the train potentially destroys anyone else who came out before) would actually support the idea that they intended for at least 1 healer and 1 tank to stay behind for the party's survivability while the others are in the ghost phase and that the party-wide death is simply a dps check.

It's not unlike SE to make dps checks for only a subset of people affect the survivability of the entire party.

Without text to support it, this version of the strat would be equally as likely to have been intentional by the devs.

And like I said, the devs have admitted they watch world first clears, which this strat was used in many of them. If they were against it, they'd have said something by now. It wasn't a strategy introduced later and only by a small fraction of groups. It was widely used.

Now if they come out tomorrow with a post saying they do not want people to use this and to stop using it until they patch it, then I'll be right with you to call this an exploit.

And this is coming from a party that doesn't use this strategy at all because none of us in my party feel confident enough to rely on it.

[whiskeybravo]

I thought they said it was due to human error from a new programmer or something. Could be mixing that up with Byakko tank-LB strat though, not sure. Since it hasn't been patched out it must not be that big of a deal, intentional or not.

Personally we choose not to do the cheese strat. I tried several times on War and couldn't get it fast enough, group got tired of wiping on it so we just do it the normal way.

[Coratanni]

People will always find ways to do strategies differently in fights. It isnt an exploit. It is exploring and finding new ways to complete the content..

[ToasterMan]

Just because you CAN do something in a game doesn't mean it isn't an exploit. CLEARLY the devs didn't intend the phase to be cheated like that. I mean, I really don't care if people do it or not but I'm baffled that people here don't see this as a glitch.

[Valkyrie_Lenneth]

Just because you CAN do something in a game doesn't mean it isn't an exploit. CLEARLY the devs didn't intend the phase to be cheated like that. I mean, I really don't care if people do it or not but I'm baffled that people here don't see this as a glitch.

People said the same thing about T2 in coil. In fact, the devs had a patch that made it nigh impossible to clear with the enrage strat. That patch in fact bugged the fight, and they fixed the bug later, making enrage viable again. If this isn't textbook for alternate means of clearing being ok then I don't know what is.

The fight is coded that the suffocating mist disappears not when all players are in the passenger cars, but when the first ghost dies.

That is all there is to it, there is no exploit. Or do we consider DRG/NIN/BRD/MCH an exploit now, since that isn't what the dev's intended most savage parties to be.

[dragorian]

There's a lot of ways to run savage/ex. Take byakko ex tank lb 3 as well as skipping stack marks with the tanks being the only one in them. Both of these are not exploits. Just because us farming groups find more efficient and get more runs in dose not mean we are exploiting in any way. Now before patch using the Ungermax out of it's intended way is.

[Bourne_Endeavor]

Just because you CAN do something in a game doesn't mean it isn't an exploit. CLEARLY the devs didn't intend the phase to be cheated like that. I mean, I really don't care if people do it or not but I'm baffled that people here don't see this as a glitch.

By that logic, you're essentially claimed Tank LB3 is a glitch. The devs not intending for people to find workarounds doesn't make them a glitch. Tank LB3 is just extremely potent mitigation. Are Crit Adlos glitches when they can let you ignore God Kefka's huge aoe? People set all that up pre-pull. What's the difference?