Regarding the dreadful error code 38...

[Alloy]

Is anyone else suffering from it? My main is suffering it again, and now it's not only monster life. After failing the cash shop too, it then proceeded to affect the character itself, when I changed channels. Now, everytime I log on it, I just crash to desktop with the "Error code 38" message popping out.

I can wave goodbye to the gingerbread man event I guess!

And also, anyone knows a way to fix it?

[Mazz]

Is anyone else suffering from it? My main is suffering it again, and now it's not only monster life. After failing the cash shop too, it then proceeded to affect the character itself, when I changed channels. Now, everytime I log on it, I just crash to desktop with the "Error code 38" message popping out.

I can wave goodbye to the gingerbread man event I guess!

And also, anyone knows a way to fix it?

Bit of a bump (sorry), but just wondering if you managed to fix this at all? I have a friend getting the exact same error and he doesn't know what to do aside from just logging a ticket and waiting :(

[SaptaZapta]

A guildy of mine has the same problem. No solution that I know of

[Foxino]

I had this a few times at HoH when a zero was on the map. Don't know if this helps?

[SaptaZapta]

I had this a few times at HoH when a zero was on the map. Don't know if this helps?

That's not the same issue. (Although it scared me a lot when I logged my Kanna on at HoH and immediately crashed with Error 38, on two different channels... But I tried again after 2x was done and she was ok.)

[SlayerZach]

The only thing that's worked for me was undoing my link skills.. I was desperate enough to re-link my skills, then undo them the next day in hopes for it to unglitch my character; it didn't seem to work until I tried to log in a few more times(?)

I cleared out some things from inventory (since it feels like an inventory issue) once I got lucky enough to log in. Unfortunately, it still did not fix the cash shop error. :|

Edit: On the subject of the Zero error 38, that's something completely different. You shouldn't have to worry about having your character locked out of logging in or whatever.

[Alloy]

I received this PM from Chilly. It was before this thread got rebumped, so I'll leave it here for people to test, and let's hope we get some results between many people.

Have in mind there's still hope, because when the error hit, I was slacking on monster life, and have been until now, and even then, I can't remember the channel I crashed in.

So please, people, mind giving it a go?

Could you try something for me?

My brother and I have both received this exact error he, twice; myself, once. We both exited the error and were able to log into the game in the same way each time and being able to replicate a result lends itself to more than a coincidence. The sample size is not nearly large enough for me to publish this as a "method," but I surely hope this works and may eventually be able to help someone:

1. Allow 3+ hours prior to your last login to that account
2. Utilize GameLauncher.exe, not the website to access your account
3. At midnight (PST, Nexon time) or slightly after to ensure server reset, login to your account and choose a character that can enter your Monster Life farm, any character will probably do, but if you have a "usual" then use it
4. Conduct business as usual if you were checking in to work on the farm (accept the new quests, complete "Play" quests, harvest Waru)
   BE SURE NOT TO STAY LONGER THAN :05, completing all the quests isn't necessary i.e. "Nurture" quests, but doing the three indicated above was part of the replication
5. Exit your farm
6. Log out
7. Log in again this time on your main, preferably on the same channel it was on when you were disconnected, e.g. if you were changing from Channel 9 to Channel 5, log in to Channel 9

I won't dare to raise your hopes, because just proofreading this method makes it sound so dubious. And we both know Nexon has done enough of that already.

My brother "discovered" this method one night after managing his farm and randomly taking a chance at logging in one more time that night before he went to sleep. At the time (two weeks ago) we were both Error Code 38ed, account locked out, D/C at PIN. I copied his best recollection the next night to try and free my account, interestingly enough, it worked. He was afflicted with the EC: 38 lockout two or three days ago, he fell asleep the first two nights and was unable to try it, he tried it yesterday and jawdroppingly, it worked.

I don't know why this works or how, but I hope it works for you.

Best of luck.

Is anyone else suffering from it? My main is suffering it again, and now it's not only monster life. After failing the cash shop too, it then proceeded to affect the character itself, when I changed channels. Now, everytime I log on it, I just crash to desktop with the "Error code 38" message popping out.

I can wave goodbye to the gingerbread man event I guess!

And also, anyone knows a way to fix it?