Such a tease, rising hopes and then dashing it down like that.
But to be fair, I suppose (grudgingly) this is needed to protect the gaming experience of players who are already in the world. I am on a JP world and last night was the first time I ever faced 1017 since Early Access. This means we just have to wait and hope that the measures SE is taking really works!
Except it's not. I was doing a leve, got booted with an error 9000 (not an issue on my end, my connection was fine) and now have 1017. What if this happens during a raid? Ridiculous.
|
![]() |
![]() |
![]() |
|
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.