PUBLIC SERVICE ANNOUNCEMENT!
I'd like to say that my software backup strategy was well thought out, and perfectly implemented...
... unfortunately, I
CAN'T!
I really should know better. I used to do manual backups every day, but then I started using Google Drive to shadow the folder that I am working in. Great - I automatically have a backup copy of my work without having to think about it. Which was fine until something very strange happened...
I am developing a puzzle game and have been getting much closer to finishing the damn thing. (I have been fiddling about with it for way too long!) It has been running reliably for weeks now, so I was startled when the development system suddenly started complaining of a fatal error that I definitely had
NOT made. The game stopped dead in its tracks before it could even get running and I was struggling to work out what was happening from the error message given to me.
Never mind, I would just go to the online backup copy, which, of course...
... had just been overwritten by the now faulty version!
I have been going round in circles trying to work out what had happened and the only plausible answer that I could come up was that a particular resource file had got corrupted. If that were a binary file then I would be stuffed, but I took a look using NotePad and was relieved to find that it was a text file. I went through the duff file and the older good one comparing them line by line and finally spotted the problem...
Good file:
[node name="labels_timer" type="Timer" parent="."]
wait_time = 0.35
autostart = true
Bad file:
[node name="labels_timer" type="Timer" parent="."]
wait_time = 0.35
autostart = true
script = ExtResource( 2 )
WTF!!!
I have absolutely
NO idea why the system had added that extra line to the resource file. It meant that an unwanted and incompatible script file had somehow been linked to that timer. I deleted the unwanted reference and all is now back to normal***.
This is a long-winded way of pointing out that you should backup your important files regularly. I know someone who once lost a year's worth of work because he hadn't backed it up, and his hard drive failed!
Don't make my mistake - keep incremental backups - don't just overwrite the previous one!
Oh, and it would also make sense to check that you can retrieve and use the backed-up files. You don't want to discover that a backup that you desperately need is in fact faulty.
*** AND NOW SECURELY BACKED UP!!!