Ashley
It was not my intention to use the beta version in the classroom.
I wanted to show the students the new Timeline feature, so I went into beta, then mistakenly stayed in beta when viewing class material. I hit save once and then I had to be in beta every time I opened that particular project. (I've tried to roll back projects to earlier versions without success - unlike how easy it was with C2).
Then it happened again when I was helping a student - I saved their project without realizing I was in beta, then they needed to be in beta in order to open it. And it literally spread like a virus from there...so then I just stayed in beta.
It's 100% my own fault, I was merely reporting how I thought it was confusing here on the forums. I never quite understood that editor.construct.net loaded the current stable version. In fact at the time I didn't realize you could get to other versions with /r142 etc... I thought it literally updated the computer you were on. I'm sure there were times I thought I was in beta but wasn't.
Ideally when I performed a SAVE, if there was a popup that warned I was saving to newer version of the software probably would have saved me grief. But I realize that is fraught with problems, since the user could have added something only available in that update, then it becomes an ordeal for the user and the program.