10102 error on Behemoth

[Fanderay]

The general order of things is 1017 errors until I get into a queue, and then a loading screen, and then I'm in the game (unless I get another 1017).

On Behemoth right now, once I get to the loading screen I get a 10102 error that says I have lost my connection to the server. I know the issue isn't on my end because I can log onto other Worlds just fine.

The problem has happened 5 times in a row now. Is my specific character bugged, or are others having that issue on Behemoth as well?

[MiokiOso]

same here, but on Cactuar instead

[Pavise]

I've been trying to log into behemoth over the past half hour then finally got into a queue of 300.. After about 5minutes it goes to a loading screen and now plagued with 10102 and 90000 when trying to get my spot back into the queue as well.

[Bluesteel]

I've been trying to log into behemoth over the past half hour then finally got into a queue of 300.. After about 5minutes it goes to a loading screen and now plagued with 10102 and 90000 when trying to get my spot back into the queue as well.

Exactly the same for me

[Maximillian]

Yep 10102 error every time I try to connect. Even after I got in que it would lose connection.

[Nightshade1]

Same... countless 10102's and 90000's.

I was unhappy with 1.0 launch, now with 2.0 the game seems better, but the terrible time it takes get in and play, and the lack of real information coming from Square other than "we know there is an issue, thanks for your patience"... I am starting to feel like I have wasted my time on this game... again.

Edit: I can deal with a queue, but not even allowing people to queue, and when they can kicking them off the server when they finally get in is just terrible and misleading.

[Yuripa]

10102 and 90000 error on Behemoth here........ a week since early access started still we are getting this? I am so over this at the moment.

[Valkrii]

Same issue here.

I've got to say, the game is AMAZING and I love it to death and I know EVENTUALLY all of these issues will be fixed...but all the same, this is a bit disheartening...

[Zarcoft]

Same here on Behemoth

[backwind]

same issue!
10102>10102>10102>90000>10102 again