I apologize for having been vague. I should have clarified that I have not written a new version of Version Checker but rather modified it to reduce the trouble modders have supporting it, fetch threads from the forum only with the code whereby Version Checker already fetches forum threads, and would not release this modification but rather personally test it to demonstrate that the Version Checker author, LazyWizard, should be include my modification in the next Version Checker release. My reasoning is that many modders do not support Version Checker because its approach to checking whether the mod is updated requires the modder to follow a complicated and surprisingly-error-prone process of writing a custom .csv inside a hardcoded nested directory and including a separate
.version file in the mod itself and maintaining another 'master'
.version file at a separate link--all because VersionChecker was written before the StarsectorAPI could read
.json files.
This hassle had deterred me from supporting Version Checker for many versions of Realistic Combat, still deters other modders from supporting Version Checker, made me have to try several times to make it work, and even afterward ensnared a mod manager with a hidden gotcha error in the .csv I had to write for Version Checker. After all this trouble, I thought, "There
must be a better way", talked to much more experienced mod and mod-manager authors, and they agreed that there is. My better way would be simple enough for more modders to support, not require separate
.version and master
.version files, and be reliable enough to avoid tangling mod managers: the modder would include the download link and forum thread ID in
mod_info.json and the current mod version number in the title of the forum thread, and Version Checker would check the title of the ID-indicated thread, fetched with its current thread-fetching code, for a mod version number and, if it found one, compare it to the one in
mod_info.json.
So... um, may I please try my code out?