Thread: re: Known Issues After Patch 4.5 (Jan. 17, 18)

Originally Posted by Dualgunner

So submit your application to SE since you apparently know how to accomplish in 5 minutes what their whole team said they're waiting till 5.0 to tackle.

First of all SE is a Japanese developer and I don't speak Japanese, let alone want to live in Japan.

Second of all I don't want to work at SE. I earn more doing what I currently do.

Thirdly providing a simple solution to a huge issue doesn't mean I want to work at their company. It just means I want them to fix the game.

Originally Posted by therpgfanatic

First of all SE is a Japanese developer and I don't speak Japanese.

Second of all I don't want to work at SE. I earn more doing what I currently do.

Thirdly providing a simple solution to a huge issue doesn't mean I want to work at their company. It means I want them to fix the game.

I doubt your "simple solution" is really so simple, else the devs would have implemented it already. They've known about this issue since 1.0. That's ~9 years of them knowing it's a thing, 9 years of knowing their own code and not having put any fixes toward it, and you expect me to believe Anon over here has the solution and it's just copypast if(Attack){Jobcan'tchangeforfiveminutes}?

Originally Posted by therpgfanatic

The two man method is actually much slower because it requires the blue mage to cast a spell and coordination between two people to deal with.

I think it's an exploit too but it's not nearly as much of a problem as every lv70 character being able to slaughter an entire zone and power level their blue mage job.

And the one man method doesn't?! Now I know you're a fearmongering troll. No, two man method is as simple as the BLU fish slaps enemy after enemy while a RDM follows mopping up behind them. Fast as can be.