Thanks @Fiel;! I'm happy you still develop nxpatcher, I still use it over Nexons most of the time ^^ especially when their patcher fails.
Thanks @Fiel;! I'm happy you still develop nxpatcher, I still use it over Nexons most of the time ^^ especially when their patcher fails.
I use @Fiel's patcher almost exclusively, lol. I'm glad he's still working on it as well!
Little bit of a dev blog here.
Now that vacation and thanksgiving are over and I'm finally caught up at work from being gone for so long, I thought I'd finish this up.
NXPatcher Advanced Logic - 75%
WZ Version checking - 50%
INI file reading - 0%
EXE Reading/Writing - 100%
Patch Reading/Applying - 100%
I'm currently struggling with the INI file that NXPatcher Advanced uses. C# doesn't like using INI files by default. I've tried using the app.config, but it's far too clunky for my tastes as it doesn't allow for hierarchical nesting (everything needs to be in the same xml depth). Pretty sure I can find an open source implementation of this.
I committed the code that I have so far. This code will not compile, but it's mostly complete.
https://github.com/mechpaul/WzPatch
Is it just me or did the links stop working?
Has anyone figured out how the new patching system works? In GMS, the CustomPatch***to***.exe exists from 147to148 until 187to188. 188to189 appears to have been deleted. The .patch files ended with 182to183.
Nexon Launcher now downloads one or more .diff files for each file requiring patching in the patch directory. I wonder if they have the same sort of structure, and if the download directory is somewhere within the current ftp. It's kinda weird because every other region seems to have retained their .patch files for patching except GMS.
Are they any different than a standard binary delta?
https://github.com/jmacd/xdelta
This thread was updated to show the new version 2 of the patch file format. I'm currently working on creating a new patcher that will support both versions 1 and 2. Coming soon.
The chinchilla lives! Huzzah!
|
Bookmarks