Mabinogi may track updates in game terms as "Generations" and "Seasons", but in technical terms for the client version it uses revision numbers (like 123 and such). The revision numbers are different for each distribution, for example KR may be up to revision 850 while NA is only at 210 at the time (KR updates a lot more often, they tend to be buggier and have more gachas and such).
The easiest way to see which revision your installation of Mabinogi is updated to would be to open your /package/ folder in the game's install directory and checking out the highest pack file in there. For example if the last file in there is 212_to_213.pack, then you can be reasonably sure that your install of Mabinogi has been updated to r213.
However the technical way that Mabinogi keeps track of the revision is with the version.dat file in the main install folder. This is a binary file that you can view with a hex editor that simply contains the version number (in hex, little-endian).
D5 in hex is 213 in decimal, so that's the version that the Mabinogi updater would consider me to be on at the time of this guide. If you were to change this number to something lower, for example, the launcher would try to update you again as if you were on the older version (in case you need to fix a botched update).
The Mabinogi patch files are kept and served through FTP.
- http://mabipatchinfo.nexon.net/patch/patch.txt contains the revision and launch info. For example the first line, patch_accept, is 0 to tell the launcher that the game is under maint and to not update, and it's 1 to tell the launcher to go ahead and update if needed.
- ftp://mabipatch.nexon.net/ is the actual patch server.
Nexon disabled directory listings a while ago. This means that unlike "normal" FTP and web browsing, folders will always appear empty and you need to know the filenames to access anything. Each revision of the game has it's own folder, for example update 214 is at ftp://mabipatch.nexon.net/214/. If a revision exists the folder will display as "empty", if a revision does not exist then you'll get an error depending on what method you're using to connect/browse.
Revision does not exist (Firefox).
Correct display (Firefox).
In order to find the filenames for the patch, you can pull up the patch file listing manually. This is generally in the form of "xxx_to_xxx.txt", listing which revision to which is being patched. For example "213_to_214.txt" in the /214/ folder will get the info on the files needed to update from 213 to 214 normally.
The data goes...
213_to_214.000, 10485760, 8e57693415089405259ccc7d2e4cce41
213_to_214.001, 10485760, 13f31052cbd5828f6aaa7b21cd85f337
213_to_214.002, 10485760, fb337bb397e47860770b0342f715cbd2
213_to_214.003, 263774, 9d2d35b77e86e8b3706d0adccb9e5e71
# of files
filename, size, hash
In the same vein, if you wanted the info on a "full" patch, you'd check out "xxx_full.txt".
ftp://mabipatch.nexon.net/214/214_full.txt - 488 files, way too many to copy here.
So anyways if we wanted to manually download the 213_to_214 patch (assuming we're on 213 right now and wanting to download the next version), we'd go put in and download those four files from the folder (ftp://mabipatch.nexon.net/214/213_to_214.000 and so on).
These four files are a split zip file. While it may be tempting to treat these as you might fancy split rars or something (especially as some archive softwares associate themselves with numerical extensions by default), you will need to concatenate/join these files before you can actually open the update zip. You can either use a hex editor, or the command line to do this.
Once the files have been downloaded and merged, you will be able to see and extract the patch successfully.