SE Employee: Yoshi-p, Players are getting fed up with 90000 and 3102. How can we fix it?
Yoshi-P: Easy.... just change the number in the error code... let's call it.... hmmm.... 10102. It's not 90000 or 3102 anymore.
SE Employee: Brilliant!!!!
SE Employee: Yoshi-p, Players are getting fed up with 90000 and 3102. How can we fix it?
Yoshi-P: Easy.... just change the number in the error code... let's call it.... hmmm.... 10102. It's not 90000 or 3102 anymore.
SE Employee: Brilliant!!!!
Except 10102 already exsisted before today, was noticed a lot more before they put the 1017 log in restrictions on all the servers as the duty finder kept crashing from heavy load, and i'm guessing its the same now. Even with the split duty finder groups it seems it wasn't enough and the groups need to be split again.
I think I know what's happening. After being locked out with the 10102 error I noticed something. When I look at the location of my character it says that I'm in the Sunken Temple of Quarn. You can only be in that location if you're doing the instance. Usually if you lose connection from the server it boots you out of the instance to the location you are at before going into the instance.
And it doesn't seem to be doing that anymore. Anyone else notice this?
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.