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

[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.

[therpgfanatic]

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.

[Dualgunner]

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}?

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.

[BillyKaplan]

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.

To be fair, I'm not sure the delay is due to the complexity of the code so much as it is how delicate and important the system in question is. Even small amounts of code can have bugs in them, and I can only imagine how much more thorough the testing cycles are for big updates, not to mention expansions, compared to hotfix patches. Which is more than a valid consideration.

[Arrius]

To be fair, I'm not sure the delay is due to the complexity of the code so much as it is how delicate and important the system in question is. Even small amounts of code can have bugs in them, and I can only imagine how much more thorough the testing cycles are for big updates, not to mention expansions, compared to hotfix patches. Which is more than a valid consideration.

Possibly have to wedge it between and make sure it doesn't break with the changes they already have in place for 5.0.

Edit: I also remember the 'delay' in slaying quests/hunt logs/relic book steps, and they might also fix that as well. And that's a whole can of worms in itself to make it work in every scenario possible without problems.


The 'suggestion' of OP's hotfix isn't smart, either - What if I am in duty queue for DPS, but am dealing with a monster as a Paladin and the queue pops?