We have discovered an issue affecting the PlayStation®5 version, whereby logging out while in certain areas and attempting to log in with the same character will result in the player being stuck on the loading screen, preventing access to the game. We offer our sincere apologies for the inconvenience caused.
■Areas Known to Be Affected
・The Puppets' Bunker
・The Fractal Continuum (Hard)
・Saint Mocianne's Arboretum (Hard)
* In the case of instanced areas, players will be able to log in again once the instance has ended.
■To All PlayStation®5 Users
We are currently doing our utmost to resolve the issue, but for the time being, we ask that you refrain from logging out while in the affected areas.
■Workaround for Players Who Have Logged out While in Rhalgr's Reach
In the event that the issue has occurred after logging out while in Rhalgr's Reach, restarting the PlayStation®5 console and starting FINAL FANTASY XIV again will allow you to log in. While we understand that following these steps may cause some inconvenience, they should provide an effective workaround. Once you have logged back in, please avoid logging out while in Rhalgr's Reach.
■Workaround for Players Who Have Logged out While in Other Areas
In the event that the issue has occurred after logging out while in other areas, please try restarting the PlayStation®5 console and starting FINAL FANTASY XIV again. However, we have confirmed that does not resolve the issue in all cases.
If this workaround does not prove to be effective, we ask that you use the PlayStation®4 version via PlayStation®5 backwards compatibility. This issue only affects the PlayStation®5 version, and we have confirmed that players will be able to log in to the PlayStation®4 without the issue occurring.
■Cause of the Issue and Steps Taken to Resolve It
We are treating this issue with the utmost importance, and we are working to resolve it in addition to a separate issue, which affects toggling to and from Japanese text input on a Japanese keyboard, occurring as of Patch 5.55.
Per our investigation into the matter thus far, we believe there is a high possibility that an error occurred during the process of optimizing the game for faster loading speeds, or that this process brought to the surface a latent error that had already been present, and that the two issues mentioned in this post are both the result of this same root cause.
At present, we have nearly finished testing whether the other areas of the game are affected by this issue. If we discover that any other areas are affected, we will make an announcement as soon as possible.
We wish to offer our sincere apologies for failing to ensure the stability of this aspect of the game, and we will do all in our power to resolve the issue quickly and prevent similar problems from occurring in the future.
*Edited on Jun. 2, 2021 at 8:45 (GMT) / 9:45 (BST) The issues above were addressed during the maintenance that took place on Jun. 2, 2021 6:00 to 8:40 (GMT) / 7:00 to 9:40 (BST). We sincerely apologise for any inconvenience this may have caused.