Binding Coil of Bahamut Discussion

[Ariyn]

Gating boss kills behind a bug like this just to prevent people from clearing content too soon is just amazing. I have little doubt they will not even mention this before 2.1 and then it will "magically" fix itself as 200+ people roll over it day one of the patch baring day long maintenance.

Exactly this. SE is known for obscene mechanics issues. It's essentially their way of halting progression until they are ready. This bug will stay there until 2.1 I'm sure. In their eyes it's killable and only those with extreme luck will be able to do it.

Guess it's back to FF XI days and class stacking just to beat a single broken mechanic

[Supap]

Great news: Twister...

....

...

received no changes.

Yup, so happy a twister thread made it to "accepted bugs" and nothing was done about it

[Senzura]

Yup, so happy a twister thread made it to "accepted bugs" and nothing was done about it

Accepted bugs are not confirmed bugs

[Vodomir]

Accepted bugs are not confirmed bugs

And even more apparently not "fixed bugs". Maybe SE needs some time to figure out what exactly causes this issue and to come up with a working fix? It's not like any accepted bugs will always be fixed with the very next updates. Some things need time for proper investigation or tricky coding. Apart from that if this is really related to the latency, position updating bug, then they probably have to rework all of their net code, which will probably take some serious ammount of time.

[Alvana]

-snip-
Video demonstrating the issue: https://www.youtube.com/watch?v=sHo3AewOwog

If that's how modified raid 1 deal with twister I can see now why Xil won't stop complaining about it everyday. I'm still laughing. *troll-eye* -> We love you guys.

[SonyaArin]

Accepted bugs are not confirmed bugs

This statement is exactly why I'm trying to draw more attention to it. There's a possibility this is 'working as intended' and that we are all missing something, it's even possible it's not working as intended but they'll say that it is as a gate to the content. But I want to keep drawing attention to it until we get a response, whatever that response may be.

[savant07]

Exactly this. SE is known for obscene mechanics issues. It's essentially their way of halting progression until they are ready. This bug will stay there until 2.1 I'm sure. In their eyes it's killable and only those with extreme luck will be able to do it.

Guess it's back to FF XI days and class stacking just to beat a single broken mechanic

Did FFXI have class stacking issue in the raids? How often?

[Doctor-]

bumping for justice.

[Greg]

We did it with 4 physical DPS, not sure how 3 magical pairs up? but it most likely can be done..

It's a bit harder because Knights reflect magic damage where as Soldiers straight up just don't take physical damage. Not undo-able but probably a harder set up than 3-4 physical.

[Subucnimorning]

Soldiers take some physical damage, it's just reduced. If this wasn't the case I wouldn't be able to beat on the soldier to keep my rotation going while waiting for dreadnought to spawn since hitting for 0 does not advance monk stances. Now if they happen to have stone skin up then yes you hit for 0 until that's down.