Incest Patcher notes:
I realize this is a bit long and 99% of you won't care but
I personally dislike silence from devs/companies that
I follow so here's what's up presently.
TL;DR
I am working on it but it may be a couple days, I want to check 0.753.6 more thoroughly and I'm adding some stuff.
Tips/Misc
With versions not in it's database you may want to run it from the command line with the "--debug" switch so you can see what's going on.
0.753.5
This version does not need patched.
The patcher shows an unexpected result because it didn't find the binary signature that, normally, is always there. (Really old builds prior to 0.752 will likely show a similar result status.)
You can ignore that message and just play the game. This build's download was pulled very quickly and replaced with 0.753.6 which does need patched, more on that below.
0.753.6
I am testing the new release (0.753.6), some stuff has changed so you may get "Unexpected result" if you run the patcher on a patched copy. I'm making some changes to the code to try to make it a bit more flexible with what it sees and I'm changing the result text so it's a bit more clear on what's going on.
I also want to test 0.753.6 more thoroughly than usual since some of the structure has changed so it may be a day or two before the new patcher version is released.
Features/Improvements
I added some new features as well, it shows the release notes for matches in the database in normal and --info modes. (I'll be adding switches to turn on/off information as well, as of this writing I have not added those switches yet.)
I'm somewhat rewriting bits of it to allow for more than one "patch type"... just in case.... (there's already a change with 0.753.6 where the second, invalid, signature is now missing so the code needs to be aware not to look for it.)
I've added functions so it can show you your save folder (and how many saves are in it). I may have it do a warning if the build being patched (or examined) is known to not be compatible with the saves.
The backup code could use a tweak too; if you run the patcher twice on the same file, the original backup is lost and it should not do that so I need to come up with something a bit more sophisticated.
Remote Database?
I've also had thoughts on having it be able to download the game database from somewhere.
The main pro for having a remote database file would be is if a new version of BoTN is released the patch wouldn't need to be updated unless the patching process itself was changed.
Concerns would be:
- If someone hacked whatever serves the database file, that would suck although I would have some safeguards (and it could only affect BoTN, the file it will patch is hard coded.)
- Some folks may be uncomfortable with having the patcher download information from a networked server.
- It would not be able to do download the database if it did not have internet access.
- I would need a good place to host the database file (which would basically be a text file in some format)
GitHub
Should I put this on GitHub as an alternate download source? Yeas? Nays?
I know there are some alternates to GitHub but I'm not that familiar with them.