This is wrong, the free edition will have limits. You can work and edit games in the free edition up to those limits. If you open a project that exceeds those limits, it will be in read only mode.
You cant do much with 100 events, so it is really not viable as an editor for old projects. The scenario of losing access to working on your own projects in construct3 after the yearly sub period has ended still stands.
As a backup people would be able to open their projects in construct2, if they have it. That way scirra has two competing products on offer.
I am assuming that construct3 made projects will not be compatible with construct2, only the other way around?
Tom does scirra plan to keep compatibility of projects between the two editors?
Will construct2 editor be able to open construct3 made projects and will that compatibility be kept for long?
Because the project filetype is binary, users will not be able to comment out lines of code that prevent the project of being loaded either.
That is one of the advantages of Fusion 3, which will allow users to also track github changes and collaborate on a project. The files that their editor uses is storing information in simple json text files - easy to edit outside of the engine editor.
Meanwhile construct's are binary blobs- not accessible for any changes or tracking outside of the editor. Your editor is probably storing information of the version that saved that file and when opening it is checking if the file is from a newer version of construct. Please correct me if I am wrong on that point.