Squadron limit break (Ungarmax) can be used in regular duties by any job

[Shurrikhan]

They were quick to fix the Sigmascape 5 Savage bug were the Warrior could skip an entire phase for the party by instantly killing their ghost in their own car.

It was still there just last night, after reset. And it's not just WAR. It's anyone who can enter the room and kill the mob within 10 seconds.

[HyoMinPark]

If a player used something that was in the game before being informed it was actually an exploit, it's not the players fault that it shouldn't be in the game/accessible in the first place.
However, now that attention and potential fixes were put in place, my understanding is that from today onward, you use the bad juju at your own peril.

Honestly, if the person has an extensive history of using Ungarmax, they should be punished. It’s fairly obvious that it wasn’t intended to be used in PvE, since no other niche content abilities (e.g., PvP-specific actions, PvP individual LB, PotD pomanders) have ever been allowed in general PvE content. And a 15 second +50% Damage Up buff? That seems very blatantly OP, and very blatantly unintended for PvE content, in my opinion.

[ThickishGerm]

That seems very blatantly OP, and very blatantly unintended for PvE content, in my opinion.

Not to mention it says so on the tooltip that it is only to be used on command missions, https://i.imgur.com/quh533K.png

Unfortunately for those involved, ignorance will probably not be accepted as an excuse.

[Ametrine]

Plus, it feels like people here can't differentiate from cheesing through a fight (Using Titan-egi to tank a primal, opening an extra party member slot for a DPS) and cheating through a fight (Using a powerful skill from one mode in the game to make another mode easier to beat).

SE can.

[Rinuko]

It was still there just last night, after reset. And it's not just WAR. It's anyone who can enter the room and kill the mob within 10 seconds.

Didn't they say this is isnt anything they gonna fix on last LL? It something they didnt expect but dont care

[Vnolan]

Didn't they say this is isnt anything they gonna fix on last LL? It something they didnt expect but dont care

http://forum.square-enix.com/ffxiv/t...=1#post4573536

[technole]

lol. And no one was banned for using Titan Egi with Ramuh Extreme either.

You must have forgot YoshiP said in a previous interview they had an official stance that they will immediately correct duties where one role ends up being required over others (Summoner). The fight normally required a tank swap.

Then we had Alexander Gordias Savage, A4S. which everyone took advantage of server ticks to sacrifice party members into multiple pentacles and using healer LB3 to mass raise. It was an unintentional strategy but it did not require any specific roles. Just like the Mario kart meteor strategy in Turn 9 savage, something they never envisioned but it worked.

[Canadane]

Didn't they say this is isnt anything they gonna fix on last LL? It something they didnt expect but dont care

It's the same deal as A11S. You can skip mechanics, skip the boss buffing itself, and cheese the fight.
It's nor a bug, just the fight design for that encounter.

[BluCross]

I think you can't see your old in-game reports, but if there's people who reported by using social media, it might help if they can provide screenshots here, or at least on Reddit if they can't post on the official forum.
Currently there isn't anything that can prove it was "reported 4 months ago."

[Shurrikhan]

Didn't they say this is isnt anything they gonna fix on last LL? It something they didnt expect but dont care

Yes. The person I was responding to seemed to believe otherwise (even that they had, in fact, "fixed" it), and I was casting doubt on that.

There’s a rumor where people believe warriors playing on an SSD have an advantage inside Omega: Sigamascape v1.0 (Savage). Using and SSD or not doesn’t change anything. The loading time is adjusted so they’re loaded the same. It’s just the timing.

What's funny is that the myth that only Warriors could do it anyways had already caught on before the Q&A...