I'd like to use the latest rev. I just downloaded it, compiled successfully, server runs great - however: the client won't start!
I've downloaded the latest data 2.0 folder, looked up the clientinfo.xml which is set to my localhost. Also I checked mmo.c as recommended which is set to 20120410.
So I downloaded 2012-04-10aRagexeRE.exe and diffed it with with ShinsDiffPatcher and this WeeDiffGenerator (just got the recommended patches). After that I simply copied the patched file to my fully updatet Miruku installation and BAM -> "attempt to call a nil value".
My only chance now to kill that is over the task-manager.
Did I miss something to do? :/
//edit1
Well, I looked arround the forum and a bit more google and tried to fix that problems by loading the LUA/LUB files from the "Lua-Project". Now the error is gone BUT the Setup shows up instantly. Well, I guess you need some Settings for your first run but after hitting "ok" or "cancel" the setup windows shows up again, and again, and... so on. As said before: the only possibility to close it is over the TM.
Question
Sacer
Hi,
I'd like to use the latest rev. I just downloaded it, compiled successfully, server runs great - however: the client won't start!
I've downloaded the latest data 2.0 folder, looked up the clientinfo.xml which is set to my localhost. Also I checked mmo.c as recommended which is set to 20120410.
So I downloaded 2012-04-10aRagexeRE.exe and diffed it with with ShinsDiffPatcher and this WeeDiffGenerator (just got the recommended patches). After that I simply copied the patched file to my fully updatet Miruku installation and BAM -> "attempt to call a nil value".
My only chance now to kill that is over the task-manager.
Did I miss something to do? :/
//edit1
Well, I looked arround the forum and a bit more google and tried to fix that problems by loading the LUA/LUB files from the "Lua-Project". Now the error is gone BUT the Setup shows up instantly. Well, I guess you need some Settings for your first run but after hitting "ok" or "cancel" the setup windows shows up again, and again, and... so on. As said before: the only possibility to close it is over the TM.
Edited by Sacer1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.