Known Issues Regarding Client Crash In Specific Conditions (Aug. 7)
■Issue ①: Client may crash upon exiting a duty
We have confirmed that the client may crash when exiting a duty if more than 101 entries are registered in the blacklist.
We have received many reports that this occurs when exiting to housing areas.
However, it is not limited to housing areas and may occur in all areas depending on the content and volume of communication between the server and client when exiting from a duty.
This issue will be addressed with a HotFix on Friday, 8th of August.
*Updated Aug. 8, 2025 10:15 (GMT) / Aug. 8, 2025 11:15 (BST) /Aug. 8, 2025 20:15 (AEST).
Issue ① was addressed by the maintenance of Aug. 8, 2025 6:00 to 8:30 (GMT) / Aug. 8, 2025 7:00 to 9:30 (BST) / Aug. 8, 2025 16:00 to 18:30 (AEST).
We sincerely apologise for any inconvenience this may have caused.
■Issue ②: Client may crash when receiving a chat
We have confirmed that the client may crash under certain conditions when the "Maximum Display Count" for chat bubbles is changed to a lower value in Chat Bubble Settings > General Settings > Basic Settings.
We have also confirmed that this issue can be avoided by either logging out and back in, or by disabling and then re-enabling chat bubbles after changing the "Maximum Display Count" to a lower value.
We kindly ask you to try one of the above methods to avoid the issue.
■Issue ③: The client may crash upon closing the tutorial window for transportation or escort quests.
Under certain conditions upon closing the tutorial-specific explanation window for quests such as transportation and escort quests, we have confirmed that the client may force close.
This issue does not occur when the tutorial-specific explanation window opens automatically for the first time. It only happens when the window is opened and closed via the objective list or chat log link. Therefore, we kindly ask that you refrain from opening the tutorial-specific explanation window from the "?" icon displayed.
Additionally, we ask for your patience as it is expected to take time to address issues ② and ③.
We sincerely apologise for any inconvenience this may cause.
*Updated Sep. 2, 2025 10:55 (GMT) / Sep. 2, 2025 11:55 (BST) / Sep. 2, 2025 20:55 (AEST)
Issues ② and ③ were addressed by the maintenance of Sep. 2, 2025 6:00 to 9:05 (GMT) / Sep. 2, 2025 7:00 to 10:05 (BST) / Sep. 2, 2025 16:00 to 19:05 (AEST)
We sincerely apologise for any inconvenience this may have caused.







