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

[Zileth]

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

They acknowledged it since Friday

[DBriggs304]

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

so cant have been a huge issue...sorry

When I first returned 5 or 6 years ago, I always got it for at least two weeks then it would just go away. They always told me it was on my end back then though.

[SturmChurro]

Well, I hope it does fix it, because there's going to be an even slimmer chance of getting in after that maintenance otherwise.

[Kes13a]

When I first returned 5 or 6 years ago, I always got it for at least two weeks then it would just go away. They always told me it was on my end back then though.

I believe you, just never experienced it until then

the fact I could look it up online and see supposed causes was evident, so I dutifully checked all the connection things they said to and havent seen it since (not saying its all connection of course, just meaning it never came back for me)

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

[Caduagm]

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?

I mean, they do ignore player feedback on the jobs (healer and tank roles), so it's fair to not believe them.

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

[Kes13a]

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

ugh.. TESO.. I remember a bug at launch in the very very early quests where a needed npc for progression wouldnt respawn very fast, over 200 people waiting for it... would die in seconds.... then more people would show up... was... unpleasant...

[KthAura]

The transparency of this dev team is something I'm thankful for. I've played plenty of games (online or not), and from what i've experienced- I've never seen a team who would go to these lengths to make sure things run smoothly. If it was any other company, they would've just been happy they're rolling in cash from all parts of the world.

Hopefully this means more people get to experience the expansion without any issues! (Including myself!)