..............................
Printable View
..............................
Hah yeah just got it after getting out of a solo instance, or at least I assume I managed to get out of it....
Same here, only got it while trying to enter a group instance. Let's hope this isn't a sign of bad things to come.
YES. I couldn't make it through Cutter's Bay tonight without being CONSTANTLY disconnected by error 90000. I thought they fixed this already???
woh, totally happened twice. Once on a solo story mission and the other one on duty finder. For some reason it bugged the dungeon and only winded up with a dps unable to recruit the rest.
same, just exited an instance and got error 90000
Hmmm, no issues for me tonight.
I thought they fixed it twice already, 3x if you consider Jp servers?
3102 after exiting dungeon ... this is so annoying
yup, getting 90000'd and 3102'd all over again.
This if f'king bullshit. Big surprise their 'fix' didn't fix anything.
Yeah, but hey we get an extra 7 days free access :)
Sigh, it ran better in beta than this trash has been. Dunno why they try to do the minimum to fix the shit, and wait till the last possible second to fix it. I've been 50 for 3 days almost now, and still havent been able to finish my story line due to miscellaneous bugs and fixes being implemented day in and day out, or can't log in, or get booted from instance on loading screen. Its getting a bit out of hand...wait no, its gotten way out of hand already.
Seems instances are down for everyone. Only making it 5/8 into Ifrit.
90k and 3102 are generic error codes. Doesn't mean what caused them are the same as before. 90k is DC, 3102 is character still logged into game.
3102 does not last long. I got back into game in 10 minutes.
The real issue is what is causing the duty service errors with the new duty service (didn't i mention, new)
yeah your server is full thats why you're getting them just wait till they open slots up, its wayyyy faster tan 2 days ago. They are not errors they are messages telling you information
Wooo locked out of the game once again. The only way I fixed this in Beta was by doing a full re install... Such bs.
.....TY for helping make up my mind about subbing SE....errors that have been around since beta....and still you cant fix it
Server is trolling me so hard. Every time I try to get into Ifrit, either I DC to the 90k or half my party does, so I have to start over. This is whack!
Edit: Always followed up to 5-10 minutes of 10102.
That's 1017, this is 90000 (disconnected from/lost connection with server) and 3102 (character still logged in, please wait until character is logged out and try again). The 90K was happening before, particularly during zone teleports/Duty Finder connects, and the 3102 is a consequence of that. 1017 would be if the server was full and they weren't even eligible for a queue position. Please don't use your Chronicler's Crown to make up for your lack of information or your clearly elitist attitude, friendo.
Yup.. got disconnected from server and now the 3102 error again.
Just give it 10 minutes Katee, 3102 will go away (usually, it has for me since after beta 4). The response time for the server to recognize that you are DC'ed from game is slow.
The duty service is borked though. Overloaded and not transferring everyone properly which is first reported as a 90K (DC) and a 10102 (still stuck in the DC state in duty service)
Luckily for me the only error I came a crossed was the 1017 error ( which isn't really an error XD).
Never seen 90k nor 3102, guess I'm just one of the lucky ones ( or server :P)
well im still getting these bullshit error codes.. i got 90k when joining a garuda battle after waiting OVER 45 MINUTES for the crap duty finder to pair me up.. finally get a party and this shit happenes!!, seriously!!! i guess SE cant fix there shit cause this has been going on for waayyy to long.
yeah buddy 3102 games crashing some more 3102 games crashed 3 times so far since reset. never had a single crash before now FF ARR has stopped working all day.
I'm getting kinda fed up with this... It's extremely sad that they take such long time to fix these problems. I was looking forward to some new content, but I guess that's just a dream, seeing all the problems they have with the servers...
Yep still getting booted and the 3102. Last one happened 15mins ago on Excalibur and still can't get back on even after restarting the game. So this isn't fixed and I can't keep playing and getting booted for example from dungeon runs. Ticking other players off and myself. This stuff has to be fixed like now.. tomorrow.. this week. Surely they aren't going to claim it's fixed and just leave it to happen all the time.
Y'all have let all the great work you have done become overshadowed by all this mess and that is just a shame. The discussion should be on the game and not the errors. Even gaming sites are starting to post up bad reviews .. it's like 1.0 again. Doesn't matter if it's not gameplay that's jacked.
The slack y'all were cut expired a long time ago. Not sure how you could afford to let this happen after all that's happened. Just sad.
Keep getting this every time I enter a instanced scene!!!