Yeah, but why use an external file to store that info?The external ini is needed so the script knows if it should download the file or not (is it a newer one?)
It's awesome, but is it possible to make it work without storing any data in any external files like *.ini?
Why can't that kind of info be stored inside of the script's code itself?
You could make the script work so:
1. It connects to the server via provided URL and reads the *.ini-file from the server.
2. Runs a comparison of the version stored in the *.ini-file and in the version in the code of the local script (*.ahk or *.exe).
3. If the server has a newer version of the script - download it and replace the existing one with it.
I mean why do you make users have an *.ini file locally? Can't the script read it's own code?
To do what I mean - users would just have to have the script's version stored in the code of the script and separately in the *.ini file (in order to reduce traffic consumption and download only lightweight *.ini at every check, instead of probably heavy *.exe/*.ahk).
That would be nice, since some scripts do work without any external *.ini-files (yeah, I like super-mega portability, when you need to copy only the executable).
That's exactily what it does now?