If I were to offer a suggestion not knowing how it currently works exactly, would be the in the download it creates a bat file thats stored in the main folder or a subfolder with an appropriate name that runs after the program closes to restarts to update and uses basic command lines to delete the specific files in the main folder, then a slight variation to delete everything in the subfolders you know exist (lib, resources) then it extracts the update into it's place and executes the f95checker.exe to relaunch the program.
thats... what it does... xD
well not exactly, but it passes the commands to powershell directly, as if it was a bat file:
- waits for app to close
- deletes every single file and subfolder in the folder (but not the folder itself, Desktop\F95Checker-Windows (example) should end up as an empty folder) ignoring errors
- moves files from the extracted folder to the new place
- starts the app again
i dont understand how its possible that on build 414 you get the update in a subfolder (like Desktop\F95Checker-Windows\F95Checker-Windows), since from 414 there is no possible way for it to end up like that... it doesnt try to move the whole folder anymore, but the individual folder contents, the worst that could happen is that it fails to delete the lib folder and you end up with Desktop\F95Checker-Windows\lib\lib. like its literally back to how 8.x autoupdate worked, so i dont understand how now it wont work
are you 110% sure youre on build 414 and that the subfolder wasnt there before or something? because im out of ideas here
Thinking about it, the bat could just delete everything in a single line since it shouldn't be able to delete itself while being ran. Not sure how this would translate over to linux/mac though if it's a problem on those OS's as well.
thankfully linux and unix like systems such as macos were made by competent people and allow you to delete files while they are being used in memory, so the issue of closing the app before updating isnt a thing and i can do it while the gui is still up, after the countdown on these OSs it just restarts the app.
As for another suggestion, I'd maybe recommend chucking a build number here for clarity's sake since it's hard to tell if there's multiple builds under the same main number.
thats a good idea, yes, will add that soon