Thread: Known Issues After Patch 6.5 (Oct. 4)

The following issues have been confirmed.
We are currently investigating and working to address these issues.

[Current Known Issues]
■During cutscenes for the main scenario quest "Down in the Dark", characters and NPC may behave abnormally.

*We are currently investigating this, but the issue may depend on the environment and we have not been able to reproduce the issue in our development environment. Therefore, if you have encountered this issue, we would greatly appreciate it if you could report it to us with the following information. We apologize for the inconvenience caused by this.

・Date and time of issue
・Name and world of the affected character
・Platform used
・Type of connection and provider used
・System information for Windows and Mac versions
　*System information can be obtained from the settings screen of the launcher.

*Edited on Oct. 31, 2023 6:29 p.m. (PDT)
The issue above was resolved during maintenance work conducted on Oct. 30, 2023 from around 11:00 p.m. to Oct. 31, 2023 4:00 a.m. (PDT).
We apologize for any inconvenience this may have caused.

■Additional information such as Legacy displayed to the right of certain world names on the character selection screen is incorrect.
We apologize for the inconvenience.

*Updated Jul. 30, 2024 8:15 p.m. (PDT) / Jul. 31, 2024 3:15 (GMT)|4:15 (BST)|13:15 (AEST)
This issue was addressed by the maintenance of Jul. 29, 2024 11:00 p.m. to Jul. 30, 2024 3:00 a.m. (PDT) / Jul. 31, 2024 6:00 to 10:00 (GMT)|7:00 to 11:00 (BST)|16:00 to 20:00 (AEST).
We sincerely apologize for any inconvenience this may have caused.

We would like to report on the current status of the following issue.

■During cutscenes for the main scenario quest "Down in the Dark", characters and NPC may behave abnormally.

We had asked for reports regarding this issue as it may depend on the environment and have received many reports from our players. We are deeply grateful for your cooperation.
Upon investigating with the provided information, we were able to confirm that the issue only occurs in some environments.

Although we have found a solution to some degree, since the issue only occurs in certain environments, we will need to perform different verifications in various environments and as such expect for the fix to take some time. Currently, we are aiming towards a fix in Patch 6.51.

We sincerely apologize for the wait and inconvenience, and ask for your patience until the issue is resolved.