[New Users] Please note that all new users need to be approved before posting. This process can take up to 24 hours. Thank you for your patience.
Check out the v.255 - The Dark Ride: Ride or DIe Patch Notes
here!
Client crash on login to leaped character.
Following the latest patch's completion:
https://maplestory.nexon.net/news/64925/complete-scheduled-minor-patch-january-27-2021
After leaping 1 character from Burning World to Bera, I was logged out from Burning World (expected) and tried to log into the same character in Bera. The client crashed after entering PIN.
Restarted the client, same thing happened twice.
Tried a few more times, from then on the client simply would not start up at all. Clicking "Play" on Nexon Launcher causes it to minimize itself but does not launch any new MapleStory process. Reinstalling the launcher did not help. Restarting the PC brings it back to the symptoms at the beginning of this post.
On the other hand, logging into a non-Burning-World character seems ok.
Comments
Could you please confirm if your transferred Burning World character was previously blocked from leaping due to the Auction House error message?
Additionally, please provide us with your IGN (in-game name) and world of the affected character.
Thank you!
I leaped from Burning World to Bera. My character was not previously blocked by the AH error (or at least I think so). I did not try to leap before the maintenance today, but I also did not use AH so probably was not affected by that issue.
Players who logged in between 6 AM and 11 AM PST may have experienced the issue where the character wasn't able to be transferred due to the Auction House error message (If you didn't log in to your character during the listed time, you may not have known). This issue was resolved during our Minor Patch maintenance, however, it seems like the affected characters cannot be logged into.
We'll relay the information to the team for investigation.
Hey body, any updade on this situation? I would like to remember that there is as limited event going on right now and we are kind of losing it.
I hope they fix this quickly.
We've deployed a fix few minutes ago at 1:30 PM PST (January 28).
Please try logging into the affected character again and let us know if you still experience this issue.