UPDATE: If you open too many nodes within a short amount of time, and change channel or disconnect, you may find yourself not be able to log back in BUT you will be able to log in a few hours later when the game deletes the data from opening Nodestones that is preventing you from logging in (this massive amount of data is from opening Nodestones, and is being sent when you log in, which is what causes you to be stuck until it gets deleted). This bug can be considered as resolved.EDIT: As of Override, you can still become stuck for the same reasons below.
-----------------------------------------------
UPDATE: As of January 12, 2017 after the Scheduled Minor Patch stuck players can now log in.
**BUT, unfortunately players who open a large amount of Nodestones may become stuck again.**
http://maplestory.nexon.net/news/20183/scheduled-minor-patch-january-12-2017Bug type:Stuck characters
Description:Specific characters are not able to log into the game
Brief bug summary:After selecting to log in on the affected character and entering the PIC, the game makes the login sound but nothing happens afterwards
More details:The accounts with the affected specific character can log in to other characters just fine. When attempting to log into the affected character, the login notification shows you as online to other players. Players in game can whisper the affected character but cannot find them using the /find command.
Steps to reproduce:(based on what the players know so far)1. Open and disassemble a very large amount of Nodestones (5,000+)
2. Experience a black screen that will not go away (or just disconnect from the game)
3. Close the game and attempt to login to the character that experienced the black screen
4. After entering PIC on that selected character, nothing happens
Expected result:After the login sound, the game should change resolutions and log you into the game
Observed result:After the login sound, the game attempts to log you in but nothing happens
What the players know so far:The GMs are able to replicate the issue when logging into the affected player's character
GMs have attempted to reset/move the player's character to multiple location and the issue still persists
A maintenance alone does not fix this issue
Players affected (AFTER the 21st of June maintenance):(only players who have publicly shared they are experiencing this issue will be posted here)IGN / Level / Job / World / Date of incident / Description of incident
https://support-maplestory.nexon.net/hc/en-us/articles/115000158463-I-m-unable-to-access-specific-characters-on-my-accountWe can use this as a discussion thread about this bug until it has **actually** been fixed.
Comments
You're right. This most likely triggers when you change channels (changing servers), and not when changing maps.
For me, I entered Cash Shop and the game resolution did not change and the screen stayed black. After a while, I closed the game and I still can't log in to my character.
It might give some insight as to what the cause is, Possibly there is no response from the server? But apparently the login noise is played. Anyway it would be interesting to take a quick comparison of the diffences between the login.
PS: Unless you know what your doing, DO NOT POST ANY LOGGED "Packets" as they may contain your pic/password/username
What I suspect is happening is that the client is stuck in a loop trying to build some internal data-structure based on the info sent by the server.
A debug-enabled client would show the exact problem easily, so really all we need to do is wait for the devs (who were apparently informed of the issue) to attempt to log in to one of the affected characters.
Meanwhile, however, we can try to speculate, in an attempt to figure out the cause and prevent other people from getting stuck.
Some questions to those affected:
1. When the black screen is on, do you observe a spike in client CPU usage? Does it seem to be leaking memory? Is it doing a lot of disk or net I/O?
2. If you just wait on the black screen, does it eventually disconnect you? Or does it stay there "forever"?
3. Can you remember what the last few things you did before changing channel were? Anything out of the ordinary? Things to consider:
- Acquiring items (including nodes)
- Accepting or completing quests
- Activating buffs or skills (in particular, 5th job skills that were still active when you cc'ed)
even a GM could not log into my kaiser.
2. If you just wait on the black screen, does it eventually disconnect you? Or does it stay there "forever"? stay forever, could not even close maple, had to restart my computer.
3. Can you remember what the last few things you did before changing channel were? Anything out of the ordinary? Things to consider:
I was using cubes on my tyrant belt
Nexon changed your password? I did not know they can do that.
Also, my screen has turned black many times and froze when I try to change channels or enter/leave the cash shop but I have never been stuck. I just use CAD to close my maple and restart it. I'm soooo happy my character never got stuck. I didn't observe any spike in CPU usage like AKRadian suggested, I just figured Nexon's servers simply are a joke and restarted the game.
-others can /find the character if they're on different channel (it will show the ch)
-'Unable to find' if already on same ch
-can whisper, invite to chat, invite to party
-can not guild/hyper teleport to stuck chars
-stuck characters are registered online on buddy list , alliance, guild, party
I believe this could possibly be fixed by rolling back the character to a state before running into this problem.
How would they prevent it from happening to other characters, or even to the same character again?
They need to find out what's causing this, and fix it. A rollback is not a fix.
Edit: I forgot to mention this happened last 2 weeks as well. It's not like Nexon will ever fix it lol.. Taken from OneLetter's thread: "These should be resolved in the following weekly maintenance.
- Got disconnected and are unable to get back into the game on a specific character." This was posted almost 2 weeks ago.
Still no solution... Stop trying so hard to sugarcoat an incompetent team. We all know they're useless. So what now? They copy paste kms codes, copy paste forum posts, are they expecting to fix this copying their 3 year old solution? Lmao.
I've been stuck since the 19th, 10 days so far.
This completely ruined my holiday break.