Concrete proof finally provided that the 2002 error has NOTHING is server side issue

[lezard21]

Someone on reddit was nice enough to do a full technical analysis of the cause of the 2002 error and JUST LIKE everyone has been saying.

The server is resetting you client every 15 minutes and if it desyncs during this client reset it crashes the client.

This has nothing to do with your internet but an internal server side check done once that causes you client to crash.

Fix this now and stop blaming your consumers for internal coding issues.

https://docs.google.com/document/u/0...jk/mobilebasic

Source: reddit user u/pitiful-marzipan

After being called a Karen, insulted and threatened by the forum's fanboys and whiteknights I feel so vindicated now.

Thank you OP and whoever did the research!

[ijuakos_xqwzts]

After being called a Karen, insulted and threated by the forum's fanboys and whiteknights I feel so vindicated now.

Thank you OP and whoever did the research!

"Vindicated"? All they did is sniff some traffic and make assumptions on a behavior of their network client. While I've been able to see similar behavior (specifically, a connection close and re-establish every 15.5 minutes), there's nothing to back the assertion that a desynchronization during this reset will crash the client.

[PredatoryCatgirl]

Guess what dude: I agree with this issue and still think you're a Karen because of how you phrase your arguments and the measures you suggest people take. Being right about one thing and being a whiny baby are not mutually exclusive.

[lezard21]

Guess what dude: I agree with this issue and still think you're a Karen because of how you phrase your arguments and the measures you suggest people take. Being right about one thing and being a whiny baby are not mutually exclusive.

First off, the way I phrase my arguments is because I'm not a native speaker. I apologise if you take offense at the way I say things, but understand not everyone on these forums is a native speaker.
Second, what measures have I suggested people take? I have suggested measures SE should take because this is a SE problem, not a user problem. The users are the ones being affected.
Keep the insults coming though.

[Belisaire]

I was defending SE early on but this is shameful especially since Yoshi-P has been going on record blaming consumers internet connection.

I've been with the game since 1.0 and have seen ups and downs but haven't seen Yoshi-P straight up misdirect like this. I'm also concerned that Square-Enix's angle seems to be to just pray the issue goes away.

[Eriane_Elis]

I was defending SE early on but this is shameful especially since Yoshi-P has been going on record blaming consumers internet connection.

I've been with the game since 1.0 and have seen ups and downs but haven't seen Yoshi-P straight up misdirect like this. I'm also concerned that Square-Enix's angle seems to be to just pray the issue goes away.

It may very well be the user's internet and not them. I'm sure they know better about the situation than we do. However, I don't think that people should lose their session entirely (auto-retry for example) but we don't really know how things work and it could potentially cause severe desync and other network related issues. They have at least allowed people to log back in and resume their queue but it doesn't always work yet. To be honest, these things aren't easy to understand or fix and it's easier to be an armchair developer and think "all they need to do is this" to fix it but the reality is always going to be complicated.

[PredatoryCatgirl]

I was defending SE early on but this is shameful especially since Yoshi-P has been going on record blaming consumers internet connection.

I'm going to give him the benefit of the doubt here and assume that he was wrong as opposed to lying.

[Hasrat]

I'm going to give him the benefit of the doubt here and assume that he was wrong as opposed to lying.

Additional consideration: player load has literally never been this high. Could as easily be a case of "we never knew this was a problem because it's never come up before."

I'd feel more confident in this assumption if they were to address it with intent to fix, tho.

[Tsukino]

Additional consideration: player load has literally never been this high. Could as easily be a case of "we never knew this was a problem because it's never come up before."

I'd feel more confident in this assumption if they were to address it with intent to fix, tho.

We get the exact same 5006 and 2002 errors every expansion. They've closed the client instead of reconnecting every time. The queue itself has never been this bad before, but the errors and the bad software design have always been there.

They only feel like they have to respond to it because the interest is so high that they're getting killed in the media about it this time.

[Hasrat]

We get the exact same 5006 and 2002 errors every expansion. They've closed the client instead of reconnecting every time. The queue itself has never been this bad before, but the errors and the bad software design have always been there.

They only feel like they have to respond to it because the interest is so high that they're getting killed in the media about it this time.

Perhaps a more accurate correction of my assumption would be along the lines of "the problem has never persisted long enough to warrant investigation/fixing."

But yes, either way it's all the same. Kinda surprised they're not giving more updates on the situation, just to at least sound like they're doing something or making progress somewhere. Even if it's just "far as we can tell, everything's running as intended."