Thank you square Enix for acknowledging 2002 and working on a fix

[jadeblade]

https://na.finalfantasyxiv.com/lodes...625.1637359909

Thank you , that’s all most of us are asking.

Just let me queue without kicking me , I don’t mind even if I wait 4 hours as long as I can do my chores , workout, etc and not to babysit the queue.

Thanks again I hope we get some good news soon

[CaptainFishSticks]

I have to wonder why anyone would have even doubted that they were aware of these error codes and working on fixes. Are newcomers just so jaded by Blizzard that they felt like the developers had just completely ignored the problems?

[Krotoan]

I have to wonder why anyone would have even doubted that they were aware of these error codes and working on fixes. Are newcomers just so jaded by Blizzard that they felt like the developers had just completely ignored the problems?

Because people wanted not just to be mad, they needed to be RIGHTOUSLY mad. They needed to believe that on top of being inconvenienced they were being outright lied to and slighted. ... or they just wanted something to claim SE was wrong about and lookit how bad they "really" are.



I dunno..


but nice, everyone got their explanation and what SE is doing about it. Hopefully we can go back to our regularly scheduled forum nonsense.

[LianaThorne]

Hopefully we can go back to our regularly scheduled forum nonsense.

I'm sure someone will still find fault with this. >_>

[Krotoan]

I'm sure someone will still find fault with this. >_>

I cannot wait to see the neg-spin they all put on it.

[ReynTime]

I have to wonder why anyone would have even doubted that they were aware of these error codes and working on fixes. Are newcomers just so jaded by Blizzard that they felt like the developers had just completely ignored the problems?

Because the 2002 error wasn't fixed in 8+ years. No one can be blamed for doubting they'd do more than apologize for it.

[Kes13a]

Because the 2002 error wasn't fixed in 8+ years. No one can be blamed for doubting they'd do more than apologize for it.

I had never heard of it even existing until Dec 3rd at 1 am.

so cant have been a huge issue...sorry

[Krotoan]

I had never heard of it even existing until Dec 3rd at 1 am.

so cant have been a huge issue...sorry

It pops up for every release during the surge when people top out the login servers. However it has never been THIS bad. I'm betting the reasoning they never really got around to fixing it was the capacity issue never stuck around for more than a few days. Once everyone settled into routine the errors became far less common and didn't necessitate addressing.

[Kes13a]

It pops up for every release during the surge when people top out the login servers. However it has never been THIS bad. I'm betting the reasoning they never really got around to fixing it was the capacity issue never stuck around for more than a few days. Once everyone settled into routine the errors became far less common and didn't necessitate addressing.

its like that door that jams every year at the Black Friday sale... 355 days of the year you dont remember it...

[Veridiano02]

I have to wonder why anyone would have even doubted that they were aware of these error codes and working on fixes. Are newcomers just so jaded by Blizzard that they felt like the developers had just completely ignored the problems?

As a newcomer... Yes, we are. Not just Blizzard, I quit WoW a long time ago, but other companies are pretty much the same. There's a bug from TESO on launch I'm still waiting for Zenimax to fix...