What the hell does that have to do with the price of beans in Bolivia?
Actually, I went over to your boards to have a look at the description of the original code. I can't say I've ever experienced what you went through, but I do get why you coded it. What I do is save every time I feel I've made some sort of significant progress. I like keeping the old builds around, but they they are either buggy or not completed or both. Maybe someday I'll convince myself to just pitch them, well, once a project is finished, of course. Until a project is completed, yes, having builds helps if you have to punt on a new concept and go back to start over on an earlier build. Lucky for me, I can only remember that happening twice in 38 years. Lucky me! If I ever do put myself into a situation like you described, I' absolutely give your routine a go.
I do use the Ctrl+Z UNDO feature, occasionally. Your autosave is similar to that type of protection, as accidents can happen with cut and paste code additions / deletions. I totally get that very large cut and paste manipulations could over-stress that ability, but I haven't encountered that problem so far.
The QB64 auto-recovery feature has saved my ascii on more than a couple of occasions. In fact, now I just rely on the fact it is there. A few weeks ago, a %$^ %$^% Windows update snuck into my system... while it was on SLEEP! It rebooted and I had 10 QB64 windows lost. Auto-recovery restored all of them. All I had to do was to figure out, by comparing the files, if the recovery files had been saved by me already, or if I needed to name them and save them as a newer build. That's not much of an inconvenience, considering what I might have lost without such a feature.
Thanks,
Pete