Finally, after three pages you finally post specific code.
And indeed like R0j0hound, from your previous' posts descriptions I thought you were having troubles in the execution of events using local storage, which was the reason your whole topic did not make sense.
Stop posting you as a victim, I asked for code and clearer description all along in order to investigate your issue which you failed to provide because you preferred moaning, whining and complaining instead of providing clear details about your issue. My goal all along is to investigate, yours is to complain.
Maybe it is not your intent, but for people understanding English that is what comes out of this topic.
Unlike what you believe I understood you "couldn't" provide your project's code but you failed to reproduce the issue in a newer capx you could have posted. That's what long time users do in these forums.
Hence why for three pages I asked for some visuals on your project AND FINALLY when you provide some your issue seems to make a bit more sense.
Do you make backup copies of your capx ? Do they display the same issue ?
Do you save on a local hard drive ? A virtual hard drive ? Have you left enough time for your last save or did you close Construct before the actual save was over ?
Such mess-ups have been observed when users try to save capx on virtual drives (dropbox) and don't let actual time for the save to completely perform.
Solution: over your development save new instances of capx, don't stay over a single one.
If you have made it clearer you were talking about a switch of variables within the editor, we would have avoided this uncomfortable situation.
I "came at you" for lack of details in your explanations and you prove me right.