I doubt the packets themselves would be useful to look at. Obviously they would be different between characters, since they contain the info about the character. 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.
I just finished opening about 130-140 nodestones when I noticed I had some pretty bad lag peaks every 4-5 seconds... So I relogged and found myself stuck... I think the client is in a loop since the nodestone data is quite a lot and it will remember all stones opened over time...
Touch (Harold)
EDIT : I like to point out that some names in the list did NOT get stuck by this bug, but due to illegal entering Dream City/Lucid before the world was officially opened! Too bad guys, I will not mention your names, but you know who you are! This is what you get when you break the rules, a bit the same when you all exploited the Kritias bug in the past, funny that it's the same team again...
I doubt the packets themselves would be useful to look at. Obviously they would be different between characters, since they contain the info about the character. 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.
I just finished opening about 130-140 nodestones when I noticed I had some pretty bad lag peaks every 4-5 seconds... So I relogged and found myself stuck... I think the client is in a loop since the nodestone data is quite a lot and it will remember all stones opened over time...
Touch (Harold)
EDIT : I like to point out that some names in the list did NOT get stuck by this bug, but due to illegal entering Dream City/Lucid before the world was officially opened! Too bad guys, I will not mention your names, but you know who you are! This is what you get when you break the rules, a bit the same when you all exploited the Kritias bug in the past, funny that it's the same team again...
Do you have any proof to back up the lachelein cause? Tons of people accessed it and still have not gotten stuck so I am curious to see where you got this from
I would think that if accessing Lachelein was the cause, people would be temp-banned, not single-character-blocked like that. It doesn't sound like something Nexon can even do on purpose (and if it were, the GM's would simply say so in response to a ticket/chat).
I don't see anything wrong entering lachelien when it was first availavle by accident. I mean, it's accessible from maple guide to anyone above 220 lol. Maybe you should pull your head out of your ass for once.
Also some macroimg NL that recently hit 250 on YMCK was also training in lachelien when it was first available by accident. He didn't get stuck or banned and was able to macro his way to 250 safe and sound (while stuck character issue is going on), despite being reported with video evidence several times already
I doubt the packets themselves would be useful to look at. Obviously they would be different between characters, since they contain the info about the character. 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.
I just finished opening about 130-140 nodestones when I noticed I had some pretty bad lag peaks every 4-5 seconds... So I relogged and found myself stuck... I think the client is in a loop since the nodestone data is quite a lot and it will remember all stones opened over time...
Touch (Harold)
EDIT : I like to point out that some names in the list did NOT get stuck by this bug, but due to illegal entering Dream City/Lucid before the world was officially opened! Too bad guys, I will not mention your names, but you know who you are! This is what you get when you break the rules, a bit the same when you all exploited the Kritias bug in the past, funny that it's the same team again...
Theres only 5 people on that list from Luna touch boy. And you talking in plural. Would you mind explaining? @AeonTouchOfAllJobs
my ticket got updated and they said they will be "looking into this issue further" So that tells me that they have a list of "things to try" and a list of people affected. They'll slowly go through the list. I'm expecting multiple extensions. as well as a possibility of still not being able to log in. best of luck and hopefully if not all but some of us see the light of our character landing.
my ticket got updated and they said they will be "looking into this issue further" So that tells me that they have a list of "things to try" and a list of people affected. They'll slowly go through the list. I'm expecting multiple extensions. as well as a possibility of still not being able to log in. best of luck and hopefully if not all but some of us see the light of our character landing.
We would like to apologize that some of you have been unable to access your characters, as observed across our forums and Customer Service portal. We posted an update last week on the forum that we have been investigating the issue, and today we’d like to let you know that we are making every effort to resolve this issue during our next scheduled maintenance on January 12th. We thank you for your ongoing patience while we looked into this issue. "
Comments
Irony
Time to spend some NX on our mules F3.
As AKradian said : I just finished opening about 130-140 nodestones when I noticed I had some pretty bad lag peaks every 4-5 seconds...
So I relogged and found myself stuck... I think the client is in a loop since the nodestone data is quite a lot and it will remember all stones opened over time...
Touch (Harold)
EDIT : I like to point out that some names in the list did NOT get stuck by this bug, but due to illegal entering Dream City/Lucid before the world was officially opened! Too bad guys, I will not mention your names, but you know who you are! This is what you get when you break the rules, a bit the same when you all exploited the Kritias bug in the past, funny that it's the same team again...
Also some macroimg NL that recently hit 250 on YMCK was also training in lachelien when it was first available by accident. He didn't get stuck or banned and was able to macro his way to 250 safe and sound (while stuck character issue is going on), despite being reported with video evidence several times already
I got stuck a few hours ago by entering the Cash Shop and claiming my reward points after doing some of my Daily Bosses.
My ticket got closed as soon as they replied. =(
"UPDATE - 1/9/17
We would like to apologize that some of you have been unable to access your characters, as observed across our forums and Customer Service portal. We posted an update last week on the forum that we have been investigating the issue, and today we’d like to let you know that we are making every effort to resolve this issue during our next scheduled maintenance on January 12th. We thank you for your ongoing patience while we looked into this issue. "
Link: https://support-maplestory.nexon.net/hc/en-us/articles/115000158463-I-m-unable-to-access-specific-characters-on-my-account