I’m not talking about an official manual patch. Instead, I just wrote how to update the Emil Chronicle Online client manually -yes, literally manually. This guide is only appropriate to you if:
- You have a very slow/unstable connection so that you cannot finish a big update.
- You have tried updating many times without success.
- You are patient enough to read and follow this guide (which I bet most of you are not).
- You don’t have any other choice left.
If you’re wondering why should you choose this way to update, one thing that is almost guaranteed is that you don’t need to repeat the update from the beginning every time you fail, since you’ll download the files manually. You can use any download manager to pause and continue every time you want.
Update (22 Aug 2013): Step 3 up to 9 can be replaced by using the application I posted here.
The big idea is to redirect the patch server into your own computer (localhost) so the launcher would request update from your own computer. To do this you need a web server. OK, for those who do not understand, you can forget this paragraph and continue.
- Download nginx (around 1.15MB).
- Extract the archive and run the nginx.exe. It will not show anything. Oh and if you run Skype (which may use port 80), close Skype first before running nginx. After you run it, try http://localhost. If it opens a nginx welcome page, you’re good to go. If it’s not (timeout or whatever), then nginx is not running yet.
Update (22 Aug 2013): Step 3 up to 9 can be replaced by using the application I posted here
- Open folder
htmlwithin that nginx folder. Create a new folder named “eco”.
- Now download this file http://patch.gungho.jp/eco/econew.ver and place it inside that eco folder.
- Now, see what version is your client currently. Don’t tell me you don’t know where to see it. It’s in the launcher’s title. It should be like “ECO Client verXXX”. I will use mine as an example. Mine is currently version 347, so I need to upgrade to 348. Therefore, you have to create a folder named “D00000348” in that eco folder.
Note for the new installation: The version will be “FullPackage”, and no folder
D00000xxx. Instead, create a folder named “fullpackage” and continue inside that folder.
- Open the D00000xxx folder you just created. This folder will contain all the update files. Of course, you have to download it manually. What files are you going to download? Firstly, this: http://patch.gungho.jp/eco/D00000348/dl_list.txt. For the noobs who confuses themselves because you see a webpage instead, save it. Don’t know how to save a web page? Hit Ctrl+S. If you’re done, place that file into the D00000xxx folder.
Note for fullpackage: dl_list.txt file is located here instead: http://patch.gungho.jp/eco/fullpackage/dl_list.txt
- Open that dl_list.txt file. This file will show you what files to download for the update. For this example, the dl_list.txt should look like this:
- For the first line, it says eco.ver,5. It means you have to download http://patch.gungho.jp/eco/D00000348/eco.ver, which has 5 bytes of size. Then you have to download http://patch.gungho.jp/eco/D00000348/ver00000348_1.cab, which has 10240000 bytes (10000 KB) of size. And so on, continue until the end of dl_list.txt.
Note for fullpackage: The URLs you need to download are http://patch.gungho.jp/eco/fullpackage/eco.ver, http://patch.gungho.jp/eco/fullpackage/ver00000345_1.cab, etc.
- Place all of the downloaded file requested by dl_list.txt in the same folder as dl_list.txt. Congratulations! You have completed the downloading task.
- Now it’s time to manipulate the client to think that your computer is the patch server. Go into your eco client installation folder (where eco_launch.exe resides). Open the upsv.lst file using notepad. For the noobs, open notepad, drag the file into the notepad. Change “patch.gungho.jp” into “localhost” or “127.0.0.1“. Don’t forget to save it.
- Run your client (eco_launch.exe) and run the patcher as usual. It should update very quickly now.
- When you’re done with the patching (updating), remember to restore the upsv.lst file (step 10) contents into “patch.gungho.jp” back, unless you will always need to do this tutorial again.
- For the new installation: The launcher might not respond for a few minutes while it’s still extracting files. It’s not a problem. Wait until the
_tempfolder in your client folder disappears. It indicates the installation has finished, and you may close the launcher.
Run nginx and repeat step 4 to 12 if you want to update manually again. Oh, and of course, adjust the version number to your need. To remind you again, the example above is to update to version 348, so the client is currently running version 347.
If you want to shutdown nginx, use task manager and kill nginx.exe process.
Sorry for my bad English. If you experience problems, you may leave comment. I may or may not reply though.